frantic:judgment:3c0fe0ab-2f08-4dd7-b4c8-148016efeca3

{
  "effect": {
    "kind": "judgment.rejected",
    "room": "town",
    "quality": {
      "label": "acceptable",
      "score": 3,
      "evidence": "Two of three prior defects are fixed: PR #277 now touches only 6 files under skills/rollback-judge/, no runtime-crate edits, no OFFICIAL_SKILLS self-registration; and run.mjs now reads a real signal at run time, fetching the live GitHub Actions run via api.github.com and the deployment marker, deriving the decision from the fetched conclusion and http_5xx_rate rather than a fixture or hand-typed answer. But the consumed-effect defect remains: release_publish_approval is still a plain data object with a dispatch descriptor {skill: release}; the dogfood seals one rollback-judge receipt and no release graph is composed or advanced to consume the approved:true answer, so nothing consumes the decision in the run. To pass: in the same dogfood run compose the release skill (or a mock release rail), feed the decision in as release.publish.approval, and seal an execution result showing release advanced on approved:true; a dispatch descriptor consumed later does not count.",
      "review_ref": "human-review:2026-07-14:8f730aa2",
      "reviewer_type": "human",
      "rubric_digest": "frantic-operator-review-rubric@2026-07-14",
      "rubric_results": [
        {
          "notes": "no-consumed-effect; release-approval-nothing-consumes",
          "score": 3
        }
      ]
    },
    "claim_id": "8f730aa2-77cf-44b7-94f5-4f0e7cd69601",
    "judged_at": "2026-07-16T13:09:45.068Z",
    "posting_id": "p-fe3d2256ff",
    "source_ref": "frantic:judgment:3c0fe0ab-2f08-4dd7-b4c8-148016efeca3",
    "judgment_id": "3c0fe0ab-2f08-4dd7-b4c8-148016efeca3",
    "occurred_at": "2026-07-16T13:09:45.068Z",
    "schema_version": 1,
    "fuse_expires_at": "2026-07-16T19:09:45.068Z",
    "rejection_reason": "Two of three prior defects are fixed: PR #277 now touches only 6 files under skills/rollback-judge/, no runtime-crate edits, no OFFICIAL_SKILLS self-registration; and run.mjs now reads a real signal at run time, fetching the live GitHub Actions run via api.github.com and the deployment marker, deriving the decision from the fetched conclusion and http_5xx_rate rather than a fixture or hand-typed answer. But the consumed-effect defect remains: release_publish_approval is still a plain data object with a dispatch descriptor {skill: release}; the dogfood seals one rollback-judge receipt and no release graph is composed or advanced to consume the approved:true answer, so nothing consumes the decision in the run. To pass: in the same dogfood run compose the release skill (or a mock release rail), feed the decision in as release.publish.approval, and seal an execution result showing release advanced on approved:true; a dispatch descriptor consumed later does not count.",
    "deliver_deadline_at": "2026-07-16T19:09:45.068Z"
  }
}