fix: right-align config values, and drop the search screen the host already provides

[serkanalgur]

Two corrections after reading OpenCode's dialog-select source

I checked the host implementation (packages/tui/src/ui/dialog-select.tsx) rather than only the plugin type definitions, and found I had reasoned from the wrong file last release.

1. The search screen was redundant, and worse than what the host does

Every ui.dialog.select already renders a live fuzzy filter over title and category, weighted 2:1 toward title, with a Search input drawn at the top of each dialog. The installed plugin API exposes neither skipFilter nor renderFilter, so it cannot be turned off.

The search screen added in 2.14.0 was therefore redundant — and worse than the host's: it required pressing Enter into a prompt before a single character could be typed, and its matching was not live. Removed, with no replacement affordance, since the filter is already on every list.

The config flow search describe (8 tests) is deleted, not weakened: there is no remaining our behaviour to test. A guard now asserts the adapter never passes skipFilter/renderFilter.

2. Values now right-align in footer

The host renders footer right-aligned against a flexing title. Values used to sit in the description immediately after the label, so every row's value began at a different column and comparing two settings meant reading nine rows.

One rule across all three screens: title names the row, description disambiguates it, footer reports its current state.

maxTotalCost                                    25  *
maxCostPerTask                                  1
alertThreshold                                  0.2

Three things verified rather than assumed

• current also moves the cursor — it draws ● and calls setStore("selected", currentIndex). On a per-block field list it would park the cursor on whichever field happened to be current and skip the first row. Set on the hub's scope row only.
• category grouping is left unused. A field list is per-block and its title already reads Nexus configuration — budget, so a bold accent header would repeat it. Left documented at fieldOptions rather than added as a redundant header.
• disabled rows are filtered out, not dimmed. filtered() drops x.disabled !== true before anything is drawn, so a field with no editor is absent. A block claiming "3 settings" while showing two was a lie; the uneditable count now moves to the block's description, the one row that survives the filter. Zero for every block shipped today.

A bug the restyle exposed

The dirty marker was driven by the adapter's whole-draft configIsDirty, so staging one field marked every row in the block. In a description that was merely redundant; in a right-aligned column it is actively harmful — that column is exactly what a user scans to find their own edit, and it lied on every untouched row. configFieldDirty now marks the row and only the row, pinned by a test asserting exactly one of three siblings is marked.

Verified

bun test 1385 pass / 0 fail, bunx tsc --noEmit clean, bun run lint clean (3 pre-existing infos), bun run build clean.

I also rendered the real rows against the real config and read them: staging budget.maxTotalCost marks that row and its block, leaves selfHealing untouched, and flips Save from No changes to write to Write the staged changes to disk.

Note

PR is a fix: — it removes a feature added in 2.14.0 and corrects a bug it introduced. The line count is large because the search screen's removal and the row-routing rewrite overlap in the same functions.