Remove automaton task management framework

- Delete .automaton/ directory and all tracked files
- Remove git hooks (pre-commit, pre-push)
- Delete ADR-0002 (automaton as issue tracker)
- Remove automaton references from AGENTS.md, HANDOFF.md, TASK_COMPLETION_SUMMARY.md, docs
- Update .gitignore to remove automaton entries
- Unregister from ~/.automaton/projects.json

docs/adr/0002-automaton-as-issue-tracker.md

@@ -1,18 +0,0 @@
-# ADR-0002: Automaton as the issue tracker for engineering skills
-
-Date: 2026-06-27
-Status: Accepted
-
-## Context
-Matt Pocock's engineering skills (to-prd, to-issues, triage, setup-*) assume an external issue tracker (gh/glab/.scratch). This project uses Automaton tasks + phases instead.
-
-## Decision
-Adopt Automaton as the issue tracker. Mapping:
-- Issues = task folders under .automaton/tasks/<name>/.
-- Triage states → phases: needs-triage=new, needs-info=research (awaiting user), ready-for-agent=decomposition:approved/implement, ready-for-human=flagged in notes, wontfix=complete+tombstone.
-- Publish issues = automaton_orchestrate_finalize(task, subtasks) from DECOMPOSITION.md.
-- The 5 issue-tracker skills are rewritten to call Automaton; the 8 methodology skills port verbatim.
-
-## Consequences
-- Skills installed as global pi dev skills at ~/.agents/skills/, symlinked into ~/.pi/agent/skills/.
-- One house flow: grill-with-docs → to-prd → to-issues → implement(tdd) → code_review:approved.