creatixchu 6d7bd7e703 fix(web): keep the plan card to decisions it can actually answer ...

Review follow-ups on the presentation intent.

The card claimed any single-question request declaring the intent, then sent one
of two labels — so a producer offering a third option, or a multi-select batch,
lost answers the generic flow would have shown. That contradicts the intent's
own contract, so `planReviewOf` now claims only a binary single choice and
leaves everything else to the flow that can express it.

`ask()` also rejects a plan-review intent on a question with no `detail`: the
intent declares detail IS the plan, and without one a honouring UI asks the
user to approve something invisible. The client keeps its own fallback — it sits
downstream of a wire boundary — but the misconfiguration now fails at the asker.

`planReviewOf` stops being a value export of the client contract face (client
export discipline: pure helpers stay internal; the tests already import it
relatively), and the ui-question README fallback list, both languages, now
states every condition the code enforces.

2026-07-30 19:38:18 +08:00

..

index.ts

fix(web): keep the plan card to decisions it can actually answer

2026-07-30 19:38:18 +08:00

invariant.ts

fix(invariants): assert runtime relationships, not API shapes

2026-07-20 19:34:19 +08:00

types.ts

fix(web): keep the plan card to decisions it can actually answer

2026-07-30 19:38:18 +08:00