@sabaiway/agent-workflow-memory 1.3.0 → 1.4.0

package/CHANGELOG.md

@@ -4,6 +4,20 @@ 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 `1.3.0`).
 
+## 1.4.0 — §2.6 right-altitude & code-grounded lens (memory)
+
+A **feature** release. The `agent_rules.md` substrate gains a **§2.6 Right-altitude & code-grounded
+(planning + review)** self-review subsection — fold by code (read + cite the `file:line`), pin
+intent/invariants/acceptance, and the convergence heuristic. Wording is **path-neutral** (the substrate
+"knows nobody": it points at "the project's planning methodology / workflow-methodology canon", never a
+sibling/engine path). The deployment-lineage head stays **`1.3.0`** (no `docs/ai` structural change, no
+migration file); the npm package version is a separate axis.
+
+- **Seed-or-preserve only (unchanged contract).** A NEW deployment gets the §2.6 lens from the seed;
+  refreshing an already-deployed file is the composition root's job.
+- **Template parity preserved** — the §2.6 block body stays byte-identical to the kit fallback template
+  (only the heading number differs), pinned by the kit's cross-package `lens-mirror.test.mjs`.
+
 ## 1.3.0 — Agent-writable config note; §2.5 Communication (memory)
 
 A **feature** release. The seeded `docs/ai/orchestration.json` note now frames the config as

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

package/capability.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-memory",
-  "version": "1.3.0",
+  "version": "1.4.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/templates/agent_rules.md

@@ -70,6 +70,11 @@ Apply this as part of §2 before any user-facing summary:
 - **No condescension, no filler.** Own a miss plainly and fix it in the same message.
 - **Large artifact (≈>100 lines):** deliver a real summary or the key excerpt inline **and** link the file — never flood the reader with a 2000-line paste, never hide the answer behind a bare pointer.
 
+### 2.6. Right-altitude & code-grounded (planning + review)
+- **Fold by code, not prose.** Before folding a code-touching finding into a plan or change, read the cited `file:line` and cite it — a prose fold drifts from the code and seeds the next bug.
+- **Right altitude.** Pin intent + invariants + acceptance criteria (named tests); leave fine code-mechanics to Execute, where prose cannot diverge from reality.
+- **Convergence heuristic.** When a review round keeps finding mechanism issues on a stable architecture, stop refining prose — raise the altitude or hand it to Execute. (Full canon: the project's planning methodology / workflow-methodology canon.)
+
 ---
 
 ## 3. Token & Session Optimization