@zalom/plastic 1.7.1 → 1.9.0

package/README.md

@@ -183,8 +183,9 @@ behind releases are part of the repository, not a hidden process.
 
 ## Conventions
 
-Plastic conventions live in `PLASTIC.md`, distributed to `~/.plastic/PLASTIC.md`
-and overwritten on every update. Project-specific rules live in `AGENTS.md`.
+The always-on core conventions live in `PLASTIC.md`, distributed to `~/.plastic/PLASTIC.md`
+and overwritten on every update. Deeper doctrine lives in the `plastic-conventions` skill,
+loaded on demand by the skills that need it. Project-specific rules live in `AGENTS.md`.
 Run `plastic-doctor` to check installation health; it compares files against
 the manifests, checks store state, and runs automatically after every update.
 

package/agents/plastic-intent-curator.md

@@ -27,9 +27,9 @@ You are the Plastic Intent Curator. Your role is to maintain the health and navi
 5. On a terminal-state transition (Completed OR Abandoned), do these things:
    a. Author a real `outcome.md` in the intent directory from `~/.plastic/templates/outcome.md`, with the frontmatter `disposition: delivered` for a completed intent or `disposition: abandoned` for an abandoned one. `outcome.md` is MANDATORY at every terminal, delivered and abandoned alike: on abandon it records the abandonment reason and replaces the scaffolded placeholder sentinel (never leave `outcome.md` a placeholder at a terminal).
    b. Call `plastic-intent-ending` for the terminal-transition close (INDEX move, savepoint `Done` bookend, store commit, disarm, and the QMD reindex last): `ruby ~/.plastic/scripts/end-intent --store <store> --id <id> --disposition delivered|abandoned`, then follow that skill's own disarm and reindex steps. Never restate the INDEX/savepoint/reindex one-liners here.
-6. Structural maintenance is move-and-record, and it is NEVER done without its receipt: remove the misplaced section, file, or ref from its artifact, then create or append `revisions.md` in that intent directory (copy the FORM from `~/.plastic/templates/revisions.md`) IN THE SAME PASS as the edit. If you cannot write `revisions.md` for any reason (permissions, a read-only path), you MUST NOT make the structural edit either - report the blocker instead of leaving an unrecorded change (this mirrors the tool-side rule: project-links, rebuild-graph, and restore-intent-v1 refuse rather than write a change with no receipt; you hold yourself to the same rule by hand). One entry per relocated item, newest at the bottom: a `## Revision vN - YYYY-MM-DD-HH:MM` header, a one-sentence `Why` ending with `[rule: <tag>]`, `Prior location`, and either `Content held` (verbatim) or a one-line `Change` for a frontmatter edit. For a stray file, embed its full content and delete the original. The violation-tag catalog is canonical in PLASTIC.md. A graph edit must move TOWARD ground truth (drop a dangling/false edge, add a reciprocity-forced or documented-real one) and must NEVER invent a relationship - "might be related" is never a valid `[rule:]` reason (PLASTIC.md > WORK vs MAINTENANCE).
+6. Structural maintenance is move-and-record, and it is NEVER done without its receipt: remove the misplaced section, file, or ref from its artifact, then create or append `revisions.md` in that intent directory (copy the FORM from `~/.plastic/templates/revisions.md`) IN THE SAME PASS as the edit. If you cannot write `revisions.md` for any reason (permissions, a read-only path), you MUST NOT make the structural edit either - report the blocker instead of leaving an unrecorded change (this mirrors the tool-side rule: project-links, rebuild-graph, and restore-intent-v1 refuse rather than write a change with no receipt; you hold yourself to the same rule by hand). One entry per relocated item, newest at the bottom: a `## Revision vN - YYYY-MM-DD-HH:MM` header, a one-sentence `Why` ending with `[rule: <tag>]`, `Prior location`, and either `Content held` (verbatim) or a one-line `Change` for a frontmatter edit. For a stray file, embed its full content and delete the original. The violation-tag catalog is canonical in `plastic-conventions > references/maintenance-and-revisions.md`. A graph edit must move TOWARD ground truth (drop a dangling/false edge, add a reciprocity-forced or documented-real one) and must NEVER invent a relationship - "might be related" is never a valid `[rule:]` reason (`plastic-conventions > references/maintenance-and-revisions.md`, WORK vs MAINTENANCE).
 7. Before performing structural maintenance on ANY intent that is NOT the one your own session is currently delivering under its own held delivery lock, you must:
