@zalom/plastic 1.0.3 → 1.1.0

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/{continuing → intent-continuing}/SKILL.md

@@ -1,12 +1,12 @@
 ---
-name: plastic-continuing
-description: Use when the user says "continue", "resume", or "pick up where we left off", or when starting a new session. Continues work with the latest project context: lands on the right dashboard, then presents choices. 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).
+name: plastic-intent-continuing
+description: 'Use when the user says "continue", "resume", or "pick up where we left off", or when starting a new session. Continues work with the latest project context: lands on the right dashboard, then presents choices. 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
 
-`plastic-continuing` continues work. It presents the latest state via the dashboard and offers
+`plastic-intent-continuing` continues work. It presents the latest state via the dashboard and offers
 choices, then stops. It does NOT execute work autonomously (that is `plastic-auto`) and does
 NOT render the dashboard itself (it only invokes it).
 

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

@@ -1,51 +1,51 @@
 {
-  "skill_name": "plastic-continuing",
+  "skill_name": "plastic-intent-continuing",
   "notes": "Intent 36, updated for 36a (boot moved into hook-session-start; the skill is now work-continuation only). Scopes: description triggering (1-8) and behavior/convention compliance of the work-continuation skill (9-14). Triggering assertions follow the plastic-auto eval style (one subagent router per case). Behavior assertions are convention checks against the SKILL.md.",
   "results": {
     "triggering": { "cases": 8, "passed": 8, "run": "2026-06-16, one subagent per case" },
-    "behavior": { "cases": 6, "passed": 6, "evidence": "convention checks against skills/continuing/SKILL.md after the intent-36 rewrite; doctor --core verified at 0.07s with 9 liveness checks and full doctor unchanged at 30 checks" }
+    "behavior": { "cases": 6, "passed": 6, "evidence": "convention checks against skills/intent-continuing/SKILL.md after the intent-36 rewrite; doctor --core verified at 0.07s with 9 liveness checks and full doctor unchanged at 30 checks" }
   },
   "evals": [
     {
       "id": 1, "scope": "triggering", "set": "train",
       "prompt": "continue",
-      "expected_output": "Activates plastic-continuing (the bare 'continue' keyword is the documented trigger).",
+      "expected_output": "Activates plastic-intent-continuing (the bare 'continue' keyword is the documented trigger).",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic-continuing", "observed": "plastic-continuing", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
       ]
     },
     {
       "id": 2, "scope": "triggering", "set": "train",
       "prompt": "resume where we left off",
-      "expected_output": "Activates plastic-continuing.",
+      "expected_output": "Activates plastic-intent-continuing.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic-continuing", "observed": "plastic-continuing", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
       ]
     },
     {
       "id": 3, "scope": "triggering", "set": "validation",
       "prompt": "pick up where we left off in this project",
-      "expected_output": "Activates plastic-continuing.",
+      "expected_output": "Activates plastic-intent-continuing.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic-continuing", "observed": "plastic-continuing", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-continuing", "result": "pass" }
       ]
     },
     {
       "id": 4, "scope": "triggering", "set": "train",
       "prompt": "boot plastic and show me where things stand",
-      "expected_output": "Activates plastic-continuing (continuing work + presenting state is the skill's purpose; boot itself is hook-owned).",
+      "expected_output": "Activates plastic-intent-continuing (continuing work + presenting state is the skill's purpose; boot itself is hook-owned).",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE == plastic-continuing", "observed": "plastic-continuing", "result": "pass" }
+        { "type": "code", "check": "router CHOICE == plastic-intent-continuing", "observed": "plastic-intent-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-continuing for execution. Shares 'continue' but the autonomous-delivery intent routes to plastic-auto.",
+      "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" }
@@ -54,35 +54,35 @@
     {
       "id": 6, "scope": "triggering", "set": "validation",
       "prompt": "continue the for-loop to the next iteration in this function",
-      "expected_output": "Does NOT activate plastic-continuing. Near-miss: shares 'continue' but is a code-editing task.",
+      "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-continuing", "observed": "none", "result": "pass" }
+        { "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-continuing. Near-miss: shares 'resume' but is unrelated to Plastic sessions.",
+      "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-continuing", "observed": "none", "result": "pass" }
+        { "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": "May activate plastic-dashboard rather than plastic-continuing; an overview request without 'continue/resume' is a dashboard task.",
+      "expected_output": "May activate plastic-dashboard rather than plastic-intent-continuing; an overview request without 'continue/resume' is a dashboard task.",
       "files": [],
       "assertions": [
-        { "type": "code", "check": "router CHOICE != plastic-continuing", "observed": "plastic-dashboard", "result": "pass" }
+        { "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/continuing/SKILL.md"],
+      "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" }
       ]
@@ -91,7 +91,7 @@
       "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/continuing/SKILL.md"],
+      "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" }
       ]
@@ -100,7 +100,7 @@
       "id": 11, "scope": "behavior", "set": "train",
       "prompt": "Is dashboard selection project-aware?",
       "expected_output": "Project loaded -> `dashboard.rb project <slug>`; otherwise -> `dashboard.rb continue`. Skill only invokes, does not render.",
-      "files": ["skills/continuing/SKILL.md"],
+      "files": ["skills/intent-continuing/SKILL.md"],
       "assertions": [
         { "type": "convention", "check": "both dashboard invocations present and gated on project detection", "observed": "'dashboard.rb project <slug>' and 'dashboard.rb continue' in the 'Continue (present the dashboard)' section", "result": "pass" }
       ]
@@ -109,7 +109,7 @@
       "id": 12, "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/continuing/SKILL.md"],
+      "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" }
       ]
@@ -118,7 +118,7 @@
       "id": 13, "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/continuing/SKILL.md"],
+      "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" }
       ]
@@ -127,7 +127,7 @@
       "id": 14, "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/continuing/SKILL.md"],
+      "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" }
       ]
@@ -136,7 +136,7 @@
       "id": 15, "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/continuing/SKILL.md"],
+      "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" }
       ]

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.

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

@@ -0,0 +1,74 @@
+{
+  "skill_name": "plastic-intent-ending",
+  "notes": "Intent 161. Scopes: description triggering (3-6) and behavior (1-2: the two mandatory D6 cases). Case B graduates into test/end_intent_test.rb (test_done_bookend_lands_once_and_is_idempotent) per evaluating-skills conventions.",
+  "evals": [
+    {
+      "id": 1,
+      "scope": "behavior",
+      "set": "train",
+      "prompt": "checklist.md has one unchecked non-completion item. Try to complete the intent.",
+      "expected_output": "Defers to the existing Bridge.check_gate hard gate rather than writing outcome.md; tells the user to finish the checklist item first instead of fighting the deny.",
+      "files": [],
+      "assertions": [
+        { "type": "human", "check": "SKILL.md Step 0 states the gate blocks outcome.md while unchecked non-completion items remain, and instructs finishing the checklist rather than attempting the write", "result": "expect-pass" },
+        { "type": "code", "check": "Bridge.check_gate(intent_dir, 'outcome.md') returns a non-nil block reason when checklist.md has an unchecked '- [ ]' item (scripts/lib/bridge.rb)", "result": "pass" }
+      ]
+    },
+    {
+      "id": 2,
+      "scope": "behavior",
+      "set": "train",
+      "prompt": "Run the mechanical close (scripts/end-intent) for a delivered intent with a real outcome.md.",
+      "expected_output": "The savepoint Done bookend lands exactly once in savepoint.md, and a second run of the same command does not duplicate it (this is the regression the intent fixes: releasing used to skip this line entirely).",
+      "files": [],
+      "assertions": [
+        { "type": "human", "check": "SKILL.md Step 1-4 calls scripts/end-intent as one script instead of restating the outcome/INDEX/savepoint one-liners in prose", "result": "expect-pass" },
+        { "type": "code", "check": "test/end_intent_test.rb#test_done_bookend_lands_once_and_is_idempotent is green", "result": "pass" }
+      ]
+    },
+    {
+      "id": 3,
+      "scope": "triggering",
+      "set": "train",
+      "prompt": "Mark intent 87 done, it shipped.",
+      "expected_output": "Activates plastic-intent-ending to run the mechanical close (outcome.md, INDEX move, savepoint bookend, commit, disarm, reindex, report).",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-intent-ending", "result": "expect-pass" }
+      ]
+    },
+    {
+      "id": 4,
+      "scope": "triggering",
+      "set": "train",
+      "prompt": "This one's not worth finishing, abandon it and wrap this up.",
+      "expected_output": "Activates plastic-intent-ending (indirect trigger: 'wrap this up' names no lifecycle vocabulary directly). Abandoned runs the identical procedure, only outcome.md content and the INDEX section differ.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-intent-ending", "result": "expect-pass" }
+      ]
+    },
+    {
+      "id": 5,
+      "scope": "triggering",
+      "set": "validation",
+      "prompt": "Start work on intent 87.",
+      "expected_output": "Does NOT activate plastic-intent-ending; this is a boarding request (plastic-intent-starting), the opposite end of the lifecycle from a close.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE != plastic-intent-ending", "result": "expect-pass" }
+      ]
+    },
+    {
+      "id": 6,
+      "scope": "triggering",
+      "set": "validation",
+      "prompt": "Cut a release and tag it v1.2.0.",
+      "expected_output": "Does NOT activate plastic-intent-ending directly; activates plastic-releasing, which internally calls scripts/end-intent for the mechanical close as one of its own steps.",
+      "files": [],
+      "assertions": [
+        { "type": "code", "check": "router CHOICE == plastic-releasing", "result": "expect-pass" }
+      ]
+    }
+  ]
+}