Git Review, Fix, and Integrate to Main

This is the sole semantic review gate before code reaches the remote. Default integration: branch → PR → CI-gated auto-merge ({INTEGRATION_MODEL} = pr-auto-merge). Legacy/break-glass: direct git push origin HEAD:main when AGENTS.md declares Integration: direct-push or for emergency admin bypass.

Review depth and deploy behavior are right-sized by ship profile (step 3): static Vercel SPAs get a light agent fleet; AWS SAM repos lean on GitHub deploy workflows (.github/workflows/deploy.yml) instead of local deploy:code. CI owner (local vs github-handoff) controls only how much of the battery runs locally before the PR — see references/ci-owner.md. After the PR opens, every PR ship is fire-and-forget (user decision 2026-06-30): success is the gate passing locally (full gate or cheap subset per owner) and the PR opened with auto-merge armed — or noted unavailable (plan-gated) on private Free repos, where the PR waits for the user or a /janitor pass. Do not watch CI, fix red checks, or babysit merge/deploy in-session unless the user explicitly asks. The skill runs the gate explicitly before push; the pre-commit hook already ran at commit time, but /ship must not rely on that alone.

The expected starting state is local uncommitted/unpushed changes on whatever branch or checkout the harness opened — integrate via /ship from there. Per rules/worktree-authoring.md, change-making work should have been authored in a worktree off main; /ship is the integrator that lifecycle points to (push branch → PR → CI-gate → cleanup). If the session used /worktree, record WORKTREE_ID, WORKTREE_PATH, and REPO_ROOT for step 15 (cleanup after successful integration).

Numbered orchestration

The orchestration is documented in references/orchestration.md — read it before each step. Summary: