Groundwork

# Final Groundwork

You are Codex, acting as the repo “kickoff engineer”.

Goal:
Do the minimal, high-leverage groundwork so this repo is ready for real development work, based on the existing docs:
- SPEC.md
- ARCHITECTURE.md
- ROADMAP.md
(and any docs/ runbook / ADR folder that already exist)

What you must set up (do not overbuild):
1) Root AGENTS.md
- Encode our development operating rules:
- per-slice loop: Plan → Code → Verify → Review → Release → Update docs
- slice packet convention: changes/<slug>/{PLAN.md,TASK_QUEUE.md,NOW.md}
- required PLAN sections: blast radius, test plan (exact commands), rollback plan, acceptance checklist, `Pre-merge Operations`
- “Proof bundle” requirement before PR: commands run + outcomes
- human approval required before final merge and production deploy
- post-merge release artifacts must land on a follow-up branch/PR, not by pushing directly to `main`
- when to split scope, and how to handle review feedback (must-fix vs optional vs ignore-with-justification)

2) Repo runnable basics
- Ensure README.md includes *real* commands for:
- install deps
- run dev server
- run tests
- lint/format
- typecheck/build (if applicable)
- If commands don’t exist, add the simplest scripts/config to make them exist (but keep it minimal).

3) CI skeleton (minimal)
- Add a basic CI workflow that runs on PR:
- install
- lint (if exists)
- test (if exists)
- build/typecheck (if exists)
- Choose the CI platform based on what’s already in the repo (GitHub Actions if nothing exists).
- Keep it simple and fast. No matrix unless needed.

4) Folder + template scaffolding
- Create:
- changes/.gitkeep (or equivalent) and a short README inside changes/ explaining the slice packet
- docs/adr/0001-template.md if ADR folder doesn’t exist
- Optional but useful:
- .github/pull_request_template.md with “What/Why/How to test/Risks/Rollback/Proof”

Rules:
- Do not invent tech stack. Detect it from the repo (package.json, pyproject, go.mod, etc.) and tailor scripts accordingly.
- If the repo is empty, propose a minimal stack aligned with ARCHITECTURE.md and ask me to confirm, but still draft the files with placeholders.
- Prefer placeholders over wrong commands.
- Keep diffs small and focused. We’re setting rails, not building features.

Deliverables:
A) A checklist of what you created/changed
B) The exact files added/edited with their contents
C) Any open questions you need me to answer (only if truly blocking)

Now scan the repo and implement this groundwork.