@ssheleg/agent-stack 0.24.1 → 0.24.3

package/CHANGELOG.md

@@ -1,3 +1,35 @@
+## 0.24.3 — the budget stops being estimated, and two skills stop naming a file they do not ship
+
+Hygiene from the 2026-09-13 family audit (HK-11).
+
+- **The body budget is MEASURED.** This gate divided by a calibrated 3.9 chars/token; the
+  calibration drifted. Measured 2026-09-14 against the authority's tokenizer:
+  `agent-evals` estimated **~4961** and measured **4374**; `agent-orchestrator` estimated
+  **~4762** and measured **4309** — two files reported past the working limit with 300+
+  tokens of real headroom. make-skill v0.28.0 closed the same defect in the family
+  auditor by measuring. With no tokenizer installed the check now **discloses** rather
+  than issuing a verdict from the wrong instrument.
+- **`agent-harness` and `agent-interop` named `test/validate.py`** — a repository file
+  that does not ship inside a skill, so it resolves at the repo root and nowhere an
+  installed reader stands. Both say "this pack's repository validator" now.
+- **`agent-harness` declares `compatibility`**: it ships `scripts/audit_agent.py`, and a
+  skill that needs an interpreter says so in front matter.
+- **`plugin.json`'s homepage** matches `package.json` and the forge
+  (`skills.sshlg.me/skills/agent-stack/`) instead of the GitHub URL.
+- **The README names what loads on demand** — 27 reference files, counted per skill from
+  the tree, not stated — and both invocation forms (`/agent-stack:<skill>` and
+  `/<skill>`), because which one resolves depends on how the pack was installed. The
+  installer line said "both skills" over a pack of four.
+
+## v0.24.2 — the ledger section names the version it ships
+
+The previous patch wrote the ledger section BEFORE bumping the version, so the
+section named the version that was being replaced and the lag it existed to
+close survived it. Order matters here: bump, then write the section against what
+is now declared.
+
+Nothing else changed.
+
 ## v0.24.1 — the ledger catches up to the version it ships
 
 A member's ledger is fixed in that member's own release. The umbrella's ratchet

package/README.md

@@ -160,7 +160,7 @@ waterfall, and model-routing precedence.
 /plugin install agent-stack@agent-stack
 ```
 
-**npm installer** — copies both skills into `~/.claude/skills/`:
+**npm installer** — copies all four skills into `~/.claude/skills/`:
 
 ```bash
 npx @ssheleg/agent-stack
@@ -180,6 +180,26 @@ npx --yes sshlg-skills@latest update
 
 Restart your agent afterwards — skills load at session start.
 
+**Reaching a skill by name.** Claude Code routes on the description, and both
+invocation forms work: `/agent-stack:agent-orchestrator` names the plugin's copy
+explicitly, `/agent-orchestrator` the plain one. Which resolves depends on how this
+pack was installed, so both are written here rather than one promised.
+
+### What loads on demand
+
+Twenty-seven reference files ship with the four skills, each with a load trigger in
+its skill body. By skill:
+
+| Skill | References |
+|---|---|
+| `agent-orchestrator` | 12 — the tool-calling loop, memory and retrieval, context budgets, provider routing, the work graph, the resale wallet and the saga across database and provider API |
+| `agent-harness` | 7, plus `scripts/audit_agent.py` |
+| `agent-interop` | 6 — one per protocol surface, each pinning the revision it was read at |
+| `agent-evals` | 2 — `otel-genai.md` (the semantic conventions an eval reads) and `statistics.md` (when a difference is a difference) |
+
+A file with no load trigger in a body is a defect, not a bonus: the skill audit
+refuses one.
+
 ---
 
 ## When it triggers

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ssheleg/agent-stack",
-  "version": "0.24.1",
+  "version": "0.24.3",
   "scripts": {
     "test": "python3 test/validate.py && python3 test/plant_guard_test.py && node test/installer_test.js && npm run test:audit",
     "test:audit": "for t in test/audit_regressions/*.py; do python3 \"$t\" || exit 1; done"

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

@@ -3,12 +3,12 @@
   "name": "agent-stack",
   "displayName": "Agent Stack",
   "description": "Four skills: agent-orchestrator — tool-calling loops, pipelines with checkpoints, provider routing with fallback, memory architecture, plus the wallet side of reselling LLM access; agent-evals — run/trace/thread evals, LLM judges, and fixtures grown from production; agent-interop — MCP servers and clients, A2A agent cards, the MCP Registry, and gateways; agent-harness — system prompts, tool shaping, workflow-vs-agent, and auditing an agent system.",
-  "version": "0.24.1",
+  "version": "0.24.3",
   "author": {
     "name": "ssheleg",
     "url": "https://x.com/sshlg93"
   },
-  "homepage": "https://github.com/ssheleg/agent-stack",
+  "homepage": "https://skills.sshlg.me/skills/agent-stack/",
   "repository": "https://github.com/ssheleg/agent-stack",
   "license": "MIT",
   "keywords": [

package/plugins/agent-stack/skills/agent-harness/SKILL.md

@@ -14,6 +14,9 @@ description: >-
   "аудит агента", "встроить агента". Not for the loop's plumbing, its evals, or its
   protocols — those are siblings.
 license: MIT
+compatibility: >-
+  scripts/audit_agent.py runs with python3 (standard library only); no network,
+  no package install. Everything else in this skill is prose and needs nothing.
 ---
 
 # Agent harness — what the agent is told, and how to audit what someone else told theirs
@@ -119,7 +122,7 @@ because a decision table with two homes is one that will disagree with itself.
 ## References
 
 Each opens with its own **Load this when** line and a revision stamp — this material moves,
-and `test/validate.py` fails the build on a reference that does not say when it was read.
+and this pack's repository validator fails the build on a reference that does not say when it was read.
 
 | File | Read it when |
 |---|---|

package/plugins/agent-stack/skills/agent-interop/SKILL.md

@@ -41,7 +41,7 @@ against the live specification rather than recalled:
   still introduced `binds` as a core concept as of 2026-08-13.
 
 So: **every reference in this skill opens with a `**Spec pinned:**` line**, and
-`test/validate.py` fails the build without one. That is a mechanical check, not an
+This pack's repository validator fails the build without one. That is a mechanical check, not an
 aspiration — the class of error it prevents is the one where prose reads as current
 because nothing on the page says otherwise.