fix(clients): inline file chips keep the text the agent wrote#29657

Problem

Inline code such as avatars/u1.webp becomes a file chip labeled only u1.webp, removing part of an example from the sentence. Line and column suffixes are also reformatted instead of showing what the agent wrote.

Fixes #29421.

Change

Preserve authored inline-code text in web/desktop file chips and mobile native pills, and index that same text for thread search. Mobile tracks links generated by the existing inline-code transform so the native renderer can retain their original text.

File classification, destinations, existence checks, and global fileLinkLabel defaults are unchanged. Missing example files still have the existing preview behavior.

Scope and approval

This is a focused obvious-bug fix under the small-fix exception: rendering drops authored content, and the issue explicitly accepts keeping that content as the chip label. Web, mobile, and shared search changes address that same content loss. No new setting, file-existence lookup, transport change, or unrelated cleanup is included.

Verification

• Extended existing regressions: three failures before the fix; 72 tests passed afterward across threadFindText, native inline-file transforms, HTML transforms, and web Markdown links.
• Focused lint, formatting, mobile typecheck, and git diff --check passed. vp run check:changed upstream/main passed formatting, lint, both Knip passes, affected-package typechecks, 46 tests, and 9 focused React compiler checks.
• In the actual Linux web client, replayed the issue's assistant text with isolated development state. Before: basename/collision labels and reformatted line suffixes. After: exact avatars/u1.webp, thumbs/u1.webp, and ./src/main.ts:12:3 labels. An explicit Markdown link retained its existing basename/location presentation. Temporary replay-fixture edits were restored and are absent from the diff.

Before:

Before: inline file chips drop the authored path prefix

After:

After: inline file chips retain the full authored path

Native-device runtime was not exercised. The iOS and Android renderers both use each occurrence's original text when a label override is absent. The native customization API is keyed by href: an ordinary Markdown link sharing an inline-code href in the same document also keeps its own authored label. Other ordinary Markdown links retain existing labels. The independent reviewer accepted this tradeoff for the focused scope.

Review found that Markdown metacharacters in native labels could still lose content. Escaped labels independently from destinations and extended the existing parser regression with ./src/__tests__/main.ts; it failed before that correction and passes after.

Reviewed with review-loop: 2 rounds with GPT-6.1 Sol on xhigh. Reviewer verdict: approved.

Current-main validation

Rebased onto upstream main and fixed the long-label review finding: authored inline-code paths wrap instead of truncating the filename or line/column suffix. Explicit Markdown link labels keep their existing layout.

The focused Markdown/search suites pass (79 tests across five files). The full changed-file check passes with one worker; browser validation uses a private Xvfb display and Xauthority. A temporary narrow-width ChatMarkdown fixture supplied the captures below and was removed from the final diff. Integrated application and native-device verification remain for the parent task.

Before: a long authored path is truncated

After: the full authored path and position wrap within the available width

Created with GPT-6.1 Sol (extra-high reasoning) in Codex through T3 Code.

Fixes pingdotgg/t3code#29421