-   a. Check the target's lock freshness: `ruby ~/.plastic/scripts/plastic-lock status --intent-dir <target-intent-dir>` and read the `lock_fresh` field of its JSON output. If `true`, DEFER: make no edit to that intent, and report it as skipped (an active delivery is in progress). This is DETECT-ONLY - you never acquire, create, or hold any lock of your own for maintenance (PLASTIC.md > WORK vs MAINTENANCE; there is exactly one lock in Plastic, the delivery lock).
+   a. Check the target's lock freshness: `ruby ~/.plastic/scripts/plastic-lock status --intent-dir <target-intent-dir>` and read the `lock_fresh` field of its JSON output. If `true`, DEFER: make no edit to that intent, and report it as skipped (an active delivery is in progress). This is DETECT-ONLY - you never acquire, create, or hold any lock of your own for maintenance (`plastic-conventions > references/maintenance-and-revisions.md`, WORK vs MAINTENANCE; there is exactly one lock in Plastic, the delivery lock).
    b. Require a clean store working tree before starting: `git -C ~/.plastic status --porcelain` (or the project store's own root, if not global) must be empty. If it is not, STOP and report the dirty paths rather than risk sweeping an unrelated concurrent change into your own commit; do not proceed until the tree is clean.
    c. Create a fresh branch from the current tip of that repo's main: `git -C <repo-root> checkout -b maintenance/curator-<UTC-timestamp> main`.
    d. Make the scoped edit plus its `revisions.md` receipt (step 6 above), touching nothing else.

package/deprecations.yml

@@ -1,6 +1,6 @@
 # Plastic deprecation notices
 # Each entry is shown to the user during SessionStart.
-# See PLASTIC.md "Deprecation Process" for the full convention.
+# See the plastic-releasing skill for the full convention.
 #
 # Schema:
 #   id: unique-slug (used for dismissal tracking)
@@ -11,4 +11,12 @@
 #   removal: semver where feature is removed
 #   link: optional URL to migration guide
 
-deprecations: []
+deprecations:
+  - id: plastic-reference-md-absorbed
+    severity: info
+    summary: "PLASTIC-reference.md has been absorbed into the plastic-conventions skill and removed; its content now lives in that skill's reference chapters."
+    migration_steps:
+      - "No action is required. Running plastic update removes the leftover ~/.plastic/PLASTIC-reference.md automatically."
+      - "If you hand-copied or hand-edited that file, delete your own copy; it is no longer read by Plastic."
+    introduced: "1.9.0"
+    removal: "1.11.0"

package/hooks/{links-gate → edit-gates}

@@ -1,3 +1,3 @@
 #!/bin/bash
 SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
-exec ruby "$SCRIPT_DIR/../scripts/hook-links-gate"
+exec ruby "$SCRIPT_DIR/../scripts/hook-edit-gates"

package/hooks/hooks.json

@@ -35,38 +35,8 @@
         "hooks": [
           {
             "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" code-gate",
-            "statusMessage": "Checking lifecycle gate..."
-          },
-          {
-            "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" lock-gate",
-            "statusMessage": "Checking lock gate..."
-          }
-        ]
-      },
-      {
-        "matcher": "Write|Edit",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" savepoint-pre",
-            "statusMessage": "Recording stage start..."
-          },
-          {
-            "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" links-gate",
-            "statusMessage": "Checking Links gate..."
-          }
-        ]
-      },
-      {
-        "matcher": "Write|Edit|mcp__serena__replace_content|mcp__serena__replace_symbol_body|mcp__serena__insert_after_symbol|mcp__serena__insert_before_symbol|mcp__serena__safe_delete_symbol|mcp__serena__rename_symbol",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" create-gate",
-            "statusMessage": "Checking create gate..."
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" edit-gates",
+            "statusMessage": "Checking Plastic gates..."
           }
         ]
       },
@@ -79,16 +49,6 @@
             "statusMessage": "Checking lifecycle gate..."
           }
         ]
-      },
-      {
-        "matcher": "Bash|Read|Grep|Glob",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" retrieval-gate",
-            "statusMessage": "Checking retrieval gate..."
-          }
-        ]
       }
     ],
     "PostToolUse": [
@@ -139,8 +99,8 @@
         "hooks": [
           {
             "type": "command",
-            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" qmd-search",
-            "statusMessage": "Searching QMD..."
+            "command": "\"${CLAUDE_PLUGIN_ROOT}/hooks/run-hook\" power-tools",
+            "statusMessage": "Checking power tools..."
           }
         ]
       }

package/hooks/power-tools

@@ -0,0 +1,8 @@
+#!/bin/bash
+# power-tools mandate hook launcher (intents 66, 66b, 187, 246). No-op when there is no global store.
+GLOBAL_INDEX="$HOME/.plastic/INDEX.md"
+if [ ! -f "$GLOBAL_INDEX" ]; then
+  exit 0
+fi
+SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
+exec ruby "$SCRIPT_DIR/../scripts/hook-power-tools"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zalom/plastic",
-  "version": "1.7.1",
+  "version": "1.9.0",
   "description": "Intent-driven idea development system for AI coding agents",
   "type": "module",
   "bin": {
@@ -38,7 +38,6 @@
     "agents/",
     "templates/",
     "PLASTIC.md",
-    "PLASTIC-reference.md",
     "deprecations.yml"
   ]
 }

package/scripts/codex-hook

