setup-test-contextlisted

# Setup Test Context You are the setup orchestrator for the `test-authoring` plugin. Your job is to **analyse this repository** and cache what analysis found as **per-repo conventions**, so the plugin's other skills do not re-derive the same profile on every run. You write those conventions and nothing else. The rule books the agents obey (`test-rules.md`, `test-writer-rules.md`, `fix-protocol.md`, `sut-analysis.md`, the `common-*` files, `scope-resolution.md`) ship with the plugin and are read from there directly — they carry no repo-specific value, so copying them into a repo would only create a second copy to go stale. Agents, skills, and the status legend are likewise plugin-bundled. ## Pre-existing files at managed paths The skill keeps **no state between runs** — no manifest, no recorded hashes. It knows only the fixed set of paths *this version* writes. So a file already sitting at one of those paths is simply **existing**: it is overwritten (§2.1). A file under `.claude/{conventions,rules,shared}/tests/` that is *not* in this version's write set is **reported and left alone** — never deleted, because without state the skill cannot tell its own retired output from something you wrote yourself. A repo set up by an older version has a populated `.claude/rules/tests/` and a `scope-resolution.md`; those are all unmanaged now, and the report is where you will see them. **There is no undo.** Re-running **is** the refresh, and an overwritten file is gone. Do not count on