@pilotspace/add 1.6.0 → 1.7.1

package/tooling/templates/GLOSSARY.md.tmpl

@@ -34,3 +34,5 @@ foundation compaction: the retrospective shrink — collapse a foundation spec's
 rolled-up settled line: the single line left when a stable run is collapsed — lossy on prose, lossless on traceability (carries a `see git` pointer).
 per-spec shape: each foundation spec's own tailored rolled-line format (PROJECT §Spec bullets · §Key-Decisions rows · CONVENTIONS learnings · GLOSSARY definition · MODEL_REGISTRY rows), all sharing one eligibility rule: shipped + zero open residues.
 newest-first append-only: every append-only foundation sequence prepends the newest record at the top; the rolled-up settled line anchors at the bottom (the oldest end), so compaction collapses upward.
+ship review: the whole-milestone, cross-task evidence the AI fills at milestone close (ship-by-domain · cross-task evidence · goal-met map), read before the exit-criteria boxes are checked — evidence, not a new gate; the ritual lives in the `add` skill's loop.md.
+release steps: the AI-defined, per-milestone ordered hints to ship a closed milestone, merge being one small step (a PR · an exported hand-off doc · a tag or publish are others); defined at close and fed into the release scope (release.md), never a second flow.

package/tooling/templates/MILESTONE.md.tmpl

@@ -24,3 +24,26 @@ Out: <explicitly deferred — the anti-scope-creep list>
 
 ## Exit criteria (observable; map each to the task that delivers it)
 - [ ] User can <observable behavior>        (← <slug>)
+
+## Close — ship review   (AI fills when every task is done — the evidence behind the engine gate, read before the boxes are checked)
+> Whole-milestone, cross-task review the AI fills in. It is the evidence behind the EXISTING engine
+> gate (milestone-done / checking the Exit-criteria boxes) — NOT a new approval. Tool-agnostic.
+
+### Ship by domain   (what changed, per bounded context)
+- tooling : <add.py / state.json / templates — what shipped, or "untouched">
+- skill   : <SKILL.md / phases/* / guides — what shipped, or "untouched">
+- book    : <docs/* — what shipped, or "untouched">
+
+### Cross-task evidence   (one row per task)
+- <slug> : gate=<PASS|RISK-ACCEPTED> · tests=<n green> · residue=<none|note>
+
+### Goal met?   (map the evidence back to this milestone's Exit criteria — read before the Exit-criteria boxes are checked)
+- [ ] each Exit criterion above is satisfied by a Cross-task evidence row or a Ship-by-domain change (cite which)
+- goal: <restate the milestone goal — and the one evidence line that proves the ship meets it>
+
+## Release steps   (AI-DEFINED — fill the ordered steps to ship this milestone; engine records, human gate)
+> The AI writes the release steps for THIS milestone here (hints, not engine commands). MERGE is one
+> small step among them. These feed the release scope (release.md) when the cut is bundled.
+- [ ] <step — e.g. open a PR from the Close ship-review above; the human reviews + merges>
+- [ ] <step — e.g. export the ship-review to a hand-off doc, e.g. `pandoc CLOSE.md -o close.docx`>
+- [ ] <step — e.g. tag / publish / deploy  (human-run, per release.md)>

package/tooling/templates/TASK.md.tmpl

@@ -133,6 +133,13 @@ Constraints: do NOT change any test or the contract; allow-list packages only; a
 - [ ] layering & dependencies follow CONVENTIONS.md
 - [ ] a person reviewed and approved the change
 
+### Build expectations — what "correct" looks like (fill BEFORE build; confirm each at the gate)
+> Pre-declare the OBSERVABLE outcomes a correct build must produce — derived from §2 SCENARIOS
+> + §3 CONTRACT — so this gate checks the build is RIGHT, not merely that tests are green. Each
+> row is evidence you can SEE, not a restatement of a test name.
+- [ ] <observable outcome a correct build must produce> — confirmed by <how / where>
+- [ ] <another observable outcome> — confirmed by <evidence seen>
+
 ### Deep checks — do not skim (fill the path that applies; the resolver judges which)
 - [ ] WIRING (code) — every new symbol is referenced; record where / how confirmed
 - [ ] DEAD-CODE (code) — no new unused or orphaned symbol introduced
@@ -150,7 +157,11 @@ Reviewed by: <name> · date: <date>
 ## 7 · OBSERVE — feed the next loop ▸ docs/09-the-loop.md
 
 Watch (reuse scenarios as monitors): <error rate / per-rejection rate / latency>
-Spec delta for the next loop: <what production taught you>
+
+### Spec delta
+Forward changes for the next loop — each re-enters at Specify as the next task. One line
+each, tagged `[SPEC · open|seeded|dropped]`, with evidence (e.g. `[SPEC · open] rate-limit
+the retry path (evidence: prod herd spikes)`). See the `add` skill's `deltas.md`.
 
 ### Competency deltas
 What did this loop teach the foundation? One line each, tagged by competency