feat(rust): Dangerous Treasures — feed, map, Treasure Hunter, Start a Dangerous Treasures event (PLAN_REDESIGNS §14.3.4) #47

wtclaude · 2026-10-15T06:46:25-05:00

wtclaude commented

2026-10-15 06:46:25 -05:00

Stage 5 of the §14.3 integration plan, on protocol 14. Spec: docs rust-link/PROTOCOL.md §20.8. Record: modules/rust/PLAN_REDESIGNS.md §14.3.18.

Feed. dt.started and dt.won are public kinds; dt.ended is staff's. The new dangerousTreasures.js reads each row for its viewer:
- everyone: the grid, and how many fought for it
- the presence audience: the winner's name (D376)
- staff: the position, the step's key, the winner's Steam id and the invaders
Lines, in the World events filter: "A Dangerous Treasures event has started · K12", "Alice won the treasure · K12 · 3 players fought for it".
Triggers rust.dt.started (with byEvent) and rust.dt.won: public, cooldown subject the server, names only.
The step rust.dt.start, Start a Dangerous Treasures event (risk change, reversible none, budget rust.dt.events): pick a server and a difficulty; DT picks the spot.
- Refused at verify where the server said DT is not loaded, or that console.plugins is false (naming Rust-Plugins#34).
- dt-not-ready answers "Dangerous Treasures is not ready yet" with retryAfterMs: 600000 (D365, D371).
- dt-no-spot retries on core's ordinary delay. DT's own refusals are not retried.
Treasure Hunter (D375): treasuresWon is stored as treasures_won, with the title category treasureswon and a sortable Treasures column. The column shows where the server reports DT or a row already counts one.
Map: a running chest is drawn on the world layer.
Server settings: the plugin line names DT and says whether a step can start one, from the admin integrations read's new console field.
Core pin: coreApi is now ^1.15.0, and ci/core-ref.json is pinned to website main at #215's merge.
Housekeeping: ci/bundle.json ships the two new files; the swagger fragment and engagement manifest are regenerated; README lists DT.

Tested:

Server: 627/627, 16 new in test/dangerousTreasures.test.js; imports, bundle, swagger and engagement checks pass.
Client: 92/92, build and externals pass.
Booted against the newly pinned core: 45 triggers, 13 actions, 11 budgets, 21 option sources; the 89 routes unchanged.

AI-assisted: written with Claude Code (disclosed per org policy).

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

Stage 5 of the §14.3 integration plan, on protocol 14. Spec: docs `rust-link/PROTOCOL.md` §20.8. Record: `modules/rust/PLAN_REDESIGNS.md` §14.3.18. - **Feed.** `dt.started` and `dt.won` are public kinds; `dt.ended` is staff's. The new `dangerousTreasures.js` reads each row for its viewer: - everyone: the grid, and how many fought for it - the presence audience: the winner's name (D376) - staff: the position, the step's key, the winner's Steam id and the invaders Lines, in the *World events* filter: *"A Dangerous Treasures event has started · K12"*, *"Alice won the treasure · K12 · 3 players fought for it"*. - **Triggers** `rust.dt.started` (with `byEvent`) and `rust.dt.won`: public, cooldown subject the server, names only. - **The step `rust.dt.start`**, *Start a Dangerous Treasures event* (risk `change`, reversible `none`, budget `rust.dt.events`): pick a server and a difficulty; DT picks the spot. - Refused at verify where the server said DT is not loaded, or that `console.plugins` is false (naming Rust-Plugins#34). - `dt-not-ready` answers *"Dangerous Treasures is not ready yet"* with `retryAfterMs: 600000` (D365, D371). - `dt-no-spot` retries on core's ordinary delay. DT's own refusals are not retried. - **Treasure Hunter (D375):** `treasuresWon` is stored as `treasures_won`, with the title category `treasureswon` and a sortable **Treasures** column. The column shows where the server reports DT or a row already counts one. - **Map:** a running chest is drawn on the world layer. - **Server settings:** the plugin line names DT and says whether a step can start one, from the admin integrations read's new `console` field. - **Core pin:** `coreApi` is now `^1.15.0`, and `ci/core-ref.json` is pinned to website `main` at #215's merge. - **Housekeeping:** `ci/bundle.json` ships the two new files; the swagger fragment and engagement manifest are regenerated; README lists DT. **Tested:** - Server: 627/627, 16 new in `test/dangerousTreasures.test.js`; imports, bundle, swagger and engagement checks pass. - Client: 92/92, build and externals pass. - Booted against the newly pinned core: 45 triggers, 13 actions, 11 budgets, 21 option sources; the 89 routes unchanged. AI-assisted: written with Claude Code (disclosed per org policy). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 1 commit 2026-10-15 06:46:27 -05:00

feat(rust): Dangerous Treasures — feed, map, Treasure Hunter, Start a Dangerous Treasures event (PLAN_REDESIGNS §14.3.4)

PR Checks / client-build (pull_request) Successful in 27s

Details

PR Checks / frozen-manifest (pull_request) Successful in 46s

Details

PR Checks / server-tests (pull_request) Successful in 7m23s

Details

bfe9b5b18d

Stage 5 of the §14.3 integration plan, on protocol 14 (docs
rust-link/PROTOCOL.md §20.8).

- dt.started and dt.won are public kinds, dt.ended a staff kind. The new
  dangerousTreasures.js reads each row per viewer: grid and invaderCount for
  everyone, the winner's name for the presence audience (D376), the position,
  the step's key, the winner's Steam id and the invaders for staff.
- Feed lines in the World events filter: "A Dangerous Treasures event has
  started · K12", "Alice won the treasure · K12 · 3 players fought for it".
- Triggers rust.dt.started (with byEvent) and rust.dt.won, public, cooldown
  subject the server, names only.
- eventDangerousTreasures.js: rust.dt.start, "Start a Dangerous Treasures
  event" (risk change, reversible none, budget rust.dt.events), server and
  difficulty. Refused at verify where the server said DT is not loaded or
  console.plugins is false (Rust-Plugins#34). dt-not-ready answers "Dangerous
  Treasures is not ready yet" with retryAfterMs 600000 (D365, D371);
  dt-no-spot retries on core's delay; DT's own refusals are permanent.
- Treasure Hunter (D375): treasuresWon -> treasures_won, the title category
  treasureswon, and a sortable Treasures column shown where the server
  reports DT or a row counts one.
- The map draws a running chest on the world layer; the server settings'
  plugin line names DT and whether a step can start one, from the
  integrations read's new `console`.
- coreApi ^1.15.0, ci/core-ref.json pinned to website main at #215's merge.
  ci/bundle.json ships the two new files; swagger fragment and engagement
  manifest regenerated; README lists DT.

Server 627/627 (16 new in test/dangerousTreasures.test.js) and every check;
client 92/92, build and externals. Booted against the pinned core: 45
triggers, 13 actions, 11 budgets, 21 option sources; 89 routes unchanged.

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

whitlocktech merged commit 140bc67fe1 into edge

2026-10-15 07:04:33 -05:00

whitlocktech deleted branch feat/dangerous-treasures

2026-10-15 07:04:34 -05:00

whitlocktech referenced this issue from a commit

2026-10-15 07:04:35 -05:00

Merge pull request 'feat(rust): Dangerous Treasures — feed, map, Treasure Hunter, Start a Dangerous Treasures event (PLAN_REDESIGNS §14.3.4)' (#47) from feat/dangerous-treasures into edge

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/Module-Rust#47