@zalom/plastic 1.14.1 → 2.0.0-alpha.10

package/skills/doctor/SKILL.md

@@ -13,7 +13,7 @@ Doctor has three scopes. Pick the right one for the situation:
 | Scope | Flag | When it runs | States |
 |-------|------|--------------|--------|
 | Core check | `--core` | SessionStart hook (automatic), also available on demand | Binary: pass or error |
-| Store check | `--store [global\|<slug>]` | Dashboard load, `plastic-project-continuing` | Three-state: pass / warn / fail |
+| Store check | `--store [global\|<slug>]` | Dashboard load, the project route of `plastic-intent-continuing` | Three-state: pass / warn / fail |
 | Full check | (no flag) | After every update (automatic), or `/plastic-doctor` | Three-state: pass / warn / fail |
 
 ### `--core` (binary, operational-readiness only)
@@ -51,8 +51,12 @@ Each manifest maps a file path to its SHA256.
 
 Checks the operations Plastic itself depends on in one store: QMD search reachability (scoped
 to that store's own collection; global uses `plastic-global`, a project slug uses
-`plastic-<slug>`), sources/chain resolution, cross-store resolution, INDEX parsing, and links
-projection. A project slug also checks tool readiness (Serena, Enola): each is a pass whether
+`plastic-<slug>`), sources/chain resolution, cross-store resolution, INDEX parsing, links
+projection, done signals (including `backfilled_complete`: a terminal intent still missing a
+real spec.md, plan.md, or action file), and, for the global store only, the session ledger
+(`orphaned_session_tmp`: a `.tmp/<session>/` directory whose heartbeat is older than 24
+hours; `day_ledger_shape`: a `.sessions/` entry that is not a `YYYYMMDD` day directory with
+its `<day>.md`). A project slug also checks tool readiness (Serena, Enola): each is a pass whether
 present or absent, present naming it available, absent noting it as an optional integration
 never installed by doctor. Scope options:
 
@@ -86,10 +90,6 @@ per-project finding**; that is `--store <slug>`'s job (see above). This is what
 - When hooks aren't firing, skills aren't loading, or something seems broken
 - When the user says "check plastic", "diagnose", "what's wrong with plastic"
 
-Read `../plastic-conventions/references/gates-and-enforcement.md` for the transition-gate
-mechanics, the audited escape, and gate logging before diagnosing a stuck or misbehaving gate.
-This path resolves relative to this skill's own installed directory.
-
 ## Procedure
 
 ### Step 1: Run the diagnostic script
@@ -159,10 +159,13 @@ Use the `fix_hint` value to determine the correct action:
 | "Add missing entries to INDEX.md" | Add orphaned intents to the appropriate INDEX.md section |
 | "Remove stale references from INDEX.md" | Edit INDEX.md to remove ghost references |
 | "Inject the missing required frontmatter field(s)" | Edit the intent's `{ID}--{slug}.md` frontmatter to add the missing key (e.g. `chain: []`) without touching other keys |
-| "Run: provision-project-store {slug}" | Run `provision-project-store <slug>` (or invoke the `plastic-store-provisioning` skill) to create the missing store |
+| "Run: provision-project-store {slug}" | Run `provision-project-store <slug>` (see Provisioning a project store below) to create the missing store |
 | "Re-run installer" | Run `npx -y @zalom/plastic@<channel> install --claude` (or `--codex`/`--hermes`/`--all` for that agent; channel: -alpha->@alpha, -beta->@beta, else @latest) |
 | "Run the Plastic installer to bootstrap the store" | Run `npx -y @zalom/plastic@<channel> install --claude` (or `--codex`/`--hermes`/`--all`; channel: -alpha->@alpha, -beta->@beta, else @latest) to restore the global store's plastic_home directory or INDEX.md |
