onboard-repository

# Onboard Repository Turn an unfamiliar repository into a verified map for future work. Treat the repository as the system of record. Separate facts from gaps and suggestions. ## Safety Contract The first pass is always inspection and proposal only, even when the worktree is writable. - Read every applicable `AGENTS.md` before inspecting deeper files. - Capture the initial Git root, revision, branch, status, and worktree list. - Preserve all pre-existing tracked and untracked changes. - In the initial boundary capture, before deeper repository inspection, record pre-state existence or safe hashes for relevant ignored state such as `.env.local`, dependency directories, and managed repository state. Never print secret contents. If an initial baseline was missed, report pre/post equivalence as **Unknown**; a later sample cannot reconstruct it. - Treat ignore rules and managed-state manifests as part of the boundary, not deeper inspection. Read them before fixing the baseline, enumerate every relevant ignored database, sidecar, dependency, environment, build, and managed-state path they reveal, and record each one explicitly. For ignored directories, use a content-sensitive per-file hash inventory; a filenames- only hash does not prove that contents stayed unchanged. - Use only read-only discovery commands. Do not install dependencies, start services, invoke migrations, create caches or state, or edit files. - Use task-prefixed shell variable names. In zsh...