@ikon85/agent-workflow-kit 0.39.0 → 0.41.0

package/.agents/skills/grill-me/SKILL.md

@@ -52,7 +52,7 @@ For a cross-cutting plan, run `python3 .claude/hooks/drift-guard.py --census-sta
 
 ## Plan-lock — writing PLAN.md
 
-Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root (gitignored since, doesn't travel over git — consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
+Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root. `PLAN.md` is **expected** to be ignored by git so it never travels over git — the kit never edits your `.gitignore` by itself, but `/setup-workflow` offers to add that rule (consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
 
 ## Re-grill reconcile — execute-ready (Wave 26)
 

package/.agents/skills/grill-with-docs/SKILL.md

@@ -40,7 +40,7 @@ For a cross-cutting plan, run `python3 .claude/hooks/drift-guard.py --census-sta
 
 ## Plan-lock — writing PLAN.md
 
-Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root (gitignored since, doesn't travel over git — consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
+Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root. `PLAN.md` is **expected** to be ignored by git so it never travels over git — the kit never edits your `.gitignore` by itself, but `/setup-workflow` offers to add that rule (consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
 
 </plan-lock>
 

package/.agents/skills/orchestrate-wave/SKILL.md

@@ -146,8 +146,8 @@ replace the ~30-second heartbeat; otherwise the standing heartbeat remains requi
    points there). Bring its branch to current `main`:
    `git -C <wave> merge --ff-only origin/main` (if your repo guards destructive
    git, ff-merge is the safe path — not `reset --hard`). Install dependencies with
-   your package manager after (the lockfile may have moved). A gitignored plan doc
-   survives the merge.
+   your package manager after (the lockfile may have moved). A plan doc the repository
+   ignores survives the merge; a tracked one may not (`/setup-workflow` offers those rules).
 5. **Run project setup steps (`§Setup`)** the later verify needs — e.g. a DB
    tunnel or service the live-verify depends on. Absent layer → start whatever your
    live-verify environment requires before Phase 4.
@@ -332,8 +332,8 @@ written · merge order documented.
 - **Release this run's slice claims.** A landed slice's PR supersedes its claim;
   for a pulled or abandoned slice remove the claim this run planted (unassign +
   `claim released` comment) so it stays grabbable. Foreign ones stay untouched.
-- **Before removing any slice worktree, read its `ANNAHMEN.md`** (an assumptions
-  log, gitignored at worktree-root) and propagate each build-time assumption marker
+- **Before removing any slice worktree, read its `ANNAHMEN.md`** (an assumptions log at
+  the worktree root, **expected** to be ignored by git — `/setup-workflow` offers that rule) and propagate each build-time assumption marker
   to the sibling issue it carries. A hand-driven multi-PR / migration landing does
   NOT run `wrapup`'s assumption-propagation step — this is the only place it
   happens; `worktree remove` deletes the log.

package/.agents/skills/setup-workflow/SKILL.md

@@ -37,6 +37,7 @@ This is a prompt-driven skill, not a deterministic script. Explore, present what
 | `docs/agents/workflow-capabilities.json` + capability assets | consumer-owned Worktree Lifecycle, Memory Lifecycle, Workflow Advisories, and Safety Guardrails choices (Sections A4–A7) |
 | `.claude/settings.json` | additive activation of the advisory kit-origin Edit/Write hint (Section A8) |
 | user-local routing profile | familiar agent surfaces + switching autonomy (Section A9; never package- or repository-owned) |
+| `.gitignore` | **offered only** — one previewed, append-only marker block with the ignore rules for the planning artifacts the skills write (Section A11) |
 
 ## Idempotency contract — read before writing anything
 
@@ -405,6 +406,55 @@ machine, checkout path, repository name, credentials, or current GitHub login.
 Even a valid capability authorizes local preparation only; a pull request,
 push, publish, or merge remains a separate explicit approval.
 
+### 2j. Section A11 — Planning-artifact ignore rules (offered)
+
+> The planning skills write `PLAN.md`, `PLAN-REVIEW-LOG.md`, and `ANNAHMEN.md`
+> into a session worktree. `.gitignore` is the consumer's file: the kit does not
+> own it and never touches it during `init` or `update`, so those artifacts are
+> ignored only if this repository already says so. Without the rules every
+> planning worktree reports a permanently dirty tree, the Worktree Lifecycle
+> cleanup refuses to remove it, and a plan doc can be committed by accident.
+
+Read the current state first. The preview is read-only and writes nothing:
+
+```bash
+python3 scripts/worktree-lifecycle/ignore_seed.py preview
+```
+
+- `nothing-to-do` — this repository already ignores every declared artifact.
+  Report it and ask nothing.
+- `blocked` — the marker block exists but no longer covers everything. That
+  block is consumer-owned: name the uncovered artifacts, let the user edit
+  `.gitignore` themselves, and never repair or rewrite it.
+- `append` — show the exact lines the preview printed, the whole marker block
+  verbatim and nothing summarized, then ask: *"Should setup add these ignore
+  rules to `.gitignore`?"*
+
+Offer exactly two choices:
+
+- **Add the rules** — run the seeder once. It appends that one marker block and
+  touches nothing else:
+
+```bash
+python3 scripts/worktree-lifecycle/ignore_seed.py apply
+```
+
+- **Not now** — write nothing. Explain that the planning skills still work, that
+  the artifacts will keep showing up as untracked changes, and that re-running
+  `/setup-workflow` offers this again.
+
+The write is append-only inside one idempotent marker block: it never rewrites,
+reorders, or removes an existing line; a re-run after an approval is a
+byte-identical no-op; and a decline leaves the file exactly as it was. An
+artifact already committed to history is reported separately — an ignore rule
+cannot untrack it, and setup never runs `git rm`. Only this explicit, approved
+step may write `.gitignore`; `init` and `update` reconciliation never reach the
+seeder.
+
+Report `appended · nothing to do (already ignored) · declined · blocked
+(consumer-edited block)`. After an approval — and only then — the Section A4
+`scratchPatterns` derivation has real ignored planning artefacts to read.
+
 ### 3. Section B — Triage labels
 
 > When `triage` processes an incoming issue it applies labels (or your tracker's equivalent). It needs strings you've actually configured, or it creates duplicates.

package/.agents/skills/setup-workflow/worktree-lifecycle.md

@@ -82,12 +82,34 @@ The exact kit-owned commands are:
 Preserve unrelated settings, hook groups, profile sections, and unknown keys.
 Repeated reconciliation with the same choice is byte-identical.
 
+## Planning-artifact ignore rules (offered, never installed)
+
+The planning artefacts the shipped skills write live in the worktree, but
+`.gitignore` is a consumer file the kit does not own: `init` and `update` never
+touch it. Setup may therefore only **offer** the rules, from Section A11, using
+`python3 scripts/worktree-lifecycle/ignore_seed.py`. The kit-owned declaration
+of which artefacts those are is `scripts/worktree-lifecycle/plan-artifacts.json`.
+
+| State | Setup action |
+|---|---|
+| `append` | Show the exact marker block, then ask. |
+| approve | Run `ignore_seed.py apply` once: it appends that one block, append-only. |
+| decline | Write nothing; a later rerun offers it again. |
+| already ignored | Report `nothing to do`; ask nothing and write nothing. |
+| re-run after approval | Byte-identical no-op; never a second block. |
+| consumer-edited block | `blocked` — report the uncovered artefacts and leave the file untouched. |
+
+The seeder never rewrites, reorders, or removes an existing line, and a tracked
+artefact is reported rather than untracked for the consumer. Only this explicit,
+approved step may write `.gitignore`.
+
 ## Scratch classification and sweep
 
 Reconcile an explicit `scratchPatterns` array when enabling a new profile.
 Derive its glob values from the consumer's ignored planning artefacts; an empty
 array is valid. Existing values are consumer-owned and remain byte-identical on
-adoption or rerun. Core never supplies filename defaults.
+adoption or rerun. Core never supplies filename defaults — the offered ignore
+rules above are what give that derivation something real to read.
 
 Also reconcile an explicit
 `wrapup.landingGeneratedArtifactPatterns` array. Derive candidates from the

package/.claude/skills/grill-me/SKILL.md

@@ -52,7 +52,7 @@ For a cross-cutting plan, run `python3 .claude/hooks/drift-guard.py --census-sta
 
 ## Plan-lock — writing PLAN.md
 
-Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root (gitignored since, doesn't travel over git — consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
+Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root. `PLAN.md` is **expected** to be ignored by git so it never travels over git — the kit never edits your `.gitignore` by itself, but `/setup-workflow` offers to add that rule (consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
 
 ## Re-grill reconcile — execute-ready (Wave 26)
 

package/.claude/skills/grill-with-docs/SKILL.md

@@ -40,7 +40,7 @@ For a cross-cutting plan, run `python3 .claude/hooks/drift-guard.py --census-sta
 
 ## Plan-lock — writing PLAN.md
 
-Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root (gitignored since, doesn't travel over git — consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
+Once all decisions are made (plan locked, before sign-off/handoff) and the session runs in a **worktree** → write the locked plan as `PLAN.md` to the worktree root. `PLAN.md` is **expected** to be ignored by git so it never travels over git — the kit never edits your `.gitignore` by itself, but `/setup-workflow` offers to add that rule (consistent with CLAUDE.md "plan inside the worktree"). This way the locked plan survives a session cut and `to-prd` finds its default source. Continuing same-session work **without** a worktree stays allowed (conversation = source); but for a deliberate **session cut** before `to-prd`, `PLAN.md` is mandatory. (The `-codex` variant already writes `PLAN.md` anyway.)
 
 </plan-lock>
 

package/.claude/skills/orchestrate-wave/SKILL.md

@@ -146,8 +146,8 @@ replace the ~30-second heartbeat; otherwise the standing heartbeat remains requi
    points there). Bring its branch to current `main`:
    `git -C <wave> merge --ff-only origin/main` (if your repo guards destructive
    git, ff-merge is the safe path — not `reset --hard`). Install dependencies with
-   your package manager after (the lockfile may have moved). A gitignored plan doc
-   survives the merge.
+   your package manager after (the lockfile may have moved). A plan doc the repository
+   ignores survives the merge; a tracked one may not (`/setup-workflow` offers those rules).
 5. **Run project setup steps (`§Setup`)** the later verify needs — e.g. a DB
    tunnel or service the live-verify depends on. Absent layer → start whatever your
    live-verify environment requires before Phase 4.
@@ -332,8 +332,8 @@ written · merge order documented.
 - **Release this run's slice claims.** A landed slice's PR supersedes its claim;
   for a pulled or abandoned slice remove the claim this run planted (unassign +
   `claim released` comment) so it stays grabbable. Foreign ones stay untouched.
-- **Before removing any slice worktree, read its `ANNAHMEN.md`** (an assumptions
-  log, gitignored at worktree-root) and propagate each build-time assumption marker
+- **Before removing any slice worktree, read its `ANNAHMEN.md`** (an assumptions log at
+  the worktree root, **expected** to be ignored by git — `/setup-workflow` offers that rule) and propagate each build-time assumption marker
   to the sibling issue it carries. A hand-driven multi-PR / migration landing does
   NOT run `wrapup`'s assumption-propagation step — this is the only place it
   happens; `worktree remove` deletes the log.

package/.claude/skills/setup-workflow/SKILL.md

@@ -37,6 +37,7 @@ This is a prompt-driven skill, not a deterministic script. Explore, present what
 | `docs/agents/workflow-capabilities.json` + capability assets | consumer-owned Worktree Lifecycle, Memory Lifecycle, Workflow Advisories, and Safety Guardrails choices (Sections A4–A7) |
 | `.claude/settings.json` | additive activation of the advisory kit-origin Edit/Write hint (Section A8) |
 | user-local routing profile | familiar agent surfaces + switching autonomy (Section A9; never package- or repository-owned) |
+| `.gitignore` | **offered only** — one previewed, append-only marker block with the ignore rules for the planning artifacts the skills write (Section A11) |
 
 ## Idempotency contract — read before writing anything
 
@@ -405,6 +406,55 @@ machine, checkout path, repository name, credentials, or current GitHub login.
 Even a valid capability authorizes local preparation only; a pull request,
 push, publish, or merge remains a separate explicit approval.
 
+### 2j. Section A11 — Planning-artifact ignore rules (offered)
+
+> The planning skills write `PLAN.md`, `PLAN-REVIEW-LOG.md`, and `ANNAHMEN.md`
+> into a session worktree. `.gitignore` is the consumer's file: the kit does not
+> own it and never touches it during `init` or `update`, so those artifacts are
+> ignored only if this repository already says so. Without the rules every
+> planning worktree reports a permanently dirty tree, the Worktree Lifecycle
+> cleanup refuses to remove it, and a plan doc can be committed by accident.
+
+Read the current state first. The preview is read-only and writes nothing:
+
+```bash
+python3 scripts/worktree-lifecycle/ignore_seed.py preview
+```
+
+- `nothing-to-do` — this repository already ignores every declared artifact.
+  Report it and ask nothing.
+- `blocked` — the marker block exists but no longer covers everything. That
+  block is consumer-owned: name the uncovered artifacts, let the user edit
+  `.gitignore` themselves, and never repair or rewrite it.
+- `append` — show the exact lines the preview printed, the whole marker block
+  verbatim and nothing summarized, then ask: *"Should setup add these ignore
+  rules to `.gitignore`?"*
+
+Offer exactly two choices:
+
+- **Add the rules** — run the seeder once. It appends that one marker block and
+  touches nothing else:
+
+```bash
+python3 scripts/worktree-lifecycle/ignore_seed.py apply
+```
+
+- **Not now** — write nothing. Explain that the planning skills still work, that
+  the artifacts will keep showing up as untracked changes, and that re-running
+  `/setup-workflow` offers this again.
+
+The write is append-only inside one idempotent marker block: it never rewrites,
+reorders, or removes an existing line; a re-run after an approval is a
+byte-identical no-op; and a decline leaves the file exactly as it was. An
+artifact already committed to history is reported separately — an ignore rule
+cannot untrack it, and setup never runs `git rm`. Only this explicit, approved
+step may write `.gitignore`; `init` and `update` reconciliation never reach the
+seeder.
+
+Report `appended · nothing to do (already ignored) · declined · blocked
+(consumer-edited block)`. After an approval — and only then — the Section A4
+`scratchPatterns` derivation has real ignored planning artefacts to read.
+
 ### 3. Section B — Triage labels
 
 > When `triage` processes an incoming issue it applies labels (or your tracker's equivalent). It needs strings you've actually configured, or it creates duplicates.

package/.claude/skills/setup-workflow/worktree-lifecycle.md

@@ -82,12 +82,34 @@ The exact kit-owned commands are:
 Preserve unrelated settings, hook groups, profile sections, and unknown keys.
 Repeated reconciliation with the same choice is byte-identical.
 
+## Planning-artifact ignore rules (offered, never installed)
+
+The planning artefacts the shipped skills write live in the worktree, but
+`.gitignore` is a consumer file the kit does not own: `init` and `update` never
+touch it. Setup may therefore only **offer** the rules, from Section A11, using
+`python3 scripts/worktree-lifecycle/ignore_seed.py`. The kit-owned declaration
+of which artefacts those are is `scripts/worktree-lifecycle/plan-artifacts.json`.
+
+| State | Setup action |
+|---|---|
+| `append` | Show the exact marker block, then ask. |
+| approve | Run `ignore_seed.py apply` once: it appends that one block, append-only. |
+| decline | Write nothing; a later rerun offers it again. |
+| already ignored | Report `nothing to do`; ask nothing and write nothing. |
+| re-run after approval | Byte-identical no-op; never a second block. |
+| consumer-edited block | `blocked` — report the uncovered artefacts and leave the file untouched. |
+
+The seeder never rewrites, reorders, or removes an existing line, and a tracked
+artefact is reported rather than untracked for the consumer. Only this explicit,
+approved step may write `.gitignore`.
+
 ## Scratch classification and sweep
 
 Reconcile an explicit `scratchPatterns` array when enabling a new profile.
 Derive its glob values from the consumer's ignored planning artefacts; an empty
 array is valid. Existing values are consumer-owned and remain byte-identical on
-adoption or rerun. Core never supplies filename defaults.
+adoption or rerun. Core never supplies filename defaults — the offered ignore
+rules above are what give that derivation something real to read.
 
 Also reconcile an explicit
 `wrapup.landingGeneratedArtifactPatterns` array. Derive candidates from the

package/README.md

@@ -469,6 +469,39 @@ the old way. Decision record:
 
 ## Release notes
 
+### 0.41.0
+
+- added: `docs/adr/0009-teardown-authority-is-stateless-repository-classification.md`
+- changed: `agent-workflow-kit.package.json`
+- changed: `docs/adr/0007-session-teardown-requires-provenance-bound-ownership.md`
+- changed: `scripts/pr-body-check.py`
+- changed: `scripts/test_pr_body_check.py`
+
+### 0.40.0 — planning ignore rules are offered, never installed
+
+Nothing in this release requires a consumer action. `kit-update` reconciles it.
+
+Several skills used to state as fact that `PLAN.md`, `PLAN-REVIEW-LOG.md` and
+`ANNAHMEN.md` are gitignored and live on disk only. In your repository that was
+simply untrue: neither `init` nor `update` has ever touched your `.gitignore`,
+and no installed file added those rules — so planning worktrees looked
+permanently dirty, cleanup refused to remove them, and a plan document could be
+committed by accident.
+
+- **The prose is honest now.** The affected skills say the artifacts are
+  *expected* to be ignored and name who can add the rule, instead of asserting
+  an installed guarantee.
+- **`/setup-workflow` offers the rules.** It previews the exact lines, asks
+  first, and appends one idempotent marker block. Declining changes nothing; a
+  re-run is a byte-identical no-op; a block you edited yourself is reported, not
+  repaired; an artifact already tracked by git is reported separately, because
+  an ignore rule cannot untrack it.
+- **`.gitignore` stays yours.** It has no manifest entry, no baseline hash and
+  no three-way reconcile — a file the kit cannot reconcile is one it must not
+  write uninvited. Ordinary `update` reconciliation never reaches the seeder.
+  Decision record:
+  [`docs/adr/0008-planning-ignore-rules-are-offered-never-installed.md`](docs/adr/0008-planning-ignore-rules-are-offered-never-installed.md).
+
 ### 0.39.0 — self-explaining guards, one glob dialect, a board you can create
 
 Nothing in this release requires a consumer action. `kit-update` reconciles it.

package/agent-workflow-kit.package.json

@@ -1,5 +1,5 @@
 {
-  "kitVersion": "0.39.0",
+  "kitVersion": "0.41.0",
   "files": [
     {
       "path": ".agents/skills/ask-matt/SKILL.md",
@@ -207,7 +207,7 @@
       "ownerSkill": "grill-me",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "e106dbb6f62415cc5eef7d923d864a30e75e108a079d12c0f1624ef7d03d6f6d",
+      "sha256": "b13087563adda186f62aa6206a9233034310ff2458535362246294a45e03079f",
       "mode": 420,
       "origin": "kit"
     },
@@ -247,7 +247,7 @@
       "ownerSkill": "grill-with-docs",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "5616f15e6660270f9f84fba245caa647c47d8af8dc9e526045bb503e7f1f5863",
+      "sha256": "93694d55fe8d164c4c0e0eef27529bd1211acdaddc18224a921c2b0f3b5a10ed",
       "mode": 420,
       "origin": "kit"
     },
@@ -447,7 +447,7 @@
       "ownerSkill": "orchestrate-wave",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "02862cd5e7e07a5f06dad89792fcebd0a6c17cf2216a27c7e0f724026fdda53a",
+      "sha256": "fab4fb2f4d6fee820c9b7a737fa955a5ea2cd398987246bd7a04c5fba2c75b26",
       "mode": 420,
       "origin": "kit"
     },
@@ -687,7 +687,7 @@
       "ownerSkill": "setup-workflow",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "4ef2a06e17e08f0fc0c5cc09e4414af67a186a73ca7634e8c378aab5b5638274",
+      "sha256": "29c61411aa42a3f456b3f27fdd15552654b64ef2d72b321bc9c9e11229745626",
       "mode": 420,
       "origin": "kit"
     },
@@ -757,7 +757,7 @@
       "ownerSkill": "setup-workflow",
       "surface": "codex",
       "installRole": "consumer",
-      "sha256": "bf68e0a80b212159f6838bc2bcd3e85714a70cceeff55ed019f87246175182e7",
+      "sha256": "f9fb7ef6d4f4e1ed603a5a480d8f97508fd6c99def8194c7ba0a95c62fd3c743",
       "mode": 420,
       "origin": "kit"
     },
@@ -1489,7 +1489,7 @@
       "ownerSkill": "grill-me",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "ec8d9f299db153a0412b7ef1d01832dc6a765f1819713ca45dc64294541cf9d4",
+      "sha256": "a63331339ed4e018d770face4e7cfe483225ce758a4a1302f39a50239e8187e1",
       "mode": 420,
       "origin": "kit"
     },
