Align mode catalog with ZCode 3.11.2 and add strict validation - #19
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.
Summary
Align the ACP adapter's mode catalog with ZCode 3.11.2's official modes and add strict validation to reject any modes outside the published catalog.
Changes
Mode Catalog
automodebuild(Ask before changes),edit(Edit automatically),plan(Plan mode),yolo(Full access)Validation
isZCodeModeId()type guard to validate client-provided mode IDsrequireZCodeModeId()to validate native modes and reject protocol mismatchesRefactoring
updateBindingSnapshot()helper to centralize snapshot state updatesMODE_OPTIONSconst with TypeScript type narrowing for type safetyTesting
MODE_OPTIONSmatches official ZCode 3.11.2 catalogcurrent_mode_updatenotificationINVALID_CONFIGURATIONerror before calling hostend_turnthis closes #17