docs(rust): protocol 13 step 2 — expiry, plugin loads, the zone helper, the tally (§19.4-19.8, MODULE_API 1.11.0) #289

Merged
whitlocktech merged 4 commits from docs/rust-protocol-13-step2 into main 2026-09-27 06:09:47 +00:00
Member

The spec for PLAN_FIXES §6 step 2, as built. Stacked on docs#288 (the D181–D185 decisions), so merge that first and this diff shrinks to its own commit.

  • PROTOCOL.md
    • §19.4: world.expired gets what, and the website records an expiry. This amends §15's "the website maps it to nothing".
    • §19.5: plugin.loaded / plugin.unloaded and the permission diff, including the one-tick reload case.
    • §19.6: the ZoneManager helper and zoneHelper at hello.
    • §19.7: what the tally counts (F1, F3, F4).
    • §19.8: the website (F7, F5/F6, F2).
  • MODULE_API.md: 1.11.0 and ctx.events.expired, with how Module-uo was proved unaffected.
  • EVENTS.md §L: the expired status (terminal and green, releases the target) and resource.expired.
  • rust-link/INSTALL.md: the helper in the tarball, in a hand install, and in doctor.
  • PLAYER_WALK.md: events step 6 can pass now. A new step-2 section: rows 1–2 were walked on both rigs without a player; rows 3–9 need one.
  • PLAN_FIXES §6: step 2 as built.

Code: Rust-Plugins#18, Module-Rust#22, Rust-Link#19, installer#35, website#209. Tracking: Module-Rust#21.

  • AI-assisted (Claude Code)

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

The spec for PLAN_FIXES §6 step 2, as built. **Stacked on docs#288** (the D181–D185 decisions), so merge that first and this diff shrinks to its own commit. - **PROTOCOL.md** - §19.4: `world.expired` gets `what`, and the website records an expiry. This amends §15's "the website maps it to nothing". - §19.5: `plugin.loaded` / `plugin.unloaded` and the permission diff, including the one-tick reload case. - §19.6: the ZoneManager helper and `zoneHelper` at hello. - §19.7: what the tally counts (F1, F3, F4). - §19.8: the website (F7, F5/F6, F2). - **MODULE_API.md:** 1.11.0 and `ctx.events.expired`, with how Module-uo was proved unaffected. - **EVENTS.md §L:** the `expired` status (terminal and green, releases the target) and `resource.expired`. - **rust-link/INSTALL.md:** the helper in the tarball, in a hand install, and in `doctor`. - **PLAYER_WALK.md:** events step 6 can pass now. A new step-2 section: rows 1–2 were walked on both rigs without a player; rows 3–9 need one. - **PLAN_FIXES §6:** step 2 as built. Code: Rust-Plugins#18, Module-Rust#22, Rust-Link#19, installer#35, website#209. Tracking: Module-Rust#21. - [x] AI-assisted (Claude Code) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 2 commits 2026-09-27 02:48:00 +00:00
Step 2 of PLAN_FIXES §6 had four open choices; the org lead answered them
before any code:

- D181/D182: F12 is a ZoneManager helper that Harmony-patches
  Zone.InitializeZone, ships in the overlay, and the bridge falls back to
  IsPositionInZone for scoring without it.
- D183: F14's expiry is core's: an `expired` ledger status and
  ctx.events.expired (MODULE_API 1.11.0), without disturbing Module-uo.
- D184: F8 is plugin.loaded / plugin.unloaded with the permission diff.
- D185: F2 is the site's labels; no wire change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
The spec for PLAN_FIXES §6 step 2, as built (D181-D185):

- PROTOCOL.md §19.4 world.expired's `what` and the website recording an
  expiry (amends §15's "maps it to nothing"); §19.5 plugin.loaded /
  plugin.unloaded with the permission diff; §19.6 the ZoneManager helper and
  `zoneHelper` at hello; §19.7 what the tally counts (F1, F3, F4); §19.8 the
  website (F7 hold, F5/F6 link fleet, F2 names).
- MODULE_API.md 1.11.0 and ctx.events.expired; EVENTS.md §L the `expired`
  status, terminal and green, and `resource.expired`.
- rust-link/INSTALL.md: the helper in the tarball, by hand, and in doctor.
- PLAYER_WALK.md: events step 6 can pass now; a step-2 section whose rows 1-2
  were walked on both rigs without a player and 3-9 need one.
- PLAN_FIXES §6: step 2 as built, with its PRs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-09-27 02:48:27 +00:00
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
wtclaude added 1 commit 2026-09-27 06:05:50 +00:00
Walked on a core running Module-Rust#22 on website#209 against rust-oxide:
F8, F13/F14, F7, F5/F6 and the helper's state all pass. The expiry walk found
a run left cleanup-pending for ever when its last resource expires while it
runs; website#209 now settles it, and EVENTS.md §L says so.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit 9aba725ca2 into main 2026-09-27 06:09:47 +00:00
whitlocktech deleted branch docs/rust-protocol-13-step2 2026-09-27 06:09:48 +00:00
Sign in to join this conversation.
No description provided.