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

wtclaude · 2026-09-27T08:19:24Z

wtclaude commented

2026-09-27 08:19:24 +00:00

What & why

Records the step-2 player walk — PLAYER_WALK.md step-2 rows 3–9, walked with the org lead in game on Oxide and then Carbon, 2026-09-27 — and the two decisions it produced. Code: Module-Rust PR fix/protocol-13-step2-walk → edge. Tracking: Module-Rust#21.

modules/rust/PLAN_FIXES.md

D186 (F6, option b): a link code's second pass skips servers the site already knows are down.
D187 (F7): no permission sync to a server the poll saw go away until a fresh hello says its world is ready.
As-walked notes on F6, F7 and F12 — F12 is narrower than written: without the helper, ZoneManager 3.1.14 counted the player every time (zone opened around them, ZoneManager reload, rejoin after restart), only late. The helper makes entry immediate; the score never depended on it.
§6 step 2: the player rows are walked; what passed, what was found, and that player-kills-player was not walked (no second player).

rust-link/PLAYER_WALK.md (step-2 section)

Row 1: unload/load the helper (oxide.unload / c.unload) — deleting or renaming the file does not unload it on either framework; Carbon's c.load only queues the compile.
Row 5: no enter message can show (the bridge makes zones without one); the evidence is rgp.inzone and the helper's log line.
Row 6: stand in a locked hut and wake at once — a sleeper can be killed, and asleep does not score (both happened).
Row 7: unload, repeat, reload ZoneManager; ZoneManager's own entry counted the player anyway.
Row 8: names D186.
A "walked" paragraph with the numbers.

How it was tested

Docs only. Every figure is from the walk's event rows, run collects and rig logs (session notes).

Checklist

I have read CONTRIBUTING.md.
The change builds and existing tests/checks pass locally.
I have added or updated tests/docs where it makes sense.
My commits are reasonably scoped with clear messages.

AI-assisted contributions (required)

No AI tools were used to produce this contribution.
AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). I have reviewed and understand
every change, and take responsibility for it. AI-authored commits are
marked with a Co-Authored-By / Assisted-By trailer.

License

I agree that my contribution is licensed under this project's license
(GNU GPL v3.0 or later), and I have the right to contribute it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why Records the step-2 player walk — `PLAYER_WALK.md` step-2 rows 3–9, walked with the org lead in game on **Oxide and then Carbon**, 2026-09-27 — and the two decisions it produced. Code: Module-Rust PR `fix/protocol-13-step2-walk` → `edge`. Tracking: Module-Rust#21. **`modules/rust/PLAN_FIXES.md`** - **D186** (F6, option b): a link code's second pass skips servers the site already knows are down. - **D187** (F7): no permission sync to a server the poll saw go away until a fresh hello says its world is ready. - As-walked notes on F6, F7 and **F12** — F12 is narrower than written: without the helper, ZoneManager 3.1.14 counted the player every time (zone opened around them, ZoneManager reload, rejoin after restart), only late. The helper makes entry immediate; the score never depended on it. - §6 step 2: the player rows are walked; what passed, what was found, and that player-kills-player was not walked (no second player). **`rust-link/PLAYER_WALK.md`** (step-2 section) - Row 1: unload/load the helper (`oxide.unload` / `c.unload`) — deleting or renaming the file does not unload it on either framework; Carbon's `c.load` only queues the compile. - Row 5: no enter message can show (the bridge makes zones without one); the evidence is `rgp.inzone` and the helper's log line. - Row 6: stand in a locked hut and wake at once — a sleeper can be killed, and asleep does not score (both happened). - Row 7: unload, repeat, reload ZoneManager; ZoneManager's own entry counted the player anyway. - Row 8: names D186. - A "walked" paragraph with the numbers. ## How it was tested Docs only. Every figure is from the walk's event rows, run collects and rig logs (session notes). ## Checklist - [x] I have read [CONTRIBUTING.md](CONTRIBUTING.md). - [x] The change builds and existing tests/checks pass locally. - [x] I have added or updated tests/docs where it makes sense. - [x] My commits are reasonably scoped with clear messages. ## AI-assisted contributions (required) - [ ] No AI tools were used to produce this contribution. - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. I have reviewed and understand every change, and take responsibility for it. AI-authored commits are marked with a `Co-Authored-By` / `Assisted-By` trailer. ## License - [x] I agree that my contribution is licensed under this project's license (**GNU GPL v3.0 or later**), and I have the right to contribute it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-09-27 08:19:27 +00:00

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

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

whitlocktech merged commit 180d6a85d9 into main

2026-09-27 08:26:32 +00:00

whitlocktech deleted branch docs/rust-step2-player-walk

2026-09-27 08:26:32 +00:00

whitlocktech referenced this issue from a commit

2026-09-27 08:26:33 +00:00

Merge pull request 'docs(rust): the step-2 player walk, and D186-D187' (#290) from docs/rust-step2-player-walk into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#290