@ssheleg/agent-stack 0.13.1 → 0.13.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,23 @@
1
1
  # Changelog
2
2
 
3
+ ## v0.13.2 — the residue scan stops answering for other runs
4
+
5
+ `test/residue.py` now tags every workspace with the process group that made it, and the
6
+ gate-wide scan reads only that tag. Scanning the shared `$TMPDIR` by prefix reported two
7
+ things that are not this run's leak: another session's trees — 37,301 entries under the
8
+ shared directory on 2026-08-24 turned a green suite red — and a tree a FAILING case in an
9
+ earlier run kept ON PURPOSE as its evidence, which poisoned every run after it. The split is
10
+ a pure function with fixtures for both directions, and what it excludes is printed rather
11
+ than dropped in silence.
12
+
13
+ The README told a reader to run commands the published package cannot run: it ships no
14
+ `test/` directory, so `python3 test/validate.py` resolves in a clone and nowhere else. Measured against the
15
+ published tarball on 2026-08-25. Shipping the suite does not fix it — the plants live in
16
+ `.github/workflows/`, which no packaging npm can express puts in a tarball — so the document
17
+ now names where the command runs instead of claiming it, beside a marker the umbrella's
18
+ validator reads. Naming a dead command is this family's own rule; claiming one is the defect.
19
+
20
+
3
21
  ## v0.13.1 — a citation into the manifesto is a phrase
4
22
 
5
23
  Five references into the manifesto had rotted, and every rule they named was
package/README.md CHANGED
@@ -191,6 +191,10 @@ teaches you to route around it.
191
191
 
192
192
  ## Verify
193
193
 
194
+ <!-- commands-run-in: a clone -->
195
+ These run **in a clone of this repository**. The published npm package ships no
196
+ `test/` directory, so from an install they are names, not commands.
197
+
194
198
  ```bash
195
199
  python3 test/validate.py
196
200
  ```
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ssheleg/agent-stack",
3
- "version": "0.13.1",
3
+ "version": "0.13.2",
4
4
  "scripts": {
5
5
  "test": "python3 test/validate.py && python3 test/plant_guard_test.py"
6
6
  },
@@ -2,7 +2,7 @@
2
2
  "name": "agent-stack",
3
3
  "displayName": "Agent Stack",
4
4
  "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.",
5
- "version": "0.13.1",
5
+ "version": "0.13.2",
6
6
  "author": {
7
7
  "name": "ssheleg",
8
8
  "url": "https://x.com/sshlg93"