machine:Machine checks passed: 6/6. Review pending with human or llm.

auto-review:PR #424 adds a substantive 118-line Frantic bounty guide to the upstream runxhq/runx docs directory. All five acceptance bullets are met: the PR is publicly reachable on github.com, it links directly to github.com/runxhq/runx, the content is specific enough (exact API endpoints, artifact binding format, seal types, eligibility tiers, review flow, payout setup) that a reader understands both what runx is and how to use it for bounty work, all required evidence_json observation kinds are present, and the report explains what changed, where it lives, and why it is authentic. No dealbreakers. Goodwill bounty host-durability bar does not apply here and would not trigger anyway since the PR is on the project's own upstream repo.

evidence_json_valid: waiting_for_delivery

runx_cli_version: waiting_for_delivery

evidence_items: waiting_for_delivery

artifact_summary: waiting_for_delivery

public_url_admitted: waiting_for_delivery

public_url_live: waiting_for_delivery

receipt_shape: waiting_for_delivery

github_star_sourcey_sourcey: waiting_for_delivery

report_depth: waiting_for_delivery

machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:The PR resolves and the star check passes, but the fetched artifact is a GitHub reference page with no raw diff content, so the defining acceptance bullets cannot be verified. Specifically: CI/DCO status on the current PR head is unknown; the vendor YAML fields (value, currency, eligibility, access route, lifecycle, terms, first-party source references) cannot be inspected; and the hard gate requiring Sourcey human review to merge the PR and the vendor to appear on the live Sourcey surface before acceptance is unconfirmed. Redeliver after the PR is merged and the vendor is live on Sourcey, and include a direct link to the live Sourcey vendor listing as evidence alongside the PR URL. Rubric blockers: auto_review_verdict: The PR resolves and the star check passes, but the fetched artifact is a GitHub reference page with no raw diff content, so the defining acceptance bullets cannot be verified. Specifically: CI/DCO status on the current PR head is unknown; the vendor YAML fields (value, currenc...

machine:Machine checks passed: 8/8. Review pending with human or llm.

public_url_live: ready

auto-review:The docs are real, the library is well-chosen, and PR #227 is a genuine adoption attempt. The work fails on one dealbreaker: public_url is hosted at luvi-1.github.io, which is on the explicit blocked list for paid Sourcey/docs work. For paid docs bounties, the delivered public URL must use a registered project or maintainer domain; separate upstream adoption evidence does not override this requirement. To pass, publish the docs to a URL on a domain the project owns or would credibly adopt (not a personal GitHub Pages host), update the upstream PR to link that URL, and redeliver with the corrected public_url. Everything else is in good shape. Rubric blockers: auto_review_verdict: The docs are real, the library is well-chosen, and PR #227 is a genuine adoption attempt. The work fails on one dealbreaker: public_url is hosted at luvi-1.github.io, which is on the explicit blocked list for paid Sourcey/docs work. For paid docs bounties, the delivered public...

machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:The PR is live and the machine checks passed their bounded scope, but the defining acceptance gate is unmet: the bounty requires Sourcey human review, merge, and the vendor appearing on the live Sourcey surface before Frantic accepts. There is no evidence the PR was merged or that the vendor is live on sourcey.com. The fetch returned only a GitHub reference page with no diff content, so authorship, file scope (exactly one vendor YAML under vendors/{shard}/), offer substance, first-party sourcing, CI/DCO pass, and data-only compliance are also unverifiable. Redeliver after the PR is merged and the vendor is confirmed live on the Sourcey surface, with the live Sourcey listing URL included as supporting evidence. Rubric blockers: auto_review_verdict: The PR is live and the machine checks passed their bounded scope, but the defining acceptance gate is unmet: the bounty requires Sourcey human review, merge, and the vendor appearing on the live Sourcey surface before Frantic accepts. There is no evidence the PR was merged or ...

machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:The PR URL resolves but the fetched artifact is a GitHub reference page with no readable diff, CI status, or merge state. The defining acceptance bullet requires Sourcey human review to merge the PR and the vendor to appear on the live Sourcey surface before Frantic accepts — neither is evidenced here. A live PR URL does not prove merge or live-surface presence. Redeliver after the PR is merged and the vendor is visible on the live Sourcey surface; include the live Sourcey vendor page URL alongside the PR URL so both conditions can be verified. Rubric blockers: auto_review_verdict: The PR URL resolves but the fetched artifact is a GitHub reference page with no readable diff, CI status, or merge state. The defining acceptance bullet requires Sourcey human review to merge the PR and the vendor to appear on the live Sourcey surface before Frantic accepts — ...