fix(tui): TicketRef renders inline so text-wrap layout is correct (#250)

[terrxo]

Fixes anomalyco#250: #N ticket refs were landing on the wrong visual line in assistant messages with multiple inline refs.

Bug

In Nik's screenshot, refs like #227, #243, #246 appeared on the wrong line, floating at end-of-unrelated-line, or duplicate-rendered. Visible examples:

• ...awaiting next dispatch.#227 → #227 lands at end of the NEXT line
• #163 amendments → re-review → surface to you #243 → #243 floats with no source reason
• Paragraph ending with #246 → #246 duplicate-rendered

Root cause

packages/opencode/src/cli/cmd/tui/routes/session/index.tsx::TextPart rendered each paragraph segment as a separate widget under <box flexDirection="row" flexWrap="wrap">:

<box flexDirection="row" flexWrap="wrap">
  <For each={segments()}>
    {(seg) => seg.kind === "text"
      ? <markdown content={seg.text} />        // block-level widget
      : <TicketRef id={seg.id} />              // block-level <text> widget
    }
  </For>
</box>

Every segment — whether a <markdown> block or the <text>-based TicketRef — became its own flex item. flexWrap="wrap" then reordered items per-item (each flex item is atomic to the flex algorithm), not per-character. So the refs ended up wherever the flex layout placed them, not where the source text put them.

Fix

Render a paragraph containing #N refs as a single <text> block with inline <span> (text segments) and <a href={hivemind-url}> (refs) children. Both are OpenTUI TextNodeRenderables — they participate in the parent <text>'s character-level wrap math, so refs flow correctly with surrounding prose.

<text fg={theme.markdownText}>
  <For each={segments()}>
    {(seg) => seg.kind === "text"
      ? <span>{seg.text}</span>
      : <TicketRef id={seg.id} />              // now an inline <a>
    }
  </For>
</text>

TicketRef itself was reshaped from a top-level <text> widget into an inline <a href={HIVEMIND_UI_BASE}/tasks/${id}>. The terminal emulator (iTerm, Ghostty, Kitty, modern Terminal.app) renders it as a real OSC-8 hyperlink — ⌘-click opens hivemind-ui at /tasks/, preserving the click affordance.

Trade-offs (acknowledged in the original splitOnTicketRefs comment)

• Inline markdown formatting (bold/italic/code) is dropped inside paragraphs that contain a #N ref. Plain-text paragraphs (no refs) keep the fast-path through full <markdown> rendering. This was the trade-off the original code documented; the previous flex-row implementation didn't honor it because each markdown block was its own block-level item.
• Hover-card preview is gone. OpenTUI TextNode (<a>/<span>) doesn't accept its own mouse event listeners — they're part of the parent <text>'s render. The <TicketHoverCard> component is left mounted in app.tsx but no longer triggered (harmless dead path). A separate ticket can reintroduce a hover preview via a coordinated overlay anchored to <text>'s cursor position.

Verified

• bun typecheck clean
• All 50 TUI tests pass (test/cli/cmd/tui/)
• 399 of 401 cli tests pass; 1 unrelated pre-existing failure in help-snapshots.test.ts (opencode→gruntcode rebrand, not introduced by this PR — confirmed by git stash then re-running)

Cross-references

• Closes hivemind Context7 MCP not working (Invalid schema for function 'context7_get-library-docs') anomalyco/opencode#250
• Related to need better sorting of models anomalyco/opencode#253 (question prompt unkillable — independent surface, sibling TUI bug)
• Adjacent: gruntcode PRs fix(grunt/tui): proper hover-preview + click for #N ticket refs #14/fix(grunt/tui): #N ticket-hover — single shared floating card, no flicker #15/fix(grunt/tui): #N ticket-hover — shadcn-svelte HoverCard parity (anchored, delayed, sticky) #16/fix(grunt/tui): TicketHoverCard text-rendering — clean preview lines, no character bleed #17/fix(grunt/tui): hivemind sidebar — text wrapping (no more right-edge truncation) #18 (TicketRef + HoverCard origin commits) — this PR supersedes the inline-rendering parts; HoverCard is left mounted-but-unused pending a reintroduction strategy

What this does NOT touch

• Hover-card component + context (kept as-is, dead path)
• Markdown renderer (the <markdown> fast-path for ref-free paragraphs is unchanged)
• Click handler semantics (still opens hivemind-ui in default browser, just via OSC-8 instead of open() call)

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.