@zalom/plastic 1.0.3 → 1.1.1

package/skills/intent-brainstorming/evals/evals.json

@@ -0,0 +1,67 @@
+{
+  "skill_name": "plastic-intent-brainstorming",
+  "notes": "Intent 66a. Spec for the QMD-first step in the Why/explore-context phase (surface prior decisions/specs/outcomes before grep/Read). Runner is intent 76; spec only. Intent 164 extended this file with the prose-grilling, conflict-supersession, and handoff-to-speccing scenarios; evals 2-4 are pending a real observed run per the plastic-evaluating-skills convention.",
+  "evals": [
+    {
+      "id": 1,
+      "scope": "behavior",
+      "set": "validation",
+      "prompt": "QMD is present. Brainstorming the active intent during the Why phase, the agent needs prior decisions and specs on caching.",
+      "expected_output": "In the explore-project-context (Why) step, before scanning the store with grep/Read, runs `ruby ~/.plastic/scripts/qmd-sync search \"caching decisions\"` to surface prior decisions, specs, or outcomes, then opens the authoritative intent file for any hit it acts on. No-op fallback to INDEX.md / file scan when QMD is absent.",
+      "files": [],
+      "assertions": [
+        {
+          "type": "human",
+          "check": "qmd-sync search is run during Why before grep/Read; authoritative file opened for any hit",
+          "observed": "SKILL.md (or agent file) carries the QMD-first step: run qmd-sync search before grep/Read, then open the authoritative file; no-op fallback when QMD is absent",
+          "result": "pass"
+        }
+      ]
+    },
+    {
+      "id": 2,
+      "scope": "behavior",
+      "set": "validation",
+      "prompt": "During Why exploration for intent X, the owner first rules that a setting ships as a CLI flag. Later in the same session, after more discussion, the owner rules that it should ship as a config-file setting instead, explicitly reversing the earlier call.",
+      "expected_output": "The skill persists BOTH rulings as separate insight-append calls with --stage Why: one for the CLI-flag ruling when it was made, and a second for the config-file ruling that names the CLI-flag ruling as superseded and states that this ruling supersedes it. Neither call is skipped, merged, or batched.",
+      "files": [],
+      "assertions": [
+        {
+          "type": "human",
+          "check": "two separate `ruby ~/.plastic/scripts/insight-append {intent_dir} \"<ruling text>\" --stage Why --author human` calls are made, one per ruling, immediately as each ruling lands; the second insight names the superseded CLI-flag ruling and states supersession",
+          "result": "expect-pass"
+        }
+      ]
+    },
+    {
+      "id": 3,
+      "scope": "behavior",
+      "set": "train",
+      "prompt": "Brainstorming a new intent about notification delivery, the agent needs to learn the owner's preferred channel (email, push, or SMS).",
+      "expected_output": "The agent asks a single conversational prose question about the preferred channel, one at a time, phrased as a sentence rather than a bulleted or lettered multiple-choice menu.",
+      "files": [],
+      "assertions": [
+        {
+          "type": "human",
+          "check": "the question is prose, not a chip/lettered multiple-choice menu; only one question is asked per message",
+          "result": "expect-pass"
+        }
+      ]
+    },
+    {
+      "id": 4,
+      "scope": "behavior",
+      "set": "train",
+      "prompt": "Design for intent Y is presented and the owner has ruled on every open section.",
+      "expected_output": "The skill states the enriched Why is captured (Context, Decisions, one insight per ruling) and invokes /plastic-intent-speccing as the handoff. It does not write spec.md itself.",
+      "files": [],
+      "assertions": [
+        {
+          "type": "code",
+          "check": "no spec.md write action is taken by this skill; the terminal message names /plastic-intent-speccing and states spec.md is not authored here",
+          "result": "expect-pass"
+        }
+      ]
+    }
+  ]
+}

package/skills/{brainstorming → intent-brainstorming}/references/design-principles.md

@@ -20,30 +20,25 @@ steps).
 
 ## Process Flow (diagram)
 
-The Checklist above already states this ordered flow as numbered steps 1-8; this
+The Checklist above already states this ordered flow as numbered steps 1-6; this
 diagram is the same flow in a visual form.
 
 ```dot
 digraph brainstorming {
     "Explore project context" [shape=box];
-    "Ask clarifying questions" [shape=box];
+    "Grill in prose" [shape=box];
     "Propose 2-3 approaches" [shape=box];
     "Present design sections" [shape=box];
-    "User approves design?" [shape=diamond];
-    "Write spec" [shape=box];
-    "Spec self-review\n(fix inline)" [shape=box];
-    "User reviews spec?" [shape=diamond];
-    "Invoke plastic-writing-plans" [shape=doublecircle];
-
-    "Explore project context" -> "Ask clarifying questions";
-    "Ask clarifying questions" -> "Propose 2-3 approaches";
+    "Owner rules?" [shape=diamond];
+    "Collect rulings\n(persist each immediately)" [shape=box];
+    "Invoke /plastic-intent-speccing" [shape=doublecircle];
+
+    "Explore project context" -> "Grill in prose";
+    "Grill in prose" -> "Propose 2-3 approaches";
     "Propose 2-3 approaches" -> "Present design sections";
-    "Present design sections" -> "User approves design?";
-    "User approves design?" -> "Present design sections" [label="no, revise"];
-    "User approves design?" -> "Write spec" [label="yes"];
-    "Write spec" -> "Spec self-review\n(fix inline)";
-    "Spec self-review\n(fix inline)" -> "User reviews spec?";
-    "User reviews spec?" -> "Write spec" [label="changes requested"];
-    "User reviews spec?" -> "Invoke plastic-writing-plans" [label="approved"];
+    "Present design sections" -> "Owner rules?";
+    "Owner rules?" -> "Present design sections" [label="no, revise"];
+    "Owner rules?" -> "Collect rulings\n(persist each immediately)" [label="yes"];
+    "Collect rulings\n(persist each immediately)" -> "Invoke /plastic-intent-speccing";
 }
 ```

package/skills/intent-continuing/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: plastic-intent-continuing
+description: >-
+  Use when a specific intent is named to resume, by id or by description, or on `continuing
+  --intent {id}`. Reads that intent's savepoint ledger and hands off to plastic-intent-starting.
+  The general "continue" / new-session triggers belong to the plastic-continuing router, not
+  here, so a bare "continue" does not settle on this skill directly. Boot (health check, core
+  context, version, statusline) is owned by the SessionStart hook, not this skill. Does not
+  drive work autonomously (that is plastic-auto).
+user-invocable: true
+---
+
+# Continuing (intent route)
+
+`plastic-intent-continuing` is the intent route of `plastic-continuing`. It resumes ONE
+specific intent by its savepoint ledger, then hands off to `plastic-intent-starting`. It does
+NOT land on a dashboard and does NOT execute work autonomously (that is `plastic-auto`); both
+of those are other routes' jobs.
+
+**Boot is not this skill's job.** The `hook-session-start` hook already runs by construction on
+every session start: it runs the core health check (`doctor --core`), primes `PLASTIC.md` +
+store/project state, and prints the `Plastic Core loaded - v{version}` banner. The
+`plastic-statusline` hook sets the statusline. So by the time this skill runs, core is loaded
+and healthy (or the banner already warned otherwise). This skill picks up from there and
+resumes the named intent. This is the seam future continue-flags build on (see [[39]]).
+
+## When to Use
+- A specific intent is named to resume, by id or by description
+- `continuing --intent {id}`
+
+## Determine Store
+
+1. **Global store** - `~/.plastic/INDEX.md` exists → global mode.
+2. **Local store** - a project store under `~/.plastic/projects/{slug}/` whose registered
+   path (in `~/.plastic/projects.yml`) matches the current working directory → project mode.
+   The SessionStart hook already detects this; here you only need the slug to scope the
+   named intent's store.
+3. If neither exists → announce "No Plastic store found. Run /plastic-install."
+
+## Conditional Ledger-Resume
+
+Fires ONLY when the user explicitly asks to continue a SPECIFIC intent, or an agent is
+instructed to continue one. It is not part of every boot.
+
+QMD-first (when available): when the user names the intent by description rather than id, before
+scanning the store with grep/Read run `ruby ~/.plastic/scripts/qmd-sync search "<terms>"` to
+surface the candidate intent, then open the authoritative intent file for the hit you resume. The
+command is a no-op when QMD is absent, so fall back to the existing INDEX.md / file scan.
+
+For that intent's directory:
+
+1. **Read `savepoint.md` FIRST (intent 81).** It is a deterministic, append-only ledger
+   (one line per event, newest at the bottom): `{utc-iso8601}  {Stage}  {milestone}`. Classify
+   the state from the **last line** alone, then verify ONLY that line's artifact. The bookends
+   are fixed: first line `What  created`, last line either a cycle position or
+   `Done  delivered|abandoned`.
+
+   | Last line | State | Verify only |
+   |---|---|---|
+   | `What  {id}--{slug}.md` | born / parked | intent file exists |
+   | `Why  started` | Why entered, no spec yet | spec.md not yet real; continue Why |
+   | `Why  spec.md created` | Why done | spec.md present; continue to How |
+   | `How  started` / `How  plan.md created` | How in progress | plan.md; continue How |
+   | `How  checklist.md created` / `Exec  started` | ready for / in Exec | plan.md + checklist.md present; continue Exec |
+   | `Exec  outcome.md created` | Exec done | outcome.md present; ready to complete |
+   | `Done  delivered` / `Done  abandoned` | terminal | do NOT cycle-resume; INDEX is authoritative |
+
+2. **Verify the stage file.** Confirm only the last line's artifact exists and is non-empty
+   (ledger `How  plan.md created` → `plan.md` must be present and non-empty). Do not re-probe
+   every lifecycle file.
+3. **Drift handling.** If the ledger's last line disagrees with files-on-disk, rebuild the
+   ledger from filesystem state and note the correction. A rebuilt ledger is the file-landing
+   skeleton (no `started`/`Done` lines), which still pins cycle position:
+   ```bash
+   ruby -r ~/.plastic/scripts/lib/bridge -e 'Bridge.rebuild_savepoint("<intent_dir>")'
+   ```
+4. **Derive the next step:**
+   - First unchecked item in `checklist.md` if it exists, else
+   - "advance to the next lifecycle stage" (e.g. ledger shows Why/spec.md → next is How).
+   - The newest `## Insights` entry supplies human-readable context (Insights are
+     append-only, newest at the bottom).
+5. **Announce, then hand off to `plastic-intent-starting`:**
+   ```
+   Resuming intent [ID] - [name]
+   Store: [global | project:<slug> | local]
+   Stage: [from ledger last line]
+   Next step: [first unchecked checklist item | advance to <stage>]
+   Context: [newest ## Insights entry]
+   Drift: [none | ledger rebuilt from filesystem]
+   ```
+   Hand off to `plastic-intent-starting`: it takes the lock, boards at this station, and is
+   where the single "auto or guided?" ask for the intent route lives, asked there exactly
+   once and never duplicated here. Its auto branch is the one that hands off to `plastic-auto`;
+   this skill never hands to `plastic-auto` directly.
+
+## References
+
+- Read `references/context-management.md` for the save/continue protocol and for
+  debugging the resume flow.

package/skills/intent-continuing/evals/evals.json

@@ -0,0 +1,145 @@
+{
+  "skill_name": "plastic-intent-continuing",
+  "notes": "Intent 158a1: slimmed to the specific-intent resume route of plastic-continuing (D8, extract not duplicate). Bare 'continue' now belongs to the router; triggering evals 1-4 were recast so this skill's positives always name a specific intent, and eval 4 asserts bare 'continue' does NOT settle here directly. Behavior eval 11 (dashboard selection) was removed, relocated to plastic-project-continuing's evals. Behavior eval 15 is new: the terminal handoff goes to plastic-intent-starting, not directly to plastic-auto. Scopes: description triggering (1-8) and behavior/convention compliance of the ledger-resume skill (9-15).",
+  "results": {
+    "triggering": { "cases": 8, "passed": 8, "run": "2026-07-10, one subagent per case" },
+    "behavior": { "cases": 7, "passed": 7, "evidence": "convention checks against skills/intent-continuing/SKILL.md after the 158a1 extraction" }
+  },
+  "evals": [
+    {
+      "id": 1, "scope": "triggering", "set": "train",
+      "prompt": "continue intent 4a",
+      "expected_output": "Activates plastic-intent-continuing (a specific intent named by id).",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
+      ]
+    },
+    {
+      "id": 2, "scope": "triggering", "set": "train",
+      "prompt": "resume the statusline-coloring intent",
+      "expected_output": "Activates plastic-intent-continuing (a specific intent named by description).",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
+      ]
+    },
+    {
+      "id": 3, "scope": "triggering", "set": "validation",
+      "prompt": "continuing --intent 96",
+      "expected_output": "Activates plastic-intent-continuing (the --intent form).",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
+      ]
+    },
+    {
+      "id": 4, "scope": "triggering", "set": "train",
+      "prompt": "continue",
+      "expected_output": "Does NOT settle on plastic-intent-continuing directly. Bare 'continue' with no specific intent named belongs to the plastic-continuing router, which defaults to plastic-project-continuing.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE != plastic-intent-continuing", "observed": "plastic-continuing", "result": "pass" }
+      ]
+    },
+    {
+      "id": 5, "scope": "triggering", "set": "train",
+      "prompt": "continue delivering this intent autonomously, don't ask me",
+      "expected_output": "Does NOT settle on plastic-intent-continuing for execution. Shares 'continue' but the autonomous-delivery intent routes to plastic-auto.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-auto", "observed": "plastic-auto", "result": "pass" }
+      ]
+    },
+    {
+      "id": 6, "scope": "triggering", "set": "validation",
+      "prompt": "continue the for-loop to the next iteration in this function",
+      "expected_output": "Does NOT activate plastic-intent-continuing. Near-miss: shares 'continue' but is a code-editing task.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE != plastic-intent-continuing", "observed": "none", "result": "pass" }
+      ]
+    },
+    {
+      "id": 7, "scope": "triggering", "set": "train",
+      "prompt": "resume the paused background download",
+      "expected_output": "Does NOT activate plastic-intent-continuing. Near-miss: shares 'resume' but is unrelated to Plastic sessions.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE != plastic-intent-continuing", "observed": "none", "result": "pass" }
+      ]
+    },
+    {
+      "id": 8, "scope": "triggering", "set": "validation",
+      "prompt": "what's the dashboard look like right now",
+      "expected_output": "Does NOT activate plastic-intent-continuing directly; an overview request without a specific intent named is a dashboard/project-board task.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE != plastic-intent-continuing", "observed": "plastic-dashboard", "result": "pass" }
+      ]
+    },
+    {
+      "id": 9, "scope": "behavior", "set": "train",
+      "prompt": "Does the skill defer boot to the SessionStart hook rather than running it itself?",
+      "expected_output": "SKILL.md states boot (health check, core context, version banner, statusline) is owned by hook-session-start / plastic-statusline, not this skill.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "SKILL.md says boot is owned by the SessionStart hook and the skill does not run it", "observed": "'Boot is not this skill's job.' paragraph naming hook-session-start and plastic-statusline", "result": "pass" }
+      ]
+    },
+    {
+      "id": 10, "scope": "behavior", "set": "train",
+      "prompt": "Does the skill avoid running doctor / setting the statusline itself?",
+      "expected_output": "SKILL.md does NOT instruct running doctor.rb --core or setting the statusline; it attributes those to the hooks.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "no in-skill boot step invokes doctor.rb --core or sets the statusline; both are attributed to hooks", "observed": "doctor --core and statusline mentioned only as hook-owned in the 'Boot is not this skill's job' note", "result": "pass" }
+      ]
+    },
+    {
+      "id": 11, "scope": "behavior", "set": "validation",
+      "prompt": "Is ledger-resume conditional and ledger-driven?",
+      "expected_output": "Resume fires only when a specific intent is named; reads savepoint.md last line as stage, verifies the stage file, rebuilds on drift, derives next step from first unchecked checklist item.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "Conditional Ledger-Resume section reads last ledger line, verifies stage file, calls rebuild_savepoint on drift, uses first unchecked checklist item", "observed": "all four present in 'Conditional Ledger-Resume'", "result": "pass" }
+      ]
+    },
+    {
+      "id": 12, "scope": "behavior", "set": "validation",
+      "prompt": "Are the stale prose-savepoint fields gone?",
+      "expected_output": "No 'In progress' / 'Blockers' fields read from a prose savepoint remain; the ledger model is used instead.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "no prose-savepoint announce template (In progress / Blockers from prose)", "observed": "absent; announce uses Stage/Next step/Context/Drift derived from ledger + checklist", "result": "pass" }
+      ]
+    },
+    {
+      "id": 13, "scope": "behavior", "set": "validation",
+      "prompt": "Is the 'Determine Store' local-store gap filled?",
+      "expected_output": "Step 2 of Determine Store describes local/project-store detection (no empty step).",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "Determine Store step 2 documents local/project store detection via projects.yml + CWD match", "observed": "filled", "result": "pass" }
+      ]
+    },
+    {
+      "id": 14, "scope": "behavior", "set": "validation",
+      "prompt": "QMD is present. The user says: continue the work on the statusline coloring (names the intent by description, not id).",
+      "expected_output": "Before scanning the store with grep/Read to locate the named intent, runs `ruby ~/.plastic/scripts/qmd-sync search \"statusline coloring\"` to surface the candidate intent, then opens the authoritative intent file for the hit it resumes. No-op fallback to INDEX.md / file scan when QMD is absent.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "human", "check": "qmd-sync search is run before grep/Read when the intent is named by description; authoritative file opened for the hit", "observed": "Conditional Ledger-Resume carries the QMD-first step: run qmd-sync search before grep/Read, then open the authoritative file; no-op fallback when QMD is absent", "result": "pass" }
+      ]
+    },
+    {
+      "id": 15, "scope": "behavior", "set": "train",
+      "prompt": "Does the ledger-resume's terminal handoff go to plastic-intent-starting or directly to plastic-auto?",
+      "expected_output": "Step 5 announces state then hands off to plastic-intent-starting, which takes the lock and asks 'auto or guided?' exactly once; plastic-intent-starting's own auto branch is the one that hands to plastic-auto. This skill never hands to plastic-auto directly.",
+      "files": ["skills/intent-continuing/SKILL.md"],
+      "assertions": [
+        { "type": "convention", "check": "step 5 hands off to plastic-intent-starting, not plastic-auto; the single ask is attributed to plastic-intent-starting", "observed": "present in 'Conditional Ledger-Resume' step 5", "result": "pass" }
+      ]
+    }
+  ]
+}