-| "Dispatch plastic-store-curating ... revisions.md ..." | Invoke the `plastic-store-curating` (or the agent) to relocate the flagged section or ref into the intent's `revisions.md` via move-and-record (one dated, `[rule: <tag>]`-tagged entry per item), per plastic-conventions > references/maintenance-and-revisions.md. For a missing required section, restore or reproject it instead. |
+| "Relocate ... revisions.md ..." | Relocate the flagged section or ref into the intent's `revisions.md` via move-and-record (one dated, `[rule: <tag>]`-tagged entry per item), per plastic-conventions > references/maintenance-and-revisions.md. For a missing required section, restore or reproject it instead. |
+| "Write the missing documents from the record via `scaffold-intent backfill ...`" | Run `ruby ~/.plastic/scripts/scaffold-intent backfill --store <store> --id <id> --disposition <delivered\|abandoned>` for each listed intent; it fills only missing or placeholder files and never touches real content |
+| "Remove each listed .tmp/<session>/ directory after confirming that session is gone" | For each listed directory, confirm no live session uses it (a live session rewrites its heartbeat on every prompt and edit), then remove that directory by hand; never remove an unlisted one |
+| "For a day directory missing its <day>.md, run `file-session-intent --day <day> ...`" | Run `ruby ~/.plastic/scripts/file-session-intent --day <day> --carry-to <today> --store <store>` for the named day; rename or remove an entry that is not a `YYYYMMDD` day directory |
 | "Run scripts/project-links ... PRESERVES ... --drop-unbacked-links" | Run `ruby ~/.plastic/scripts/maintenance-run --tool project-links --intent <id> --apply` for the one flagged id (never run bare `project-links` against a real store outside the rare owner-approved batch exception, D2) |
 
 For fixes the agent cannot handle automatically, explain what the user needs
@@ -247,6 +250,50 @@ removes exactly the dead rows through the same writer and commit, but holds back
 intent dir carries a fresh lock or has not gone terminal yet (nothing to suppress there yet),
 naming both as kept.
 
-## References
+## Locks (auto teams only)
+
+Locks exist for auto teams: a `delivery.lock` file in the intent directory names the owning
+session, and the `record` hook refreshes its mtime on every edit (the lease heartbeat; stale
+means older than the TTL). Direct work takes no lock. When a lock reads held by a session
+that is gone, when work resumes after a crash, reboot, or `/tmp` wipe, or when the user says
+"fix the lock", "who holds the lock", or "reclaim the lock", use the CLI (intent 304 folded
+the former locking skill here):
+
+| Verb | What it does | When |
+|---|---|---|
+| `who` | Owner, heartbeat, claims, delegates, from durable files only | Safe inspection; needs `--intent-dir` |
+| `status` | Lock file, freshness, the derived worktree, whether this session's pointer names the intent, claims | Always safe; run first |
+| `fix` | Idempotent repair from disk truth for this session; never touches a fresh foreign lock | Interrupted work, corrupt state, `/tmp` wiped |
+| `release` | The owner clears the lock | Ending or abandoning an auto delivery |
+| `reclaim` | Explicit takeover of a stale lock; appends an audit line to `savepoint.md` | The owner is gone and the lease expired |
+| `delegate` | The owner registers a subagent session, or marks it `finished` or `failed` | Auto-team orchestration |
+
+```
+ruby ~/.plastic/scripts/plastic-lock status --intent-dir <store>/<id>--<slug>
+ruby ~/.plastic/scripts/plastic-lock who --intent-dir <store>/<id>--<slug>
+ruby ~/.plastic/scripts/plastic-lock fix --intent-dir <store>/<id>--<slug>
+ruby ~/.plastic/scripts/plastic-lock reclaim --intent-dir <store>/<id>--<slug>
+```
+
+`fix` exits non-zero when another session holds a fresh lock: back off, `status` shows the
+owner. `reclaim` refuses a fresh lock; every takeover is audited. The lock file's mtime is the
+sole freshness truth. Never delete a lock file by hand. Read
+`../plastic-conventions/references/locks-and-worktrees.md` when a lock question goes beyond
+these verbs (claims, worktrees, the station ledger).
+
+## Provisioning a project store
+
+When a project is registered in `~/.plastic/projects.yml` but has no store on disk (doctor
+reports `project_store_dir`), provision it (intent 304 folded the former provisioning skill
+here). The slug is the project's key under `projects`; an unregistered slug exits non-zero and
+creates nothing, and this procedure never edits `projects.yml`.
+
+```bash
+ruby ~/.plastic/scripts/provision-project-store <slug>
+ruby ~/.plastic/scripts/qmd-sync register --store ~/.plastic/projects/<slug>/store
+```
 
-- Read `references/gates-stuck-detection.md` for the full gate enforcement table, bridge file pattern, and the recorded stuck-detection signals when diagnosing gate failures or stuck agents
+The provisioner is pure filesystem and idempotent: it creates
+`~/.plastic/projects/<slug>/store/` with `.gitkeep`, writes `INDEX.md` and `project.yml` only
+when missing, and never clobbers. The QMD registration is a separate, optional step that
+no-ops when QMD is absent. New projects are provisioned by `plastic-project-creating`, not here.

package/skills/doctor/report.md

@@ -18,6 +18,8 @@
        core_files         -> "Core Files"
        project_stores     -> "Project Stores"
        deprecations       -> "Deprecations"
+       done_signals       -> "Done Signals"
+       session_ledger     -> "Session Ledger" (global store only)
   4. For each check within a category, emit one line with the status icon
      and the check message. If the check has non-empty details, list them
      as indented sub-items.
@@ -59,7 +61,7 @@ Checked at: {{timestamp}}
 - [PASS] Claude Code adapter registered
 - [FAIL] 2 hook scripts not executable
   - ~/.claude/hooks/plastic-session-start
-  - ~/.claude/hooks/plastic-gate-check
+  - ~/.claude/hooks/plastic-record
 
 <!-- =====================================================================
   Repeat the above pattern for each category found in the checks array.

package/skills/install/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plastic-install
-description: 'Use when initializing Plastic globally (~/.plastic/) or locally in a project, or to re-install/repair a broken installation. Accepts channel flags (--alpha, --beta, --latest) to select release channel. First install defaults to --latest (stable); reinstalls match the already-installed channel. Global install is recommended: it creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.'
+description: 'Use when initializing Plastic globally (~/.plastic/) or locally in a project, or to re-install/repair a broken installation. The package pin selects the channel (@latest, @beta, @alpha; the channel flags were removed in 2.0). First install defaults to @latest (stable); reinstalls match the already-installed channel. Global install is recommended: it creates the global intent store as a git-backed repository. Local install creates .plastic/ in the current project for testing.'
 user-invocable: true
 ---
 
@@ -16,8 +16,10 @@ user-invocable: true
 
 If Plastic is installed, derive `<channel>` from `~/.plastic/VERSION`: a version containing
 `-alpha` means `@alpha`, `-beta` means `@beta`, otherwise `@latest`. If not installed
-(first install), default to `@latest`. The user can always override with
-`--alpha` / `--beta` / `--latest`.
+(first install), default to `@latest`. To change channel, pin the package instead of
+passing a flag: `npx -y @zalom/plastic@alpha install --claude` (or a version such as
+`@2.0.0-alpha.1`); the `--alpha`, `--beta`, and `--latest` flags were removed in 2.0
+(intent 310) because they never selected a package.
 
 ## Re-install / repair
 
@@ -31,13 +33,13 @@ npx -y @zalom/plastic@<channel> install --reinstall --claude
 
 Then **run `/plastic-doctor`** and report what it found.
 
-## Channel Flags
+## Channels
 
-| Flag | Behavior |
-|------|----------|
-| `--latest` | Install from the stable channel (default on a first install) |
-| `--beta` | Install from the beta channel |
-| `--alpha` | Install from the alpha channel |
+| Package | Channel |
+|---------|---------|
+| `@zalom/plastic@latest` | stable (default on a first install) |
+| `@zalom/plastic@beta` | beta |
+| `@zalom/plastic@alpha` | alpha; `npx -y @zalom/plastic@alpha install --claude` is the 2.0 alpha path |
 
 When invoked from within Claude Code (re-install or channel switch), the skill
 runs the appropriate npx command:

package/skills/intent-continuing/SKILL.md

@@ -1,103 +1,154 @@
 ---
 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).
+  The front door for resuming work. Use when the user says "continue", "resume", "pick up
+  where we left off", "where was I", "what should I work on", names a specific intent to
+  resume (by id or description, or `--intent {id}`), or names a roadmap or delivery batch to
+  resume (`--roadmap {slug}`, "where is the roadmap", "where did that batch land"). Presents
+  state and resumes at the last delivered stage; it never asks auto or guided, never boots
+  (the SessionStart hook owns boot), and never drives work autonomously (plastic-auto does).
+  Absorbs the former continuing, project-continuing, and roadmap-continuing skills and the
+  read half of the former intent-starting skill (intent 304).
 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.
-
-Read `../plastic-conventions/references/lifecycle-and-savepoints.md` for the subagent
-report-home contract behind the resume below. This path resolves relative to this skill's own
-installed directory.
-
-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:
+# Continuing: the front door for resuming work
+
+One skill with three routes. It reads state and presents it; the work itself continues in
+whatever mode the session is in (direct by default, `plastic-auto` when the owner says auto).
+There is no lock to take and no mode to ask here: locks exist only for auto teams, and the
+mode is the owner's word, not a question this skill puts.
+
+**Boot is not this skill's job.** `hook-session-start` runs on every session start: the core
+health check (`doctor --core`), `PLASTIC.md` and store or project state, the
+`Plastic Core loaded - v{version}` banner. By the time this skill runs, core is loaded and
+healthy or the banner already warned.
+
+## Route
+
+| Args or context | Route |
+|---|---|
+| `--intent {id}`, or the user names one specific intent to resume (by id or description) | Intent route (below) |
+| `--roadmap {slug}`, or the user asks to continue or resume a roadmap or delivery batch | Roadmap route (below) |
+| bare "continue", "resume", "what should I work on", or no target (the default) | Project route (below) |
+
+State the chosen route in one line before doing anything ("Landing on the project board: no
+specific intent or roadmap named.").
+
+## Determine store
+
+1. A project store under `~/.plastic/projects/{slug}/` whose registered path in
+   `~/.plastic/projects.yml` matches the working directory means project mode; the
+   SessionStart hook already detected this, the slug scopes the reads below.
+2. Otherwise the global store, `~/.plastic/store/`.
+3. Neither exists: announce "No Plastic store found. Run /plastic-install." and stop.
+
+## Project route: land on the board
+
+Land on the Markdown board through the `plastic-dashboard` skill; rendering belongs there.
+Run the data payload and fill the matching template:
+- project loaded: `ruby ~/.plastic/scripts/dashboard.rb project <slug> --data`
+- otherwise (the global fallback): `ruby ~/.plastic/scripts/dashboard.rb continue --data`
+
+Fill the template from `plastic-dashboard`'s `templates/` and present the filled Markdown in
+your reply, every time: tool-call stdout and hook context are invisible to the user. Read
+`references/board-fill.md` for the fill mechanics and the store-health line when filling the
+board. The board load runs the scoped store check (`doctor --store <scope>`); its result
+arrives in the payload as `store_health` and is shown as one line of data, never a blocker.
+
+Priority order on the board: active intents first, then project context (governing plus
+tactical intents in a registered project), then stale future intents for triage, then fresh
+future intents as next work. A future intent older than `stale_threshold_days` (default 3) is
+surfaced for triage without action: activate, abandon, or leave. Activating moves it to
+`## Active` in `INDEX.md` and auto-commits. The board's ranked next-work order is computed by
+`dashboard.rb`; cite the rule names only (Effort, Value, Flags, Override, Caps) and read
+`plastic-dashboard`'s `references/classification.md` for their definitions.
+
+When the tier root (the directory holding `INDEX.md`) has a mid-flight roadmap
+(`ruby ~/.plastic/scripts/roadmap-next --roadmaps-dir <root>/roadmaps` reports a `state`
+other than `none`), say so in one line and offer the roadmap route; the board still presents
+project state and stops.
+
+Then stop: "here is the state, what next?". Do not start executing work. When the user names
+an intent, take the intent route.
+
+## Intent route: resume one intent from its ledger
+
+QMD-first when the intent is named by description: run
+`ruby ~/.plastic/scripts/qmd-sync search "<terms>"` to find the candidate, then open the
+authoritative intent file. The command is a no-op when QMD is absent; fall back to
+`INDEX.md`.
+
+If the intent is terminal (`## Completed` or `## Abandoned` in `INDEX.md`): print the
+intent screen (Status shows the terminal section, Next is empty), summarize its
+`outcome.md`, and ask what is next; never reopen it.
+
+For a live intent's directory:
+
+1. **Read `savepoint.md` first.** It is a deterministic, append-only ledger, one line per
+   event, newest at the bottom: `{utc-iso8601}  {Stage}  {milestone}`. Classify the stage
+   from the last line alone (the table in `references/boarding-matrix.md`, read when
+   classifying), then verify only that line's artifact is real (sentinel-aware:
+   `Savepoint.stage_file_present?`). Do not re-probe every lifecycle file.
+2. **Stale ledger.** When the last line disagrees with the files on disk, rebuild the ledger from
+   disk and note the correction. A rebuilt ledger is the file-landing skeleton, which still
+   pins the stage:
    ```bash
-   ruby -r ~/.plastic/scripts/lib/bridge -e 'Bridge.rebuild_savepoint("<intent_dir>")'
+   ruby -r ~/.plastic/scripts/lib/savepoint -e 'Savepoint.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]
+3. **Read the hand-off.** The newest `~/.plastic/store/.sessions/<day>/handoff--*.md` (today,
+   else the newest prior day) is the prior session's own account of where things stand; read
+   it after the ledger, never instead of it.
+4. **Derive the next step:** the first unchecked item in `checklist.md` when it exists, else
+   the next thing the stage needs (see the matrix). The newest `## Insights` entry supplies
+   the human-readable context; an entry marked `(autonomous)` means an auto team was
+   delivering it, so say so and offer to hand back to `plastic-auto`.
+5. **Print the report screen as the first thing in the reply, then continue at that stage.**
+   The screen must open the message with nothing before it. On Claude Code, a fail-open
+   `MessageDisplay` hook recognizes a reply that opens this way and substitutes a styled ANSI
+   rendering for it there; the transcript and every other harness keep exactly this plain
+   form. For "where are we" on one named intent, run
+   `ruby ~/.plastic/scripts/report-screen state <intent_dir>` and print its output as it is:
+   the title, the field table, the `Changed` row, and the Steps table come from the record,
+   never by eye. For "where are we" with no intent named, run
+   `ruby ~/.plastic/scripts/report-screen state --all <store_root>` for the roster across every
+   in-delivery intent. Route "why did X take so long" to
+   `ruby ~/.plastic/scripts/report-screen delay <intent_dir>` instead - every verb prints the
+   same plain screen on any harness, painted only where the harness supports it, with no
+   branching on harness name. Under the `state` screen
+   write **What this means** as two to four bullets in plain words (what the intent is for,
+   what has landed, what is left, any defect named by step), then close with **needs input:**
+   naming the first open step. Then continue the work in the
+   session's current mode. In auto mode the running team already holds the delivery lock; if a
+   lock is held by a session that is gone, the `plastic-doctor` skill's lock section repairs or
+   reclaims it.
+
+## Roadmap route: resume the mid-flight roadmap
+
+1. Resolve the tier root (project or global) and run the shared reader in which mode:
+   ```bash
+   ruby ~/.plastic/scripts/roadmap-next --roadmaps-dir <root>/roadmaps --which
    ```
-   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.
+   Read `state` and the winning `roadmap`. A `tie` lists `tie_candidates` to present side by
+   side and let the user pick; never pick silently. The reader ranks liveness the way
+   `references/liveness-ranking.md` describes (read it when a ranking needs explaining): a
+   `delivering` or `blocked` entry wins, else the newest ledger or `## Log` timestamp.
+   `roadmaps/<slug>.savepoint.md` is a derived signal read here, never a status field;
+   `INDEX.md` stays the sole status writer.
+2. **Present state:** the roadmap's `## Goal`, the current batch with each entry's mirrored
+   status, the ledger's newest line beside the newest `## Log` line. Read
+   `../plastic-conventions/references/roadmaps.md` for the file format and the status-mirror
+   rule when a roadmap file needs interpreting.
+3. Then continue with the next dispatchable entry in the session's mode: direct work on it,
+   or `plastic-auto` when the owner says auto. The coordinator that drives a batch appends
+   to `roadmaps/<slug>.savepoint.md` at its dispatch, merge, park, and handoff points with
+   `ruby ~/.plastic/scripts/roadmap-savepoint append`; this skill only reads it.
 
 ## References
 
-- Read `references/context-management.md` for the save/continue protocol and for
-  debugging the resume flow.
+| Trigger | Read |
+|---|---|
+| Filling the board on the project route | `references/board-fill.md` |
+| Classifying the stage from the ledger's last line | `references/boarding-matrix.md` |
+| Explaining why one roadmap ranked above another | `references/liveness-ranking.md` |
+| Saving or restoring context across a long session, or debugging a resume | `references/context-management.md` |

package/skills/intent-continuing/references/boarding-matrix.md

@@ -0,0 +1,34 @@
+# Boarding matrix: which stage a resume lands at
+
+The stage is derived from `savepoint.md`'s last line plus the real artifacts on disk.
+Classify from the last line alone, then verify only that line's artifact is real
+(sentinel-aware). When the ledger is stale, rebuild it from disk and note it.
+
+| savepoint last line | latest delivered | lands at | continue with |
+|---|---|---|---|
+| `What  {id}--{slug}.md` (born) | What | **Why** | the thinking conversation (`plastic-intent-speccing`) or direct work |
+| `Why  started` (spec still sentinel) | What | **Why** | continue the conversation; rulings land as insights |
+| `Why  spec.md created` | Why | **How** | the action files, `plan.md`, `checklist.md` |
+| `How  started` / `How  plan.md created` | (How in progress) | **How** | finish `plan.md` and `checklist.md` |
+| `How  checklist.md created` / `Exec  started` | How | **Exec** | do the work, check off the checklist |
+| `Exec  outcome.md created` | Exec | **ready to complete** | the ending procedure (`plastic-intent-ending`) |
+| `Done  delivered` / `Done  abandoned` | terminal | **report only** | immutable; ask what is next |
+
+## Per-stage behaviour (what "continue" means)
+
+- **Why**: continue the conversation, or run the work directly when the request is already
+  clear; every ruling is recorded as it lands.
+- **How**: write or finish the action files, `plan.md`, and `checklist.md`.
+- **Exec**: verify what is delivered, then continue (or restart) the delivery or research.
+  The first unchecked `checklist.md` item is the next step; the newest `## Insights` entry
+  supplies the context.
+- **ready to complete**: `outcome.md` is real; run the ending procedure.
+- **Done**: terminal. Report the outcome, ask what is next. Never reopen; `INDEX.md` is
+  authoritative.
+
+## Notes
+
+- A Plastic 1.x ledger may carry a `Tier  <letter>` line under the `Why  spec.md created` line
+  (the intent tier was removed in 2.0, intent 304). It is inert: skip it when classifying.
+- An `## Insights` entry marked `(autonomous)` means an auto team was delivering the intent;
+  say so and offer to hand back to `plastic-auto`.

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

@@ -19,10 +19,10 @@ step looks stale):
    (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>")'`
+3. If the two disagree, the ledger is stale: rebuild it rather than hand-editing:
+   `ruby -r ~/.plastic/scripts/lib/savepoint -e 'Savepoint.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.
+`plastic-intent-continuing`; this file no longer duplicates it.

package/skills/intent-creating/SKILL.md

@@ -12,7 +12,7 @@ user-invocable: true
 - User explicitly says "new intent" or "create intent"
 - An agent discovers work needed during implementation
 
-## Determine Tier
+## Determine the store
 
 **Global intent** (strategic): created when working outside a registered project, or when the user expresses a high-level goal. Stored in `~/.plastic/store/`.
 
@@ -79,7 +79,7 @@ rule and the tool.
 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-intent-linking` skill and `scripts/link-suggest`.
+`scripts/link-suggest` and `scripts/project-links`.
 
 Read `../plastic-conventions/references/knowledge-graph.md` for the full linking doctrine: the
 tiers of influence, sources versus chain, and how the `## Links` projection is derived. This path

package/skills/intent-creating/references/lifecycle.md

@@ -78,4 +78,4 @@ State is derived from what exists, not from what's declared.
 
 The intent file is born complete with all five sanctioned `##` sections; the lifecycle files (`spec.md`/`plan.md`/`checklist.md`/`outcome.md`) are sentinel placeholders that read as "stage not reached" until an agent fills them and deletes the `<!-- plastic:placeholder -->` first line.
 
-Always scaffold through `new-intent` (or this skill). Never hand-author intent files: the write-time create gate blocks an incomplete or malformed intent file, and hand-authoring is the bypass this contract is designed to remove.
+Always scaffold through `new-intent` (or this skill). Never hand-author intent files: `new-intent` validates the file it writes (`scripts/validate-intent`) and `end-intent` checks it again at close, and hand-authoring is the bypass this contract is designed to remove.