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

pr_url_admitted: waiting_for_delivery

pr_url_live: waiting_for_delivery

x_yaml_admitted: waiting_for_delivery

x_yaml_live: waiting_for_delivery

skill_md_admitted: waiting_for_delivery

skill_md_live: waiting_for_delivery

verification_json_valid: waiting_for_delivery

source_url_admitted: waiting_for_delivery

source_url_live: waiting_for_delivery

runx_skill_harness: waiting_for_delivery

evidence_dogfood_present: waiting_for_delivery

receipt_shape: waiting_for_delivery

github_star_runxhq_runx: waiting_for_delivery

report_depth: waiting_for_delivery

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

auto-review:The PR is live and the machine floor passed (URL admitted, HTTP 200, repo starred), but the fetch returned only a rendered GitHub reference page with no diff or file content. No substantive acceptance bullet can be verified from what was retrieved: offer quality, YAML structure, field completeness, source validity, CI/DCO status, and file-path correctness are all unconfirmed. A resolving URL is the floor, not acceptance. Redeliver with the raw YAML content, a direct link to the first-party vendor source, and CI status (Sourcey Candidate Verifier pass, DCO) so the review system can read the actual evidence rather than the GitHub HTML wrapper. Rubric blockers: auto_review_verdict: The PR is live and the machine floor passed (URL admitted, HTTP 200, repo starred), but the fetch returned only a rendered GitHub reference page with no diff or file content. No substantive acceptance bullet can be verified from what was retrieved: offer quality, YAML structur...