fix(pi): show an extension dialog's title once#22463

Problem

A Pi extension that asks with ctx.ui.select(title, options) or ctx.ui.editor(title) shows the whole title twice in the pending question panel, once in the header row and again as the question. An input dialog without a placeholder does the same. A long or multi-line title, like the ones rpiv-ask-user-question sends, also fills the header row, runs past the card edge and leaves no room for the collapsed preview.

Pi's RPC select and editor requests carry only a title (plus options or prefill), with no message or placeholder. piQuestion set header: title and fell back to question = title, so both fields got the same text.

Change

When a Pi dialog has no message or placeholder, piQuestion now shows the title once, as the question, under the "Question" header that the Codex, Grok and Antigravity adapters already use when a question has no header of its own. An input dialog with a non-blank placeholder keeps its title as the header, as before. A blank placeholder counts as none, as main does since #23235, so that dialog also shows its title once under "Question". Answers are keyed by question id, so the responses sent to Pi do not change.

This covers the duplicated title in #17895. On current main the expanded question already keeps its line breaks (screenshots below), so this PR does not touch the renderers.

Scope and approval

Fixes the duplicated-title part of #17895, which has no maintainer triage yet. I'm submitting it as a very small, focused fix for an obvious bug. The panel showed the same text twice, and the issue's expected behavior is that the title appears once. The change touches only the line the issue's diagnosis names. It doesn't change any default, setting or answer sent to Pi. Prior PRs: none. No open or closed PR references #17895 or changes piQuestion.

Verification

• Focused tests, from packages/provider-pi: vp test run src/server/adapter.test.ts -t "input dialog|empty select option|editor prefill". The existing select and editor tests now also assert the header and question, and a new test pins an input dialog with a placeholder. With main's adapter.ts, the two title-only cases fail because the header is the title, and the placeholder case passes. With this change all three pass.
• Full packages/provider-pi suite: 128 of 128 pass. tsc-rs --noEmit exits 0. vp fmt --check passes on both files. vp lint exits 0 with main's existing unused layer warning.
• Real Pi in the web app. I ran Pi 1.3.0 in RPC mode with one extension command, /merge-target, that calls ctx.ui.select with a five-line title and the options main and dev, plus a placeholder local model entry so T3 lists Pi as available. No model request is made. Pi sends {"method":"select","title":"Merge target\n\nWhich branch should this change merge into?\n\n...","options":["main","dev"]} with no message or placeholder. The T3 server and web dev server ran from source with a fresh state dir, once with main's adapter.ts and once with this branch, in Chrome 155 at 1920x1081. Each time I picked /merge-target from the composer menu, sent it and captured the panel as it opened, then clicked the header row to collapse it.

Main, panel open: the whole title is the header row, running past the card edge over the toggle icon, and it repeats as the question.

Main: the full title fills the header row and repeats as the question

This branch, panel open: the header reads "Question" and the title appears once, with its line breaks.

Branch: the header reads Question and the title appears once

Main, collapsed: the header row still holds the full title, so the preview has no room.

Main collapsed: the header row holds the full title

This branch, collapsed: "Question" followed by a truncated preview of the title.

Branch collapsed: Question followed by a truncated preview

This branch, after clicking main: the panel closes and the extension's own notice, "Merge target: main", shows that Pi received the answer.

Branch: after answering, the thread shows the extension's notice Merge target: main

Focused tests with main's adapter.ts, captured before #22557 deleted the bare input test: three failures, each with the title where "Question" was expected.

Focused tests on main: three header assertions fail

Focused tests on this branch, same earlier run: all four pass.

Focused tests on this branch: all four pass

Not checked:

• Mobile. PendingUserInputCard renders the same header and question fields, so I expect the same result there, but I did not run a simulator or emulator.
• Pi editor and bare input dialogs in the app. A unit test covers editor; bare input takes the same no-message, no-placeholder branch.
• The rpiv-ask-user-question extension itself. The test extension sends the same request shape, a multi-line title with options.
• The desktop app, Windows and macOS.

Generated with Claude Opus 5.5 in T3 Code Nightly