@zalom/plastic 1.1.0 → 1.1.2

package/skills/roadmap-continuing/references/liveness-ranking.md

@@ -0,0 +1,56 @@
+# Liveness Ranking (read time, no new field)
+
+Depth reference for "Find the mid-flight roadmap" in `SKILL.md`. This is the full algorithm the
+body summarizes. Since intent 148, this algorithm is IMPLEMENTED in
+`scripts/lib/roadmap_queue.rb` behind the `scripts/roadmap-next` CLI; it is no longer a by-eye
+procedure. This page documents what that reader does, and is the specification the reader
+satisfies.
+
+## Why read-time, not a stored field
+
+INDEX.md stays the sole writer of intent status; the roadmap file mirrors it (see
+`plastic-roadmap`'s `references/file-format.md`). Adding a "mid-flight" flag to the roadmap
+file or to INDEX.md would create a second thing to keep in sync for a question that is cheap to
+answer by reading what is already there. So liveness is computed fresh, every call, from the
+tier's live `roadmaps/*.md` files (excluding `roadmaps/archived/`), by `RoadmapQueue` (intent
+148) rather than by eye.
+
+## The algorithm
+
+1. **Enumerate.** List every `roadmaps/*.md` at the tier (project or global), skipping
+   `roadmaps/archived/`.
+2. **Delivering/blocked wins outright.** If any candidate roadmap has at least one `## Waves`
+   entry whose mirrored status token is `delivering` or `blocked`, it is in flight right now.
+   That candidate wins the ranking immediately; skip the rest of the ranking for it.
+3. **Otherwise, newest `## Log` entry wins.** Among the remaining candidates (none have a
+   `delivering`/`blocked` entry), read each file's last `## Log` line (append-only, newest at
+   the bottom) and rank by that line's `YYYY-MM-DD HH:MM UTC` timestamp. The most recent wins.
+   When a candidate's paired `roadmaps/<slug>.savepoint.md` (intent 134) is present, its last
+   line is a cheaper, machine-timestamped read of the same fact (the ledger is derived from `##
+   Log`, so the two should already agree); reading it first is an optimization, not a second
+   source of truth, so a missing or stale ledger never blocks falling back to `## Log` itself.
+4. **Genuine tie -> present, do not silently pick.** If two or more candidates are equally live
+   (for example two roadmaps both idle with `## Log` entries on the same timestamp, or two both
+   showing `delivering` entries with no other signal to separate them), do not choose for the
+   user. Present both/all tied candidates' state side by side, then let the single "auto or
+   guided?" ask (asked once regardless of how many candidates were presented) double as the
+   resolution: the user's answer implicitly picks by naming which roadmap to continue, or the
+   agent asks a short one-line disambiguation immediately before that same single ask, never a
+   second separate prompt.
+
+## What this closes
+
+Before this skill existed, nothing resumed a mid-flight roadmap automatically. The `171`
+(consistency-dividend) roadmap handoff had to be resumed by hand: a free-prose "SESSION
+HANDOFF" note written into `171`'s own `## Insights`, because nothing read `## Waves` +
+`## Log` and reconstructed where the batch stood. This ranking, now a deterministic reader
+rather than a by-eye judgment, is the mechanism that replaces that hand-carried note.
+
+## Grammar pointer (do not duplicate)
+
+The roadmap file's four sections, entry line shape, and status vocabulary
+(`queued|delivering|delivered|abandoned|blocked`) are owned by `plastic-roadmap`:
+`skills/roadmap/references/file-format.md` for the shape, and
+`skills/roadmap/references/operations.md#read--consume` for how a reader (human or
+coordinator) is meant to walk `## Waves` and `## Log`. This page assumes that grammar and adds
+only the liveness-ranking judgment on top of it.

package/skills/skill-evaluating/evals/evals.json

@@ -1,5 +1,5 @@
 {
-  "skill_name": "skill-evaluating",
+  "skill_name": "plastic-skill-evaluating",
   "evals": [
     {
       "id": 1,

package/skills/tutorial/references/track-1-guided.md

@@ -71,10 +71,11 @@ an answer given in station 3.
 
 Type `/plastic-intent-planning`.
 
-Artifact: `plan.md` and `checklist.md`. At the S tier used here, `actions/` stays empty and
-the task rationale lives inline in `plan.md` instead of separate action files; only the L
-tier (many independent tasks, dispatched in parallel) gets one `actions/ACTION_N.md` file
-per task. `checklist.md` follows a fixed form: tasks start under `## In Progress`, move to
+Artifact: `plan.md`, `checklist.md`, and at least one real `actions/ACTION_N.md`. At the S
+tier used here, the planner consolidates the whole delivery into a single
+`actions/ACTION_1.md` (the ordered steps plus the exact changes); the L tier (many
+independent tasks, dispatched in parallel) instead gets one `actions/ACTION_N.md` file per
+task. `checklist.md` follows a fixed form: tasks start under `## In Progress`, move to
 `## Completed` as they land, and a `## Session Log` table records what happened each session.
 A task that depends on an owner decision landing first (a destructive step, a structural
 ruling) gets an `[ORCHESTRATOR]` prefix and blocks every other item until that decision is

package/skills/tutorial/references/track-2-auto.md

@@ -72,7 +72,7 @@ line.
 
 ### 5. Continue and where-was-I after time away
 
-Type `/plastic-intent-continuing`.
+Type `/plastic-continuing`.
 
 Artifact: the current state, presented and then the session stops. If a specific intent is
 named, the agent reads its stage and savepoint and resumes exactly there, rather than

package/skills/uninstall/SKILL.md

@@ -14,7 +14,7 @@ underlying uninstaller and adds reporting + verification.
 
 If Plastic is installed, derive `<channel>` from `~/.plastic/VERSION`: a version containing
 `-alpha` means `@alpha`, `-beta` means `@beta`, otherwise `@latest`. If not installed,
-default to `@beta`. The user can always override with `--alpha` / `--beta` / `--latest`.
+default to `@latest`. The user can always override with `--alpha` / `--beta` / `--latest`.
 
 ## Procedure
 
@@ -74,5 +74,5 @@ Delete it too?
 ```
 
 - **Keep:** "Your data is at ~/.plastic/. Re-install anytime with
-  `npx -y @zalom/plastic@beta install --claude` (or your channel)."
+  `npx -y @zalom/plastic@latest install --claude` (or your channel)."
 - **Delete:** run `rm -rf ~/.plastic/` and confirm.

package/skills/update/SKILL.md

@@ -22,7 +22,7 @@ clean no-op. You do not compute the target yourself, the script does.
 
 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 `@beta`. The user can always override with
+(first install), default to `@latest`. The user can always override with
 `--alpha` / `--beta` / `--latest`.
 
 ## Flags
@@ -40,7 +40,7 @@ confirmed. To roll **back** to a previously-installed version, use `plastic-roll
 ## Prerequisites
 
 Plastic must be installed (`~/.plastic/VERSION` present). If not, run `plastic-install`
-first (or `npx -y @zalom/plastic@beta install --claude` directly).
+first (or `npx -y @zalom/plastic@latest install --claude` directly).
 
 ## Procedure
 

package/templates/config.yml

@@ -14,7 +14,8 @@ architect:
 
 # Per-agent model override (intent 116). Uncomment and set to a Claude Code
 # alias (opus, sonnet, haiku) to override the shipped tier for one agent. With
-# no entry, the shipped default applies. Never resolves to Fable.
+# no entry, the shipped default applies and never resolves to Fable; naming
+# Fable here is an explicit, sanctioned override, honored as written.
 # agents:
 #   models:
 #     plastic-executor: sonnet

package/templates/index.md

@@ -1,13 +1,16 @@
 # Index
 
 ## Active
+<!-- Line shape: `- [ID — Title](path)`. The em-dash (U+2014, not a plain hyphen)
+     between id and title is load-bearing: Bridge.intent_active? matches only that
+     shape, and a plain hyphen there fails the lock gate open (see docs/internals.md). -->
 (no active intents)
 
 ## Future
 (no future intents)
 
 ## Clusters
-(clusters emerge as intents accumulate — add headings when 3+ intents share a topic)
+(clusters emerge as intents accumulate; add headings when 3+ intents share a topic)
 
 ## Completed
 (links preserved, never deleted)