@sabaiway/agent-workflow-memory 8.1.0 → 8.1.1

package/CHANGELOG.md

@@ -4,6 +4,14 @@ 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 `4.0.0`).
 
+## 8.1.1 — the gate-migration's checker screen takes an argument tail (AD-158)
+
+`references/scripts/migrate-gates.mjs`: the guarded `checker-claim canon` region is byte-identical to the kit's
+`tools/checker-claim.mjs` again. `checkerClaimTool` gains an optional third parameter, the exact argument tail
+(default `--check`), matched as literal space-separated tokens at the end of the command; every existing call passes
+two arguments and matches exactly as before. The kit's new declare verb (kit 14.12.0) uses the tail for
+`--check --in-flight` and `--all`. PATCH: no migration result changes.
+
 ## 8.1.0 — the deployment-lineage head moves to 4.0.0 (AD-157)
 
 `scripts/stamp-takeover.mjs`: `LINEAGE_HEAD` is `4.0.0`, so a memory bootstrap stamps `docs/ai/.memory-version` with

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: '8.1.0'
+  version: '8.1.1'
 ---
 
 # agent-workflow-memory

package/capability.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-memory",
-  "version": "8.1.0",
+  "version": "8.1.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",

package/references/scripts/migrate-gates.mjs

@@ -157,7 +157,7 @@ export const isCoverageProducerGate = (gate) => {
 // A cmd makes exactly ONE of three claims about a given tool, and collapsing them into a boolean is
 // what makes a VENDORED copy of the tool read as "the tool is not declared at all" — a false
 // absence, with a remedy (adopt it) that then collides with the entry already there:
-//   • canonical      — this tool's `--check` invocation, resolving to THIS copy of it
+//   • canonical      — this tool's invocation with its tail (`--check` by default), resolving to THIS copy
 //   • tool-elsewhere — the same invocation shape, resolving to a DIFFERENT real copy
 //   • not-the-tool   — anything else: another command, a masked form, an inadmissible token, or a
 //                      path nothing can resolve
@@ -195,16 +195,18 @@ const bareTokenSafe = (text) => text.length > 0 && ![...text].some((ch) => {
 
 const RE_META = /[.*+?^${}()|[\]\\]/g;
 
-// checkerClaimTool(basename, canonicalPath) → the screen for ONE tool. The shape is the STRICT full
-// command — `node` + ONE (quoted or bare) path token + the exact basename + ` --check` + END — so a
-// masked form (`--check --help`, `--check || true`, a prefix command) is never any claim at all.
-// Separators are PLAIN SPACES, not \s: a newline between the tokens is not a command a runner would
-// execute as written. The basename is regex-escaped here, never by the caller — a caller-escaped
-// literal is one forgotten backslash away from a dot matching any byte.
-export const checkerClaimTool = (basename, canonicalPath) => {
+// checkerClaimTool(basename, canonicalPath, tail) → the screen for ONE tool. The shape is the STRICT
+// full command — `node` + ONE (quoted or bare) path token + the exact basename + the exact argument
+// tail (`--check` by default) + END — so a masked form (`--check --help`, `--check || true`, a prefix
+// command) or a reordered tail is never any claim at all. Separators are PLAIN SPACES, not \s: a
+// newline between the tokens is not a command a runner would execute as written. The basename and
+// every tail token are regex-escaped here, never by the caller — a caller-escaped literal is one
+// forgotten backslash away from a dot matching any byte.
+export const checkerClaimTool = (basename, canonicalPath, tail = '--check') => {
   const safe = basename.replace(RE_META, '\\$&');
+  const args = tail.split(' ').map((token) => token.replace(RE_META, '\\$&')).join(' +');
   return Object.freeze({
-    re: new RegExp(`^node +(?:"((?:[^"]*[/\\\\])?${safe})"|((?:[^\\s"]*[/\\\\])?${safe})) +--check$`),
+    re: new RegExp(`^node +(?:"((?:[^"]*[/\\\\])?${safe})"|((?:[^\\s"]*[/\\\\])?${safe})) +${args}$`),
     canonical: canonicalPath,
   });
 };