Repository navigation
fix(ai): keep tool activity within the transcript content width - #249
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
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.
Tool groups bypassed the centered bounded content surface used by ordinary messages. In Mapre's full-width transcript, a completed group summary spanned 1160px instead of the configured 768px. Share the same centered content helper across both row kinds while keeping the scroll viewport full width and preserving host-rendered keyed children.
The grouped-only mounted test fails before the fix with a non-default 560px content width. All 25 AI cases and all 148 native test_lui cases pass; Melange and install targets compile, changed-file AST64 and whitespace/credential checks pass. No Dune files, warnings, public signatures, dependencies or scroll ownership change. Final installed-package Mapre browser acceptance is still pending.
The new decision document validates. Repository-wide spec-dev-tool check still reports the two existing legacy paths docs/agent-guide/001-implementation-review_report.md and docs/agent-guide/002-review-fixes.md; unrelated historical files are unchanged.