release(flow): bump 3.21.1 -> 3.22.0; attestation sweep; finalize v3.22.0 release notes + CHANGELOG (selftest 116/116+2)

Author: Pavel Sher

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "fusebase-flow",
   "description": "The framework client-facing teams use to build internal and client apps with AI. Two agents (Product Owner + AI Developer) run a disciplined spec-to-deploy lifecycle, packaged with FuseBase Apps domain skills. Closes the gaps that break real AI app development: drift, context rot, scope creep, unreliable hand-offs.",
-  "version": "3.21.1",
+  "version": "3.22.0",
   "author": {
     "name": "FuseBase (Nimbus Web Inc.)"
   },

.claude/agents/ai-developer.md

@@ -12,9 +12,9 @@ tools: Read, Glob, Grep, Bash, Write, Edit
 
 Choose the role from the handoff filename:
 
-> **AI Developer:** "Operating as AI Developer under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for AI Developer."
+> **AI Developer:** "Operating as AI Developer under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for AI Developer."
 
-> **Deploy phase:** "Operating as Deploy phase under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Deploy phase."
+> **Deploy phase:** "Operating as Deploy phase under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Deploy phase."
 
 **Lightweight lane (FR-21).** When the handoff is a **change-note** (or an implement handoff marked `change_tier: lightweight`), attest as AI Developer and add: "Running the Lightweight Lane (FR-21): one change-note, one build→verify→deploy pass, plain operator go-ahead; safety floor (live proof, explicit go-ahead, FR-07, rollback, one commit) kept; I will STOP and promote to Full if this turns non-trivial." Then follow `workflows/lightweight-lane.md` — no stop-at-gate handoff to a second session, deploy on a plain go-ahead (no DP.6 / DP.1). See `flow-skills/lightweight-lane/SKILL.md`.
 

.claude/agents/product-owner.md

@@ -10,7 +10,7 @@ tools: Read, Glob, Grep, Bash, Write, Edit
 
 ## Self-attestation (first response of every invocation)
 
-> "Operating as Product Owner under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Product Owner, and additionally the Architect (escalation) section when this ticket triggers escalation criteria."
+> "Operating as Product Owner under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Product Owner, and additionally the Architect (escalation) section when this ticket triggers escalation criteria."
 
 ## State announcement (every output)
 

.codex/agents/ai-developer.md

@@ -12,9 +12,9 @@ tools: Read, Glob, Grep, Bash, Write, Edit
 
 Choose the role from the handoff filename:
 
-> **AI Developer:** "Operating as AI Developer under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for AI Developer."
+> **AI Developer:** "Operating as AI Developer under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for AI Developer."
 
-> **Deploy phase:** "Operating as Deploy phase under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Deploy phase."
+> **Deploy phase:** "Operating as Deploy phase under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Deploy phase."
 
 **Lightweight lane (FR-21).** When the handoff is a **change-note** (or an implement handoff marked `change_tier: lightweight`), attest as AI Developer and add: "Running the Lightweight Lane (FR-21): one change-note, one build→verify→deploy pass, plain operator go-ahead; safety floor (live proof, explicit go-ahead, FR-07, rollback, one commit) kept; I will STOP and promote to Full if this turns non-trivial." Then follow `workflows/lightweight-lane.md` — no stop-at-gate handoff to a second session, deploy on a plain go-ahead (no DP.6 / DP.1). See `flow-skills/lightweight-lane/SKILL.md`.
 

.codex/agents/product-owner.md

@@ -10,7 +10,7 @@ tools: Read, Glob, Grep, Bash, Write, Edit
 
 ## Self-attestation (first response of every invocation)
 
-> "Operating as Product Owner under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Product Owner, and additionally the Architect (escalation) section when this ticket triggers escalation criteria."
+> "Operating as Product Owner under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for Product Owner, and additionally the Architect (escalation) section when this ticket triggers escalation criteria."
 
 ## State announcement (every output)
 

.cursor/rules/fusebase-flow-always.mdc

