feat(autopilot): init skill — scaffold the loop's control-plane surface

[pcamarajr]

What

Milestone 1: /autopilot:init scaffolds a target site repo with everything the autopilot loop needs — 10 labels, intention/task issue forms, .autopilot/config.yml, and three workflows (executor, gates, nightly GSC metrics).

How it was built and verified

• Implemented against the locked architecture (autopilot/docs/architecture.md) by parallel subagents, then adversarially reviewed. The review caught 3 P0s, all fixed:
  • Executor now authenticates with a fine-grained AUTOPILOT_PAT (implements G2) — PRs opened with the default GITHUB_TOKEN would never trigger the gates workflow.
  • Branch-protection setup (require PR + the four gate checks) added to the follow-up checklist; constraints note that without it the boundary is advisory.
  • Path-guard scoped to autopilot/task-* so init's own scaffold PR doesn't fail its own gate.
• Proven on the sandbox: the skill was executed end-to-end against pcamarajr/autopilot-sandbox — 10/10 labels created, 6/6 files valid with zero surviving placeholders, scaffold PR opened (autopilot-sandbox#1). Four skill bugs found by the dogfood run (label description over GitHub's 100-char cap, placeholder grep false-positiving on ${{ }} GHA syntax, allow_auto_merge PATCH silently no-oping, branch-dependent idempotence detection) are all fixed in this PR.

Accepted v1 gaps (documented in architecture.md §5)

• Parent-intention linkage is a text reference verified by the executor guard, not a GitHub sub-issue relation.
• Prompt-injection hardening for public repos remains deferred per G8.

Next

Milestone 2: prove the executor path on the sandbox (hand-written task → autopilot:run → PR → gates → auto-merge). Needs ANTHROPIC_API_KEY + AUTOPILOT_PAT secrets on the sandbox repo.

🤖 Generated with Claude Code