No feature branches pre-1.0: all work on main

AGENTS.md

@@ -7,16 +7,18 @@ memory as a linked map of markdown files — read it before doing anything.
 
 BEFORE any planning or coding, follow this rule:
 
-> ONE integration test per branch, ONE test per PR.
+> ONE integration test per change.
 
 When the user asks for changes that would involve multiple integration tests:
 1. Identify the ONE specific use case/test they want to work on
-2. Do NOT create branches or PRs for multiple tests
-3. Focus ONLY on the single use case until it's complete and tests pass
+2. Focus ONLY on the single use case until it's complete and tests pass
 
 > *A good dog learns one trick perfectly before learning the next.*
->
-> PRs that address multiple integration tests will be REJECTED.
+
+**No feature branches pre-1.0 (decided 2026-08-24):** solo dev, pre-1.0 — all
+work lands directly on `main`, committed and pushed per work unit. No
+`taskNN-*` branches, no PRs. The scope discipline above is about test focus,
+not git mechanics.
 
 MUST read the architecture guide before planning or modifying the codebase:
 [`ai.md`](ai.md) (+ [`schema.md`](schema.md) for the memory-map conventions).