docs(rust): console commands built — command.run (PROTOCOL §20.11, PLAN_REDESIGNS §16.10, D385) #359

wtclaude · 2026-10-16T07:44:34Z

wtclaude commented

2026-10-16 07:44:34 +00:00

What

The record of PLAN_REDESIGNS §16's build, which happened the day it was planned.

rust-link/PROTOCOL.md §20.11 documents command.run:
- its three shapes: once with a stored teardown; per online recipient with {steamid} / {name}; and teardownOf;
- the at-most-once key file and the per-frame budget;
- command.ran / command.error and their reasons;
- how unknown-command is told (the game's own log line, not Run's return);
- POST /commands/run, and the website side.
modules/rust/PLAN_REDESIGNS.md:
- D385, asked during the build: the bridge keeps a step's teardown with its key, because core reverts a failed or lost-answer step with only the key.
- §16.10, the build record: three spike findings, the rig run, and twelve settled-in-code points, each overrulable.
- A D385 walk row in §16.9, and pointers from the status paragraph, §9 and §10.
website/EVENTS.md: a paragraph saying an action can be text the module cannot read. It covers what core already bounds, and two things a module copying it needs: a failed step's revert has only the key, and multiple drops duplicates.

Code: Rust-Plugins, Rust-Link and Module-Rust, each on feat/command-steps into edge.

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

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What The record of PLAN_REDESIGNS §16's build, which happened the day it was planned. - **`rust-link/PROTOCOL.md` §20.11** documents `command.run`: - its three shapes: once with a stored teardown; per online recipient with `{steamid}` / `{name}`; and `teardownOf`; - the at-most-once key file and the per-frame budget; - `command.ran` / `command.error` and their reasons; - **how `unknown-command` is told** (the game's own log line, not `Run`'s return); - `POST /commands/run`, and the website side. - **`modules/rust/PLAN_REDESIGNS.md`:** - **D385**, asked during the build: the bridge keeps a step's teardown with its key, because core reverts a failed or lost-answer step with only the key. - **§16.10**, the build record: three spike findings, the rig run, and twelve settled-in-code points, each overrulable. - A D385 walk row in §16.9, and pointers from the status paragraph, §9 and §10. - **`website/EVENTS.md`:** a paragraph saying an action can be text the module cannot read. It covers what core already bounds, and two things a module copying it needs: a failed step's revert has only the key, and `multiple` drops duplicates. Code: Rust-Plugins, Rust-Link and Module-Rust, each on `feat/command-steps` into `edge`. - [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 07:44:37 +00:00

docs(rust): console commands built — command.run (PROTOCOL §20.11, PLAN_REDESIGNS §16.10, D385) d914a50523

- rust-link/PROTOCOL.md §20.11: command.run in its three shapes (once with a
  stored teardown, per online recipient with {steamid}/{name}, teardownOf),
  the at-most-once key file, the frame budget, command.ran / command.error
  and their reasons, how unknown-command is told (the game's log line, not
  Run's return), POST /commands/run, and the website side.
- modules/rust/PLAN_REDESIGNS.md: D385 (the bridge keeps a step's teardown
  with its key, asked during the build), §16.10 the build record (three
  spike findings, the rig run, twelve settled-in-code points), a D385 walk
  row in §16.9, pointers from the status paragraph, §9 and §10.
- website/EVENTS.md: an action can be text the module cannot read: what
  core already bounds, and the two things a module copying it needs (a
  failed step's revert has only the key; `multiple` drops duplicates).

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

whitlocktech merged commit 1148967b6c into main

2026-10-16 07:47:19 +00:00

whitlocktech deleted branch docs/command-steps-built

2026-10-16 07:47:20 +00:00

whitlocktech referenced this issue from a commit

2026-10-16 07:47:20 +00:00

Merge pull request 'docs(rust): console commands built — command.run (PROTOCOL §20.11, PLAN_REDESIGNS §16.10, D385)' (#359) from docs/command-steps-built into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#359