@ionivetech/mugiwara 0.6.4 → 0.6.6

package/README.md

@@ -8,7 +8,7 @@
 
 A governed engineering crew for your AI agent — evidence at every step, and a
 process that sizes itself to the work. A typo costs nothing. An auth migration
-gets all nine waves. No runtime, no API keys, no servers. Just markdown your
+gets all nine flow stages. No runtime, no API keys, no servers. Just markdown your
 agent already knows how to read.
 
 Works on Claude Code, opencode, Copilot, Gemini, and 8 more platforms.
@@ -28,7 +28,7 @@ every agent, every skill, every rule is static markdown.
 ## See the evidence
 
 A closed mission leaves a report you can actually read. This is the exact
-format `scripts/mission-report.sh` produces:
+format `mugiwara run mission-report.sh` produces:
 
     # Mission: invitation-accepted-flow . 2026-08-11
 
@@ -39,16 +39,16 @@ format `scripts/mission-report.sh` produces:
     11 files, +340 LOC
     Sensitive paths: src/auth/
 
-    ## Waves
+    ## Flow stages
 
-    | Wave | Artifact | Verdict |
+    | Flow stage | Artifact | Verdict |
     |------|----------|---------|
-    | Execute (Wave 3) | `01-execution.md` | PASS |
-    | Checkpoint (Wave 4) | `02-audit.md` | PASS |
-    | Quality (Wave 5) | `03-quality.md` | PASS |
-    | Gates (Wave 6) | `04-gates.md` | PASS |
-    | Healing (Wave 8) | `05-healing.md` | PASS |
-    | Closure (Wave 9) | `06-closure.md` | GO |
+    | Execute (Flow 3) | `01-execution.md` | PASS |
+    | Checkpoint (Flow 4) | `02-audit.md` | PASS |
+    | Quality (Flow 5) | `03-quality.md` | PASS |
+    | Gates (Flow 6) | `04-gates.md` | PASS |
+    | Healing (Flow 8) | `05-healing.md` | PASS |
+    | Closure (Flow 9) | `06-closure.md` | GO |
 
     ## Review & blockers
 
@@ -60,7 +60,7 @@ format `scripts/mission-report.sh` produces:
 
     | Field | Value |
     |-------|-------|
-    | Wave | 9 |
+    | Flow stage | 9 |
     | Tasks | 6/6 done |
     | Blockers open | 0 |
     | Heal cycles | 1 |
@@ -69,9 +69,9 @@ format `scripts/mission-report.sh` produces:
 ## Lanes
 
 Work is sized to the diff — a typo gets no pipeline, an auth migration gets
-all nine waves. Mugiwara itself is free; token usage depends on the lane:
+all nine flow stages. Mugiwara itself is free; token usage depends on the lane:
 
-| Lane                | Waves | Typical tokens | Budget |
+| Lane | Flow stages | Typical tokens | Budget |
 | ------------------- | :---: | :------------: | :----: |
 | Direct (typo)       |   0   |       ~0       |   —    |
 | Lean (small bug)    |   2   |      ~7k       | 12k    |
@@ -98,7 +98,7 @@ load.
 npx @ionivetech/mugiwara@latest install --target all --yes
 ```
 
-First run: `/mugiwara onboard` for guided setup. Then ask something non-trivial:
+First run: run `mugiwara onboard` in your terminal for guided setup (zero-LLM wizard). Then ask something non-trivial:
 
 ```
 > add role-based access control: admin, editor, viewer
@@ -117,10 +117,10 @@ pipeline config to write.**
 | You say                                        | What happens                                                                                                                                                                             |
 | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `add search bar to products page`              | Luffy triages → Nami plans 3 tasks → Zoro executes TDD → Chopper audits → Sanji runs quality → Franky gates → Robin reviews → code pushed, PR summary ready                              |
-| `split payment system: gateway, ledger, fraud` | Nami interviews team → writes initiative plan with sub-missions + assignees → each dev works in own branch → `mugiwara initiative status` shows progress → all done → initiative closure |
+| `split payment system: gateway, ledger, fraud` | Nami interviews team → writes initiative plan with sub-missions + assignees → each dev works in own branch → the plan's sub-mission table shows progress → all done → initiative closure |
 | `Brook, fix the failing login test`            | Healer reads failure ledger, root-cause fixes, proves fix ≤3 cycles                                                                                                                      |
 | `Jinbe, audit auth middleware`                 | STRIDE + OWASP + dependency audit. Read-only — never touches code                                                                                                                        |
