Digest CH-003: the cause, the record, and what may honestly be promoted.

AN-006 now carries the established cause instead of a suspect. The death
never reaches any bot: the Tank Royale server emits it before the turn's bot
snapshot exists, so it fans out over nobody. The repair is committed upstream
on its own branch with a positive and a negative server test; the bridge is
correct throughout and needs no change. The Bot API event queue, the negative
priority, the instant death handler, and the bridge are each recorded as
ruled out, with the probe that ruled them out.

EVT-004 stays draft, because the repair is unreleased and the bridge builds
against released artifacts. Its reason is now a named cause with a named fix.
EVT-007 is blocked by the same cause, which nobody had written down.

EVT-003 is promoted and M-103 closes: three conformance tests prove exactly
what it says, and they pass.

EVT-005 is not promoted, which is what this change set out to do. The tests
tagged for it assert round and battle completion -- behaviour no criterion in
CAP-001 covers -- and the win-handler test tagged EVT-004 is mistagged the
same way. Promoting on that evidence would have recorded a promise as kept
that nothing kept. G-002 carries the repair as a proposed goal, since fixing
it means minting criteria and retagging tests.

AN-008 records a second divergence the death fix made visible: Tank Royale
declares more round winners than a battle has rounds, which classic never
does. It is pre-existing and independent -- it occurs on the unrepaired
server too.

The harness README gains the build caveat that cost a whole comparison: the
runner jar embeds a shrunk server jar that Gradle will happily not rebuild.

Verification: tier 1 green; the conformance tier ran (not skipped) and is
green, with the EVT-004 death test skipped by design. The regression gate is
untouched because no runtime source changed in this change.

Cliewen-Route: full

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011CzphhW5SDHycZJFfaAKLm

Author: flemming-n-larsen

.clue/id-ledger.yaml

@@ -1,14 +1,14 @@
 counters:
     ADR: "1"
-    AN: "7"
+    AN: "9"
     API: "6"
     ARCH: "3"
     C: "7"
     CAP: "8"
     CH: "3"
     CRIT: "8"
     DES: "8"
-    G: "1"
+    G: "2"
     IDR: "2"
     OQ: "2"
     P: "1"
@@ -57,6 +57,16 @@ entries:
       state: live
       prefix: AN
       component: "7"
+    - id: AN-008
+      kind: numeric
+      state: live
+      prefix: AN
+      component: "8"
+    - id: AN-009
+      kind: numeric
+      state: reserved
+      prefix: AN
+      component: "9"
     - id: API-001
       kind: numeric
       state: live
@@ -277,6 +287,11 @@ entries:
       state: live
       prefix: G
       component: "1"
+    - id: G-002
+      kind: numeric
+      state: live
+      prefix: G
+      component: "2"
     - id: IDR-001
       kind: numeric
       state: live

changes/CH-003-own-death-reaches-on-death/findings.md

@@ -224,3 +224,10 @@ therefore safe to run over a state file holding results from several eras.
   chunk it; checkpointing makes chunking free.
 - Per-side timeout (`--timeout`, default 600 s) kills the entire worker process tree
   (server/booter/bot JVMs included) and records the robot as failed.
+- **Comparing two Tank Royale server builds**: the runner jar carries an embedded server
+  jar, and rebuilding it does not reliably pick up a change to the server's sources —
+  Gradle's up-to-date check reused a stale shrunk server jar and produced byte-identical
+  runner jars for two different source trees, which silently made a whole comparison
+  meaningless. Clean the modules first (`gradlew :server:clean :runner:clean`) and check
+  the runner jar's checksum between builds; if the checksum did not change, neither did
+  the server.

changes/CH-003-own-death-reaches-on-death/proposal.md

@@ -19,18 +19,24 @@
  * routed through the Bot API's event queue, the bridge dispatched them from a hand-written
  * switch that had no case for the robot's own death, so {@code onDeath} was never called for
  * any robot. A manual switch fails silently on the branch nobody wrote, and nothing in a
- * score report shows it.
+ * score report shows it. Routing through the queue did not fix it either, and AN-006 now has
+ * the reason: the death never reaches the bot, so there is nothing for any dispatcher to route.
+ *
+ * Two of the tests here are tagged for criteria they do not prove -- the win-handler test and
+ * both round-completion tests assert behaviour no criterion in CAP-001 covers. G-002 carries
+ * that; do not read a passing test in this class as evidence for the criterion in its name.
  */
 class RoundOutcomeEventsConformanceTest extends ConformanceTestBase {
 
     private static final String ROBOT = "tested.robots.BattleWin";
 
     @Test
-    @Disabled("Fails against the bridge: onDeath is never called. Confirmed and recorded in "
-            + "AN-006, which has the measured marker counts for both engines. Kept rather than "
-            + "deleted because it is the only thing that detects the defect, and disabled rather "
-            + "than left failing so the build stays honest. Re-enable in M-001, which owns the "
-            + "root cause in the Bot API's event queue.")
+    @Disabled("Fails against the bridge: onDeath is never called, because no death event reaches "
+            + "any bot at all. AN-006 has the cause -- the Tank Royale server emits a death before "
+            + "the turn's bot snapshot exists, so it fans out over nobody -- and the repair is "
+            + "committed upstream and unreleased. Kept rather than deleted because it is the only "
+            + "thing that detects the defect, and disabled rather than left failing so the build "
+            + "stays honest. Re-enable when a Tank Royale release carries the repair.")
     @DisplayName("EVT-004: a robot's own death reaches onDeath on both engines")
     void testEVT004_IntegrationPositive_OwnDeathReachesTheDeathHandler() {
         assertOnBothEngines(ROBOT, (outcome, engine) ->