RunicGateway/docs
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(rust): the last fixes' docs (N1 N2 W20 W22 W23) and stage 4's core docs #367

Merged
whitlocktech merged 2 commits from docs/rust-last-fixes-docs into main 2026-10-22 05:11:30 -05:00
Conversation 0 Commits 2 Files Changed 9 +177 -39
wtclaude commented 2026-10-22 01:37:21 -05:00
Member
Copy Link

What & why

Stage 5 of modules/rust/PLAN_LAST_FIXES.md (docs#366): the docs-only fixes, the answers to Q37–Q40, and the docs that stages 2–4 owed.

# Where Change
N2 modules/rust/OPERATING.md A new Runic Gateway section, RaidableBases: change its config with a server restart, never a reload. A reload left a null in its list of live raids, and every hook that walks the list threw.
N1 same Switching from the paid edition to the free one rewrites a paid pack's profiles and drops their bases, so back them up first.
W20 (Q39) PLAN_REDESIGNS.md §14.3.4, D365 Dangerous Treasures has no manual retry: core retries only a failed step, and the automatic retry succeeds by the third attempt. Removed from the walk rows too.
W23 PROTOCOL.md §20.12, PLAN_REDESIGNS.md §11.4, PLAYER_WALK.md 2.2 rbevent setowner A lockout locks (raid.locked). The plain form raises raid.purchased.
W22 PLAYER_WALK.md 2.8: Backpacks fills the pages that are left before the inventory. 2.9: the message goes to chat or a popup. Before you start gains item 8, BetterChat and the four title rules. Carbon's share is cut to 2.11, as walked. There is also a "walked 2026-10-21" note.
W3, W9 (owed by stage 3) PROTOCOL.md §20.5, §20.12 world.error already-out for a second Travelling Vendor. A rolled-back RaidableBases profile write carries RaidableBases' own log lines written since the write, not the server log's tail.
W19 (owed by stage 4) website/MODULE_SYSTEM.md §2.5 + decision 35, website/MODULE_API.md §4.2 and the Team-provider note The loader starts the first module directory by name and refuses every other before requiring it. No MODULE_API change.
W1 (owed by stage 4) website/MODULE_API.md, website/EVENTS.md §L A resource's optional until. A reconcile that finds a resource gone past its until files it expired, not orphaned.
W5 (owed by stage 4) website/EVENTS.md §D, §I, §K, routes; website/BACKEND_DESIGN.md draft_verified_at, draft_verified_by and draft_verified_hash. A draft's passing dry run carries to the version published from it when the spec's fingerprint matches (draftRecorded, verified).
W2 (owed by stage 4) website/EVENTS.md observability The console's new words: "Why this phase has not advanced" and "Phase p3: steps done, waiting to advance".
status PLAN_LAST_FIXES.md Stages 1–5 done. Q37–Q40 answered. §7 reflects Q40, which keeps BetterChat and the title rules. A new §8 lists the PR for each fix. PLAN_REDESIGNS §9.1 and the status line point to it.

Stage 6 (the release and the cutover) waits for the org lead's go.

How it was tested

Docs only. I checked each statement against the merged code: website#219 (loader.js refuseSecond, cleanup.js settleExpired, spec.fingerprint, schema.sql), Rust-Plugins#43 (TravellingVendorOut, RaidProfileErrors) and Module-Rust#55 and #56 (the already-out note text). Every new relative link resolves.

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.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why Stage 5 of [`modules/rust/PLAN_LAST_FIXES.md`](modules/rust/PLAN_LAST_FIXES.md) (docs#366): the docs-only fixes, the answers to Q37–Q40, and the docs that stages 2–4 owed. | # | Where | Change | |---|---|---| | N2 | `modules/rust/OPERATING.md` | A new Runic Gateway section, **RaidableBases**: change its config with a server restart, never a reload. A reload left a null in its list of live raids, and every hook that walks the list threw. | | N1 | same | Switching from the paid edition to the free one rewrites a paid pack's profiles and drops their bases, so back them up first. | | W20 (Q39) | `PLAN_REDESIGNS.md` §14.3.4, D365 | Dangerous Treasures has no manual retry: core retries only a failed step, and the automatic retry succeeds by the third attempt. Removed from the walk rows too. | | W23 | `PROTOCOL.md` §20.12, `PLAN_REDESIGNS.md` §11.4, `PLAYER_WALK.md` 2.2 | `rbevent setowner A lockout` locks (`raid.locked`). The plain form raises `raid.purchased`. | | W22 | `PLAYER_WALK.md` | 2.8: Backpacks fills the pages that are left before the inventory. 2.9: the message goes to chat **or** a popup. *Before you start* gains item 8, BetterChat and the four title rules. *Carbon's share* is cut to 2.11, as walked. There is also a "walked 2026-10-21" note. | | W3, W9 (owed by stage 3) | `PROTOCOL.md` §20.5, §20.12 | `world.error` `already-out` for a second Travelling Vendor. A rolled-back RaidableBases profile write carries RaidableBases' own log lines written since the write, not the server log's tail. | | W19 (owed by stage 4) | `website/MODULE_SYSTEM.md` §2.5 + decision 35, `website/MODULE_API.md` §4.2 and the Team-provider note | The loader starts the first module directory by name and refuses every other before requiring it. No MODULE_API change. | | W1 (owed by stage 4) | `website/MODULE_API.md`, `website/EVENTS.md` §L | A resource's optional `until`. A reconcile that finds a resource gone past its `until` files it `expired`, not `orphaned`. | | W5 (owed by stage 4) | `website/EVENTS.md` §D, §I, §K, routes; `website/BACKEND_DESIGN.md` | `draft_verified_at`, `draft_verified_by` and `draft_verified_hash`. A draft's passing dry run carries to the version published from it when the spec's fingerprint matches (`draftRecorded`, `verified`). | | W2 (owed by stage 4) | `website/EVENTS.md` observability | The console's new words: *"Why this phase has not advanced"* and *"Phase p3: steps done, waiting to advance"*. | | status | `PLAN_LAST_FIXES.md` | Stages 1–5 done. Q37–Q40 answered. §7 reflects Q40, which keeps BetterChat and the title rules. A new §8 lists the PR for each fix. `PLAN_REDESIGNS` §9.1 and the status line point to it. | Stage 6 (the release and the cutover) waits for the org lead's go. ## How it was tested Docs only. I checked each statement against the merged code: website#219 (`loader.js` `refuseSecond`, `cleanup.js` `settleExpired`, `spec.fingerprint`, `schema.sql`), Rust-Plugins#43 (`TravellingVendorOut`, `RaidProfileErrors`) and Module-Rust#55 and #56 (the `already-out` note text). Every new relative link resolves. ## 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-22 01:37:23 -05:00
docs(rust): the last fixes' docs (N1 N2 W20 W22 W23) and stage 4's core docs 20518ca816 
Stage 5 of PLAN_LAST_FIXES (docs#366).

- OPERATING.md: a RaidableBases section. Change its config with a
  restart, never a reload (N2); switching to the free edition rewrites
  a paid pack's profiles (N1).
- PLAN_REDESIGNS 14.3.4: no manual retry for Dangerous Treasures (Q39,
  W20); 11.4: which hook rbevent setowner raises (W23); 9.1 status.
- PLAYER_WALK: rows 2.2, 2.8 and 2.9, Before you start item 8 (BetterChat
  and the four title rules), Carbon's share trimmed to 2.11 (W22, W23).
- PROTOCOL: 20.5 world.error already-out (W3), 20.12 the rollback's log
  is RaidableBases' own (W9) and setowner's two hooks (W23).
- Core, from website#219: MODULE_SYSTEM 2.5 and MODULE_API 4.2 (one
  module at boot, W19), MODULE_API and EVENTS L (a resource's until read
  at reconcile, W1), EVENTS D/I/K and BACKEND_DESIGN (a draft's dry run
  carried by fingerprint, W5), EVENTS observability (W2's words).
- PLAN_LAST_FIXES: status, Q37-Q40 answers, 7 updated, 8 what was built.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-22 01:37:39 -05:00
docs(rust): name docs#367 in PLAN_LAST_FIXES section 8 5e54b85d53 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit 4a6a65f45a into main 2026-10-22 05:11:30 -05:00
whitlocktech deleted branch docs/rust-last-fixes-docs 2026-10-22 05:11:31 -05:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
ksfixitman whitlocktech wtclaude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RunicGateway/docs#367
No description provided.
Delete Branch "docs/rust-last-fixes-docs"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?