@@ -10,7 +10,7 @@ Read `FLOW_RULES.md` (stop at `## Amendment log` — dated history, never load i
 
 ## Self-attestation (first response of every session)
 
-State: "Operating as {Product Owner | AI Developer | Architect (escalated) | Deploy phase} under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for {role}."
+State: "Operating as {Product Owner | AI Developer | Architect (escalated) | Deploy phase} under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for {role}."
 
 ## State announcement (every output)
 

.github/copilot-instructions.md

@@ -1,13 +1,13 @@
 # GitHub Copilot / VS Code — Fusebase Flow repository instructions
 
-This repo runs **Fusebase Flow v3.21.1**. Read these files before any other action:
+This repo runs **Fusebase Flow v3.22.0**. Read these files before any other action:
 
 - `AGENTS.md` — portable always-on baseline (rules vs skills vs workflows vs hooks vs policies)
 - `FLOW_RULES.md` — full always-on rules (FR-01..FR-26) with enforcement-surface map (stop at `## Amendment log` — dated history, never load it)
 
 ## Self-attestation (first response of every session)
 
-> "Operating as {Product Owner | AI Developer | Architect (escalation) | Deploy phase} under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for {role}."
+> "Operating as {Product Owner | AI Developer | Architect (escalation) | Deploy phase} under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for {role}."
 
 ## State announcement (every output)
 

AGENTS.md

@@ -157,7 +157,7 @@ Fusebase Flow ships:
 
 **Self-attestation (every session's first response):**
 
-> "Operating as {role} under Fusebase Flow v3.21.1. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for {role}."
+> "Operating as {role} under Fusebase Flow v3.22.0. I will follow FR-01 through FR-26. I will apply Mode A on chat output and Mode B on every internal-artifact write. I will apply the role-discipline skill section for {role}."
 
 **Operator questions:** per FR-19, ask questions in chat text, not popup / clickable menu tools. Use short option tables or numbered lists so the operator can copy, forward, quote, and follow up.
 

CHANGELOG.md

@@ -12,7 +12,7 @@ Phase 1 of the ceremony-efficiency-middle-lane ticket (solves PR-2 + PR-3; Phase
 
 - **A3 ratchet governance** — `policies/ratchet-governance.yml`: the `prevents: <incident-class>` annotation convention + the `catastrophic-low-frequency` severity tag (makes a control harder to prune; a clean window is expected for rare-but-severe controls). A 9-class incident taxonomy is the WHY-home; a D5-scoped coverage map (deploy/gate controls + the elements rule 6 reads) states its own scope (silence ≠ safety). Scoped `prevents:` markers added to `templates/{handoff-deploy,handoff-implement,gate-report,verification-gate}.md` + `workflows/{greenlight-deploy,eight-phase-flow}.md`. **Pruning is PO-owned and never automatic** — an un-annotated, non-firing element is a *review candidate* only (needs named incident-class, severity, window, negative examples, operator confirmation).
 - **A2 `/find-wasted-effort` (31st skill, read-only)** — the **process-per-outcome** ceremony sibling of `/token-waste-audit` (**tokens-per-rule**). Different axis, different inputs (Flow artifacts on disk vs transcripts), **shared discipline**: it reuses the shipped `token-economy` substrate (FP header, read-only-first posture, gitignored `state/audit/<date>.md` output) — not reinvented. 6 active rules (rule 4 **CUT** — already in token-waste-audit's v3.21.0 cross-session aggregate; rule 7 scoped to the cross-session ceremony layer only), each emitting **confirmed / dismissed / inconclusive** with required contrary-evidence + per-rule FP examples.
-- **`hooks/local/find-wasted-effort.py` + `hooks/local/find_wasted_effort/` package** — deterministic, stdlib-only, **READ-ONLY** analyzer (thin CLI orchestrator + a 6-module package split along the per-rule + test-layer seam; every module under the FR-25 800-line ceiling). Reads gate/deploy reports, handoffs, approval artifacts, git log, and `prevents:` annotations; writes only its own gitignored report. NO memory/overlay/spec writes, NO prune/reclassify recommendations (those are Phase 2/3, gated on per-rule FP fixtures — D4). `--selftest` runs synthetic + evidence-sourcing/scoping + end-to-end + path-containment + parser fixtures (**107 passed, 2 skipped** — skips = host-symlink fixtures).
+- **`hooks/local/find-wasted-effort.py` + `hooks/local/find_wasted_effort/` package** — deterministic, stdlib-only, **READ-ONLY** analyzer (thin CLI orchestrator + a 6-module package split along the per-rule + test-layer seam; every module under the FR-25 800-line ceiling). Reads gate/deploy reports, handoffs, approval artifacts, git log, and `prevents:` annotations; writes only its own gitignored report. NO memory/overlay/spec writes, NO prune/reclassify recommendations (those are Phase 2/3, gated on per-rule FP fixtures — D4). `--selftest` runs synthetic + evidence-sourcing/scoping + end-to-end + path-containment + parser fixtures (**116 passed, 2 skipped** — skips = host-symlink fixtures).
 - **`/find-wasted-effort`** (6th command) + recovery snapshot; skill mirrored to `.claude/skills/` + `.agents/skills/`; counts swept 30 → **31** skills, 8 → **9** policies.
 
 Spec: `docs/specs/ceremony-efficiency-middle-lane/spec.md` (decisions D1..D7; Phase 1 cites D5, D7). Detail: `docs/release-notes/v3.22.0.md`.

CLAUDE.md

@@ -1,6 +1,6 @@
 # CLAUDE.md - Claude Code adapter for Fusebase Flow
 
-This repo runs **Fusebase Flow v3.21.1**. The portable always-on baseline is in `AGENTS.md`. The full rule set is in `FLOW_RULES.md`. Read both before any other action (stop `FLOW_RULES.md` at `## Amendment log` — dated history, never load it).
+This repo runs **Fusebase Flow v3.22.0**. The portable always-on baseline is in `AGENTS.md`. The full rule set is in `FLOW_RULES.md`. Read both before any other action (stop `FLOW_RULES.md` at `## Amendment log` — dated history, never load it).
 
 ## Claude Code-specific notes