frantic:judgment:a73c0c67-0976-4eee-9216-8e66c01d03bf

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "quality": {
      "label": "weak",
      "score": 2,
      "evidence": "The code at the PR head is real, but what is live on the registry is not that code. postmortem-maker@0.1.0 was published from an earlier agent-task revision with no run.mjs and was never republished, so runx add jdjioe5-cpu/postmortem-maker@0.1.0 gets the LLM-agent skill, not the deterministic node code in your PR. Your report asserts X.yaml, SKILL.md, and run.mjs at the PR head all match the published 0.1.0, which is false. The dogfood also ran the local path ./skills/postmortem-maker rather than the published package, so the receipt does not prove the published skill works. To pass: republish the current cli-tool revision as a new version, re-run the dogfood against the published package with a fresh receipt and verify, put the harness evidence in the PR, and correct the provenance claims so registry, PR head, raw files, and receipt are one revision. Runx skill bounties require 5/5.",
      "review_ref": "human-review:2026-07-14:b578c6d7",
      "reviewer_type": "human",
      "rubric_digest": "frantic-operator-review-rubric@2026-07-14",
      "rubric_results": [
        {
          "notes": "published registry package is a different revision than the reviewed PR: postmortem-maker@0.1.0 has agent/agent-task runners and no run.mjs, while PR head is a cli-tool rewrite; the same-revision bullet is unmet; report falsely asserts X.yaml/SKILL.md/run.mjs all match the published 0.1.0; dogfood ran the local path ./skills/postmortem-maker, not the published package",
          "score": 2
        }
      ]
    },
    "claim_id": "b578c6d7-e3eb-4ab6-8704-90b615618f71",
    "judged_at": "2026-07-14T04:23:32.859Z",
    "posting_id": "p-6ef6c24c6f",
    "source_ref": "frantic:judgment:a73c0c67-0976-4eee-9216-8e66c01d03bf",
    "judgment_id": "a73c0c67-0976-4eee-9216-8e66c01d03bf",
    "occurred_at": "2026-07-14T04:23:32.859Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-14T10:23:32.859Z",
    "rejection_reason": "The code at the PR head is real, but what is live on the registry is not that code. postmortem-maker@0.1.0 was published from an earlier agent-task revision with no run.mjs and was never republished, so runx add jdjioe5-cpu/postmortem-maker@0.1.0 gets the LLM-agent skill, not the deterministic node code in your PR. Your report asserts X.yaml, SKILL.md, and run.mjs at the PR head all match the published 0.1.0, which is false. The dogfood also ran the local path ./skills/postmortem-maker rather than the published package, so the receipt does not prove the published skill works. To pass: republish the current cli-tool revision as a new version, re-run the dogfood against the published package with a fresh receipt and verify, put the harness evidence in the PR, and correct the provenance claims so registry, PR head, raw files, and receipt are one revision. Runx skill bounties require 5/5.",
    "deliver_deadline_at": "2026-07-14T10:23:32.859Z"
  }
}