@@ -5,8 +5,8 @@
 # Usage: codex-hook <gate>
 #   file-mutation gates: code-gate | lock-gate | savepoint-pre | gate-check | create-gate | links-gate
 #   live-state hooks (intent 199): session-start | check-update | continue |
-#     future-intent-check | auto-arm | qmd-search | savepoint
-#   shell-tool gates (intent 203): bash-gate | retrieval-gate
+#     future-intent-check | auto-arm | power-tools | savepoint
+#   shell-tool gate (intent 203): bash-gate
 #
 # The Codex input adapter (intent 102, extended by 199 and 203). Reads a Codex
 # hook stdin payload once. Three shapes exist and the gate name alone selects
@@ -20,17 +20,17 @@
 # that hook (hooks/<name>), which is already harness-agnostic (resolves
 # ~/.plastic off $HOME, reads only the common stdin fields the guide confirms
 # Codex shares with Claude for these three events), so the body is reused, not
-# rewritten (D3). The shell-tool gates (bash-gate, retrieval-gate) report
-# tool_name: "Bash" with the command in tool_input.command, but MUST NOT be
-# routed through ApplyPatchEnvelope.parse below: a plain shell command has no
+# rewritten (D3). The shell-tool gate (bash-gate) reports tool_name: "Bash" with
+# the command in tool_input.command, but MUST NOT be routed through
+# ApplyPatchEnvelope.parse below: a plain shell command has no
 # *** Begin Patch/*** End Patch envelope, so it would parse to an empty op list
 # and hit this file's own `exit 0 if ops.empty?` line, silently allowing every
-# Bash call and reopening the exact hole intent 203 closes. So these two exec
-# the SAME scripts/hook-bash-gate / scripts/hook-retrieval-gate files Claude
-# already runs, unmodified, the identical "drive the body, relay its output"
-# pattern used for the live-state hooks. The one adaptation shared by both the
-# live-state and shell-tool paths is threading the payload's session_id into
-# CLAUDE_CODE_SESSION_ID, since Codex's own process env never carries it, plus
+# Bash call and reopening the exact hole intent 203 closes. So it execs the SAME
+# scripts/hook-bash-gate file Claude already runs, unmodified, the identical
+# "drive the body, relay its output" pattern used for the live-state hooks. The
+# one adaptation shared by both the live-state and shell-tool paths is threading
+# the payload's session_id into CLAUDE_CODE_SESSION_ID, since Codex's own
+# process env never carries it, plus
 # a bounded timeout: hooks/check-update backgrounds a real npm network call
 # without redirecting its output away from the inherited stdout/stderr pipes,
 # and Codex invokes hooks synchronously, so without a bound a slow network call
@@ -50,9 +50,9 @@ require_relative "lib/links_gate"
 # caller that merges the dispatcher's own stdout and stderr.
 $stdout.sync = true
 
-STATE_HOOKS = %w[session-start check-update continue future-intent-check auto-arm qmd-search savepoint].freeze
+STATE_HOOKS = %w[session-start check-update continue future-intent-check auto-arm power-tools savepoint].freeze
 STATE_TIMEOUT = 5
-SHELL_HOOKS = %w[bash-gate retrieval-gate].freeze
+SHELL_HOOKS = %w[bash-gate].freeze
 
 gate = ARGV[0].to_s
 raw = ($stdin.read rescue nil)
@@ -78,20 +78,15 @@ if STATE_HOOKS.include?(gate)
 end
 
 if SHELL_HOOKS.include?(gate)
-  # bash-gate / retrieval-gate (intent 203): a shell command has no apply_patch
-  # diff envelope, so this branch execs the SAME scripts/hook-bash-gate /
-  # scripts/hook-retrieval-gate files Claude already runs, unmodified, and
-  # relays their exit code and stderr. It must never fall through to
-  # ApplyPatchEnvelope.parse below (see header comment).
+  # bash-gate (intent 203): a shell command has no apply_patch diff envelope, so
+  # this branch execs the SAME scripts/hook-bash-gate file Claude already runs,
+  # unmodified, and relays its exit code and stderr. It must never fall through
+  # to ApplyPatchEnvelope.parse below (see header comment).
   cwd = payload["cwd"].to_s
   cwd = Dir.pwd if cwd.empty? || !Dir.exist?(cwd)
   env = { "CLAUDE_CODE_SESSION_ID" => (session.empty? ? nil : session) }
   script = File.join(__dir__, "hook-#{gate}")
   argv = [script]
-  # hook-retrieval-gate reads plastic_home off ARGV[0] (mirrors hooks/retrieval-gate's
-  # own launcher, which passes "$HOME/.plastic"); hook-bash-gate takes no args, it
-  # resolves Dir.home directly.
-  argv << ENV.fetch("PLASTIC_HOME") { File.join(Dir.home, ".plastic") } if gate == "retrieval-gate"
   out, err, status = begin
     Timeout.timeout(STATE_TIMEOUT) { Open3.capture3(env, RbConfig.ruby, *argv, stdin_data: raw, chdir: cwd) }
   rescue StandardError