🧪 Preserve API-owned region context - #331
Merged
Merged
Conversation
Exercise compact and complete dynamic-region responses through the real CLI while keeping API exclusion semantics out of client code.
Robdel12
force-pushed
the
rd/compact-dynamic-region-context
branch
from
July 26, 2026 17:34
441571a to
c8534d1
Compare
Robdel12
changed the title
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
1 participant
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.
Why
Vizzly now owns compact versus complete dynamic-region response detail in API PR #653. The CLI should preserve those server-provided facts without understanding exclusion reasons or duplicating API rules.
What changed
The real CLI boundary test now serves distinct compact and complete API responses, then verifies the CLI preserves each
dynamic_regionsshape exactly. Compact agent requests continue usingdetails=summaryordetails=diffs; explicit--fullcontinues requesting the complete response.There is no dynamic-region filtering or exclusion taxonomy in CLI product code. Local TDD behavior and the rest of the agent evidence formatting remain unchanged.
Confidence
The real CLI process passes all compact, full, pagination, diff-detail, source-provenance, comparison, and local-workspace context scenarios. This follow-on is intentionally test-only because the existing client pass-through was already the correct implementation once the API owned response detail.
Depends on the merged Vizzly API PR #653.