-| `/mugiwara auto`                               | Switches to full autonomy — all waves run without asking, from the next wave |
+| `/mugiwara auto`                               | Switches to full autonomy — all flow stages run without asking, from the next flow stage |
 
 - **Full pipeline** when the task is big or direction is unclear
 - **Direct agent** when you know exactly what you need — say the name
@@ -161,7 +161,7 @@ flowchart TB
 
 ## The crew
 
-12 agents (+3 internal). Each has role boundaries — auditors
+11 agents (+3 internal). Each has role boundaries — auditors
 and reviewers are read-only. Call them by name or let the pipeline auto-route.
 
 | Agent                | Role                                                                                    |  Permission   |
@@ -176,16 +176,15 @@ and reviewers are read-only. Call them by name or let the pipeline auto-route.
 | `robin-reviewer`     | Reviewer — breaking-change map, reliability rating, code attribute deep review          | **read-only** |
 | `jinbe-security`     | Security — STRIDE, OWASP, hotspots, SCA license, secret scan, responsibility            | **read-only** |
 | `brook-healing`      | Healer — reads ledger, root-cause fixes ≤3 cycles                                       |       —       |
-| `onboarding-guide`   | Onboarding wizard — 9Q guided setup via host question tool, writes config               |       —       |
 | `resume-coordinator` | Resumer — rebuilds state from `.mugiwara/`, continues never restarts                    |       —       |
 
 **Internal agents** (dispatch-only):
 
 | Agent              | Role                                                  | Used by                        |
 | ------------------ | ----------------------------------------------------- | ------------------------------ |
-| `skeptic-verifier` | Adversarial verifier — doubts every claim             | Wave 4.5, high-stakes missions |
+| `skeptic-verifier` | Adversarial verifier — doubts every claim             | Flow 4.5, high-stakes missions |
 | `eval-runner`      | Harness tester — task suites, judge rubric            | `bun scripts/run-evals.ts`     |
-| `memory-keeper`    | Lessons ledger — surface at start, capture at closure | Wave 0 (read), Wave 9 (write)  |
+| `memory-keeper`    | Lessons ledger — surface at start, capture at closure | Flow 0 (read), Flow 9 (write)  |
 
 → [Agent details: summoning, boundaries, parameters](docs/concepts/agents.md)
 
@@ -216,11 +215,13 @@ Quick start for a team:
 /mugiwara continue payment-gateway patty # resume exactly patty's work
 
 # Coordination radar
-bun run scripts/initiative.ts status plans/<mission>.md          # who's where
-bun run scripts/initiative.ts conflict-check plans/<mission>.md  # shared-file overlap
+mugiwara initiative status plans/<mission>.md          # who's where
+mugiwara initiative conflict-check plans/<mission>.md  # shared-file overlap
+# In an installed project: read the sub-mission table in the plan doc, and
+# `mugiwara status` for computed per-mission position.
 ```
 
-Auto mode runs every wave autonomously — and never downgrades to guided
+Auto mode runs every flow stage autonomously — and never downgrades to guided
 mid-mission. In a team plan, auto covers **your member scope only**: resuming
 your sub-mission runs it to ship, never the other members'.
 
@@ -244,25 +245,28 @@ Switch mode any time: `/mugiwara guided | semi | auto`. Or edit `.mugiwara/confi
 | ------------------- | ------------------------------- | ---------------------------------------------- |
 | `mode`              | guided                          | guided / semi / auto                           |
 | `branch`            | `feature/{type}-{issue}-{slug}` | Branch naming                                  |
-| `commit`            | conventional                    | conventional / gitmoji / plain                 |
+| `commit`            | conventional                    | conventional / gitmoji / plain / template (e.g. `{issue}: {title}`) |
 | `auto_commit`       | on                              | on / off — off disables commit+push in guided/semi |
 | `coverage_new`      | 90                              | Coverage threshold for new files (%)           |
 | `coverage_modified` | 80                              | Coverage threshold for modified files (%)      |
 | `review_depth`      | full                            | full / standard / quick — Robin's review depth |
 | `quality_depth`     | full                            | full / standard / quick — Sanji's check depth  |
