[Bug]: OMP questions show as two steps with no options, and the question text runs out of the card#23505

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/server (ACP elicitation mapping), plus apps/web (question card)

Steps to reproduce

1. Add OMP (oh-my-pi 18.12.6) as an ACP registry provider.
2. Have OMP call its ask tool with one single-select question that has a header, a long question and two options. The tool input from my thread, trimmed:

3. Look at the question card above the composer.

Expected behavior

One question, so no "1/2". The card's top line shows "Safety-hook false positive". The body shows the full question, the two options, and the usual inline field for a custom answer.

Actual behavior

• The card shows "1/2". Step 2 is OMP's "Other (type your own)" field, shown as a question of its own.
• The long question sits on the header line. It doesn't wrap or truncate, so it runs under the "1/2" counter and the chevron, and past the right edge of the card.
• The body shows "Safety-hook false positive" where the question should be.
• No options are shown.

The user_input_request that T3 stored:

Impact

Major degradation or frequent failure

Version or commit

0.1.2-nightly.20261021.3499 (b5a226e49c52)

Environment

macOS 26.7, T3 Code Nightly desktop app, OMP 18.12.6 over ACP, model anthropic/claude-opus-5-5

Cause

OMP 18.12.6 builds its elicitation form like this (from its askDialog):

• q{N}: title is the question, description is the header, choices are in oneOf: [{ const, title, description }] (items.anyOf for multi-select), and default is the recommended choice.
• q{N}__other: { "type": "string", "title": "Other (type your own)" } for a custom answer.
• When the answer comes back, OMP reads q{N} as one of the option labels and q{N}__other as the custom text.

The generic mapping in packages/provider-acp/src/server/adapter.ts (handleElicitation):

• reads choices only from enum and boolean, so the oneOf choices are dropped.
• turns every property into its own question, so q0__other becomes step 2.
• maps title to the header and description to the question, which is the reverse of what OMP sends.

On the web side, the header span in apps/web/src/components/chat/ComposerPendingUserInputPanel.tsx is shrink-0 with no truncate or wrap, so any long header spills out of the card.

Related

• #21005 and #22479 report the same problems for Factory Droid. The fix in #20417 only covers Droid. droidAcp.ts matches Droid's <id>_other field and its const: "other" choice, so OMP's q{N}__other form still goes through the generic path.
• The open PR #21770 reads oneOf and items.anyOf choices, which fixes the missing options. Its test input puts the short label in title and the question in description, and its expected output still keeps q0__other as a separate question. With OMP's real form, the card would still show "1/2" and the long question on the header line.

Suggested fix

• Add an OMP form handler in provider-acp-registry through extractElicitationForm, the way droidAcp.ts handles Droid. It folds q{N}__other into its question, takes the question from title and the header from description, and replies with the chosen label(s) in q{N} and any typed text in q{N}__other.
• In the question card, truncate or wrap the header so a long one stays inside the card.