validating-mergeslisted
Install: claude install-skill WingedGuardian/GENesis-AGI
## Tracking is a separate completion gate
Before selecting a batch, read `docs/reference/validator-tracking.md` and run its
preflight. Discover the actual tools exposed by this client; do not infer a private
writer from an ordinary Codex connection, silently activate another profile, or
register an external client as a Genesis session.
For EACH row: persist valid measurement evidence immediately, classify every
concern, file/reuse its safely redacted public issue (private only for the concrete
disclosure harm in CLAUDE.md), read the task back, and add structured `tracking`.
Free-text `findings[].disposition`, chat, a run log, or a verification row does not
prove routing. Receipts carry the exact live task excerpt plus your rationale for
how it covers this concern. Verify meaning as well as existence; quote matching
does not decide semantic relevance for you. Each private receipt states the actual
harm and why redaction/public-task/private-evidence cannot avoid it.
Both writers retain the measurement verdict when routing is pending and leave the
row OPEN. CLI exit **4 means measurement recorded or previewed, tracking pending**;
re-read before retrying. MCP exposes `recorded`, `tracking_complete`, `tracking`
and `would_close` separately. A preview stores nothing. Never call the batch
handled until the selected-row checkpoint reports complete tracking.
Checkpoint after each row, before moving batches, and before a completion report.
**Honor a user pause immediately:** stop s