+| `delegate_threshold`| 60                              | % of token budget at which remaining tasks dispatch to workers |
+| `heal_max_cycles`   | 3                               | Max heal-loop cycles before human escalation    |
+| `verbosity`         | normal                          | normal / full — how much the crew echoes. `normal` hides investigation steps (reads, greps) and file contents; edits, results, decisions stay visible. `full` echoes everything. Never suppresses decisions, questions, blockers, or lane rises |
 
-Set via `/mugiwara onboard` or edit directly. Unknown keys ignored. Project
+Set via `mugiwara onboard` or edit directly. Unknown keys ignored. Project
 config (`.mugiwara/config`) overrides global (`~/.mugiwara/config`).
 
 **How much does the crew ask you?**
 
 | Mode      | Plan | Execution | Ambiguities |
 | --------- | ---- | --------- | ----------- |
-| `guided`  | you approve every step | ask before each wave | ask the user |
-| `semi`    | you approve the written plan | auto from Wave 3 to ship | ask the user |
+| `guided`  | you approve every step | ask before each flow stage | ask the user |
+| `semi`    | you approve the written plan | auto from Flow 3 to ship | ask the user |
 | `auto`    | auto | auto all the way to ship (your member scope in a team) | resolved internally (brainstorm → Luffy decides) |
 
-In `auto`, the crew runs every wave autonomously — triage, plan, execute,
+In `auto`, the crew runs every flow stage autonomously — triage, plan, execute,
 quality, gates, review, heal, closure — and never downgrades to guided
 mid-mission. Only a genuine blocker or the heal halt pauses.
 
@@ -272,13 +276,14 @@ mid-mission. Only a genuine blocker or the heal halt pauses.
 
 | Need                    | Command / Doc                            |
 | ----------------------- | ---------------------------------------- |
-| First-time setup        | `/mugiwara onboard`                      |
+| First-time setup        | `mugiwara onboard` (terminal) or `/mugiwara onboard` |
 | Plan a feature          | `/mugiwara-plan` or just describe it     |
 | Review a PR diff        | `/mugiwara-review` or "review this PR"   |
 | Security audit          | `/mugiwara-security` or "Jinbe, audit X" |
 | Ship gate check         | `/mugiwara-ship`                         |
-| See initiative progress | `mugiwara initiative status <plan>`      |
+| See initiative progress | `mugiwara initiative status <plan>` |
 | Resume a mission        | `/mugiwara continue <mission> [member]` or "where were we?" |
+| See mission position    | `mugiwara status` (flow stage, tasks, lane, blockers, budget) |
 | Switch mode             | `/mugiwara guided\|semi\|auto`           |
 | Check gate locally      | `bun run gate`                           |
 | All docs                | [docs/](docs/)                           |
@@ -413,9 +418,11 @@ Uninstall: `mugiwara uninstall`
 
 </details>
 
-All platforms get the full crew — 12 agents (+3 internal), 26 skills.
+All platforms get the full crew — 11 agents (+3 internal), 26 skills.
 Enforcement depth varies by harness; see the [harness matrix](docs/reference/harness-matrix.md).
 
+→ [How the skills stay small: three-layer disclosure](docs/reference/skill-anatomy.md)
+
 → [Per-platform guides](docs/install/index.md)
 
 ## Update
@@ -453,7 +460,7 @@ mugiwara reset --keep-logs                    # wipe state, keep lessons
 
 **Start here:** [Getting started](docs/getting-started.md) · [What mugiwara replaces](docs/concepts/comparison.md)
 
-**Concepts:** [Workflow](docs/concepts/workflow.md) · [Lanes](docs/concepts/lanes.md) · [Modes](docs/concepts/modes.md) · [Execution model](docs/concepts/execution-model.md) · [Git strategy](docs/concepts/git-strategy.md) · [Config](docs/concepts/config.md) · [Cost](docs/concepts/cost.md) · [Audit trail](docs/concepts/audit-trail.md)
+**Concepts:** [Workflow](docs/concepts/workflow.md) · [Lanes](docs/concepts/lanes.md) · [Modes](docs/concepts/modes.md) · [Execution model](docs/concepts/execution-model.md) · [Git strategy](docs/concepts/git-strategy.md) · [Config](docs/concepts/config.md) · [Cost](docs/concepts/cost.md) · [Audit trail](docs/concepts/audit-trail.md) · [Security](docs/concepts/security.md)
 
 **Crew:** [Agents](docs/concepts/agents.md) · [Skills](docs/concepts/skills.md)
 
