Add headless project onboarding primitives + Coda prompt (0.5.2)

[dilawarabbas1]

Summary

Three dotagent commands gain --from-stdin + --format json so Coda (or any orchestrator) can run the full project-setup ceremony headlessly. dotagent stays the data layer; the conversation lives in the orchestrator. Plus a complete drop-in Coda system prompt that drives them.

New primitives

# Brief — markdown body on stdin, JSON receipt out
echo "<brief.md>" | dotagent project brief upload --from-stdin --force --format json

# Project — JSON payload on stdin, JSON receipt out
echo '{"name":"X","goal":"...","success_criteria":[...]}' \
  | dotagent project init --from-stdin --format json

# Module — JSON payload on stdin, JSON receipt out
echo '{"name":"Auth","plan":{"acceptance_criteria":[...]}}' \
  | dotagent project add-module --from-stdin --format json

JSON receipts return structured success/error data. Structured errors: missing required field → exit 2; invalid JSON → exit 2; already-initialized → exit 1 with {ok: false, error: "already-initialized"}.

Coda onboarding prompt

CODA_ONBOARDING_PROMPT.md — drop-in system prompt with:

• Phase 1: Brief — 14 questions, probe rule for vague answers, brief upload
• Phase 2: Project init — payload JSON shape, brief-linkage fields
• Phase 3: Module slate — per-feature decomposition, dependency wiring
• End-of-setup checklist — 5 verification commands with brief check as the gate
• Failure handling table — branchable on each receipt error

Fresh-project reality (the second part of the ask)

Explicit section telling Coda which files are EXPECTED to be absent on day-zero and must not be created during setup:

docs/feature_master.md + docs/feature_master/FM-*.md
docs/db-impact-map*.md   docs/redis-key-registry*.md
docs/bug-registry*.md    docs/anti-patterns.md
docs/architecture.md     docs/ARCHITECTURE.md
docs/dependency-map.md   docs/ops/*.md
src/*  (no code yet)

Schema marks all required=False. CLAUDE.md still points at them (canonical pointer); the AI reading the manifest sees the pointers, finds the files absent, and knows "fresh project — I'm the one who creates them as work ships."

The boundary holds on day zero: dotagent never writes hand-maintained docs; Coda doesn't write them during onboarding either. Claude inside cycles populates them, with rationale, as features ship.

The end-of-setup summary lists these explicitly so the user understands what's empty and why.

Test plan

• tests/test_headless_onboarding.py — 15 tests (5 brief · 4 project · 5 module · 1 end-to-end)
• Full suite: 748 passed, 2 skipped

Docs

• CODA_ONBOARDING_PROMPT.md — drop-in system prompt
• CODA_PROMPT.md — added "Headless project onboarding (0.5.2)" pointer in Section 8.5
• CHANGELOG.md — 0.5.2 entry

Version

0.5.1 → 0.5.2

---

Generated by Claude Code