Readiness summary and gated Generate

[mrwadams]

Parent

#45 — Harden the scenario-generation journey: persistent state, guided setup, and resilient progress

What to build

Each scenario page supplies its page-specific requirements as data, and the coordinator derives a readiness summary that lists every missing global and page-specific input. Generate is disabled until all requirements are valid, so the user never spends a click discovering predictable validation errors, and the summary + Generate state update immediately as setup is corrected. Custom scenarios require at least one technique; AI Insider requires at least one threat category (distinguished from optional STRIDE threats).

Acceptance criteria

• Generate is disabled whenever any required global or page-specific input is missing, across all three scenario pages
• A concise readiness summary lists every missing requirement in one place; it and the Generate state update immediately when inputs change
• Custom Scenarios: Generate is disabled until ≥1 technique is selected; AI Insider: disabled until ≥1 required threat category is selected
• Readiness is represented as data (page-supplied requirements → shared summary), not derived only after the click
• Tests parameterised across the three pages assert global requirements behave consistently while page-specific requirements remain distinct, and that no model call occurs while not-ready

Blocked by

• Shared setup sidebar on every scenario page #46 — Shared setup sidebar on every scenario page
• Neutral, dead-end-free threat-group and case-study selectors #47 — Neutral, dead-end-free threat-group and case-study selectors