autometta-setuplisted

## What this skill does Walks the operator through adopting Autometta in the current working repository. There are two passes: - **Pass 1: dispatch contract.** Stage cards, worker prompt template, verifier prompt template, cross-family verifier pattern. A human orchestrator authors a card, dispatches a worker, runs a verifier, commits. No daemon, no cron. This pass is stable and the recommended starting point. - **Pass 2: phat-controller autonomous loop.** A cron-driven `tick.sh` that drives pass-1 dispatches across one or more subscribed repos. Reads stage cards, spawns workers, runs verifiers, tracks budget and failure counters, halts on cap. This pass requires more setup and trust. Adopt pass 1 first. Add pass 2 only after at least one pass-1 cycle has run cleanly in the target repo. ## When NOT to use - The current repo is Autometta itself. Skill is for *adopters*, not the source repo. - The user wants a generic orchestrator pattern; use `agent-orchestrator` instead. - The user wants to set up publish guards; use `repo-publish-guard-init` or `repo-publish-guard-retrofit` instead. - The user is asking about commit attribution or cross-family verification as abstract concepts. Point them at the source docs in Autometta (`docs/dispatch-contract.md`, `docs/lessons.md`, `docs/verification.md`) without running the setup flow. ## Decision tree ``` Are you adopting Autometta in another repo? ├── No -> wrong skill, stop here └── Yes ├── Do you want an unattended cron l