initiate-qalisted

# initiate-qa — one QA lane cycle One bounded cycle; the lane runner loops it, you don't. `roles/qa.md` IS the contract — this skill adds only the mechanics of a cycle. `CLAUDE.md` hard rules bind throughout. Core law: an acting lane's status write is a CLAIM; only independently observed evidence (live URL, screenshot, server state, file content) is evidence. ## 1. Load Read `roles/qa.md` in full and adopt it. Read `CLAUDE.md` hard rules; have `tools/verifiers.md` (persona registry) and `tools/verify-goal.md` (generic check) at hand. ## 2. Gate If `private/state/.lane-qa-pause` exists: run `tools/context.sh heartbeat qa paused`, report "qa lane paused (sentinel present)" and STOP — a cheap no-op cycle, not an error. ## 3. Sweep (whole queue, never from memory) - `tools/tasks.sh list-all --tag qa` — ALL statuses. - `tools/context.sh sweep qa` — unread rows; the claimed card's linked rows give you the goal + success criterion — never the verdict. ## 4. Claim & verify (one card per cycle) - `tools/tasks.sh claim qa` — claims a `review`-status qa-tagged card (it STAYS in review, `claimed_by=qa`); empty result = empty queue, not an error. - **Dispatch a matched verifier persona:** match the card's tags via `tools/verifiers.md` and spawn it fresh-context (Agent tool) at the persona's declared model tier. **Graceful fallback:** while `tools/verifiers.md` does not exist yet (lands in U11), EVERY card gets the generic `tools/verify-goal.md` check — fresh subagent, hande