@@ -1569,7 +1569,7 @@
       "ownerSkill": "grill-with-docs",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "a17521a8d72eb19316c6adb21837e790c9839834ff441abf3ff44d8e1f63809a",
+      "sha256": "0cb1b41fc6bde94d3e71f3377cbb15b9d7a9a4089df66f591fc907dc19b6c1b5",
       "mode": 420,
       "origin": "kit"
     },
@@ -1769,7 +1769,7 @@
       "ownerSkill": "orchestrate-wave",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "02862cd5e7e07a5f06dad89792fcebd0a6c17cf2216a27c7e0f724026fdda53a",
+      "sha256": "fab4fb2f4d6fee820c9b7a737fa955a5ea2cd398987246bd7a04c5fba2c75b26",
       "mode": 420,
       "origin": "kit"
     },
@@ -2029,7 +2029,7 @@
       "ownerSkill": "setup-workflow",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "4ef2a06e17e08f0fc0c5cc09e4414af67a186a73ca7634e8c378aab5b5638274",
+      "sha256": "29c61411aa42a3f456b3f27fdd15552654b64ef2d72b321bc9c9e11229745626",
       "mode": 420,
       "origin": "kit"
     },
@@ -2099,7 +2099,7 @@
       "ownerSkill": "setup-workflow",
       "surface": "claude",
       "installRole": "consumer",
