From 1f6255adecf340d5c09d16f638f71b0b191de383 Mon Sep 17 00:00:00 2001 From: wtclaude Date: Mon, 5 Oct 2026 13:13:34 -0500 Subject: [PATCH] docs(runicnpc): stage 6 tested line says what ran The s6 group passed 41/41 on both rigs; its 42nd check (a dead boss's id taking its adds) came with the walk's fix and has not been run in the harness yet. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY --- runicnpc/PLAN.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/runicnpc/PLAN.md b/runicnpc/PLAN.md index b54febb..0143c34 100644 --- a/runicnpc/PLAN.md +++ b/runicnpc/PLAN.md @@ -1275,10 +1275,11 @@ What this adds to the build (D283, D284): the latest public build), Oxide 2.0.7801 and Carbon 2.0.262 (both the latest releases). This morning's spike ran on the previous Rust build, before either rig restarted. -**Tested.** The harness's `s6` group (42 checks) passes on both rigs: refusals, passive (never fights, unhurtable +**Tested.** The harness's `s6` group passed 41 of 41 on both rigs: refusals, passive (never fights, unhurtable by default, press E once a second, a window, wandering), the boss (three phases, its own copy of the profile, the -death hook's contributors, adds that fight on, `RunicNpc_Despawn` of the dead boss taking its adds) and the -examples. `rnt.run all`: 244/246 on Oxide and 243/246 on Carbon before two checks were fixed (below); each fixed +death hook's contributors, adds that fight on) and the examples. A 42nd check, `RunicNpc_Despawn` of the dead +boss taking its adds, was added with the walk's fix below; the walk showed that behaviour (run 65), and the check +has **not yet been run in the harness**: the walk site, which re-pushes profiles, was running. `rnt.run all`: 244/246 on Oxide and 243/246 on Carbon before two checks were fixed (below); each fixed check and the escort check then passed on both rigs. Module-Rust: 491 server and 67 client tests, and every `check:*` script.