spec(queen): claim.t27 - the round's stateOfDispatch as a card, the review valve imported (Closes #8765)

.trinity/seals/queen_QueenClaim.json

@@ -0,0 +1,33 @@
+{
+  "built_by": "t27c-bootstrap@0.5.2+c31c059ef",
+  "closure": [
+    {
+      "spec": "specs/queen/review_valve.t27",
+      "spec_hash": "sha256:5177806d264aa3611b5187a89b929c2231cbf7f95eb3cb78d246d913b658d8a6"
+    }
+  ],
+  "config": "gen=c,rust,verilog,zig;tests=zig",
+  "gen_hash_c": "sha256:94cb2ddefbe72c36a94e33fe7aa1d7431dde06620fa9853a92a35351a92f8885",
+  "gen_hash_rust": "sha256:566b400d7e72278fa32999f03fbd911b0b445f4b1dd8d110fb9983d9bd88d11d",
+  "gen_hash_verilog": "sha256:1c18ff19805ce881c1444bcfa48b6de40e980f24830869fc0f6a7fc8b0d8ce70",
+  "gen_hash_zig": "sha256:9ec7f998801cf283659bad1eccb70b0d53e947bd9bb3200defc1c8ed34042fe1",
+  "module": "QueenClaim",
+  "ring": 12,
+  "seal_schema": 2,
+  "sealed_at": "2026-10-10T19:49:14Z",
+  "sealed_by": "t27c-bootstrap@0.5.2",
+  "spec_hash": "sha256:f031594c8c0c5078a126ad4ed3ec0e3ef6b1179658572878fa24361c4b17cec9",
+  "spec_path": "specs/queen/claim.t27",
+  "tests": {
+    "failed": 0,
+    "failing": [],
+    "forced": false,
+    "passed": 11,
+    "total": 11,
+    "vacuous": 0
+  },
+  "toolchain": {
+    "test_runner": "sha256:1982ae948e24d00c5d221ccec12dfce1eb01204b53e37b0f857f93b16d64629d",
+    "zig": "0.16.0"
+  }
+}

docs/now/2026-10-10-queen-claim.md

@@ -0,0 +1,10 @@
+# NOW -- claim.t27: what a dispatch row still claims, the round's stateOfDispatch as a card (2026-10-10)
+
+## specs/queen/claim.t27 (Closes #8765; runtime gHashTag/trios#1767)
+
+- Every round the trios supervisor asks of every `queen_dispatch` row whether it still claims its issue. The answer (`running`, `accepted`, `rejected`, `awaitingReview`, `failed`, `cancelled`) is `stateOfDispatch` in `queen-tick.ts`, hand-written TypeScript. `dispatch.t27` `claim_of` (the audit at pin 879799a8) and trios `rings/T27-02/tick_core.t27` describe older versions; neither agrees with the code on the `queen` branch (3654fdd2).
+- The card states the rule as it runs: `claim_of`, `claim_of_step`, `criteria_read_as`, `escalation_kind_of`. It imports `escalation_kind`, `next_step`, the kind and step codes and `RETRY_FLOOR_MINUTES` from `review_valve.t27`; nothing of the valve is restated. The seal's closure names `review_valve.t27`.
+- Clocks are whole minutes since `finished_at`. Every floor is a whole number of minutes, so the supervisor's `idle_ms >= floor_ms` holds exactly when `floor(idle_ms / 60000) >= floor_minutes`.
+- `t27c test-report`: 11 tests, 0 FAIL, 0 vacuous, 2 invariants. `tri mutate spec`: 40 mutants (drop-guard 11, flip-cmp 21, swap-logic 4, ret-default 4), 40 killed by a failing test. The first run left 4 survivors: the send-back's own floor was masked by the valve when `releases = 0` (2, a test gap, closed by asserting `releases = 1`), and the dead-letter and reviewer-miss ceilings could not change the claim because the valve gives those kinds the step of an unrecorded one (2, closed by `escalation_kind_of` and its own test).
+- Recorded, not changed: after a spent ceiling is handed back, the redispatch resets `send_backs` and keeps `ceiling_releases = 1`, so the first send-back of the new attempt reaches the valve with a spent release and is closed inside its hour. The card keeps today's answer; the trios issue records it.
+- Runtime: gHashTag/trios `queen`, `stateOfDispatch` calls `claim_of` in `specs/queen/claim.wasm` (gen-c + zig 0.16.0 cc wasm32-wasi), proven equal to the hand-written function first.

docs/reports/t27b_expectations.json

@@ -933,6 +933,7 @@
   {"path": "specs/queen/actors_hw_jtag.t27", "t27b": "pass"},
   {"path": "specs/queen/actors_hw_top.t27", "t27b": "pass"},
   {"path": "specs/queen/app.t27", "t27b": "pass"},
+  {"path": "specs/queen/claim.t27", "t27b": "pass"},
   {"path": "specs/queen/control.t27", "t27b": "pass"},
   {"path": "specs/queen/dashboard.t27", "t27b": "pass"},
   {"path": "specs/queen/dispatch.t27", "t27b": "pass"},