scenario

# `scenario` — Edge Case & Scenario Explorer Systematic pre-implementation scenario analysis. For a given feature or change, produces a severity-ranked table of test scenarios across 12 dimensions tuned to gflow-cli's known failure surfaces. Feed the output into PLAN.md tasks and `tests/features/` BDD scenarios before entering EXECUTE mode. --- ## When to invoke Use before implementing any of: - A new generation path (T2V, I2V, R2V, batch manifest runner) - Transport changes (any new HTTP call against `aisandbox-pa.googleapis.com`) - Auth or session changes (new strategy, cookie extraction, SAPISIDHASH wiring) - Selector cascade changes (`ONBOARDING_SELECTORS`, `NEW_PROJECT_SELECTORS`, `FRAME_SLOTS_STRUCT`, `IMAGE_MODEL_OPTION_SELECTORS`) - Data layer changes (schema migration, new `OperationRecorder` callsite, redaction change) - New CLI subcommand, flag, or exit code Skip for: pure doc changes, CHANGELOG/version bumps, `scripts/` tooling with no production callpath. --- ## Invocation ``` /gflow:scenario <feature or change description> ``` `<feature or change description>` is a brief summary of what you're about to implement. Examples: - "SAPISIDHASH auth header wired into `_post_json` for `aisandbox-pa` routes" - "gflow video batch manifest ledger (skip already-completed rows)" - "Image model picker converted from English has-text to structural anchor" - "CDP-attach transport as opt-in alongside ui_automation" --- ## The 12 dimensions For each dimension, enumera...