didericis
4cb106b48d
#315 already merged `start --headless` (assume_yes on _launch_bottle + AgentProvider.headless_prompt). The PRD's proposed start_headless / attach_agent_headless helpers were redundant with it, and the latter diverged by hand-rolling --no-interactive/-p instead of using the headless_prompt provider abstraction. Drop them. Scope the remaining headless work to what's actually new: a forge_env hook threaded into the existing _launch_bottle core, and a `resume --headless` path (resume has no non-interactive entry point today). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WL77TgFxKbs3cidGMG9dz7
Docs
How this project records what it builds and why — and a guide to picking the right document for what you're capturing.
When to write which document
| Artifact | For |
|---|---|
PRD (docs/prds/) |
A feature: what to build, scope, success criteria. |
Research note (docs/research/) |
A landscape/tradeoff investigation. |
Decision record (docs/decisions/) |
A decision that isn't itself a feature — a policy, a convention, a "we will / won't do this," or a load-bearing choice made inside a larger PRD that deserves to be discoverable on its own. |
A decision that's fully specified by a PRD doesn't need duplicating in a decision record. Write one when the decision would otherwise be buried in prose, lost in an issue thread, or have no in-repo home at all (small requests that don't merit a PRD; non-feature choices like merge strategy or a trust posture).