RunicGateway/Rust-Link
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 6 Wiki Activity

feat(sidecar): protocol 14 — the raid base spawn and spot check forwards (PLAN_REDESIGNS §11.4) #31

Merged
whitlocktech merged 1 commits from feat/raidable-bases into edge 2026-10-17 01:32:57 -05:00
Conversation 0 Commits 1 Files Changed 2 +52
wtclaude commented 2026-10-16 19:30:34 -05:00
Member
Copy Link

POST /raid/spawn stamps the body raid.spawn and POST /raid/check stamps it raid.check, and each forwards it. The plugin keeps the key and the run's base in its world registry, so world.revert takes it back like a zone, and nothing is kept here. The five raid.* events ride the feed like any other. Spec: docs rust-link/PROTOCOL.md §20.12.

cargo fmt --check, clippy -D warnings, tests 75/75 (one new: both routes stamp their own verb and pass the plugin's names, the spot and the settings through untouched).

Siblings: Rust-Plugins, Module-Rust and installer feat/raidable-bases, and website#217.

  • AI-assisted: written with Claude Code (Claude Opus 5.5)

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

`POST /raid/spawn` stamps the body `raid.spawn` and `POST /raid/check` stamps it `raid.check`, and each forwards it. The plugin keeps the key and the run's base in its world registry, so `world.revert` takes it back like a zone, and nothing is kept here. The five `raid.*` events ride the feed like any other. Spec: docs `rust-link/PROTOCOL.md` §20.12. `cargo fmt --check`, `clippy -D warnings`, tests 75/75 (one new: both routes stamp their own verb and pass the plugin's names, the spot and the settings through untouched). Siblings: Rust-Plugins, Module-Rust and installer `feat/raidable-bases`, and website#217. - [x] AI-assisted: written with Claude Code (Claude Opus 5.5) 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
wtclaude added 1 commit 2026-10-16 19:30:37 -05:00
feat(sidecar): protocol 14 — the raid base spawn and spot check forwards (PLAN_REDESIGNS §11.4)
All checks were successful
PR Checks / rust-gates (pull_request) Successful in 7m7s
Details
b8e860d85e 
POST /raid/spawn stamps the body raid.spawn and POST /raid/check stamps it
raid.check, and each forwards it. The plugin keeps the key and the run's
base in its world registry, so world.revert takes it back like a zone;
nothing is kept here. The five raid.* events ride the feed like any other.
Spec: docs rust-link/PROTOCOL.md §20.12.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
whitlocktech merged commit a61d7794d9 into edge 2026-10-17 01:32:57 -05:00
whitlocktech deleted branch feat/raidable-bases 2026-10-17 01:32:58 -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/Rust-Link#31
No description provided.
Delete Branch "feat/raidable-bases"

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?