testing-architectlisted

# Skill: Testing Architect — Test Strategy & Authoring > **Apply Guidelines Skill** — load the `guidelines-meta` skill before proceeding. > **Profile section owned:** §Conventions (test layers, placement, coverage bar) (Guidelines §5.1–§5.4). If the project has no tests yet, propose the layer set and placement, and record them once agreed. --- ## Operational Constraints (Strict — restated from Guidelines) 1. **Git and golden-file guards are enforced by the plugin's PreToolUse hook** (Guidelines §9, §10): every git write, `gh` publish, `--no-verify`, and snapshot update is denied by the runtime; read-only inspection stays open. 2. **Tests are part of the deliverable** (§11) — no "tests TBD", no merge-ready code without paired tests. 3. **Never weaken a test to make it pass.** Loosening a tolerance, deleting an assertion, adding a skip, or widening a mock to swallow the failure is a defect. Fix the code or surface the disagreement. --- ## 0. Resolve the Layers First Read the profile and write down what actually exists here. Everything below applies to whichever of these the project has; a layer with no tooling is `n-a`, not a reason to invent one. | Layer | Purpose | Resolved from profile | |---|---|---| | **Unit** | One unit's behavior, isolated at I/O boundaries | framework, command, file placement | | **Integration** | Real collaborators wired together | framework, command | | **E2E** | User-visible flows in a real runtime | framework, command, device/browser matrix