@pilotspace/add 1.8.0 → 1.10.0

package/tooling/templates/TASK.fast.md.tmpl

@@ -0,0 +1,72 @@
+# TASK: {{title}}
+
+slug: {{slug}} · created: {{date}} · stage: {{stage}}
+autonomy: {{autonomy}}
+phase: ground   <!-- fast lane: ground -> specify -> contract -> tests -> build -> verify -> observe -> done -->
+fast: true   <!-- the fast lane: a small task, collapsed flow + minimal template. Omit --fast for full rigor. -->
+
+> Fast lane — one small task, minimal sections, filled top-to-bottom. The trust floor still
+> holds: a FROZEN §3 contract · ≥1 red test before build · a recorded §6 gate (security = HARD-STOP).
+> The acceptance scenario collapses into §1 `Accept:`; OBSERVE is one optional line at the gate.
+
+---
+
+## 0 · GROUND — the real codebase
+
+Touches (files · symbols): <path:symbol — what it is / how it is keyed>
+Anchors the contract cites: <the symbols §3 will name>
+
+---
+
+## 1 · SPECIFY — the rules
+
+Feature: <name>
+Must:
+  - <required behavior>
+Reject:
+  - <bad input / situation> -> "<error_code>"
+Accept: <the one acceptance scenario, Given/When/Then condensed to one line — it drives the §4 test>
+Assumptions: ⚠ <the one most likely wrong> — why; if wrong: <cost>   (or "none material — biggest risk: X")
+
+---
+
+## 3 · CONTRACT — freeze the shape
+
+```
+<the shape that freezes: signature / fields · success + each rejection's response>
+```
+
+`Least-sure flag surfaced at freeze:` <[spec|contract|test] the point most likely wrong — why; if wrong: cost>
+Status: DRAFT
+<!-- The freeze IS the one approval. Approved -> Status: FROZEN @ vN — approved by <name>.
+     Changing a frozen contract = change request back to SPECIFY. -->
+
+---
+
+## 4 · TESTS — failing-first (red)
+
+Plan: test_<accept> — assert the §1 Accept line's Then (behavior, not internals).
+Tests live in: `./tests/` · MUST run red (missing implementation) before Build.
+
+---
+
+## 5 · BUILD — AI writes code
+
+Scope (may touch): `./src/`   <every file the build may write — declared before the §3 freeze>
+Code lives in: `./src/`   ·   Constraints: change no test, no contract; allow-list packages only.
+
+---
+
+## 6 · VERIFY — evidence + gate
+
+- [ ] all tests pass · coverage held · no test or contract altered during build
+- [ ] green was EARNED — no overfit / vacuous asserts / stubbed-away logic
+- [ ] no exposed secrets, injection openings, or unexpected dependencies (security = HARD-STOP)
+
+Build expectations (from §1 Accept + §3 CONTRACT): <the observable outcome a correct build must produce — confirmed by <how / where>>
+
+### GATE RECORD
+Outcome: <PASS | RISK-ACCEPTED | HARD-STOP>
+Reviewed by: <name> · date: <date>
+<!-- A security finding is ALWAYS HARD-STOP. Record exactly one outcome — no silent pass.
+     OBSERVE (optional): one `[SPEC · open]` or competency-delta line here if the loop taught the foundation something. -->

package/tooling/templates/TASK.md.tmpl

@@ -1,7 +1,7 @@
 # TASK: {{title}}
 
 slug: {{slug}} · created: {{date}} · stage: {{stage}}
-autonomy: {{autonomy}}   <!-- inherited from the project default (PROJECT.md); explicit level: manual < conservative < auto (visible · overridable) — lower below if a high-risk task needs it, or run `add.py autonomy set`. -->
+autonomy: {{autonomy}}   <!-- inherited from the project default (PROJECT.md); explicit level: manual < conservative < auto (visible · overridable) — lower below if a high-risk task needs it, or run `add.py autonomy set`. Multi-component repo (monorepo/multi-repo)? add a `component: <name>` line (declared in `.add/components.toml`) to ADD that component's root to your §5 Scope; omit for single-component projects (byte-identical default). -->
 phase: ground   <!-- ground -> specify -> scenarios -> contract -> tests -> build -> verify -> observe -> done -->
 <!-- high-risk/method-defining scope? declare `risk: high` on the slug line above and lower the
      autonomy level to `manual` or `conservative` — the engine refuses an unguarded completion