Skip to content

feat(client): drive addon and movement scenarios - #17

Merged
Mathih13 merged 3 commits into
mainfrom
feat/addon-control
Sep 10, 2026
Merged

Mathih13 merged 3 commits into
mainfrom
feat/addon-control

Conversation

@Mathih13

Copy link
Copy Markdown
Contributor

The Headless Client can now keep one authenticated Character connected while an acceptance caller sends addon commands, moves, and enters AreaTriggers. This supports companion routes and lost-acknowledgement tests through the real client protocol.

The addon-control scenario reads bounded commands from a caller-owned directory and records sent packet bytes and complete addon replies. A pause after send stops before the next receive. Movement uses the existing receive path and worldport acknowledgements. The client takes complete addon text and reply prefixes from its caller and uses the existing protocol types.

Validation passes formatting, Clippy across all targets, 87 tests, doc tests, and both release builds. Six new tests cover exact PARTY bytes, received addon text and sender, reply filtering, command decoding, movement timing, and evidence retention. Independent Standards and Spec review is clear.

Prepared with GPT-6 in Codex, with an independent subagent review.

@Mathih13
Mathih13 merged commit 68f4a0d into main Sep 10, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant