@zalom/plastic 2.0.0-alpha.27 → 2.0.0-alpha.28

package/skills/tutorial/evals/evals.json

@@ -1,186 +0,0 @@
-{
-  "skill_name": "plastic-tutorial",
-  "notes": "Intent 166, Phase 1. Scopes: triggering (1-6, should and should-not with near-misses) and track routing (7-10, one case per track plus a direct-menu case). plastic-tutorial is a natural-language guided command with no backing Ruby test, so every assertion carries result: expect-pass pending a real observed run, per the intent-speccing evals.json convention. Phase 2 (post-164) can tighten these into observed pass/fail after a paired run.",
-  "evals": [
-    {
-      "id": 1,
-      "scope": "triggering",
-      "set": "train",
-      "prompt": "I want a tutorial on how Plastic works.",
-      "expected_output": "Activates plastic-tutorial and offers the three-track menu.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE == plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 2,
-      "scope": "triggering",
-      "set": "train",
-      "prompt": "Teach me Plastic from scratch.",
-      "expected_output": "Activates plastic-tutorial and offers the three-track menu.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE == plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 3,
-      "scope": "triggering",
-      "set": "train",
-      "prompt": "Walk me through Plastic before I try it on my real project.",
-      "expected_output": "Activates plastic-tutorial and offers the three-track menu.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE == plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 4,
-      "scope": "triggering",
-      "set": "validation",
-      "prompt": "How do I use Plastic day to day?",
-      "expected_output": "Activates plastic-tutorial and offers the three-track menu.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE == plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 5,
-      "scope": "triggering",
-      "set": "validation",
-      "prompt": "I have never touched this tool before. What can it actually do for me before I commit real work to it?",
-      "expected_output": "Activates plastic-tutorial; an indirect trigger that names neither the skill nor the word tutorial.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE == plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 6,
-      "scope": "triggering",
-      "set": "train",
-      "prompt": "Create an intent for adding a search feature.",
-      "expected_output": "Does NOT activate plastic-tutorial; activates plastic-intent-creating (a near-miss that shares the word intent but starts real work, not a walkthrough).",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE != plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 7,
-      "scope": "triggering",
-      "set": "validation",
-      "prompt": "Just run the whole thing for me, I do not want to steer any of it.",
-      "expected_output": "Does NOT activate plastic-tutorial; activates plastic-auto (a near-miss that describes autonomous delivery of real work, not a walkthrough of how auto works).",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "router CHOICE != plastic-tutorial",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 8,
-      "scope": "track-routing",
-      "set": "train",
-      "prompt": "Inside the tutorial menu: show me auto mode.",
-      "expected_output": "Routes to track 2 (references/track-2-auto.md), the auto handover track.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "TRACK == track-2-auto",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 9,
-      "scope": "track-routing",
-      "set": "train",
-      "prompt": "Inside the tutorial menu: I want a roadmap.",
-      "expected_output": "Routes to track 3 (references/track-3-projects-and-roadmaps.md), the projects and roadmaps track.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "TRACK == track-3-projects-and-roadmaps",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 10,
-      "scope": "track-routing",
-      "set": "validation",
-      "prompt": "Inside the tutorial menu: start a project.",
-      "expected_output": "Routes to track 3 (references/track-3-projects-and-roadmaps.md), the projects and roadmaps track.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "TRACK == track-3-projects-and-roadmaps",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 11,
-      "scope": "track-routing",
-      "set": "validation",
-      "prompt": "Walk me through my first intent, one stage at a time.",
-      "expected_output": "Routes to track 1 (references/track-1-guided.md), the guided delivery track.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "code",
-          "check": "TRACK == track-1-guided",
-          "result": "expect-pass"
-        }
-      ]
-    },
-    {
-      "id": 12,
-      "scope": "track-routing",
-      "set": "train",
-      "prompt": "Tutorial. (No further detail given.)",
-      "expected_output": "Activates plastic-tutorial and presents the three-track menu itself, since no track was named; this is the one case where the menu is the expected output rather than a routed track.",
-      "files": [],
-      "assertions": [
-        {
-          "type": "human",
-          "check": "the reply shows the three-track menu (guided, auto, projects and roadmaps) and does not jump into any one track uninvited",
-          "result": "expect-pass"
-        }
-      ]
-    }
-  ]
-}

package/skills/uninstall/SKILL.md

