setup-codebase-harness

# Set up the codebase harness **Harness engineering:** the model is fixed — what you engineer is the *scaffolding* around it (the environment, the docs, the feedback loops) so an agent can build and verify software with minimal human attention. Humans steer; agents execute. Your job is to make the repo **legible, executable, and verifiable.** Work **incrementally and depth-first**: assess what exists, build the one missing capability, use it to unlock the next. Don't boil the ocean — set up what the repo actually needs. When the agent struggles, the fix is almost never "try harder" — ask *"what capability is missing, and how do I make it legible and enforceable?"* and add it. This skill orchestrates the focused sub-skills: **`dev-local-setup`**, **`e2e-setup`**, **`crabbox-setup`** (cloud/parallel), and **`verifier-setup`** (scaffolds a repo-specific **`/verify`** loop; supersedes the older **`pr`** skill). ## 0. Assess Survey the repo: stack, package manager, services/ports, infra deps, existing docs/tests/CI, and the *implicit* rules (buried in READMEs, PR comments, people's heads). Note what's missing per pillar below. ## 1. Legible — the agent can reason about the repo > What the agent can't see doesn't exist. Knowledge in chat threads / heads is > invisible — push it into versioned, repo-local artifacts. - **a) Map, not manual.** Shrink the root agent doc (`AGENTS.md` / `CLAUDE.md`) to a ~100-line **table of contents**: one-line overview, project tree, **golden...