@ssheleg/agent-stack 0.10.0 → 0.10.1

package/CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## [0.10.1] — 2026-08-15
+
+### Changed
+
+- **`graph-engineering.md`'s stamp names all three of its sources, and the two numbers that
+  come from the third say so.** The file pins an article and Claude Code's changelog, and
+  its execution section also states a concurrency cap and a lifetime agent cap that come
+  from **neither** — they are the Workflow tool contract the host presents at runtime, a
+  source with its own lifetime and no public changelog entry to check them against. A
+  revision stamp that names two sources for a file carrying three is the exact defect the
+  stamp exists to prevent, one level up. Both numbers now carry the instruction to read them
+  back from the running host.
+
 ## [0.10.0] — 2026-08-15
 
 ### Added

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/agent-stack",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "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.10.0",
+  "version": "0.10.1",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"

package/plugins/agent-stack/skills/agent-orchestrator/references/graph-engineering.md

@@ -6,7 +6,8 @@ placing a check between a parallel layer and the node that consumes it, or decid
 whether the structure may be discovered while it runs.
 
 **Spec pinned:** *Graph Engineering with Claude*, `https://x.com/Mahaximus_/status/2082442856417956173`
-(published 2026-07-29); Claude Code `CHANGELOG.md` v2.1.154 – v2.1.229 · read 2026-08-15
+(published 2026-07-29); Claude Code `CHANGELOG.md` v2.1.154 – v2.1.229, and the Workflow
+tool contract as presented in-session at CLI **2.1.223** · read 2026-08-15
 
 `SKILL.md` §2 owns the tool-calling loop and §5 the multi-stage pipeline. Both assume
 the shape is already decided. **This file is how it gets decided**, and it is upstream of
@@ -251,7 +252,10 @@ authors and executes a **script** whose primitives are the real contract:
 | `isolation: "worktree"` | a private checkout per agent | the only safe way to fan out writers |
 
 Concurrency is capped at `min(16, cores − 2)` per run, and a run's total agents at 1000.
-Passing 100 items is fine — they queue.
+Passing 100 items is fine — they queue. **Those two numbers and the primitive table come
+from the tool contract the host presents to the agent, not from the changelog** — a
+different source with a different lifetime, which is why the stamp above names both. Read
+them back from the running host before relying on them.
 
 **Why this matters for the model above:** the article's diamond is `parallel()`, and the
 next section is the distinction it does not draw.