@sabaiway/agent-workflow-kit 1.9.0 → 1.9.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,28 @@ Semantically versioned ([semver](https://semver.org)), newest first. The `versio
4
4
  is the current release. `upgrade` mode reads a project's `docs/ai/.workflow-version` and applies
5
5
  every `migrations/<version>-<slug>.md` newer than it, in semver order.
6
6
 
7
+ ## 1.9.1 — Front-door value framing for the optional bridges; kit flow-pointer
8
+
9
+ The optional execution-backends (the `codex` / `agy` bridges) were **listed** but never **sold**: a
10
+ reader couldn't tell what they add to the workflow or why they'd want them. Promoted per **AD-009**
11
+ altitude — value lives at the **family front door**, the per-package page stays a manual.
12
+
13
+ - **Root README** — the existing `## 🔌 Optional delegated execution (the bridges)` section now
14
+ frames what the bridges add to **plan → execute → review**: an *independent reviewer* (a second
15
+ opinion in the **review** phase) and a *delegated executor / parallel hand* (a bounded task to
16
+ `codex exec` in the **execute** phase), under your own subscription (no pay-as-you-go billing,
17
+ subject to each provider's quotas). The honesty caveats are unchanged (`init` bundles but never
18
+ places a bridge; link-only `setup`; third-party services; context-file priority).
19
+ - **Kit README** — one manual-altitude flow-pointer in the composition-root bridge bullet: the
20
+ bridges plug into the **execute** and **review** phases, routing **up** to the front door for the
21
+ *why*. No value pitch duplicated into the manual (AD-009 anti-drift).
22
+
23
+ Documentation change only — no code, detector, or `init`/npx behaviour change, no `docs/ai`
24
+ structural change, deployment-lineage head stays **`1.3.0`**, `agent-workflow-memory` untouched, no
25
+ migration. The **kit** README + metadata ship in the kit tarball (the root README is the GitHub
26
+ family front door, outside the package), so the kit README edit rides a patch bump — three version
27
+ sources in sync.
28
+
7
29
  ## 1.9.0 — `upgrade` surfaces the optional backends at every successful exit
8
30
 
9
31
  `/agent-workflow-kit upgrade` said **nothing** about the optional execution-backends (the `codex` /
package/README.md CHANGED
@@ -258,7 +258,10 @@ agent-workflow-kit — the composition root (installed via npx … init)
258
258
  - **Injects** the bounded workflow methodology into the deployed `AGENTS.md`. Its *future* home is
259
259
  **`agent-workflow-engine`** — today an `available: false` stub, never one of the shipped backends.
260
260
  - **Detects & (opt-in) sets up** the optional `codex` / `agy` **bridges** — agent skills (not npm, not
261
- installed by `init`). `/agent-workflow-kit backends` reports readiness **read-only**;
261
+ installed by `init`). They plug into the workflow's **execute** and **review** phases — for *what
262
+ each adds and why*, see the
263
+ [family front door](https://github.com/sabaiway/agent-workflow#readme). `/agent-workflow-kit backends`
264
+ reports readiness **read-only**;
262
265
  `/agent-workflow-kit setup` does the **link-only** part (place the bundled bridge skill + link its
263
266
  wrappers), while the binary install + the subscription login stay manual. A bridge reads the deployed
264
267
  memory only if it wins that tool's context-file priority, and the bridges call third-party services
package/SKILL.md CHANGED
@@ -3,7 +3,7 @@ name: agent-workflow-kit
3
3
  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".
4
4
  disable-model-invocation: true
5
5
  metadata:
6
- version: '1.9.0'
6
+ version: '1.9.1'
7
7
  ---
8
8
 
9
9
  # agent-workflow-kit
package/capability.json CHANGED
@@ -3,7 +3,7 @@
3
3
  "schema": 1,
4
4
  "name": "agent-workflow-kit",
5
5
  "kind": "composition-root",
6
- "version": "1.9.0",
6
+ "version": "1.9.1",
7
7
  "provides": [],
8
8
  "roles": {},
9
9
  "detect": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sabaiway/agent-workflow-kit",
3
- "version": "1.9.0",
3
+ "version": "1.9.1",
4
4
  "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.",
5
5
  "keywords": [
6
6
  "ai-agents",