harness(gatepolicy): read the door's JSON-RPC body, carry a done_when; addendum 4 final numbers

gatepolicy 01a0c211 7/7, microvm 01a0c213 12/12 on pass B.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01WZb5A2kfVfjpdwSochkuHz

docs/NEXT-SESSION.md

@@ -317,14 +317,24 @@ What shipped, with the measurement each carries:
   operator's stop; cascade on purge. Granularity is the mission — the door
   is installed once per mission and serves every phase.
 
+Pass B, live on prod (`fa650bf` rolled, migration 0087):
+
+- `gatepolicy` `01a0c211` **7/7**: container-tier `gate.denied` with
+  `rule=curl-body` and `rule=hook-files`; 1 credential revoked at close, no
+  row carries the mission, the door answers `unauthorized` to the token
+  read from the container. Two harness traps on the first try: the door is
+  JSON-RPC and rejects inside a 200 (read the body, not the code), and a
+  scenario with no `done_when` inherits the RECIPE's default condition — the
+  judge failed it honestly for lacking an IMPLEMENTATION_BRIEF.
+- `microvm` `01a0c213` **12/12**: "4 earlier verdict(s) on this repo; the
+  brief carried the recalled section" — BM25 picked the most relevant past
+  verdict and the guidance arrived redacted, not the operator reason.
+
 Open after this pass:
 
-1. `gatepolicy` and a second `microvm` run against pass B once it rolls —
-   the container-tier `gate.denied` events, the 401 to the revoked token,
-   and the brief carrying project memory are the three things not yet seen
-   live. Also `01a0c1fa`'s tap drained ZERO tool calls on a VM where the
-   agent plainly read `lib.rs` — one occurrence, on the older `:latest`;
-   watch for it.
+1. `01a0c1fa`'s tap drained ZERO tool calls on a VM where the agent plainly
+   read `lib.rs` — one occurrence, on the pre-pass-A `:latest`; every run
+   since recorded calls. Watch for it.
 2. Jev pilot (item 7) when a key exists; DAG phases (item 8) as a design.
 3. A declarative per-role policy is still a deny-list with ids. The next
    step is per-role allowlists (tools × path globs × hosts) rendered by the