testing-workflowlisted

# testing-workflow Execute the approved Project Test Baseline plus Release Delta. This workflow does not prescribe how the feature was developed, redesign expected behaviour from implementation, repair product code, or release the candidate. Read repository instructions and its `## harness-ship` Config v3 block. Run `hs-setup` only when the block is absent or unsupported. Resolve test capabilities at the point of use; never install a framework without approval or infer PASS from `not-configured`. ## 1 — Validate the candidate handoff Use [candidate-handoff-template.md](candidate-handoff-template.md), written to `.harness-ship/candidates/<short-sha>/handoff.md`. Require: - approved Test Contract revision and scenario scope; - an exact review target when a human-readable PR/ticket projection is wanted; - the user-visible change in plain language; - full source SHA — or, where the contract's **Release surface owner** is not this repository, its **Candidate identifier** plus what that was read from; - exact non-production artifact/environment revision; - provenance source and receipt binding the artifact to that SHA or identifier; - a writable `.harness-ship/candidates/<short-sha>/`, whose name is that SHA's first twelve characters, or that identifier; and - access path, safe fixtures/accounts, known risks, and established test evidence. Any missing, placeholder, stale, or mismatched required value makes the handoff `Not ready`. Do not execute against production. ### P