@sabaiway/agent-workflow-memory 4.6.0 → 4.6.1

package/CHANGELOG.md

@@ -4,6 +4,25 @@ All notable changes to the memory substrate. Versions are this **package's** npm
 they are distinct from the **deployment-lineage** stamp written into a project's
 `docs/ai/.memory-version` (which tracks the shared `agent-workflow` lineage, head `3.0.0`).
 
+## 4.6.1 — the standalone upgrade delivers the spec layer behind a checker it can prove (AD-113)
+
+4.6.0 shipped the feature-spec layer for FRESH bootstraps; an EXISTING deployment at lineage head
+`3.0.0` had no lane to it. The standalone (skill-only) upgrade now closes that gap in prose, with no
+digest catalog and no change to the shipped payload:
+
+- **SKILL.md upgrade step 2 gains the spec-layer twin.** The reader pair (`scripts/spec-schema.mjs`
+  + its test) seeds create-only if missing. The store root `docs/ai/specs/index.md` seeds ONLY when
+  BOTH deployed pairs — reader and checker — are regular files byte-equal to the bundled copies
+  (checked via lstat; a dangling symlink anywhere means nothing is written), with the template's
+  date placeholder rendered. Every other state — a custom or partial pair, reader or checker — is
+  reported as is, with the composition root's upgrade named as the refresh lane and NO store root
+  written.
+- **`standalone-bootstrap.test.mjs` models the equal-head upgrade both ways:** both pairs
+  bundle-equal -> store seeded and the installed pre-commit hook exits 0 over a seeded spec; a
+  custom or partial pair -> reported, no store.
+
+PATCH: prose + the E2E model only.
+
 ## 4.6.0 — the feature-spec layer: a store under `docs/ai/specs/`, one text-only reader, a counted navigator row (AD-112)
 
 A deployed project gains a middle altitude of durable knowledge between the whole-project

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-memory
 description: Deploy or upgrade a portable AI-agent memory substrate in any project — an entry-point `AGENTS.md` (+ `CLAUDE.md` alias) and a structured `docs/ai/` context store with cap/archive/index enforcement. Use when the user wants to bootstrap `docs/ai/`, set up the Memory Map and session protocols, install the docs-rotation pre-commit hook, or run `/agent-workflow-memory` / `/agent-workflow-memory upgrade`. Triggers on "set up the memory system", "deploy the AI memory here", "bootstrap docs/ai", "upgrade the memory substrate". This is the substrate only — the workflow methodology (plan→execute→review, queue, Cleanup) is owned elsewhere and injected into AGENTS.md by the family composition root.
 disable-model-invocation: true
 metadata:
-  version: '4.6.0'
+  version: '4.6.1'
 ---
 
 # agent-workflow-memory
@@ -225,6 +225,20 @@ Fill strategy:
    hook gains its `archive-decisions.mjs --check` line only when the hook is next refreshed via
    `node scripts/install-git-hooks.mjs`; an old hook without the line stays consistent-safe (the
    decisions gate is simply not enforced yet — never a broken hook). **Same gate, also
+   stamp-independent — ensure the SPEC LAYER (Node projects; skip on a No-Node project like the
+   pair above):** copy `spec-schema.mjs` + `spec-schema.test.mjs` from
+   `${CLAUDE_SKILL_DIR}/references/scripts/` into the project's `scripts/` **if missing** (preserve
+   an existing file byte-for-byte). Then seed `docs/ai/specs/index.md` **if missing** from
+   `${CLAUDE_SKILL_DIR}/references/templates/specs/` (date filled; an existing root is preserved
+   byte-for-byte) **ONLY if BOTH pairs** — that reader pair AND `check-docs-size.mjs` +
+   `check-docs-size.test.mjs` — are regular files (probe with `ls -l`, never a follow-the-link
+   test: a symlink, dangling or not, or a directory at any of the five paths means NOTHING is
+   written) **byte-equal** to this skill's bundled copies (compare with `cmp`): the deployed checker
+   is what the pre-commit hook runs, and an older or edited one renders the store row by row and
+   reds its own index check. Otherwise seed NO store root and report which file differs: a
+   checker still on a body a release shipped is refreshed by the composition root's own upgrade
+   (it carries the catalog of shipped bodies), an edited one is the user's to refresh by hand — this
+   substrate carries no such catalog and never overwrites a deployed script. **Same gate, also
    stamp-independent — ensure the NAVIGATOR:** `docs/ai/index.md` is a GENERATED artifact the entry
    point declares always-loaded, so a deployment that never had one must gain it even at head — run
    `node ${CLAUDE_SKILL_DIR}/references/scripts/check-docs-size.mjs --ensure-index --root=<target>`

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-memory",
   "kind": "memory-substrate",
-  "version": "4.6.0",
+  "version": "4.6.1",
   "provides": ["context"],
   "roles": {},
   "detect": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-memory",
-  "version": "4.6.0",
+  "version": "4.6.1",
   "description": "Portable, cross-agent memory substrate for AI coding agents — an AGENTS.md entry point + docs/ai context with cap/archive/index enforcement, deployable standalone or as part of the agent-workflow family. The memory layer of the agent-workflow family.",
   "keywords": [
     "ai-agents",