docs(rust): say which half of the step-2 walk rows was walked

Rows 1-2 of PLAYER_WALK's step-2 section had their game side walked on both
rigs; their site side (the servers-page warning, a grant landing within a
minute) needs a walk core running Module-Rust#22 on website#209, which the
first commit claimed as walked.

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

modules/rust/PLAN_FIXES.md

@@ -399,9 +399,9 @@ in Rust-Plugins, Rust-Link and Module-Rust, and the three cut over to `main` tog
    installer#35 and website#209 (core's `expired` status, MODULE_API 1.11.0). The spec is
    [`PROTOCOL.md`](../../rust-link/PROTOCOL.md) §19.4–19.8. Walked on both rigs without a player: the
    bridge and the ZoneManager helper compile and load, the helper patches ZoneManager 3.1.14, the hello
-   carries its state, and `plugin.loaded` / `plugin.unloaded` carry the right permissions. The rows that
-   need somebody in the game are [`PLAYER_WALK.md`](../../rust-link/PLAYER_WALK.md)'s step-2 section,
-   rows 3–9.
+   carries its state, and `plugin.loaded` / `plugin.unloaded` carry the right permissions. Still to walk:
+   the site side (a walk core running Module-Rust#22 on website#209), and the rows of
+   [`PLAYER_WALK.md`](../../rust-link/PLAYER_WALK.md)'s step-2 section that need somebody in the game (3–9).
 3. **The redesigns**, each planned in detail before code and walked on both frameworks: the permission manager
    (§4.1), the event step editor with the kit-weekend template (§4.2, §4.3), zones and domes (§4.4), the map's
    marker types (§4.5), the chat title conditions (§4.6), and the NPC research (§4.7).