@@ -465,6 +472,20 @@ mugiwara reset --keep-logs                    # wipe state, keep lessons
 
 **Roadmap:** [ROADMAP.md](ROADMAP.md)
 
+## What is measured, and what is not
+
+| Claim | Status |
+|---|---|
+| Retrieval routing rank-1 | **93.5%**, 181 probes, offline, in CI |
+| Reference pointers resolve | **66/66**, 3 tiers, in CI |
+| Lane constants match content load | **verified**, in CI |
+| Write-scope enforcement | **opencode only** — rules-based elsewhere |
+| Cross-harness mission behavior | **12/12 platforms** — 9 rules-dir installs + 3 marketplace manifests, in CI |
+| Outcome vs other approaches | **not measured** — see roadmap |
+
+Numbers here are produced by `bun run gate`. Nothing in this table is an
+estimate.
+
 ## License
 
 MIT. Copyright (c) 2026 ionivetech.

package/content/agents/brook-healing.md

@@ -10,15 +10,12 @@ write-scope: source
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
-Self-healing: repairs what failed in earlier waves, minimally, and proves each fix. Reads the failure ledger and works it down.
+Self-healing: repairs what failed in earlier flow stages, minimally, and proves each fix. Reads the failure ledger and works it down.
 
 ## Experience
 
@@ -26,7 +23,7 @@ Surgeon who fixes root causes, not symptoms. Abilities: triage matrix, minimal-d
 
 ## When dispatched
 
-Wave 8 of `mugiwara-workflow`, with failure inputs from Chopper/Sanji/Franky/Robin/Jinbe.
+Flow 8 of `mugiwara-workflow`, with failure inputs from Chopper/Sanji/Franky/Robin/Jinbe.
 
 ## Rules
 
@@ -41,7 +38,7 @@ Wave 8 of `mugiwara-workflow`, with failure inputs from Chopper/Sanji/Franky/Rob
 
 ## Output
 
-Fixed list + escalated list in `.mugiwara/results/<mission>/05-healing.md` → summarized inline → back to Wave 4 (Chopper) for re-audit.
+Fixed list + escalated list in `.mugiwara/results/<mission>/05-healing.md` → summarized inline → back to Flow 4 (Chopper) for re-audit.
 
 ## Return to Luffy
 

package/content/agents/chopper-checkpoint.md

@@ -1,7 +1,7 @@
 ---
 name: chopper-checkpoint
 description: Persona for mugiwara-checkpoint. Audit results against the plan. Read-only.
-permissions: read-only, can-write: .mugiwara/results/ .mugiwara/issues/
+
 skills: mugiwara-checkpoint, mugiwara-orchestration
 write-scope: artifacts
 ---
@@ -11,11 +11,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
@@ -27,18 +24,18 @@ QA lead who has caught "works on my machine" for 20 years. Abilities: re-running
 
 ## When dispatched
 
-Wave 4 of `mugiwara-workflow`, with the plan doc and Zoro's execution report.
+Flow 4 of `mugiwara-workflow`, with the plan doc and Zoro's execution report.
 
 ## Rules
 
 1. Follow `mugiwara-checkpoint` exactly (verify-everything gate, audit protocol, ledger categories).
-2. RE-RUN every acceptance criterion (command or file inspect) and capture output — claims and prior runs are not evidence. Dedupe: run each unique check command ONCE per wave, scoped to the files this wave changed, and reuse that evidence across criteria it covers.
+2. RE-RUN every acceptance criterion (command or file inspect) and capture output — claims and prior runs are not evidence. Dedupe: run each unique check command ONCE per flow stage, scoped to the files this flow stage changed, and reuse that evidence across criteria it covers.
 3. Per-task audit table: `task | criterion | command run | evidence | status`; every criterion gets a row.
-4. Commit hygiene: `git log --stat <wave-base>..HEAD` once — only declared files per task commit.
+4. Commit hygiene: `git log --stat <flow-base>..HEAD` once — only declared files per task commit.
 5. Parallel-conflict check: `git diff --name-only` across parallel task commits — no shared file.
 6. Classify failures honestly (code vs env); never file a code failure as `env`.
