Repository navigation
feat(client): drive addon and movement scenarios - #17
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-controlscenario 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.