@sabaiway/agent-workflow-memory 4.7.0 → 5.0.0

package/CHANGELOG.md

@@ -4,6 +4,33 @@ 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`).
 
+## 5.0.0 — the scenario floor: a contract can no longer pin NOTHING (AD-117)
+
+The reader enforced a minimum on `## Out of scope` and none on `## Scenarios`. A `kind: spec`
+document could therefore carry an EMPTY scenario section and pass everything — the reader, both
+`spec-check` lanes, the gate row. Measured cost, from writing the layer's first real specs: three
+stub specs would have satisfied every mechanical check of that slice and delivered nothing.
+
+> ### ⚠ BREAKING — the reader refuses a document it used to accept
+>
+> `SPEC_SCHEMA.rules` gains ONE frozen rule, **`scenarios-empty`**, in table position between
+> `scenario-path` and `out-of-scope`: a `## Scenarios` section carrying no scenario line is now an
+> error. The rule list is a frozen ordered contract, so a consumer that deep-equals it sees a 34th
+> id, and a deployment's spec gate can turn red with no edit of its own. The remedy is one line per
+> scenario — `- S<N> <name> :: unbound` while no test pins it.
+
+- **`*(empty)*` is deliberately NOT an escape here.** Written under `## Scenarios` it still refuses,
+  as `scenario-line`, and a fixture now pins that. The asymmetry with `## Out of scope` (where the
+  marker IS the decision) is the point: an empty exclusion list is a claim, an empty scenario list is
+  an absence, and the grammar already carries the honest form for the absence.
+- **`unbound` accepts on every status** — `draft`, `live` and `retired` alike — so the floor costs a
+  spec nothing but the statement that a scenario exists.
+- Measured before shipping: no document in the fixture corpus, the live store or the shipped
+  templates carries an empty section, so the floor refuses nothing that already exists.
+- The other 33 rule ids, every existing refusal and the whole `structure` extraction stay
+  behaviour-identical. The new arm was red-proofed against the pre-change reader.
+
+
 ## 4.7.0 — the reader's verdict gains the additive `structure` extraction (AD-114)
 
 The slice-2 checker (`spec-check`, next release) must read a document's structure through the SAME

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.7.0'
+  version: '5.0.0'
 ---
 
 # agent-workflow-memory

package/capability.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-memory",
-  "version": "4.7.0",
+  "version": "5.0.0",
   "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/spec-schema.mjs

@@ -38,7 +38,7 @@ export const SPEC_SCHEMA = Object.freeze({
     'frontmatter', 'frontmatter-key', 'substrate-key', 'type', 'kind', 'maxlines', 'status', 'revision',
     'root-owns', 'slug', 'kind-path', 'root-uplink', 'title', 'section-missing', 'section-order',
     'section-forbidden', 'fence', 'children-link', 'children-duplicate', 'fan-out', 'scenario-line',
-    'scenario-number', 'scenario-marker', 'scenario-path', 'out-of-scope', 'module-line', 'module-empty',
+    'scenario-number', 'scenario-marker', 'scenario-path', 'scenarios-empty', 'out-of-scope', 'module-line', 'module-empty',
     'module-traversal', 'module-absolute', 'module-backslash', 'module-glob', 'module-mix', 'parts',
   ]),
 });
@@ -238,6 +238,10 @@ const checkScenarios = (parsed, slug, status, errors, warnings) => {
     }
     scenarios.push(scenario);
   }
+  if (scenarios.length === 0) {
+    errors.push({ rule: 'scenarios-empty', message: `at least one scenario line (\`${SPEC_SCHEMA.unboundMarker}\` while no test pins it)` });
+    return;
+  }
   const gap = scenarios.findIndex((scenario, i) => scenario.n !== i + 1);
   if (gap !== -1) errors.push({ rule: 'scenario-number', message: `scenario ${gap + 1} is numbered S${scenarios[gap].n} — N runs contiguously from 1` });
   for (const scenario of scenarios) {

package/references/scripts/spec-schema.test.mjs

@@ -131,6 +131,14 @@ describe('readSpecDocument — refuse, exactly one rule per defect', () => {
     refuses(specDoc({ scenarios: ['- S1 a :: /abs/login.test.mjs :: spec:login/S1'] }), 'login.md', 'scenario-path');
   });
 
+  it('scenarios-empty / no empty-marker escape', () => {
+    refuses(specDoc({ scenarios: [] }), 'login.md', 'scenarios-empty');
+    refuses(specDoc({ scenarios: ['*(empty)*'] }), 'login.md', 'scenario-line');
+    for (const status of SPEC_SCHEMA.statuses) {
+      expect(readSpecDocument(specDoc({ scenarios: ['- S1 x :: unbound'], fields: { status } }), 'login.md').errors).toEqual([]);
+    }
+  });
+
   it('out-of-scope / module-empty / module-* path refusals / module-mix / parts', () => {
     refuses(specDoc({ outOfScope: '' }), 'login.md', 'out-of-scope');
     refuses(specDoc({ outOfScope: 'nothing excluded' }), 'login.md', 'out-of-scope');