[Bug]: Malformed Markdown links from Codex output render as raw text

Before submitting

• I searched existing issues and found related reports, but this is a distinct malformed-Markdown case.
• I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

1. Run T3 Code with the Codex provider and ask it to report several generated files using Markdown links whose destinations are local paths.
2. Inspect the completed assistant message in the T3 Code conversation.
3. Compare the displayed message with the provider completion payload or persisted assistant text.

Expected behavior

Valid Markdown links should be preserved and rendered as clickable links. A link such as [file](<local/path/file.md>) should retain the closing > and render as a file link or a clear plain-text fallback.

Actual behavior

The completed message can contain a link such as [file](<local/path/file.md) with the closing > missing before ). The bracketed label and destination are then shown literally instead of as a clickable link.

Affected area

Assistant-message persistence and Markdown rendering for Codex-backed conversations, especially local-file links using angle-bracket destinations.

Impact

Users cannot open generated local files directly from the assistant response and must manually reconstruct the path. Lists containing many affected links become difficult to scan.

Version or commit

T3 Code Nightly 0.0.41-nightly.20260914.1707; Codex CLI runner codex-cli 0.154.0.

Environment

Codex provider. The same malformed string was observed in the provider completion payload and the persisted T3 Code transcript, so the exact internal owner may be provider output formatting or T3 Code message normalization.

Evidence

A screenshot shows the raw bracketed Markdown and destination text instead of a rendered link. The persisted transcript and provider completion notification contain the same missing > character.

Workaround

Manually copy and repair the path, then open the file outside the conversation.

Start in the apps/web assistant-message flow by comparing the Codex provider completion payload, persisted transcript, and rendered conversation message. Trace where the closing > is lost for angle-bracket local-file destinations; done when the link is preserved and rendered as a clickable file link or clear plain-text fallback.