package/skills/intent-continuing/references/context-management.md

@@ -0,0 +1,28 @@
+# Context Management (Save, then resume-flow debugging)
+
+## Save Point
+Triggered by PreCompact hook or manually:
+1. Find active intent(s) from `~/.plastic/INDEX.md`
+2. Update active intent's `checklist.md` (check off completed items)
+3. Update active intent's `savepoint.md` (in-progress, next steps, blockers, discoveries)
+4. Add observations to `## Insights`
+5. Update INDEX.md
+6. Commit: `cd ~/.plastic && git add . && git commit -m "chore: savepoint - [intent name]"`
+7. Notify user to `/clear`
+
+## Debugging the resume flow
+
+When a resume looks wrong (the announced stage does not match what is on disk, or the next
+step looks stale):
+
+1. Read `savepoint.md`'s last line directly; that line alone is the source of truth for stage
+   (see `SKILL.md`'s `## Conditional Ledger-Resume` for the full state table).
+2. Confirm the artifact that line implies (`plan.md`, `checklist.md`, `outcome.md`, ...) is
+   present and non-empty on disk.
+3. If the two disagree, the ledger has drifted: rebuild it rather than hand-editing:
+   `ruby -r ~/.plastic/scripts/lib/bridge -e 'Bridge.rebuild_savepoint("<intent_dir>")'`
+4. Re-read the rebuilt last line and re-derive the next step from `checklist.md`'s first
+   unchecked item.
+
+The general "land on the board / priority order / stale future intents" flow now lives in
+`plastic-project-continuing`; this file no longer duplicates it.

package/skills/{creating-intent → intent-creating}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic-creating-intent
+name: plastic-intent-creating
 description: Use when new work begins, the user expresses a new goal, says "new intent", or no active intent exists for the current task. Creates intents in the global store (~/.plastic/store/) or in a project's store (~/.plastic/projects/{slug}/store/) depending on context.
 user-invocable: true
 ---
@@ -73,7 +73,7 @@ Having a "parent" in mind does NOT automatically mean branch. Choose by meaning:
 frontmatter edge and reproject. Links are decided by context influence (a `chain` edge has a high
 bar: the candidate's context must materially help deliver this intent), not by shared files or a
 similarity score. To gather candidates with their context and record an edge, use the
-`plastic-linking-intents` skill and `scripts/link-suggest`.
+`plastic-intent-linking` skill and `scripts/link-suggest`.
 
 ### 3. Determine Intent Properties
 
@@ -126,7 +126,7 @@ cleanly, and do not work around the failure by hand-writing the files.
 ### 6. If Implementation Intent Spawns a Project
 
 When the user says "start building" or the plan calls for a new project, invoke the
-`plastic-creating-project` skill; it owns project directory creation, AGENTS.md
+`plastic-project-creating` skill; it owns project directory creation, AGENTS.md
 population, projects.yml registration, store provisioning, and the auto-commit of
 both stores. Add `project-<slug>` to this intent's `tags` array either before
 invoking it or as part of that skill's handoff.

package/skills/{creating-intent → intent-creating}/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "plastic-creating-intent",
+  "skill_name": "plastic-intent-creating",
   "notes": "Intent 68. Scope: output-quality for the sources-vs-chain construction rules (D1/D2). Asserts the related-but-not-spawned case produces NO sources plus a predecessor chain link and a ## Links mirror, contrasted with the created-from case (true ascendant -> --sources set, reciprocal chain). The machine-checkable half lives in test/new_intent_test.rb (test_sources_path_gets_child_in_chain_frontmatter); this file documents the agent-facing scenario for skill evaluation and is NOT run by bin/test.",
   "evals": [
     {

package/skills/{intent-discovery → intent-discovering}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: plastic-intent-discovery
+name: plastic-intent-discovering
 description: >-
   What-stage context deposit at intent activation: run QMD discovery over the
   intent's chain/sources and related parked intents, and write findings to

package/skills/intent-ending/SKILL.md

@@ -0,0 +1,151 @@
+---
+name: plastic-intent-ending
+description: >
+  Wrap, finish, close, or mark an intent Done, delivered or abandoned. Use
+  when completing or abandoning an intent, when a checklist reaches 100
+  percent and Exec is finished, or when asked to "wrap this up".
+user-invocable: true
+---
+
+# Intent Ending
+
+The one procedure every terminal transition routes through. Auto mode, the
+curator path, and releasing all call this skill (or its backing script,
+`scripts/end-intent`) for the mechanical close instead of restating the same
+prose three times. `abandoned` is the SAME procedure as `delivered`, not a
+failure branch: only outcome.md content and the INDEX section differ.
+
+## The 8 steps (0-7)
+
+| # | Step | Who does it |
+|---|---|---|
+| 0 | Precondition check | You, before touching outcome.md |
+| 1 | outcome.md + intent-file `## Outcome` summary | `scripts/end-intent` |
+| 2 | INDEX.md terminal move (Active -> Completed/Abandoned) | `scripts/end-intent` |
+| 3 | savepoint `Done` bookend | `scripts/end-intent` |
+| 4 | store auto-commit | `scripts/end-intent` |
+| 5 | disarm (worktree + lock) | You, after end-intent exits 0 |
+| 6 | QMD reindex, async, LAST | You |
+| 7 | EM-to-CTO report | You |
+
+Steps 1-4 are ONE callable script, not four separate one-liners: this is
+exactly what the failure mode this intent fixes looked like (releasing hand
+authored the close in prose and dropped the savepoint bookend for two real
+deliveries). Never restate outcome/INDEX/savepoint prose inline again; call
+`scripts/end-intent`.
+
+### Step 0. Precondition (the gate is section-blind, not selective)
+
+`Bridge.check_gate` (scripts/lib/bridge.rb) is LIVE code already wired into
+the write-time hook. Its outcome.md rule is a blind scan of the WHOLE
+checklist.md: `content.scan(/^- \[ \]/)` counts every unchecked box, in
+every section, with no awareness of which section a box lives in. ANY
+unchecked box anywhere blocks the outcome.md write; there is no exemption
+for orchestrator-owned or completion-tracking items.
+
+1. Read checklist.md. Tick every item as it is actually performed, including
+   an item that describes the close itself: running this very procedure IS
+   what that item describes, so tick it at the moment you begin the close,
+   before authoring outcome.md. By the time outcome.md is written,
+   checklist.md must read 100 percent checked; there is no other way past
+   the gate.
+2. Confirm every acceptance criterion in spec.md is verifiable (tests pass,
+   or the manual check described in its HOW line was actually run).
+3. If checklist.md still has an unchecked box, stop here. Finish it first
+   (tick it if the described work is actually done, or do the remaining
+   work); do not attempt outcome.md and fight the gate's deny.
+
+### Step 1-4. Run `scripts/end-intent`
+
+First author outcome.md for real (never leave the scaffold placeholder in
+place): copy `templates/outcome.md`, set the frontmatter to
+`disposition: delivered` or `disposition: abandoned`, and fill `## Summary`,
+`## Delivered`, `## Verification`, `## Follow-ups`. On abandon, `## Summary`
+states the abandonment reason and the trail (see Pivot below). Also author
+the rich INDEX entry note now (a short line in the store's existing
+Completed/Abandoned convention: mode/tier, what shipped or why it was
+abandoned, suite result, merge/spawn notes); content authoring stays with
+you, `--index-note` only appends what you write.
+
+Then call the script once:
+
+```bash
+ruby ~/.plastic/scripts/end-intent \
+  --store <store_path> --id <intent_id> --disposition delivered|abandoned \
+  --outcome-summary "<one-line ## Outcome summary for the intent file>" \
+  --index-note "<rich Completed/Abandoned entry description>"
+```
+
+This does all of steps 1-4 in order: guards outcome.md (refuses a missing,
+still-placeholder, or wrong-disposition file with exit 2 and authors
+nothing), stamps the intent file's `## Outcome` section, moves the INDEX.md
+line from `## Active` to `## Completed` or `## Abandoned` (dated today,
+idempotent) with the `--index-note` text appended after the date so the
+entry stays rich, appends the savepoint `Done` bookend, and commits the
+store repo. Omit `--index-note` for a thin id+date entry, add `--no-commit`
+when a separate commit step already covers the store, and `--dry-run` to
+preview with no writes. Exit 0 is success; exit 1 is a usage or resolution
+failure; exit 2 is the outcome.md guard refusing (fix outcome.md and re-run,
+nothing was written).
+
+### Step 5. Disarm (worktree + lock)
+
+Two branches, decided by how this intent ships:
+
+- **Shipped through a release** (the `plastic-releasing` flow reached this
+  close): merge the code branch back BEFORE removing the worktrees, via
+  `Worktree.finish(bridge_data, merge: true)`. Releasing's own workflow
+  already drives this; this skill's job here is only the outcome/INDEX/
+  savepoint/commit core above.
+- **Auto mode or the curator path** (no release involved): plain remove,
+  branch survives for reclaim.
+  ```bash
+  ruby -r ~/.plastic/scripts/lib/bridge -e \
+    'Bridge.disarm_auto(ENV["CLAUDE_CODE_SESSION_ID"], intent_id: "<ID>")'
+  ```
+  `disarm_auto` releases both worktrees, clears the `delivery.lock`, and only
+  then makes the bridge purge-eligible, in that order. Never leave an
+  orphaned worktree; run `git worktree prune` on a stale reference.
+
+### Step 6. QMD reindex, LAST
+
+Only after step 5 has released the worktrees and cleared the lock, so the
+index never references state about to disappear:
+
+```bash
+ruby ~/.plastic/scripts/qmd-sync reindex --store <store-root> --async
+```
+
+No-op when QMD is absent. Runs in the background so it never blocks the
+turn.
+
+### Step 7. EM-to-CTO report
+
+Brief the human like an engineering manager to a CTO: impact and risk first,
+in plain language, the decision left to them (merge, release, or accept).
+See `outcome.md` for the details; do not restate it verbatim.
+
+## Abandoned is the same procedure
+
+`disposition: abandoned` runs the identical steps 0-7. The only differences
+are outcome.md content (Summary states why this was abandoned, not what was
+delivered) and the INDEX target section (`## Abandoned` instead of
+`## Completed`). Never branch the mechanical steps by disposition; the
+script already does that internally.
+
+## Mid-flight pivot
+
+When the work that shipped differs from what spec.md or plan.md originally
+called for, do not retcon those documents. Record the decision once in
+`## Insights`, then let outcome.md carry the truth of what actually
+happened, including the abandoned trail when part of the work was dropped
+mid-flight. outcome.md is truth of delivery; spec and plan stay the
+historical record of what was planned.
+
+## Routing
+
+`plastic-releasing`, `plastic-auto`, the curator agent, `store-curating`, and
+`store-indexing` all delegate their mechanical close to this skill (or call
+`scripts/end-intent` directly for steps 1-4). None of them restate the
+outcome/INDEX/savepoint prose inline any more; if you find one that does,
+that surface has drifted and should route here instead.