hs-setuplisted

# hs-setup Write the smallest repository config that cannot be recovered safely at the point of use. Setup is not a framework selector, readiness gate, or repository audit. An empty repository needs no lint, test, UI, QA, CI, deployment, or automation decision yet. ## Fast path Read `AGENTS.md` or `CLAUDE.md` first. If it already contains exactly one supported `## harness-ship` block and the user did not request a policy change, report that it is configured and run `advise`. Do not rescan for policy, run a readiness command, or rewrite informational versions. Do not add `## harness-ship-watch`, `.harness-ship/watch/`, or host hooks on this path. Duplicate blocks and unsupported Config versions are zero-mutation stops. Preserve every explicit choice in a supported existing block, including fields written later by other workflows. A missing **Test engineer watch** field means off. ## First run Inspect local evidence once: - repository instructions for forbidden tools; - configured remotes and remote-tracking refs for the tracker/PR host and branch topology; and - an existing repository convention file only when it directly identifies those policies. Do not run tests, query for a preferred framework, or probe network services when local evidence is enough. The absence of code or tooling is valid, not a blocker. Ask only when either of these cannot be resolved safely: 1. the tracker and its allowed access method; or 2. the integration branch versus protected release bra