Repository navigation
fix(chat): trim padding around internal thread links - #81
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.
Model-written thread links with padding, such as
< t3-thread://v2/environment/thread >, appear as raw internal URLs instead of thread links. Trim that padding before rendering assistant messages on mobile and web/desktop, while keeping strict link parsing and stored messages unchanged.The shared normalization preserves code spans, fenced and indented code, invalid addresses, and blank-line boundaries. Regression coverage includes the opaque delegated-thread ID from the incident, spaces/tabs, LF/CRLF padding, labeled destinations, and title substitution.
Validation: focused regression tests and
vp run check:changed main; iPhone 18 Pro simulator before/after verification confirms a titled thread chip, successful navigation to its target, and unchanged literal code. Web is covered through the shared parser checks; no live web session was run.Before/after captures are saved locally at
/tmp/t3-link-padding-evidence/before.pngandafter.png. GitHub image upload is unavailable in this session; no evidence assets are committed.Implemented with Claude Opus 5.5 through the Claude Agent harness; reviewed, hardened, and verified by GPT-6-Astra through Codex.