@sabaiway/agent-workflow-kit 1.5.0 → 1.5.2

package/CHANGELOG.md

@@ -4,6 +4,28 @@ Semantically versioned ([semver](https://semver.org)), newest first. The `versio
 is the current release. `upgrade` mode reads a project's `docs/ai/.workflow-version` and applies
 every `migrations/<version>-<slug>.md` newer than it, in semver order.
 
+## 1.5.2 — README uplift to front-door grade (docs)
+
+Docs-only patch. The npm-facing `README.md` is uplifted to match the GitHub family front door's
+pitch and voice while staying the kit's **manual**: a stronger hero, a compact "Part of the
+agent-workflow family" callout, a new **composition-root** section (the kit delegates to the memory
+substrate, injects the methodology, and detects the optional `codex` / `agy` bridges — all on the
+in-repo deploy, never on `npx … init`), a two-tier cross-agent note, and links **up** to the family
+front door instead of re-telling the whole-family story (AD-009). Accuracy passes hold: `init` ≠
+project deploy, the scoped `dependency-free` / `no telemetry` claims, bridges-as-skills, the
+`available:false` engine stub, and the bridge context-file priority. A new dev-only test
+(`test/readme-structure.test.mjs`) enforces fenced-ASCII width ≤ 78, in-page anchor resolution, and
+local-link existence across the published READMEs. No code, schema, or deployed-payload change; the
+deployment-lineage head stays `1.3.0` (no migration).
+
+## 1.5.1 — README hero fix (docs)
+
+Docs-only patch. The hero showed a hardcoded `v1.4.0` chip while the kit was 1.5.0; the chip is
+removed (the shields.io npm-version badge already shows the live version). A repo test
+(`test/readme-no-stale-version.test.mjs`, dev-only — not shipped) now asserts no published README
+hero carries a pinned `vX.Y.Z` chip, so the drift can't recur. No code, schema, or deployed-payload
+change; the deployment-lineage head stays `1.3.0` (no migration).
+
 ## 1.5.0 — Backend detection (detect + guide)
 
 The kit's onboarding can now **see the optional execution-backends** — the thin bridges to

package/README.md

@@ -2,24 +2,43 @@
 
 # 🧠 agent-workflow-kit
 
-**A portable, cross-agent memory & workflow system for AI coding agents.**
+**Durable, cross-agent memory & workflow for AI coding agents — the one command that installs it.**
 
-*Bootstrap it once — then every future session reconstructs project context in seconds
-instead of re-reading your whole repo.*
+*Run it once per machine, deploy it once per project — then every future session boots from a
+small, structured memory instead of re-reading your whole repo and re-deriving yesterday's
+decisions. Works with Claude Code, Codex, Cursor, and any agent that reads `AGENTS.md`.*
 
 [![npm version](https://img.shields.io/npm/v/@sabaiway/agent-workflow-kit?logo=npm)](https://www.npmjs.com/package/@sabaiway/agent-workflow-kit)
 [![npm downloads](https://img.shields.io/npm/dm/@sabaiway/agent-workflow-kit)](https://www.npmjs.com/package/@sabaiway/agent-workflow-kit)
 [![license](https://img.shields.io/npm/l/@sabaiway/agent-workflow-kit)](./LICENSE)
 [![node](https://img.shields.io/node/v/@sabaiway/agent-workflow-kit)](https://nodejs.org)
 
-`v1.4.0`  ·  `Node ≥ 18`  ·  `kernel-only`
+`Node ≥ 18`  ·  `dependency-free scripts`  ·  `no telemetry in family code`
+
+**One command to start:**
+
+```bash
+npx @sabaiway/agent-workflow-kit init
+```
+
+<sub>This installs the **global skill** — deploying into a project is a separate step ([below](#-install)).</sub>
 
 **Works with any tool that reads `AGENTS.md`** — Claude Code · Codex · Cursor · Devin Desktop (formerly Windsurf) · GitHub Copilot · Gemini CLI · Cline · Aider · and 20+ more.
 
+**Quick-jump:** [Install](#-install) · [What it deploys](#-what-it-deploys-into-your-project) · [How it works](#-how-it-works-60-seconds) · [Composition root](#-the-composition-root-of-the-family)
+
 </div>
 
 ---
 
+> **Part of the [`agent-workflow`](https://github.com/sabaiway/agent-workflow) family.** This package
+> is the **composition root** + entry point: it **delegates** memory deployment to the substrate,
+> **injects** the workflow methodology, and **detects** optional execution backends. This page is the
+> kit's **manual** (install · commands · what it deploys) — for the whole-family story, start at the
+> **[family front door](https://github.com/sabaiway/agent-workflow#readme)**.
+
+---
+
 ## ❓ The problem
 
 AI coding agents are **stateless between sessions**. Every new chat starts from zero:
@@ -59,22 +78,25 @@ WITH the kit · boots from memory, cost flat
   s3   ~5k tok  █            ← decisions kept
 ```
 
-<sub>*Illustrative — exact numbers scale with repo size. The point is the **shape**: cold re-reads that grow vs. a flat, cache-warm boot.*</sub>
+<sub>*Illustrative/directional, not a measured guarantee — exact numbers scale with repo size. The point is the **shape**: cold re-reads that grow vs. a flat, cache-warm boot.*</sub>
 
 | | 🚫 Without | ✅ With `agent-workflow-kit` |
 |---|---|---|
-| **Session boot** | re-read source + grep to rebuild context | read 4 small docs, ~constant |
+| **Session boot** | re-read source + grep to rebuild context | read a few small docs, ~constant |
 | **Boot cost** | grows with repo, paid every session | flat; stable layer stays prompt-cache-warm |
 | **Cross-session memory** | none | `handover` (where we left off) |
 | **Past decisions** | re-litigated | `decisions.md` (ADRs) — settled once |
 | **Known bugs** | re-discovered | `known_issues.md` — impact + workaround |
 | **Doc growth** | unbounded sprawl | frontmatter caps + 3-tier rolling archive |
 | **Drift** | docs ≠ code over time | pre-commit gate keeps them honest |
+| **Cross-agent** | re-explain the project to each tool | one `AGENTS.md`, read by 20+ agents |
 
 ---
 
 ## 📦 What it deploys into your project
 
+Invoking the skill **inside a project** creates a portable memory and its maintenance policy:
+
 ```
 your-repo/
 ├── AGENTS.md              ← single entry point
@@ -94,24 +116,35 @@ your-repo/
     ├── tech_reference.md  ← configs & patterns
     ├── pages/             ← one spec per page/route
     └── history/           ← archive (HOT→WARM→COLD)
-  + scripts/               ← caps · index · archive (Node)
-  + pre-commit hook        ← keeps it all honest
+  + scripts/               ← caps · index · archive (Node path)
+  + pre-commit hook        ← keeps it all honest    (Node path)
 ```
 
-Two visibility modes, chosen at bootstrap: **visible** (committed) or **hidden**
-(in-tree but git-ignored, so the repo "looks normal").
+The Markdown memory is **stack-agnostic**; the `scripts/` + pre-commit hook are the **Node path**
+(dependency-free, `node --test`). Non-Node projects keep the same policy by hand.
+
+Two **visibility** modes, chosen at deploy time: **visible** (committed with the repo) or **hidden**
+(same files in-tree but git-ignored via the global `core.excludesFile`, so the repo "looks normal").
+Hidden changes how the files are *tracked*, not where agents find them.
 
 ---
 
 ## 🚀 Install
 
-**One command** installs the kit into `~/.claude/skills/` and wires any Codex / Devin Desktop you have:
+### 1. Install the global skill — once per machine
 
 ```bash
 npx @sabaiway/agent-workflow-kit init
 ```
 
-Then invoke it **inside a project** — first time vs. already-deployed use different sub-commands:
+`init` installs/refreshes the skill at `~/.claude/skills/agent-workflow-kit/` and wires launchers for
+any Claude Code / Codex / Devin Desktop it finds. It **does not** deploy into a project, and **does
+not** install the optional bridges.
+
+### 2. Deploy into a project — once per repo
+
+Invoke the installed skill **inside the target repository** — first time vs. already-deployed use
+different sub-commands:
 
 | Agent | First time in the project | Project already has the kit |
 |-------|---------------------------|-----------------------------|
@@ -119,21 +152,22 @@ Then invoke it **inside a project** — first time vs. already-deployed use diff
 | **Codex** | `/skills` menu → `agent-workflow-kit` | …→ `agent-workflow-kit upgrade` |
 | **Devin Desktop** (Windsurf · Devin Local) | `/agent-workflow-kit` | `/agent-workflow-kit upgrade` |
 
-<sub>`/agent-workflow-kit` bootstraps a fresh deployment (and asks your **visibility**, **conversational language**, and whether the agent may **attribute work to itself / AI** — default off); `/agent-workflow-kit upgrade` migrates an existing one to the kit's current version. The `npx … init` above is a third, separate thing — it updates the **kit itself**, not any project.</sub>
+<sub>`/agent-workflow-kit` bootstraps a fresh deployment (and asks your **visibility**, **conversational language**, and whether the agent may **attribute work to itself / AI** — default off); `/agent-workflow-kit upgrade` migrates an existing one to the kit's current version.</sub>
 
-> **New in 1.4.0 — optional memory substrate.** The memory layer is now also published
-> standalone as [`@sabaiway/agent-workflow-memory`](https://www.npmjs.com/package/@sabaiway/agent-workflow-memory).
-> If it is installed, the kit **delegates** substrate deployment to it and injects the workflow
-> methodology; if not, the kit uses its **own bundled copy** — the one command above keeps
-> working with no new dependency. Same `docs/ai/` either way.
+> **Optional standalone memory substrate.** The memory layer is also published standalone as
+> [`@sabaiway/agent-workflow-memory`](https://www.npmjs.com/package/@sabaiway/agent-workflow-memory).
+> If a **healthy** copy is installed (the kit validates it with its own shipped validator), the kit
+> **delegates** substrate deployment to it and injects the workflow methodology; otherwise it uses
+> its **own bundled copy** — the one command above keeps working with no new dependency. Same
+> `docs/ai/` either way.
 
-**Upgrade the kit itself** later — same command with `@latest`:
+### Refresh the kit itself — same command with `@latest`
 
 ```bash
 npx @sabaiway/agent-workflow-kit@latest init
 ```
 
-<sub>That refreshes the **kit's own files** — distinct from `/agent-workflow-kit upgrade`, which migrates a **project's** deployment (see **Use** below).</sub>
+<sub>That refreshes the **kit's own files** in `~/.claude/skills/` — distinct from `/agent-workflow-kit upgrade`, which migrates a **project's** deployment (see **Use** below).</sub>
 
 <details>
 <summary><b>Manual install</b> — no <code>npx</code></summary>
@@ -180,7 +214,7 @@ command is printed).
 | Command | When | What happens |
 |---------|------|--------------|
 | `/agent-workflow-kit` | new / empty project | recon → **asks visible-or-hidden** + **conversational language** + **agent attribution** (default off) → deploys `AGENTS.md` + `docs/ai/` filled with real recon data → installs enforcement → **asks before committing** |
-| `/agent-workflow-kit upgrade` | existing deployment | reads `docs/ai/.workflow-version`, shows the changelog diff, applies migrations, re-stamps |
+| `/agent-workflow-kit upgrade` | existing deployment | reads `docs/ai/.workflow-version`, shows the changelog diff, preserves your authored memory, applies migrations, re-stamps |
 | `/agent-workflow-kit backends` | any time | **read-only** check of the optional execution-backends (the `codex` / `agy` bridges): what's set up vs missing and the next step. Never writes, never commits, never runs a subscription CLI (credentials = marker-file presence, not a live login). |
 
 It **never auto-commits** and **never overwrites** an existing `AGENTS.md` without asking.
@@ -196,18 +230,50 @@ It **never auto-commits** and **never overwrites** an existing `AGENTS.md` witho
 - **Layered, lazy loading** — *always-loaded* = `AGENTS.md` + `index.md` (~160 lines, cache-warm). *On-demand* = open a `docs/ai/` file only when its "Read When" applies. *Hierarchical* = subdir `AGENTS.md` loads when you work in that folder. *Archive* = old history rolls out of the hot files.
 - **Caps + freshness** — every doc declares a `maxLines` cap; a pre-commit hook blocks commits that bust a cap or let the auto-generated index go stale.
 - **3-tier rolling archive** — `changelog.md` (HOT, last days) → `history/recent.md` (WARM) → per-month COLD + a one-line condensed index. Hot files stay small forever.
-- **Plan lifecycle** — Plan → Phase → Step → Substep, ephemeral plan files, a mandatory Cleanup phase, and a session-continuity heuristic tuned for large-context models (e.g. Opus 4.8).
+- **Plan lifecycle** — Plan → Phase → Step → Substep, ephemeral plan files, a mandatory Cleanup phase, and a session-continuity heuristic tuned for large-context models (e.g. Claude Opus).
 - **No silent failures** — every guard that rejects an action logs structured context.
 
 Enforcement ships as dependency-free **Node** scripts (`node --test`, no package manager assumed). Non-Node projects follow the same policy by hand.
 
 ---
 
+## 🧩 The composition root of the family
+
+The kit is the member you install — the family's **composition root**. `npx … init` only installs
+the kit globally; the composition happens when you **deploy it in a repo** (`/agent-workflow-kit`):
+
+```
+agent-workflow-kit  —  the composition root (installed via npx … init)
+   on /agent-workflow-kit in a repo, the kit:
+   ├─ delegates ─▶ memory substrate   (healthy copy, else bundled fallback)
+   ├─ injects   ─▶ workflow methodology  (engine = future supplier; stub)
+   ├─ deploys   ─▶ AGENTS.md + docs/ai/ + Node scripts + pre-commit hook
+   └─ detects   ─▶ optional backends     (codex / agy — not by init)
+```
+
+- **Delegates** substrate deployment to **`@sabaiway/agent-workflow-memory`** when a healthy
+  standalone copy is present, else uses its **bundled fallback** — same `docs/ai/` either way.
+- **Injects** the bounded workflow methodology into the deployed `AGENTS.md`. Its *future* home is
+  **`agent-workflow-engine`** — today an `available: false` stub, never one of the shipped backends.
+- **Detects** the optional `codex` / `agy` **bridges** — agent skills with a manual once-per-machine
+  setup (not npm, not installed by `init`); `/agent-workflow-kit backends` reports readiness
+  read-only. A bridge reads the deployed memory only if it wins that tool's context-file priority,
+  and the bridges call third-party services (so "no telemetry" covers family code, not those).
+
+> Full member-by-member map + the whole-family story: the
+> **[family front door](https://github.com/sabaiway/agent-workflow#readme)** — this page stays the
+> kit's manual.
+
+---
+
 ## 🤝 Cross-agent by design
 
-One kit, three front doors — the *output* (`AGENTS.md` + `docs/ai/`) is read natively by
-Codex, Cursor, Devin Desktop, Copilot, Gemini CLI & 20+ tools, and the *bootstrapper* runs from
-Claude Code, Codex, or Devin Desktop. No logic is duplicated per tool.
+One kit, two tiers — **no logic is duplicated per tool:**
+
+- The **output** (`AGENTS.md` + `docs/ai/`) is read natively by Claude Code (via the `CLAUDE.md`
+  alias) · Codex · Cursor · Devin Desktop · Copilot · Gemini CLI & 20+ tools.
+- The **bootstrapper** runs from Claude Code · Codex · Devin Desktop — their launchers point at the
+  same `SKILL.md`, so deployment logic lives in one place.
 
 ---
 
@@ -215,16 +281,21 @@ Claude Code, Codex, or Devin Desktop. No logic is duplicated per tool.
 
 ```
 agent-workflow-kit/
-├── README.md        ← you are here
-├── SKILL.md         ← agent-facing algorithm
+├── README.md        ← you are here (the kit's manual)
+├── SKILL.md         ← agent-facing deploy / upgrade algorithm
 ├── CHANGELOG.md     ← version history
 ├── capability.json  ← agent-workflow family manifest (composition-root)
 ├── references/
-    ├── templates/   ← AGENTS.md + every docs/ai file
-    ├── scripts/     ← caps / archive / index + tests
-    ├── contracts.md ← visibility / language / attribution rules
-    └── planning.md  ← plan lifecycle + continuity
-├── tools/           ← family tooling: manifest schema + validator, methodology-slot injection, backend detector (detect-backends)
+│   ├── templates/   ← AGENTS.md + every docs/ai file
+│   ├── scripts/     ← caps / archive / index + tests
+│   ├── contracts.md ← visibility / language / attribution rules
+│   └── planning.md  ← plan lifecycle + continuity
+├── tools/           ← family tooling:
+│   ├── manifest/    ← capability-manifest schema + validator
+│   ├── delegation.mjs        ← detect substrate · delegate-or-fall-back
+│   ├── inject-methodology.mjs ← write the methodology slot
+│   ├── detect-backends.mjs    ← read-only backend detector
+│   └── release-scan.mjs       ← attribution / release gate
 ├── launchers/       ← Codex / Devin Desktop / Cursor entries
 └── migrations/      ← per-version upgrade steps
 ```
@@ -232,5 +303,5 @@ agent-workflow-kit/
 ---
 
 <div align="center">
-<sub>Kernel-only · stack-agnostic · distilled from a multi-year-verified reference implementation.</sub>
+<sub>Kernel-only · stack-agnostic · no telemetry in family code · distilled from a multi-year-verified reference implementation — <a href="https://github.com/sabaiway/agent-workflow">sabaiway/agent-workflow</a></sub>
 </div>

package/SKILL.md

@@ -3,7 +3,7 @@ name: agent-workflow-kit
 description: Deploy or upgrade a portable AI-agent memory-and-workflow system in any project. Use when the user wants to bootstrap `docs/ai/` + an entry-point `AGENTS.md` (+ `CLAUDE.md` alias) + cap/archive/index enforcement in a new or existing repo, set up the Memory Map and session protocols, install the docs-rotation pre-commit hook, or run `/agent-workflow-kit` / `/agent-workflow-kit upgrade`. Triggers on phrases like "set up the memory system", "deploy the AI workflow here", "bootstrap docs/ai", "upgrade the workflow".
 disable-model-invocation: true
 metadata:
-  version: '1.5.0'
+  version: '1.5.2'
 ---
 
 # agent-workflow-kit

package/capability.json

@@ -3,7 +3,7 @@
   "schema": 1,
   "name": "agent-workflow-kit",
   "kind": "composition-root",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "provides": [],
   "roles": {},
   "detect": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sabaiway/agent-workflow-kit",
-  "version": "1.5.0",
+  "version": "1.5.2",
   "description": "Portable, cross-agent memory & workflow for AI coding agents — Claude Code, Codex, Cursor, Devin Desktop. One command deploys an AGENTS.md entry point + docs/ai context with cap/archive/index enforcement into any repo.",
   "keywords": [
     "ai-agents",