repo-harness-check

# repo-harness-check Use this command when the user asks whether the harness, migration, or release surface is ready. ## Protocol 1. Confirm the repo path and report dirty-worktree boundaries. 2. Read the canonical required-check list from the target repo's root agent context (`CLAUDE.md` for Claude, `AGENTS.md` for Codex) `## Required Checks` section, then apply its scope conditions and run the applicable commands through the global/package helper runtime. This self-host source repo may also use root `scripts/` for source-only maintenance commands. Use focused checks by default; a conditional full-suite command is not an unconditional requirement. Consume current canonical acceptance evidence for already-satisfied expensive criteria. After a bounded follow-up edit, have the parent retain the baseline full-run identity and revise final criteria to focused delta checks when no explicit full-suite requirement or uncovered integration risk remains; never relabel a baseline pass as current-subject full evidence. If `## Required Checks` is missing or empty, report that as the first blocking finding instead of substituting a default list. 3. Run advisory readiness when available: - `repo-harness run check-agent-tooling --host both --json` 4. Treat missing CodeGraph or missing Codex `health`/`check`/`mermaid` as hard failures. 5. Treat Waza staging drift as a yellow readiness flag; report the fix or acceptance reason without failing the repo gate. 6. Report skill eval authorit...