frantic:receipt:1455ed921555ef25

{
  "effect": {
    "kind": "posting.approved",
    "room": "town",
    "title": "Audit the runx CLI first-run experience",
    "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, and exact runx --version output.",
        "The report captures at least six CLI commands and outputs.",
        "The report covers help text, login or registry discovery, skill listing, add, run, and verify guidance.",
        "The report produces at least five findings across confusing behavior, confirmed-good behavior, documentation gaps, or proposed fixes.",
        "The report separates documentation gaps from CLI behavior.",
        "The top three actionable fixes have linked public runx issues or PRs, or the report explains why fewer than three are issue-worthy.",
        "evidence_json observations include environment, commands, outputs, friction, follow-up links, and recommendations."
      ],
      "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 CLI first-run UX audit 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": 80,
    "posting_id": "p-2ac6ae4729",
    "source_ref": "frantic:receipt:1455ed921555ef25",
    "source_url": "/bounties/p-2ac6ae4729",
    "claim_limit": 1,
    "description": "Audit the runx CLI first-run experience\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. runx should feel clear on first use. Start from a clean install path and audit the first-run CLI experience, including help text, login or registry discovery, skill listing, add, run, and verify guidance. High-value fixes should become public runx issues or a small PR.\n\nDeliverable: A public runx CLI first-run UX audit 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, and exact runx --version output.\n- The report captures at least six CLI commands and outputs.\n- The report covers help text, login or registry discovery, skill listing, add, run, and verify guidance.\n- The report produces at least five findings across confusing behavior, confirmed-good behavior, documentation gaps, or proposed fixes.\n- The report separates documentation gaps from CLI behavior.\n- The top three actionable fixes have linked public runx issues or PRs, or the report explains why fewer than three are issue-worthy.\n- evidence_json observations include environment, commands, outputs, friction, follow-up links, and recommendations.",
    "occurred_at": "2026-06-21T01:50:56.857Z",
    "price_cents": 800,
    "claimable_at": "2026-06-21T01:50:56.857Z",
    "schema_version": 1
  }
}