@ssheleg/agent-stack 0.7.0 → 0.7.2

package/CHANGELOG.md

@@ -1,9 +1,57 @@
 # Changelog
 
+## v0.7.2 — the plants say whether they landed, and two of them were not
+
+Eight negative self-tests asserted inline, in Python, that their edit had happened —
+which works, and is the **fifth** careful copy of an idea this family already scripted.
+`plant_guard.py`'s own docstring was written against exactly that shape: five hand-written
+variants produced five different bugs, one of which reached a pull request.
+
+Adopting the shared implementation found two plants that were doing nothing at all.
+
+### Fixed
+
+- **`cp -R . /tmp/x` into an existing `/tmp/x` nests the tree instead of replacing it.**
+  The plant then edits a file left by the previous run, and `touch` on a file that already
+  exists changes neither content nor mode — so *a reference nobody links* and *stray
+  SKILL.md* both planted nothing, the validator honestly passed, and the step would have
+  reported a healthy guard as broken. CI is always fresh, so this was invisible there and
+  only ever bit the machine the plants were written on. Every copy is now `rm -rf`'d first.
+
+### Added
+
+- **`test/plant_guard.py` and its nine fixtures**, shared with `make-skill`, the umbrella
+  and `seo-aeo-audit`. It compares content **and permission bits**, because the variant
+  that shipped compared bytes against a plant whose whole effect was `chmod`.
+- **Every plant wrapped in `snap` / `verify`**, the description being the step's own name,
+  so a refusal names which plant died.
+- **A negative for the guard itself**: an unchanged copy must be reported, not passed.
+
+All eight plants were then watched landing on the machine they were written on.
+
 All notable changes to this project are documented here.
 Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 Versioning: [SemVer](https://semver.org/spec/v2.0.0.html).
 
+## [0.7.1] - 2026-08-14
+
+A red `validate` could not stop a publish anywhere in this family, and one member
+proved it: on 2026-08-12 `sheleg-dev` tagged v0.4.1 while its own validate run for that
+exact tag **failed**, and npm served 0.4.1 four minutes later.
+
+### Fixed
+
+- **The release now runs the whole validate suite before anything is published.**
+  `validate.yml` gained a `workflow_call` trigger and `release.yml` calls it with
+  `needs: validate` — the release runs *after* the real suite rather than beside a copy
+  of it. **Not one plant is duplicated:** each still has exactly one home.
+- **A guard keeps the connection there.** It fails when the trigger, the call, or the
+  `needs` goes missing — calling the suite without depending on it lets the jobs run in
+  parallel, which looks gated and is not. Watched failing against the planted removal.
+
+Proven end to end on `sheleg-dev` v0.4.3 before it reached here: the release run shows
+`validate / validate` completing first, then `release`, then `publish`.
+
 ## [0.7.0] — 2026-08-14
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/agent-stack",
-  "version": "0.7.0",
+  "version": "0.7.2",
   "description": "Production patterns for AI agent orchestrators \u2014 tool-calling loops, multi-stage pipelines with checkpoints, LLM provider routing with fallback, four-layer memory with confidence decay \u2014 plus the wallet side of reselling LLM access. This package is the installer CLI.",
   "bin": {
     "agent-stack": "bin/agent-stack.js"

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

@@ -2,7 +2,7 @@
   "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.7.0",
+  "version": "0.7.2",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"