@naswerks/engineering-loop 0.2.0 → 0.2.1

package/.claude-plugin/marketplace.json

@@ -10,11 +10,11 @@
     {
       "name": "naswerks",
       "description": "The engineering loop: docs-* knowledge loop, spec-* execution loop, and init for a fresh repository.",
-      "version": "0.2.0",
+      "version": "0.2.1",
       "source": {
         "source": "npm",
         "package": "@naswerks/engineering-loop",
-        "version": "0.2.0"
+        "version": "0.2.1"
       }
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "naswerks",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "The engineering loop: a knowledge loop (docs-*) and an execution loop (spec-*) for repositories driven by hosted agent sessions, plus init to make a repository ready for both.",
   "author": { "name": "naswerks" },
   "license": "MIT",

package/CHANGELOG.md

@@ -5,6 +5,14 @@ version is the one in `package.json` and `.claude-plugin/plugin.json`, which mus
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-09-20
+
+### Changed
+
+- `spec-seat`'s fallback for a `verify-staged` that is not on PATH names the pack root as `${CLAUDE_PLUGIN_ROOT}`
+  (substituted under Claude Code), with the folder two levels above the skill as the reading elsewhere — a
+  seat in a fresh worktree no longer has to locate the pack before it can take a staging receipt.
+
 ## [0.2.0] - 2026-09-20
 
 ### Changed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@naswerks/engineering-loop",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "The engineering loop as a Claude Code plugin: a knowledge loop (docs-*), an execution loop (spec-*), and init for a fresh repository. The package root is the plugin root.",
   "license": "MIT",
   "type": "module",

package/references/docs-workflow.md

@@ -1,4 +1,4 @@
-<!-- naswerks-loop: version=0.2.0 -->
+<!-- naswerks-loop: version=0.2.1 -->
 # Docs Workflow
 
 > How knowledge flows through `docs/`: the loop, the folder rules, the templates, and the `docs-*` skills.

package/references/engineering-loop.md

@@ -1,4 +1,4 @@
-<!-- naswerks-loop: version=0.2.0 -->
+<!-- naswerks-loop: version=0.2.1 -->
 # The Engineering Loop — flow, seats, skills, and the ceremony
 
 > The quick intro to how work gets built with this loop: the two loops (`docs-*` knowledge, `spec-*`

package/skills/spec-seat/SKILL.md

@@ -352,7 +352,9 @@ doorbell with no follow-through**; if you receive one bare, retry anyway and say
   exit 0 and NO output, and `git status` cannot show the loss** (an ignored file is neither staged nor
   dirty, so status looks *cleaner* after it — a `bin/` rule can eat a composition root, a `*.log` rule a
   folder of receipts). Run `verify-staged {your explicit staging list}` — one command, gate-legal (not on
-  PATH: `node <pack root>/bin/verify-staged.mjs {list}`; `--from-file` takes the list from a file,
+  PATH: `node ${CLAUDE_PLUGIN_ROOT}/bin/verify-staged.mjs {list}` — under Claude Code that variable is the
+  pack root, the folder this skill loaded from; in another harness it is the folder holding
+  `.claude-plugin/plugin.json`, two levels above this SKILL.md; `--from-file` takes the list from a file,
   `--against head` checks after the commit). Exit 0 is your staging receipt; non-zero names every missing
   file and the `.gitignore` rule that ate it, and is a **stop-the-line finding**: do not commit, do not
   `git add -f`, do not touch `.gitignore` — rename the artifact off the pattern (receipts stage as `.txt`,