feat(grammar): selecting four options selected one, and said nothing

[AminChirazi]

Re-landed onto main. The original stack (#317/#319/#321/#322/#326) merged into each other's branches rather than up to main, so only #316 actually landed. These five commits are the unchanged remainder, rebased onto current main.\n\nStacked. Re-land of #321. Moves obstacle 94441.

Select commits through the value setter, which is a replacement — so four Select steps at one <select multiple> left the last option standing, fired four change events at an app expecting one, and reported success. Confirmed against a real page before writing anything.

Select "A", "B" and "C" from the "<label>" field drives it to exactly that set in one commit, one input+change. Set-a-state like Check.

Every item is quoted, and that is the design. "Rock, Paper and Scissors" is one option on somebody's page; a split on commas and "and" would read it as three, silently.

Names resolve before anything is selected, so a typo in the third leaves the control untouched, and the step reads the selection back to verify it took.

This is where the call_js_fn bug surfaced: a JS exception does not reach Rust as an Err, so the first version reported success on an option that does not exist. The outcome is now a status value that comes back and is inspected.

Red path: a missing option, and a single <select> given a list. Proved live: four options in exactly one change event, asserted on an event counter.

The one question: still a recording — one target, one set of names, no branch or repetition.

🤖 Generated with Claude Code