@@ -1,75 +0,0 @@
----
-name: plastic-uninstall
-description: Use when the user wants to remove Plastic from an agent. Runs the manifest-driven uninstaller (removes skills, hooks, statusline, and any legacy plugin layout), reports exactly what was removed and what was left behind, then gives verification steps. The intent store always stays.
-user-invocable: true
----
-
-# Uninstall Plastic
-
-The installer tracks every file it writes in a manifest, so uninstall is exact and
-leaves no orphans. Prefer running it through the CLI; this skill wraps the same
-underlying uninstaller and adds reporting + verification.
-
-## Channel rule
-
-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 `@latest`. The user can always override with `--alpha` / `--beta` / `--latest`.
-
-## Procedure
-
-### Step 1: Run the uninstaller
-
-```bash
-npx -y @zalom/plastic@<channel> uninstall --claude
-```
-
-(Use `--codex` / `--hermes` / `--all` to target other agents. `bunx -y @zalom/plastic@<channel> uninstall --claude` works too.)
-
-This removes, for the targeted agent:
-- all `~/.claude/skills/plastic-*/` skills
-- all `~/.claude/hooks/plastic-*` hooks (and restores any saved original statusline)
-- the `~/.claude/plastic/` state dir + manifest
-- any **legacy** plugin layout: `plugins/marketplaces/plastic`, `plugins/cache/plastic`,
-  the old nested `skills/plastic/`, and the `plastic@plastic` /
-  `extraKnownMarketplaces.plastic` / `known_marketplaces.json` registrations
-
-### Step 2: Report removed vs left
-
-Relay the uninstaller's output to the user: what was **removed** and what was
-**left in place**.
-- **Left:** `~/.plastic/` (intent store, history, projects) and any non-Plastic
-  settings.json entries.
-
-### Step 3: Verify removal
-
-Tell the user to confirm:
-
-```bash
-ls ~/.claude/skills | grep '^plastic-'    # -> no output
-ls ~/.claude/hooks  | grep '^plastic-'    # -> no output
-grep -n plastic ~/.claude/settings.json   # -> no plastic hook/plugin refs
-```
-
-### Step 4: Report
-
-Emit the reporting block, using the Step 3 checks for the verification line:
-
-```
-Plastic uninstall (<channel>)
-Command:  npx -y @zalom/plastic@<channel> uninstall --claude <flags>
-Version:  removed
-Verification: <Step 3 results, or "clean">
-```
-
-Then:
-
-```
-Plastic is uninstalled from [agent].
-Your intent store at ~/.plastic/ is untouched.
-```
-
-Uninstall removes installed harness files only. The store at `~/.plastic/` (intents,
-history, projects, config, version ledger) always stays; no uninstall path deletes it.
-Tell the user: "Your data is at ~/.plastic/. Re-install anytime with
-`npx -y @zalom/plastic@latest install --claude` (or your channel)."

package/skills/update/SKILL.md

@@ -1,126 +0,0 @@
----
-name: plastic-update
-description: Use when updating Plastic. Runs the `update` verb, which reads the installed VERSION, derives its channel, queries npm dist-tags, and advances to the next version on that channel (or switches channel with a flag).
-user-invocable: true
----
-
-# Update Plastic
-
-## When to Use
-- User says "update plastic", "sync plastic", or "upgrade plastic"
-- Statusline shows "Plastic update available"
-- After a version-bump notification
-
-## What it does
-
-`update` is a single deterministic command. It reads `~/.plastic/VERSION`, derives the
-channel from the version string (`-alpha`/`-beta`/none -> stable), queries `npm` dist-tags,
-and advances to the **next version on the current channel**. "Already up to date" is a
-clean no-op. You do not compute the target yourself, the script does.
-
-## Channel rule
-
-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`.
-
-## Flags
-
-| Flag | Behaviour |
-|------|-----------|
-| (none) | Advance to the next version on the **current** channel |
-| `--latest` | Switch to / advance the **stable** channel (toward stability, frictionless) |
-| `--beta` | Switch to / advance the **beta** channel |
-| `--alpha` | Switch to / advance the **alpha** channel (bleeding edge, confirmed if moving down in stability) |
-
-Switching toward a more stable channel is frictionless; switching toward bleeding edge is
-confirmed. To roll **back** to a previously-installed version, use `plastic-rollback`.
-
-## Prerequisites
-
-Plastic must be installed (`~/.plastic/VERSION` present). If not, run `plastic-install`
-first (or `npx -y @zalom/plastic@latest install --claude` directly).
-
-## Procedure
-
-### Step 1: Run the update
-
-```bash
-npx -y @zalom/plastic@<channel> update
-# channel switch: append --beta / --latest / --alpha
-# to target a specific harness instead of every installed one: --claude / --codex / --hermes / --all
-```
-
-`bunx -y @zalom/plastic@<channel> update` works as a fallback if `npx` is unavailable.
-
-With no harness flag, `update` targets **every currently-installed harness** (read from
-each agent's own `<agent-dir>/plastic/VERSION`), never Claude alone. Pass an explicit flag
-only to target one harness specifically.
-
-If the core is already on the target version but a targeted harness's own record is stale
-or missing (for example a harness added after the last sync), `update` still re-syncs that
-harness at the same version instead of reporting a clean no-op (same-version repair).
-
-The command prints the transition (`vX -> vY`) or "already up to date", a per-agent
-transaction summary when more than one harness synced, runs a post-update doctor summary
-per synced harness, and records one `versions.json` ledger row per synced harness (each
-row's `harness` field names which one).
-
-### 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-primary-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
-
-Relay what `update` printed, do not recompute the version transition or the doctor
-summary:
-
-```
-Plastic update (<channel>)
-Command:  npx -y @zalom/plastic@<channel> update <flags>
-Version:  <before> -> <after>
-Doctor:   <relayed summary, or "all clear">
-```
-
-Then read `~/.plastic/PLASTIC.md` and announce convention changes that affect the
-current session, and recommend `/clear` for a clean session with all new conventions
-loaded.
-
-### Step 4: Health check only on a relayed failure
-
-If the relayed doctor summary shows a failure, invoke `plastic-doctor` for the full
-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 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
-```