@ssheleg/agent-stack 0.13.0 → 0.13.2

package/CHANGELOG.md

@@ -1,5 +1,45 @@
 # Changelog
 
+## v0.13.2 — the residue scan stops answering for other runs
+
+`test/residue.py` now tags every workspace with the process group that made it, and the
+gate-wide scan reads only that tag. Scanning the shared `$TMPDIR` by prefix reported two
+things that are not this run's leak: another session's trees — 37,301 entries under the
+shared directory on 2026-08-24 turned a green suite red — and a tree a FAILING case in an
+earlier run kept ON PURPOSE as its evidence, which poisoned every run after it. The split is
+a pure function with fixtures for both directions, and what it excludes is printed rather
+than dropped in silence.
+
+The README told a reader to run commands the published package cannot run: it ships no
+`test/` directory, so `python3 test/validate.py` resolves in a clone and nowhere else. Measured against the
+published tarball on 2026-08-25. Shipping the suite does not fix it — the plants live in
+`.github/workflows/`, which no packaging npm can express puts in a tarball — so the document
+now names where the command runs instead of claiming it, beside a marker the umbrella's
+validator reads. Naming a dead command is this family's own rule; claiming one is the defect.
+
+
+## v0.13.1 — a citation into the manifesto is a phrase
+
+Five references into the manifesto had rotted, and every rule they named was
+intact — the worst shape a dead citation takes, because it still reads as a
+receipt. `manifesto.md:419-422`, which this pack cited as the home of the four
+priority axes, now holds *"The strongest is mechanical"*; the axes moved twenty
+lines down when the document grew.
+
+Converted to phrase anchors, each verified unique in the subject:
+`:156` → *"one input, one job, one output, one owner, and its own completion
+test"*, `:114` → *"you cannot connect it to the evidence graph later without
+inventing the test"*, `:122` → *"The evidence graph says how the result will be
+known"*, `:419-422` → *"How many agents, repositories, services, and owners meet
+at the change"*, `:424` → *"These axes are not a fake numerical score"*.
+
+`PRIORITY_AXES_SOURCE` was a constant holding one of the dead addresses; it holds
+the phrase now.
+
+Swept from the umbrella's conformance register in the same pass — R-003, run the
+fix against its siblings rather than its instance. `seo-aeo-audit` got the four
+axes this pack already had, in the other direction, on the same day.
+
 ## v0.13.0 — 2026-08-20 — the audit refused a score and computed one
 
 `references/audit.md` said *"a prioritized change plan … **not** a score"* at `:20`, argued

package/README.md

@@ -191,6 +191,10 @@ teaches you to route around it.
 
 ## Verify
 
+<!-- commands-run-in: a clone -->
+These run **in a clone of this repository**. The published npm package ships no
+`test/` directory, so from an install they are names, not commands.
+
 ```bash
 python3 test/validate.py
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/agent-stack",
-  "version": "0.13.0",
+  "version": "0.13.2",
   "scripts": {
     "test": "python3 test/validate.py && python3 test/plant_guard_test.py"
   },

package/plugins/agent-stack/.claude-plugin/plugin.json

@@ -1,8 +1,8 @@
 {
   "name": "agent-stack",
   "displayName": "Agent Stack",
-  "description": "Two skills: agent-orchestrator \u2014 tool-calling loops, multi-stage pipelines with checkpoints, provider routing with fallback, four-layer memory, context engineering, plus the wallet side of reselling LLM access; and agent-evals \u2014 run/trace/thread evals, judges, and fixtures grown from production.",
-  "version": "0.13.0",
+  "description": "Two skills: agent-orchestrator — tool-calling loops, multi-stage pipelines with checkpoints, provider routing with fallback, four-layer memory, context engineering, plus the wallet side of reselling LLM access; and agent-evals — run/trace/thread evals, judges, and fixtures grown from production.",
+  "version": "0.13.2",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/agent-stack/skills/agent-harness/references/audit.md

@@ -125,8 +125,8 @@ needs.
 <!-- priority-axes: impact, irreversibility, uncertainty, coordination -->
 
 So the inputs are published and the arithmetic is not. The axes are the manifesto's four
-(`~/DATA/pod-manifesto/manifesto.md:419-422`, under *these axes are not a fake numerical
-score* at `:424`), and two of them were absent here entirely while `effort` — a **cost**,
+(`manifesto` → *"How many agents, repositories, services, and owners meet at the
+change"*, under *"These axes are not a fake numerical score"*), and two of them were absent here entirely while `effort` — a **cost**,
 not a risk axis — had been substituted into their place:
 
 | Axis | Question | High · Medium · Low |