-      "sha256": "bf68e0a80b212159f6838bc2bcd3e85714a70cceeff55ed019f87246175182e7",
+      "sha256": "f9fb7ef6d4f4e1ed603a5a480d8f97508fd6c99def8194c7ba0a95c62fd3c743",
       "mode": 420,
       "origin": "kit"
     },
@@ -2627,7 +2627,7 @@
       "path": "scripts/pr-body-check.py",
       "kind": "script",
       "installRole": "consumer",
-      "sha256": "864dad50be7904cf0c1d70956352c70d2195a350a5a6875de6b866c494f16612",
+      "sha256": "7fa67a672d6f6986b0fba99e78157d51225ab91f61b691a4cc184d316b521882",
       "mode": 493,
       "origin": "kit"
     },
@@ -2815,6 +2815,22 @@
       "mode": 420,
       "origin": "kit"
     },
+    {
+      "path": "scripts/worktree-lifecycle/ignore_seed.py",
+      "kind": "script",
+      "installRole": "consumer",
+      "sha256": "defd667ed94301cffb0f08e0a910873c246be267cb458adf40f5e7b2109ae4d0",
+      "mode": 493,
+      "origin": "kit"
+    },
+    {
+      "path": "scripts/worktree-lifecycle/plan-artifacts.json",
+      "kind": "doc",
+      "installRole": "consumer",
+      "sha256": "fe7f805ca9c698f9d77bdda4372f6f5a516b1e60c46ae732a94de184cb0ce3b4",
+      "mode": 420,
+      "origin": "kit"
+    },
     {
       "path": "scripts/worktree-lifecycle/profile.py",
       "kind": "script",
@@ -2827,7 +2843,7 @@
       "path": "scripts/worktree-lifecycle/README.md",
       "kind": "doc",
       "installRole": "consumer",
-      "sha256": "91cfa8ebb74872ccec1160c0a7b28edcfacea3217900805034dca0f0c8f39c05",
+      "sha256": "0dbba4a87d41171f3fce22a4842eecd2a989ea6a5ddf44832d7b2aed9feb4226",
       "mode": 420,
       "origin": "kit"
     },

