e2e-scenario-authorlisted

# E2E Scenario Author — Catalog Generation Protocol This skill is **normative**. **MUST / MUST NOT / SHOULD** carry RFC-2119 meaning. Rules are cited by ID (`SCA-n`). > **Authority**: [`AGENTS.md`](../../../AGENTS.md) is binding. This skill writes a project-wide *shared* document (`docs/e2e-scenarios/catalog.md`), so its output is reviewable in PRs alongside the code change that triggered it. > **Shared contract**: [`docs/e2e-scenarios/CONTRACT.md`](../../../docs/e2e-scenarios/CONTRACT.md) is the project SSOT. When it is absent, copy the bundled version-1 source at [`reference/e2e-scenario-contract.md`](reference/e2e-scenario-contract.md) once. If the project copy already exists, never overwrite or repair it silently. If this skill disagrees with the project contract, the project contract wins. > **Reference loading:** The SCA rules below and project contract govern authoring. Read > [surface discovery](reference/kb/api-surface-discovery.md) for supported framework extraction; > [boundary cases](reference/kb/boundary-and-negative-cases.md) only for constraint classification, and > [idempotent scenarios](reference/kb/idempotent-scenarios.md) only for mutation/teardown design. > Read [principles](reference/principles.md) only for rationale, and [the KB index](reference/kb/INDEX.md) > only for an unresolved topic. MUST NOT recursively load the entire KB. --- ## A. Boundary **SCA-1 (Write targets) — MUST.** Repository writes are limited to: - `docs/e2e-scenarios/CONTRACT.m