@pilotspace/add 1.0.0 → 1.1.0

package/tooling/templates/TASK.md.tmpl

@@ -2,6 +2,9 @@
 
 slug: {{slug}} · created: {{date}} · stage: {{stage}}
 phase: specify   <!-- specify -> scenarios -> contract -> tests -> build -> verify -> observe -> done -->
+<!-- high-risk/method-defining scope? declare `risk: high` on the slug line above and lower
+     the dial with `autonomy: conservative` — the engine refuses an unguarded completion
+     (`unguarded_high_risk_auto`, run.md guard). A comment is never a declaration. -->
 
 > One file = one task. Fill sections top-to-bottom; the `add` skill drives each phase.
 > When a phase is unclear, read its book chapter in `.add/docs/` (linked per section).
@@ -66,6 +69,10 @@ Plan (one test per scenario, asserting behavior not internals):
   - test_<scenario>: arrange <Given> / act <When> / assert <Then> + assert <unchanged>
 
 Tests live in: `./tests/` · MUST run red (missing implementation) before Build.
+<!-- declare paths as backticked tokens on this line: `./…` = this task dir ·
+     a token with "/" = project root · a bare name = sibling of the previous
+     token's dir · a directory counts its *.py files (non-recursive); reports
+     mark declared counts with † · anything resolving outside the project root counts 0 -->
 
 <!-- EXIT: one test per scenario; suite red for the RIGHT reason; target recorded. -->