Skip to content

Readable outcome picker and flows ranked by the chosen outcome - #479

Closed
wmobley wants to merge 1 commit into
developfrom
fix/ui-outcome-picker-and-flow-ranking
Closed

wmobley wants to merge 1 commit into
developfrom
fix/ui-outcome-picker-and-flow-ranking

Conversation

@wmobley

@wmobley wmobley commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Problems

  • The Desired Outcome picker showed descriptions as titles (hiding the variable name), "(no label)" entries for semantic hits with empty labels, and the same variable twice when it came from both the catalog and an adapter contract.
  • Choosing a flow's output variable did not put that flow first on the Models step: the step filtered by outcome but kept tree order, and matched outputs by id only.

Change

  • Each option leads with the humanized label, description below; empty-label hits take the catalog label by id; options deduped by id and, for adapter rows, by label.
  • Models step ranks rows that produce the outcome (models and flows, matched by id or name) first, then rows reachable by a transform, then the rest. Each card says why ("Produces …" / "Can be transformed into …"). Rows found by text but missing from the semantic index are kept.

Tests

  • New StandardVariableCombobox.options.test.tsx and ModelsStepOutcomeRanking.test.tsx; picker tests updated for humanized titles.
  • vitest 157 files / 1595 tests pass; tsc -b and prettier clean; eslint 0 errors.
  • Not yet checked against dev's live flow rows.

Do not merge until dev testing is scheduled.

🤖 Generated with Claude Code

…tcome producers first

The picker led each option with its description and listed the same variable
under its catalog id and its adapter URI. Options now lead with the humanized
label, show the description as secondary text, and drop repeats by id and,
across merged sources, by label.

The Models step only filtered, in tree order, and matched a flow's output by id
alone. Rows that declare the outcome (by id or name) now sort first, then rows
reachable by a transform, each with a reason; a search keeps an exact match the
semantic index does not carry.
@vercel

vercel Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
monorepo Ready Ready Preview Nov 20, 2026 7:29pm UTC

@wmobley

wmobley commented Nov 20, 2026

Copy link
Copy Markdown
Contributor Author

Combined into #482 so all five build and deploy together.

@wmobley wmobley closed this Nov 20, 2026

This branch was successfully deployed

1 active deployment
Preview — 023bcc70 Deployed Nov 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant