@zalom/plastic 1.3.0 → 1.4.0

package/skills/tutorial/references/track-3-projects-and-roadmaps.md

@@ -56,16 +56,16 @@ in the global store.
 Type `/plastic-roadmap`.
 
 Teach the roadmap file shape exactly: a title and short meta header, a `## Goal` section in
-prose describing what "done" looks like for the whole batch, a `## Waves` section (an
-ordered list of groups of intents; intents inside one wave are safe to run in parallel,
-waves themselves run one after another), and an append-only, dated `## Log`. `INDEX.md`
+prose describing what "done" looks like for the whole batch, a `## Batches` section (an
+ordered list of groups of intents; intents inside one batch are safe to run in parallel,
+batches themselves run one after another), and an append-only, dated `## Log`. `INDEX.md`
 stays the single source of truth for each intent's status; the roadmap only mirrors it.
 
 Artifact: a new `roadmaps/<slug>.md` file, sitting next to the project's `INDEX.md`, listing
-the two or more intents from station 3 across one or more waves.
+the two or more intents from station 3 across one or more batches.
 
-Checkpoint: name which of the two intents from station 3 share a wave (so they run in
-parallel) and which one, if any, sits in a later wave (so it waits).
+Checkpoint: name which of the two intents from station 3 share a batch (so they run in
+parallel) and which one, if any, sits in a later batch (so it waits).
 
 ### 5. Drive delivery with /goal
 
@@ -74,18 +74,18 @@ and Claude keeps working, turn after turn, until a fast checker model confirms f
 Claude has actually reported that the condition holds; `/goal` never reads files on its own,
 so the condition has to name a check Claude's own output can prove.
 
-Turn the roadmap's `## Goal` and current `## Waves` into that condition, for example:
+Turn the roadmap's `## Goal` and current `## Batches` into that condition, for example:
 
-`/goal every intent in wave 1 of roadmaps/<slug>.md shows Completed in INDEX.md, and the test
+`/goal every intent in batch 1 of roadmaps/<slug>.md shows Completed in INDEX.md, and the test
 suite is green`
 
-Claude then works through the wave itself, one intent at a time, and stops on its own once the
+Claude then works through the batch itself, one intent at a time, and stops on its own once the
 checker agrees the condition holds. Run `/goal` with no argument at any point to see how long
 it has run and how many turns it has spent; run `/goal clear` to stop it before that.
 
 On a harness without `/goal`, just tell the agent to deliver the roadmap in auto mode instead.
 
-Checkpoint: point at the exact file (`roadmaps/<slug>.md`) whose `## Goal` and `## Waves`
+Checkpoint: point at the exact file (`roadmaps/<slug>.md`) whose `## Goal` and `## Batches`
 sections you turned into the condition above.
 
 ### 6. Merge discipline and releases

package/skills/update/SKILL.md

@@ -57,22 +57,35 @@ unavailable. The command prints the transition (`vX -> vY`) or "already up to da
 a post-update doctor summary, and records the move in the append-only
 `~/.plastic/versions.json` ledger.
 
-### Step 2: Ask the advisor question once, if unset (Claude Code only)
-
-If this update brought in the advisor feature and `advisor.claude.default` is still
-unset in `~/.plastic/config.yml`, ask the same question `plastic-install` asks on a
-fresh install, once, then never again (a key already set is respected, never re-asked):
-> "Which advisor should be the default?"
-> - **Faux Fable** (recommended): Opus 4.8 carrying the frontier reasoning
->   instructions. Much cheaper, available on any plan, reasons in the same
->   disciplined way.
-> - **Fable 5**: the frontier model itself. The strongest reasoning available,
->   billed through usage credits, so summon it for a few rounds and close it.
-
-Write the answer with `npx -y @zalom/plastic@<channel> install --claude --reinstall
---advisor faux` (or `--advisor real`). Non-interactive sessions skip the question; the
-`plastic-agent-advisor` skill's own routing falls back to `plastic-faux-advisor` at
-consult time, so nothing is silently broken by leaving the key unset.
+### Step 2: Relay any pending config question(s) the update printed
+
+If `update`'s own output (Step 1) printed a "Config question(s) introduced by
+this update" block, relay each question to the user exactly as printed
+(question, options, and the `write-config` command for each option). Do not
+invent or hardcode a specific question here: it comes from the CLI's fresh
+output (`config_asks.yml`, read by code that just synced from the new version),
+never from this skill file, which is always one release behind and cannot know
+what a future release will ask.
+
+Once the user picks an option, run the printed `write-config` command for that
+option, for example:
+
+```
+ruby ~/.plastic/scripts/write-config advisor.claude.default plastic-faux-advisor
+```
+
+If they say "not now" / want to keep the default, run the printed dismissal
+command instead, for example:
+
+```
+ruby ~/.plastic/scripts/write-config config_asks_dismissed --push advisor-default
+```
+
+If `update` printed nothing under that heading, skip this step silently - there
+is nothing pending. A question already answered or dismissed is never re-asked
+(both the CLI print and the doctor check verify this before showing anything),
+and a pending question missed here still shows up as a `config_asks` warn on
+the next `/plastic-doctor` run, so nothing is silently lost.
 
 ### Step 3: Relay the result, announce convention changes
 
@@ -98,6 +111,6 @@ report and offer to fix. If it already reads clean, do not re-run doctor.
 ### Step 5: Commit + clear update cache
 
 ```bash
-cd ~/.plastic && git add PLASTIC.md scripts/ AGENTS.md VERSION versions.json 2>/dev/null && git commit -m "chore: update Plastic to $(cat ~/.plastic/VERSION)" --allow-empty
+cd ~/.plastic && git add PLASTIC.md scripts/ AGENTS.md VERSION versions.json deprecations.yml config_asks.yml 2>/dev/null && git commit -m "chore: update Plastic to $(cat ~/.plastic/VERSION)" --allow-empty
 rm -f ~/.plastic/.cache/update-check.json
 ```

package/templates/roadmap.md

@@ -9,17 +9,17 @@ roadmap's goal is reached, move this file from `roadmaps/{slug}.md` to
 (a checkable prose condition — one or a few sentences a human or coordinator reads to decide the
 roadmap is done. Not an executable checker.)
 
-## Waves
-Entries in a wave are parallel-safe; waves run top to bottom. The checkbox is checked once an entry
-is delivered, unchecked otherwise; the trailing token after the em-dash is the precise mirrored
-status (queued | delivering | delivered | abandoned | blocked) from INDEX.md. INDEX always wins on
-any conflict between the checkbox/token here and INDEX's real status.
+## Batches
+Entries in a batch are parallel-safe; batches run top to bottom. The checkbox is checked once an
+entry is delivered, unchecked otherwise; the trailing token after the em-dash is the precise
+mirrored status (queued | delivering | delivered | abandoned | blocked) from INDEX.md. INDEX
+always wins on any conflict between the checkbox/token here and INDEX's real status.
 
-### Wave 1
+### Batch 1
 - [ ] <intent-id> <title> — queued
 - [ ] <intent-id> <title> — queued
 
-### Wave 2
+### Batch 2
 - [x] <intent-id> <title> — delivered
 
 ## Log
@@ -27,4 +27,4 @@ any conflict between the checkbox/token here and INDEX's real status.
 what shipped and its impact for a non-expert reader, no jargon or internal codenames, ending with a
 link to that entry-intent's `outcome.md`. Never restate outcome detail here; link to it instead.
 Newest at the bottom.)
-- 2026-01-01 00:00 UTC Shipped the first wave of this roadmap; see store/<intent-id>--<slug>/outcome.md.
+- 2026-01-01 00:00 UTC Shipped the first batch of this roadmap; see store/<intent-id>--<slug>/outcome.md.