package/docs/adr/0007-session-teardown-requires-provenance-bound-ownership.md

@@ -1,6 +1,6 @@
 # Session teardown requires provenance-bound ownership
 
-Status: accepted (2026-07-26, Wave #271)
+Status: superseded by [ADR-0009](./0009-teardown-authority-is-stateless-repository-classification.md) (2026-07-27, #320)
 
 Long agent sessions create branches, linked worktrees, setup outputs, and
 landing-time build artifacts. The desired end state is that every

package/docs/adr/0008-planning-ignore-rules-are-offered-never-installed.md

@@ -0,0 +1,84 @@
+# Planning ignore rules are offered, never installed
+
+Status: accepted (2026-07-26, #255)
+
+The shipped planning skills write `PLAN.md`, `PLAN-REVIEW-LOG.md`, and
+`ANNAHMEN.md` into a session worktree, and several of them told the agent those
+files were gitignored and lived on disk only. In a consumer repository that was
+simply untrue: `init` and `update` never touch `.gitignore`, and no installed
+file adds the rules. The consequence mirrors what this repository fixed for
+itself in #254 — every planning worktree reports a permanently dirty tree, the
+shipped Worktree Lifecycle cleanup refuses to remove it, genuinely unlanded work
+becomes indistinguishable from plan scratch, and a consumer who never notices
+can commit a plan doc into their history that the prose implied could not be
+committed.
+
+The constraint is the consumer contract. Consumer-owned files are written once
+and never overwritten by ordinary reconciliation, and `.gitignore` is stronger
+still: the kit does not own it at all and has no manifest entry, no baseline
+hash, and no three-way reconcile for it. A file the kit cannot reconcile is a
+file the kit must not write uninvited.
+
+We decided to close the gap from both ends:
+
+1. **`/setup-workflow` offers the rules as an explicit, previewed, approved
+   step.** Section A11 previews with
+   `python3 scripts/worktree-lifecycle/ignore_seed.py preview`, shows the exact
+   lines verbatim, asks, and only an approval runs `apply`. The write is
+   append-only inside one idempotent marker block. It never rewrites, reorders,
+   or removes an existing line; a re-run is a byte-identical no-op; a decline
+   changes nothing; a repository that already ignores the artefacts reports
+   `nothing to do`; and a marker block the consumer has since edited is
+   `blocked`, never repaired. Nothing in `init` or `update` can reach the
+   seeder.
+2. **Shipped skill prose states the assumption instead of asserting the fact.**
+   A skill now says these artefacts are *expected* to be ignored and names
+   `/setup-workflow` as the thing that can make it true, rather than claiming
+   the kit already did. The claim is pinned by a census lint over both skill
+   trees, so the assertion cannot silently return.
+
+This is the same shape the kit shipped for the GitHub-Projects board in 0.39.0
+(#24): offer, preview, obtain an explicit yes, never write an outward or
+consumer-owned artefact silently.
+
+Which artefacts the offer covers is a kit-owned fact — the kit knows which files
+its own skills write — declared once in
+`scripts/worktree-lifecycle/plan-artifacts.json`. That is deliberately not the
+consumer's `worktreeLifecycle.scratchPatterns`, which is derived *from* the
+consumer's ignored planning artefacts and would otherwise be circular: before
+this decision there was nothing ignored for it to be derived from.
+
+## Considered options
+
+- **Append-only seed at `init`:** rejected. It respects append-only mechanics
+  but still writes a file the kit does not own, uninvited, on first install —
+  the one action the consumer contract exists to prevent.
+- **Readiness capability only:** rejected. Reporting the gap and letting the
+  affected skills degrade honestly leaves the friction in place and fixes
+  nothing for the consumer who wants the promise to hold.
+- **Prose-only fix:** rejected as insufficient on its own. It removes the false
+  claim but leaves every consumer with dirty planning worktrees and a cleanup
+  that refuses to run. It is kept as one half of the decision, not the whole.
+- **Deriving the rules from `worktreeLifecycle.scratchPatterns`:** rejected as
+  circular, and because that array is consumer-owned deletion-adjacent policy
+  that Core never supplies defaults for.
+- **Untracking an already-committed artefact:** rejected. An ignore rule cannot
+  untrack a tracked file, and running `git rm` on consumer history is far past
+  what a setup step may do. The seeder reports the tracked artefact and stops.
+
+## Consequences
+
+- A consumer who runs `/setup-workflow` and approves gets the guarantee the
+  skills describe; a consumer who declines keeps a byte-identical `.gitignore`
+  and loses nothing but the convenience.
+- The never-overwrite contract is untouched: the only write is an append behind
+  an explicit yes, and `update` reconciliation still never touches
+  `.gitignore`.
+- The offer reaches only consumers who run setup again. That is accepted: it is
+  the price of not writing an unowned file, and re-running `/setup-workflow` is
+  already the documented way to pick up a new project-layer capability.
+- After an approval, `scratchPatterns` derivation finally has real ignored
+  planning artefacts to read, so the Worktree Lifecycle scratch classification
+  stops being vacuous in a fresh consumer repository.
+- A consumer who edits or deletes the marker block owns the outcome; the kit
+  reports and stops rather than restoring its own block.