[prestoncabe]

Undecided benefits now list the unanswered questions they still need in Next steps and the Print summary. People can see what information to find instead of only receiving a generic need-more-information message.

Closes #560. Follow-up for #552, after #579.

The list uses static labels from bound form fields and missing inputs referenced by each undecided check. Shared questions are deduplicated, and checks or benefits that already have a decision do not contribute prompts. Zero, No, and explicit None answers count as answered. The mapping uses the same normalized answers sent for evaluation, preserving unknown CRM prefill as null and handling repeated sections.

Published screeners and Preview place only question labels in their immutable results snapshots. The shared Next steps renderer includes them in printouts without printing answers or input paths. Dynamic labels are omitted rather than evaluated; inputs without a static question label retain the generic message. Pending or failed evaluations hide old prompts, and prompts disappear after a decision. In whenComplete mode, missing questions remain available while decided instructions wait. The CRM extension retains its existing decided-benefits-only format.

Validation:

• All 322 frontend tests passed across 50 files on the final commit in CI.
• Production frontend build passed.
• All 12 public Playwright tests passed locally, including missing questions in both display modes, partial print summaries, completion cleanup, and unchanged CRM integrations.
• Regressions cover unknown CRM prefill, explicit No/zero/None, arrays, nested paths, duplicate check votes, decided checks, template labels, immutable snapshots, published forms, and Preview.
• All six CI checks passed: frontend, builder API, library API, examples, documentation, and end-to-end (25 browser tests).
• git diff --check passed.