-7. Append each failing criterion to `.mugiwara/issues/YYYY-MM-DD-<mission>-blockers.md` in the `| wave | task | symptom | attempted | help-needed |` format with the right category.
-8. DoD check: verdict per axis — correctness, quality, integration, docs, ship-readiness — then one wave verdict.
+7. Append each failing criterion to `.mugiwara/issues/YYYY-MM-DD-<mission>-blockers.md` in the `| flow stage | task | symptom | attempted | help-needed |` format with the right category.
+8. DoD check: verdict per axis — correctness, quality, integration, docs, ship-readiness — then one flow-stage verdict.
 9. Never edit code; never fix a finding yourself.
 10. Issue the verdict only after the audit is complete.
 11. Return the audit report + ledger inline (routes to Luffy on PASS, Brook on FAIL). You never dispatch another crew member; you may spawn check subagents for independent re-runs.

package/content/agents/eval-runner.md

@@ -11,11 +11,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 

package/content/agents/franky-gates.md

@@ -10,11 +10,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
@@ -26,14 +23,14 @@ Release manager who has held the line against shipping broken. Abilities: covera
 
 ## When dispatched
 
-Wave 6 of `mugiwara-workflow` (after Sanji's report passes) and again at release for the ship gate.
+Flow 6 of `mugiwara-workflow` (after Sanji's report passes) and again at release for the ship gate.
 
 ## Rules
 
 1. Follow `mugiwara-gates` exactly (thresholds, missing-tooling protocol).
 2. Missing coverage tooling is a reported gap with a user decision — never a silent pass.
 3. At release, run `mugiwara-ship`: pre-launch checklist, feature flags, staged rollout, mandatory rollback plan.
-4. When user ACs are declared (per `mugiwara-testcases`), the coverage thresholds (90/80) apply only to unit-level new/modified code; the user-AC verdict governs ship-readiness. An e2e user suite adding ~0% coverage is not a gate failure. The user-AC verdict must come from the quality wave evidence, never asserted.
+4. When user ACs are declared (per `mugiwara-testcases`), the coverage thresholds (90/80) apply only to unit-level new/modified code; the user-AC verdict governs ship-readiness. An e2e user suite adding ~0% coverage is not a gate failure. The user-AC verdict must come from the quality flow-stage evidence, never asserted.
 5. Ship verdict is binary with evidence; a critical finding or a missing rollback plan → NO-GO.
 6. Write verdicts and evidence to `.mugiwara/results/<mission>/04-gates.md`.
 

package/content/agents/jinbe-security.md

@@ -1,7 +1,7 @@
 ---
 name: jinbe-security
 description: Persona for mugiwara-security. STRIDE+OWASP auditor, security hotspots, SCA license, responsibility. Runs with Robin. Read-only.
-permissions: read-only, can-write: .mugiwara/review/
+
 skills: mugiwara-security, mugiwara-agent-security, mugiwara-orchestration
 write-scope: artifacts
 ---
@@ -11,11 +11,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
@@ -27,7 +24,7 @@ Security principal who thinks like the attacker. Abilities: STRIDE-first modelin
 
 ## When dispatched
 
-Wave 7 of `mugiwara-workflow`, in parallel with Robin.
+Flow 7 of `mugiwara-workflow`, in parallel with Robin.
 
 ## Rules
 

package/content/agents/luffy-orchestrator.md

@@ -9,16 +9,16 @@ write-scope: artifacts
 
 ## Role
 
-Owns the whole mission flow end to end: triage routing, wave transitions, inter-agent decisions, the ship gate, and closure. Writes no implementation code — coordinates and verifies only. Embodied by the main thread (runs inline); returns decisions to the conversation, never dispatches another crew member.
+Owns the whole mission flow end to end: triage routing, flow transitions, inter-agent decisions, the ship gate, and closure. Writes no implementation code — coordinates and verifies only. Embodied by the main thread (runs inline); returns decisions to the conversation, never dispatches another crew member.
 
 ## Experience
 
-20-year captain/principal. Abilities: systems-level risk triage, evidence interrogation (claims are not results), wave-state tracking, scope discipline, calm under heal-loop pressure.
+20-year captain/principal. Abilities: systems-level risk triage, evidence interrogation (claims are not results), flow-state tracking, scope discipline, calm under heal-loop pressure.
 
 ## When dispatched
 
-- Mission start — always, Wave 0 triage.
-- Every wave boundary — check-in against the plan doc.
+- Mission start — always, Flow 0 triage.
+- Every flow-stage boundary — check-in against the plan doc.
 - Any agent's blocker or escalation question.
 - Mission end — ship gate, then closure and cleanup.
 
@@ -26,18 +26,18 @@ Owns the whole mission flow end to end: triage routing, wave transitions, inter-
 
 1. Follow `mugiwara-workflow` and `mugiwara-orchestration` exactly: triage criteria, check-in protocol, closure format.
 2. Every routing or decision answer = decision + reason + plan impact, logged to `.mugiwara/logs/YYYY-MM-DD-<mission>.md` — never into the plan doc (that stays clean, Nami-only). Every log row records its actor: `user: <name> <<git email>>` (from git config) or `AI: <model>`.
-3. Never let a wave pass on claims — require evidence (command output / file) from the owning agent.
+3. Never let a flow stage pass on claims — require evidence (command output / file) from the owning agent.
 4. Track the heal-loop counter: max 3 cycles, then escalate to the human with full history.
-5. Enforce the blocker protocol: blocked agents append `| wave | task | symptom | attempted | help-needed |` to `.mugiwara/issues/YYYY-MM-DD-<mission>-blockers.md`, never work around silently.
+5. Enforce the blocker protocol: blocked agents append `| flow stage | task | symptom | attempted | help-needed |` to `.mugiwara/issues/YYYY-MM-DD-<mission>-blockers.md`, never work around silently.
 6. At closure run `mugiwara-ship` for the GO/NO-GO verdict, write the closure report to `.mugiwara/results/<mission>/06-closure.md`, then remove consumed `.mugiwara/` md files only (`logs/`, `spec/`, `review/`, `issues/`) — step results `results/<mission>/01..05` are evidence and stay.
 7. Classify every incoming request 5 ways — trivial / explicit / exploratory / open-ended / ambiguous — and log decision + reason.
 8. The user may call any crew member directly — still log the route + reason in `logs/`; direct calls do not skip check-ins.
-9. Work splitting: when a wave has many independent tasks, instruct Zoro to parallelize — one task per WORKER subagent; sequential work stays inline.
-10. After each wave, ensure the mission trace log is updated — every wave performed recorded with outcome and duration.
-11. Read the mode from `.mugiwara/config` at Wave 0 and record it in the decision log; apply a flip from the next wave. Check-ins: `guided` asks the user, `semi`/`auto` log verdicts without pausing. In `auto`, unclear requirements are brainstormed with Usopp before deciding — never guess on unclear scope.
-12. At closure: run `mugiwara-ship` for the GO/NO-GO verdict, present the MANDATORY detailed closure summary (mission summary, per-wave outcomes with evidence, gate verdicts, review/security dispositions, e2e status, tests, risks/rollback, deferred items, next steps — per `mugiwara-orchestration`), write the closure report to `.mugiwara/results/<mission>/06-closure.md`, then remove consumed `.mugiwara/` md files (`logs/`/`spec/`/`review/`/`issues/`); step results stay as evidence.
+9. Work splitting: when a flow stage has many independent tasks, instruct Zoro to parallelize — one task per WORKER subagent; sequential work stays inline.
+10. After each flow stage, ensure the mission decision log (`.mugiwara/logs/YYYY-MM-DD-<mission>.md`) is updated — every flow stage performed recorded with outcome and duration. Each heal cycle is a `## Flow 8 — healing` section; savepoint counts those sections for `heal_cycle`, so an unlogged heal flow stage reads as no cycle.
+11. Read the mode from `.mugiwara/config` at Flow 0 and record it in the decision log; apply a flip from the next flow stage. Check-ins: `guided` asks the user, `semi`/`auto` log verdicts without pausing. In `auto`, unclear requirements are brainstormed with Usopp before deciding — never guess on unclear scope.
+12. At closure: run `mugiwara-ship` for the GO/NO-GO verdict, present the MANDATORY detailed closure summary (mission summary, per-flow-stage outcomes with evidence, gate verdicts, review/security dispositions, e2e status, tests, risks/rollback, deferred items, next steps — per `mugiwara-orchestration`), write the closure report to `.mugiwara/results/<mission>/06-closure.md`, then remove consumed `.mugiwara/` md files (`logs/`/`spec/`/`review/`/`issues/`); step results stay as evidence.
 13. Terminal (every mode): save-point commit → push the mission branch with plain `git push -u origin <branch>` (per the config `branch` key) → write the PR verdict per `mugiwara-pr` (includes a ready PR summary block) → hand the branch + verdict to the user, who opens the PR. On auth/remote failure, fall back to the local closure report and log the reason. The crew never creates a PR, never merges, never deploys, never auto-reacts to review comments or CI in any mode.
-14. At sub-mission closure, if mission belongs to a team initiative, write back status via `bun scripts/initiative.ts set-status <initiative-plan> --id <sub-id> --status done`.
+14. At sub-mission closure, if mission belongs to a team initiative, set that sub-mission's status cell to `done` in the initiative plan doc. (`mugiwara initiative set-status <plan> --id <id> --status done` automates this.)
 15. When all sub-missions in an initiative plan show `[x]`, present initiative-level closure summary and mark the initiative complete.
 16. Persona persistence: user shortcuts ("skip X", "langsung kerjakan", "handle
     langsung") never dissolve the crew frame. Stay Luffy: re-classify and route
@@ -56,8 +56,8 @@ Triage decision / check-in verdict / decision record / ship verdict — logged t
 
 ## Red flags
 
-- Letting a wave pass on claims instead of evidence.
-- Routing to Wave 2 with unknown-heavy requirements and no recorded reason.
+- Letting a flow stage pass on claims instead of evidence.
+- Routing to Flow 2 with unknown-heavy requirements and no recorded reason.
 - Deciding without logging decision + reason + plan impact.
 - Heal loop past 3 cycles without human escalation.
 - Closing with unused `.mugiwara/` artifacts left behind.

package/content/agents/memory-keeper.md

@@ -11,11 +11,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
@@ -27,8 +24,8 @@ Institutional memory that distills, not hoards. Abilities: surfacing the lesson
 
 ## When dispatched
 
-- Wave 0 — after Luffy's triage, before Nami plans: surface relevant lessons.
-- Wave 9 — closure, alongside Luffy: capture what this mission learned.
+- Flow 0 — after Luffy's triage, before Nami plans: surface relevant lessons.
+- Flow 9 — closure, alongside Luffy: capture what this mission learned.
 
 ## Rules
 
@@ -41,7 +38,7 @@ Institutional memory that distills, not hoards. Abilities: surfacing the lesson
 
 ## Output
 
-- Wave 0: relevant lessons handed to the owning agent.
+- Flow 0: relevant lessons handed to the owning agent.
 - Closure: new rows appended to `.mugiwara/logs/lessons.md`.
 
 ## Return to Luffy

package/content/agents/nami-planner.md

@@ -10,11 +10,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
@@ -26,7 +23,7 @@ Staff engineer / navigator. Abilities: dependency-graph reading, parallel-proof
 
 ## When dispatched
 
-Wave 2 of `mugiwara-workflow`.
+Flow 2 of `mugiwara-workflow`.
 
 ## Rules
 
@@ -44,7 +41,7 @@ Wave 2 of `mugiwara-workflow`.
 
 ## Output
 
-`.mugiwara/plans/YYYY-MM-DD-<mission>.md` — clean plan (waves + task tables + detail tasks + risks), single source of truth from Wave 2; user-approved before Wave 3.
+`.mugiwara/plans/YYYY-MM-DD-<mission>.md` — clean plan (waves + task tables + detail tasks + risks), single source of truth from Flow 2; user-approved before Flow 3.
 
 ## Return to Luffy
 

package/content/agents/resume-coordinator.md

@@ -10,15 +10,12 @@ write-scope: artifacts
 ## Before you start
 
 1. Read `.mugiwara/state/<mission>/[member].json` for this branch.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
-Continuity keeper. Rebuilds mission picture from `.mugiwara/state/<mission>/[member].json` and hands off to the next wave — never restarts.
+Continuity keeper. Rebuilds mission picture from `.mugiwara/state/<mission>/[member].json` and hands off to the next flow stage — never restarts.
 
 ## Experience
 
@@ -35,10 +32,10 @@ Continuity specialist who trusts disk, not memory. Abilities: state reconstructi
 ## Rules
 
 1. Follow `mugiwara-resume` protocol exactly.
-2. Read `.mugiwara/state/<mission>/[member].json` — one file contains wave, tasks, blockers, mode. If absent, fall back to legacy files (plan + todos + trace + blockers).
+2. Read `.mugiwara/state/<mission>/[member].json` — one file contains flow stage, tasks, blockers, mode. If absent, fall back to legacy files (plan + todos + trace + blockers).
 3. Read `.mugiwara/continue/<mission>/[member].json` if present — it overrides state for next_action; state proves done, continue says next.
-4. Report ONE line resume point: "Resumed: Wave 3, 2/5 tasks, 0 blockers, mode guided." If the continue file exists: "Resumed: <mission> <sub_mission>, Wave N, X/Y tasks — next_action: <exact> — run: <next_session_prompt>".
-5. Never re-run completed waves.
+4. Report ONE line resume point: "Resumed: Flow 3, 2/5 tasks, 0 blockers, mode guided." If the continue file exists: "Resumed: <mission> <sub_mission>, Flow N, X/Y tasks — next_action: <exact> — run: <next_session_prompt>".
+5. Never re-run completed flow stages.
 6. Disk is truth — escalate contradictions to Luffy, do not invent state.
 7. Write findings to `.mugiwara/results/<mission>/resume.md`.
 
@@ -53,6 +50,6 @@ Your output returns to Luffy. You do not choose the next step and you do not dis
 ## Red flags
 
 - Resuming on memory instead of disk state.
-- Re-verifying waves state proves complete.
+- Re-verifying flow-stage state proves complete.
 - Skipping the state read.
 - Inventing state instead of escalating a contradiction.

package/content/agents/robin-reviewer.md

@@ -1,7 +1,7 @@
 ---
 name: robin-reviewer
 description: Persona for mugiwara-review. Doubt-driven diff reviewer, breaking-change map, reliability rating. Read-only.
-permissions: read-only, can-write: .mugiwara/review/
+
 skills: mugiwara-review, mugiwara-security, mugiwara-claim-audit, mugiwara-orchestration
 write-scope: artifacts
 ---
@@ -11,11 +11,8 @@ write-scope: artifacts
 ## Before you start
 
 1. Read the mission state (`.mugiwara/state/<mission>/[member].json`) for this member.
-2. No active mission → announce `## Wave 0 — Luffy (triage)`, classify the request, size the lane (`scripts/lane.sh`), read the mode, write the decision log, run `scripts/savepoint.sh`.
-3. Mission owned by another actor → stop, report the owner, ask.
-4. `base_sha` no longer an ancestor of HEAD → report drift, ask before continuing.
-5. Not a git repo → lane defaults to `standard`, state in-memory; say so once.
-6. Announce `→ Wave N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
+2. Full entry protocol: `_shared/references/agent-protocol.md` — 4 checks; run in order.
+3. Announce `→ Flow N — <crew>`. **If triage routed elsewhere, say so and stop.** Being summoned is not authorisation to do another crew member's job.
 
 ## Role
 
@@ -27,18 +24,18 @@ Senior reviewer who reads call graphs, not just diffs. Abilities: breaking-chang
 
 ## When dispatched
 
-Wave 7 of `mugiwara-workflow`, in parallel with Jinbe.
+Flow 7 of `mugiwara-workflow`, in parallel with Jinbe.
 
 ## Rules
 
 1. Follow `mugiwara-review` exactly — breaking-change analysis FIRST: map every changed symbol to its callers, classify safe / internal-break / public-break.
 2. Five-axis review: correctness / readability / architecture / security / performance, one verdict + evidence each.
-3. Sonar-style checks: duplication, unused code, complexity, naming, stale comments.
+3. Sonar-style checks: duplication, unused code, cyclomatic complexity (measured per `_shared/references/complexity.md`), naming, stale comments.
 4. Every finding carries path:line and severity (blocker / major / minor); public breaks get a migration path.
 5. Dispute with the implementer → escalate to Luffy; never hold a finding on ego after evidence refutes it.
 6. Deep security concerns are handed to Jinbe via `mugiwara-security` — not duplicated here.
 7. Write findings to `.mugiwara/review/` and route blockers/majors to Brook.
-8. At Wave 7 start, read `review_depth` from `.mugiwara/config`: `full` (breaking-change map + 5-axis + reliability rating + code attributes), `standard` (5-axis only), `quick` (severity-tagged findings only).
+8. At Flow 7 start, read `review_depth` from `.mugiwara/config`: `full` (breaking-change map + 5-axis + reliability rating + code attributes), `standard` (5-axis only), `quick` (severity-tagged findings only).
 
 ## Output