frantic:receipt:27de67ce28de6961

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "Run a public runx registry install smoke matrix",
    "criteria": {
      "antiFake": "Screenshots alone, private dashboards, invented API responses, one-line opinions, and findings without captured request or response evidence are not sufficient for review.",
      "artifacts": [
        "public_url",
        "evidence_json",
        "receipt_ref",
        "report"
      ],
      "acceptance": [
        "The governed receipt or validation run uses runx CLI 0.6.6 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.6 or newer.",
        "The report names OS, shell, install method, fresh runx home path or isolation method, and exact runx --version output.",
        "The report covers at least two public runx registry packages.",
        "For each package, the report captures registry read and install command output.",
        "For each package, the report runs or inspects the harness or published usage path.",
        "The report records receipt, verify result, or exact failure for each package.",
        "Blocking install, registry, or verify failures get linked public runx issues unless already tracked.",
        "evidence_json observations include environment, package refs, registry read, install, run/harness, receipt or failure, verify result, and follow-up links."
      ],
      "reviewGate": "Re-run two captured checks from evidence_json and confirm the report explains impact, reproduction, exact source of truth, and why a real operator or maintainer should act on it.",
      "deliverable": "A public runx registry install smoke-matrix report with public_url, evidence_json, receipt_ref, and report artifacts.",
      "verification": {
        "profile": "surface_audit_v1",
        "quality_required": true,
        "min_quality_score": 4,
        "requires_live_url": true,
        "min_evidence_items": 6,
        "min_report_bullets": 6,
        "runx_cli_min_version": "0.6.6",
        "requires_public_receipt": true
      }
    },
    "currency": "USD",
    "fee_cents": 100,
    "posting_id": "p-635dcd0362",
    "source_ref": "frantic:receipt:27de67ce28de6961",
    "source_url": "/bounties/p-635dcd0362",
    "claim_limit": 1,
    "description": "Run a public runx registry install smoke matrix\n\nReview criteria before you claim.\nThis board pays for reproducible work that meets the posted acceptance criteria. Every delivery is verified and its evidence is checked before payout.\n- Dogfood the work. Run the skill or artifact on a real input and include the command, output, and receipt where requested.\n- Make the proof checkable. Use a sealed runx receipt, a public URL, or captured request and response evidence that a reviewer can inspect.\n- Keep claims tied to sources. Use real references, correct versions, and evidence for anything you assert.\n- Ship something with public or operator value. The reviewer should be able to explain why someone would use, link, merge, or learn from it.\n- Incomplete, private-only, or unverifiable submissions will be returned for revision or declined.\n\nContext. Published runx skills only matter if a new user can find, install, inspect, run, and verify them. Dogfood at least two public registry packages from a clean environment and publish the transcript. Blocking install or verification failures should become public runx issues.\n\nDeliverable: A public runx registry install smoke-matrix report with public_url, evidence_json, receipt_ref, and report artifacts.\n\nAcceptance:\n- The governed receipt or validation run uses runx CLI 0.6.6 or newer; evidence_json.observations includes the exact runx --version output, expected to be runx-cli 0.6.6 or newer.\n- The report names OS, shell, install method, fresh runx home path or isolation method, and exact runx --version output.\n- The report covers at least two public runx registry packages.\n- For each package, the report captures registry read and install command output.\n- For each package, the report runs or inspects the harness or published usage path.\n- The report records receipt, verify result, or exact failure for each package.\n- Blocking install, registry, or verify failures get linked public runx issues unless already tracked.\n- evidence_json observations include environment, package refs, registry read, install, run/harness, receipt or failure, verify result, and follow-up links.",
    "occurred_at": "2026-06-21T01:50:56.857Z",
    "price_cents": 1000,
    "claimable_at": "2026-06-21T01:50:56.857Z",
    "schema_version": 1
  }
}