@sabaiway/agent-workflow-memory 3.0.1 → 3.1.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 `3.0.0`).
 
+## 3.1.0 — plain-language communication bar in §2.5 of the agent_rules template (AD-061)
+
+The `agent_rules.md` template's **§2.5 Communication** section gains a plain-language bar: every
+user-facing message is short, clear, and written in plain words of the dialogue language; when the
+dialogue language is not English, transliterated English jargon is banned — an English term
+survives only as the NAME of a thing (a flag / command / file / test), glossed in plain words when
+helpful; plain English stays plain for English-dialogue users.
+
+The bar is byte-identical to the kit's fallback copy of the same template (a hand-kept pair), so
+both deploy paths carry it. Existing deployments are reconciled into the bar by the kit's upgrade
+lane (not only new bootstraps); a standalone memory upgrade does not touch the §2.5 region. This is
+a COMMUNICATION contract (§2.5 of the deployed template), not a §2.x process invariant — the
+methodology engine is untouched.
+
 ## 3.0.1 — bundled reference scripts refreshed (no behavior change)
 
 PATCH rider on the kit 3.1.0 release — the publish workflow's changed-but-unbumped tooth caught

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

package/capability.json

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

package/package.json

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

@@ -67,6 +67,7 @@ Before proposing changes or committing, review against:
 
 ### 2.5. Communication (user-facing messages)
 Apply this as part of §2 before any user-facing summary:
+- **Plain language.** User-facing narration is short, clear, plain words of the dialogue language; when the dialogue language is not English, transliterated English jargon is banned — an English term survives only as the NAME of a thing (a flag / command / file / test), glossed in plain words when helpful; plain English stays plain for English-dialogue users.
 - **Deliver the artifact IN the message** — paste the prompt / diff / version / command inline; never "see §X / open the file / run it and you'll see" as a *substitute* for showing what was asked.
 - **Lead with the result**, then the details; show exactly what was asked — no deflection, no "almost done" when the ask was the finished thing.
 - **No condescension, no filler.** Own a miss plainly and fix it in the same message.