docs(rust): the step-2 player walk, and D186-D187

PLAYER_WALK's step-2 rows 3-9 walked with the org lead in the game on
both rigs (2026-09-27). Records the results, corrects four rows (the
helper is unloaded, not deleted; no enter message can show; sleepers do
not score; ZoneManager's own entry counted the player anyway), and adds
D186 (a link code's second pass skips servers known down) and D187 (no
permission sync to a server the poll saw go away) with F6, F7 and F12's
as-walked notes.

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

rust-link/PLAYER_WALK.md

@@ -420,15 +420,24 @@ walked there without a player. The rest need somebody in the game.
 
 | # | Do this | You should see |
 |---|---|---|
-| 1 | *No player.* `rgz.status` in the server console | `Runic Gateway Zones 0.1.0: patched`, and the servers page says nothing about the helper. Delete `RunicGatewayZones.cs` and wait a minute: the servers page warns that ZoneManager's flags miss a player already inside a new zone (D182). Put it back |
+| 1 | *No player.* `rgz.status` in the server console | `Runic Gateway Zones 0.1.0: patched`, and the servers page says nothing about the helper. Unload it (`oxide.unload RunicGatewayZones`; Carbon: `c.unload RunicGatewayZones`) and wait a minute: the servers page warns that ZoneManager's flags miss a player already inside a new zone (D182). Deleting or renaming the file does **not** unload it on either framework. Load it again (`oxide.load`, or `c.load` — Carbon only queues the compile, so allow a minute) |
 | 2 | *No player.* `oxide.unload Kits` (Carbon: `c.unload Kits`), grant a site group `kits.admin`, then `oxide.load Kits` | The sidecar's `/events?kind=plugin.loaded` shows Kits with `["kits.admin","kits.rgreward"]`, and the grant lands **within a minute** — not on the fifteen-minute audit (F8) |
 | 3 | A fells a tree and picks up a hemp plant | The next `player.tally` counts the wood the inventory shows — the final hit's bonus included — and the cloth from the hemp (F1, D159) |
 | 4 | A breaks a wall of their own base | `entity.destroyed` arrives; the next tally's `structures` does **not** move (F3) |
-| 5 | Staff open a zone with a timed event while A stands where it will be | ZoneManager counts A at once: the zone's enter message shows, and the run's tally gives A seconds without A walking out and back in (F12) |
-| 6 | With A standing in a live event zone, restart the server | After the restart A is in the zone again (ZoneManager says so) and keeps scoring without moving (F12). The site's restart permission sync goes **after** "Server startup complete", not before, and says what it applied (F7) |
-| 7 | Staff delete the helper, then repeat step 5 | A still scores (the bridge measures the zone's shape, D182), but the zone's enter message does not show for A |
-| 8 | Stop another enabled server, then have A type a made-up code on the website | "That code is unknown or has expired" — not "one of the servers could not be reached … your code is still good" (F5) — in a second or two, not many (F6). A real code from A's server still links |
+| 5 | Staff open a zone with a timed event while A stands where it will be | ZoneManager counts A at once — `rgp.inzone` names A, and the helper may log `1 player(s) already inside were counted in` (on Carbon ZoneManager's own entry got there first) — and the run's tally gives A seconds without A walking out and back in (F12). No enter message shows: the bridge makes its zones without one |
+| 6 | With A standing in a live event zone, restart the server. A sleeper can be killed while A is away, so stand in a small locked hut, and wake up at once on rejoining — asleep does not score | After the restart A is in the zone again (ZoneManager says so) and keeps scoring without moving (F12). The site's restart permission sync goes **after** "Server startup complete", not before, and says what it applied (F7) |
+| 7 | Staff unload the helper (row 1), then repeat step 5, and reload ZoneManager with A still inside | A still scores, through the zone's re-creation too (the bridge measures the zone's shape, D182). On ZoneManager 3.1.14 its own entry counted A anyway, a moment late — the helper only makes that immediate |
+| 8 | Stop another enabled server, then have A type a made-up code on the website | "That code is unknown or has expired" — not "one of the servers could not be reached … your code is still good" (F5) — in a second or two, not many (F6): a server the site already knows is down is not waited on (D186). A real code from A's server still links |
 | 9 | A is killed by a wolf, then by a scientist | The killfeed says **Wolf** and **Scientist**, not `wolf2` or `scientistnpc full any` (F2) |
 
 **What counts as a pass:** a zone counts somebody who was already standing in it, on both frameworks,
 and an expired zone reads `expired` on the run console.
+
+**Walked 2026-09-27, rows 3–9, on Oxide and then Carbon, with the org lead in the game.** Every row passed but row 8's timing.
+The tallies matched the inventory exactly (653 and 654 wood, 10 cloth, a hemp seed); an own wall brought down
+with C4 was an `entity.destroyed` and no raid; a zone scored a player who stood still through its opening, a
+restart (128 s and 246 s, against the time actually spent inside) and a ZoneManager reload with the helper
+unloaded (105 s and 90 s); a real code linked in under two seconds with the other rig stopped; and the killfeed
+read Bear, Wolf, Boar and Scientist. Two findings were fixed the same day and walked on the walk core: a
+made-up code still waited one timeout on a stopped rig, 12 s (D186 — now 360 ms), and on Carbon a due audit
+went out before the restarted world's hello was read (D187). Not walked: a player killed by another player.