@ionivetech/mugiwara 0.6.0 → 0.6.2

package/.claude-plugin/marketplace.json

@@ -5,13 +5,13 @@
   },
   "metadata": {
     "description": "The Straw Hat crew for AI agents",
-    "version": "0.6.0"
+    "version": "0.6.2"
   },
   "plugins": [
     {
       "name": "mugiwara",
       "description": "The Straw Hat crew of AI agents and skills: brainstorm, plan, execute, checkpoint, quality, gates, review, security, healing.",
-      "version": "0.6.0",
+      "version": "0.6.2",
       "source": "./"
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mugiwara",
   "displayName": "Mugiwara",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "The Straw Hat crew of AI agents and skills: brainstorm, plan, execute, checkpoint, quality, gates, review, security, healing.",
   "author": {
     "name": "ionivetech"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mugiwara",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "The Straw Hat crew of AI agents and skills: brainstorm, plan, execute, checkpoint, quality, gates, review, security, healing.",
   "author": {
     "name": "ionivetech"

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "mugiwara",
   "displayName": "Mugiwara",
   "description": "The Straw Hat crew of AI agents and skills: brainstorm, plan, execute, checkpoint, quality, gates, review, security, healing.",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "author": {
     "name": "ionivetech"
   },

package/.kimi-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "mugiwara",
-  "version": "0.6.0",
+  "version": "0.6.2",
   "description": "The Straw Hat crew of AI agents and skills: brainstorm, plan, execute, checkpoint, quality, gates, review, security, healing.",
   "author": {
     "name": "ionivetech"

package/.opencode/commands/mugiwara-onboard.md

@@ -0,0 +1,15 @@
+---
+description: Run the Mugiwara onboarding wizard — conversation via the onboarding-guide agent, or the terminal wizard (bun scripts/onboard.ts) for CLI users.
+---
+Mugiwara onboard: $ARGUMENTS
+
+Run the onboarding wizard. Two paths:
+
+1. Conversation (default): the onboarding-guide agent runs the 9-question
+   wizard through the host's native question tool (choices + free type),
+   then writes .mugiwara/config. No network.
+2. Terminal (CLI users / non-interactive hosts):
+   `bun scripts/onboard.ts`
+
+The wizard never writes .mugiwara/onboard.json. All 15 crew agents are always
+active — no agent-selection step.

package/.opencode/mugiwara-helpers.mjs

@@ -88,3 +88,27 @@ export function applyModeChange(mode, { projectDir = process.cwd(), home = homed
   mkdirSync(dirname(log), { recursive: true });
   appendFileSync(log, `| ${new Date().toISOString()} | mode flip | guided/semi/auto -> ${mode} | user |\n`);
 }
+
+export const DEFAULT_CONFIG_LINES = [
+  'mode=guided',
+  'branch=feature/{type}-{issue}-{slug}',
+  'commit=conventional',
+  'base=main',
+  'coverage_new=90',
+  'coverage_modified=80',
+  'review_depth=full',
+  'quality_depth=full',
+];
+
+// Idempotent: writes the full default config only when .mugiwara/config is
+// absent (a fresh repo's first use). Never overwrites an existing config —
+// mode=guided is the safe default; the user's later edits win.
+export function ensureDefaultConfig({ projectDir = process.cwd() } = {}) {
+  const dir = join(projectDir, '.mugiwara');
+  const file = join(dir, 'config');
+  if (existsSync(file)) return false;
+  assertNotSymlink(file);
+  mkdirSync(dir, { recursive: true });
+  writeFileSync(file, DEFAULT_CONFIG_LINES.join('\n') + '\n');
+  return true;
+}

package/.opencode/plugins/mugiwara.mjs

@@ -14,7 +14,7 @@
 import { existsSync, readdirSync, readFileSync } from 'node:fs';
 import { dirname, join } from 'node:path';
 import { fileURLToPath } from 'node:url';
-import { readMode, parseModeChange, applyModeChange } from '../mugiwara-helpers.mjs';
+import { readMode, parseModeChange, applyModeChange, ensureDefaultConfig } from '../mugiwara-helpers.mjs';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 
@@ -55,10 +55,11 @@ function parseFrontmatter(text) {
   return { data, body: text.slice(m[0].length) };
 }
 
-// write-scope is the single source of truth (content/agents/*.md frontmatter).
-// opencode permission.edit accepts glob/pattern -> action, last match wins, so
-// the path boundary IS runtime-enforceable: artifacts agents get deny-all-edit
-// except .mugiwara/**, source agents (zoro, brook) get full edit allow.
+// write-scope is a RULE for user-facing crew agents (mode 'all'): they run
+// inline in the main thread, so binding permission to active-agent identity
+// would force tab-switching per wave and break auto mode + resume. Runtime
+// enforcement stays for internal subagent-only agents (mode 'subagent'), where
+// the permission actually binds at dispatch time.
 function permissionFromScope(scope) {
   if (scope === 'source') return { edit: 'allow' };
   if (scope === 'artifacts') return { edit: { '*': 'deny', '.mugiwara/**': 'allow' } };
@@ -82,10 +83,15 @@ function readAgents() {
       continue;
     }
     if (!parsed.data.description || !parsed.body) continue;
-    agents[name] = { description: parsed.data.description, mode: 'all', prompt: parsed.body };
+    const internal = parsed.data.internal === 'true';
+    agents[name] = {
+      description: internal ? `[INTERNAL] ${parsed.data.description}` : parsed.data.description,
+      mode: internal ? 'subagent' : 'all',
+      prompt: parsed.body,
+    };
     if (CREW[name]) agents[name] = { ...agents[name], ...CREW[name] };
     const perm = permissionFromScope(parsed.data['write-scope']);
-    if (perm) agents[name].permission = perm;
+    if (perm && agents[name].mode === 'subagent') agents[name].permission = perm;
   }
   return agents;
 }
@@ -94,6 +100,9 @@ export default async () => ({
   dispose: () => {},
 
   config: (config) => {
+    // only seed .mugiwara/config when the cwd looks like a project — a global
+    // install must not create .mugiwara/ in an arbitrary non-project dir.
+    if (existsSync(join(process.cwd(), '.git'))) ensureDefaultConfig();
     config.skills = config.skills || {};
     config.skills.paths = config.skills.paths || [];
     if (!config.skills.paths.includes(skillsDir)) config.skills.paths.push(skillsDir);

package/AGENTS.md

@@ -173,7 +173,7 @@ Conventional Commits: `feat:`, `fix:`, `refactor:`, `docs:`, `chore:`.
 
 ```
 content/skills/    — 26 skill dirs, each with SKILL.md + optional references/
-content/agents/    — 14 agent .md files (11 user-facing + 3 internal)
+content/agents/    — 15 agent .md files (12 user-facing + 3 internal)
 references/         — shared reference files (definition-of-done, source-grounding, etc.)
 docs/               — user-facing documentation
 scripts/            — validation + tooling scripts

package/README.md

@@ -4,13 +4,17 @@
 [![npm downloads](https://img.shields.io/npm/dm/@ionivetech%2fmugiwara)](https://www.npmjs.com/package/@ionivetech/mugiwara)
 [![License: MIT](https://img.shields.io/github/license/ionivetech/mugiwara)](https://github.com/ionivetech/mugiwara/blob/main/LICENSE)
 
-**Ship quality code, not just fast code.** Mugiwara gives your AI agent a
-governed engineering team — 12 specialists who plan, build, audit, review, and
-heal — with evidence at every step. No runtime, no API keys, no servers. Just
-markdown your agent already knows how to read.
+**Your agent writes the code. Mugiwara proves it.**
+
+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
+agent already knows how to read.
 
 Works on Claude Code, opencode, Copilot, Gemini, and 8 more platforms.
 
+![Mugiwara banner](assets/banner.png)
+
 ## Why this exists
 
 AI agents are fast. They're also **unverified.** No audit trail. No review. No
@@ -21,43 +25,63 @@ every agent, every skill, every rule is static markdown.
 
 → [Full pitch: why mugiwara vs just asking your agent](docs/concepts/comparison.md)
 
-## What Mugiwara does
+## See the evidence
 
-### 9-wave pipeline
+A closed mission leaves a report you can actually read. This is the exact
+format `scripts/mission-report.sh` produces:
 
-```mermaid
-flowchart TB
-    L0["Luffy<br>Triage"] --> L1["Usopp<br>Brainstorm"] --> L2["Nami<br>Plan"] --> L3["Zoro<br>Execute"] --> L4["Chopper<br>Audit"]
-    L4 --> L5["Sanji<br>Quality"] --> L6["Franky<br>Gates"]
-    L6 --> L7R["Robin<br>Review"]
-    L6 --> L7J["Jinbe<br>Security"]
-    L7R --> L8["Brook<br>Heal"]
-    L7J --> L8
-    L8 --> L9["Luffy<br>Closure"]
-    L8 -. "heal ≤3 cycles" .-> L4
-```
+    # Mission: invitation-accepted-flow . 2026-08-11
 
-→ [Full pipeline details](docs/concepts/workflow.md)
+    **Lane** full . **Mode** guided . **Actor** farid . **Branch** feature/MKR-412
 
-### All features
+    ## What changed
+
+    11 files, +340 LOC
+    Sensitive paths: src/auth/
+
+    ## Waves
+
+    | Wave | 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 |
+
+    ## Review & blockers
+
+    Review + security files: invitation-accepted-flow-review.md, invitation-accepted-flow-security.md
+    Findings: 3
+    Blocker ledger rows: 1
+
+    ## State
 
-| Feature                     | What you get                                                                                    |
-| --------------------------- | ----------------------------------------------------------------------------------------------- |
-| **Lane sizing**             | Work auto-sized from `git diff`. Typo = instant fix. Auth migration = full pipeline.            |
-| **Team initiatives**        | Sub-missions with assignee + branch, shared plan doc, status tracking per sub-mission.          |
-| **Sonar-style quality**     | Duplication %, complexity, maintainability rating (A–E), code attributes, per-condition gate.   |
-| **STRIDE + OWASP security** | Threat modeling, secret scan, injection check, SCA license, hotspot review.                     |
-| **Self-healing**            | Brook reads all failures at once, fixes root causes, re-runs verification. ≤3 cycles.           |
-| **3 autonomy modes**        | guided (ask) / semi (auto branch+commit) / auto (hands-off). Flip mid-session.                  |
-| **Configurable depth**      | `review_depth` + `quality_depth`: full / standard / quick. Set per project.                     |
-| **Resume from anywhere**    | Session lost? Rebuilds from `.mugiwara/state.json`. Continues, never restarts.                  |
-| **Onboarding wizard**       | 10 questions — project type, team size, mode, depth. `/mugiwara onboard`.                       |
-| **Evidence trail**          | `.mugiwara/` workspace: plans, audit reports, quality reports, review findings, blocker ledger. |
-| **12 platforms**            | Claude Code, opencode, Copilot, Gemini, Codex, Cursor, Kimi, Pi, Antigravity + CLI.             |
-| **Cost tracking**           | Token budget per lane. Warn at 1.5×, pause at 3×. Surfaced in mission reports.                  |
-| **Multi-actor safe**        | Branch-scoped state. Two engineers, one repo. Reset refuses without `--force`.                  |
-
-→ [Every feature, explained with how-to-use + scenarios](docs/concepts/features.md) · [Full pipeline](docs/concepts/workflow.md) · [Lanes](docs/concepts/lanes.md) · [Modes](docs/concepts/modes.md) · [Config](docs/concepts/config.md) · [Audit trail](docs/concepts/audit-trail.md) · [Cost](docs/concepts/cost.md)
+    | Field | Value |
+    |-------|-------|
+    | Wave | 9 |
+    | Tasks | 6/6 done |
+    | Blockers open | 0 |
+    | Heal cycles | 1 |
+    | Tokens used | 14,200 / 20,000 |
+
+## 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:
+
+| Lane                | Waves | Typical tokens |
+| ------------------- | :---: | :------------: |
+| Direct (typo)       |   0   |       ~0       |
+| Lean (small bug)    |   2   |      ~4k       |
+| Standard (feature)  |  5–7  |      ~10k      |
+| Full (architecture) | 9–11  |      ~20k      |
+
+Usage tracked in `.mugiwara/state.json` per mission. Budget warns at 1.5×,
+pauses at 3×.
+
+→ [Full cost model](docs/concepts/cost.md)
 
 ## 30-second try
 
@@ -85,10 +109,6 @@ A Standard lane mission (~10k tokens) produces a branch with test-first
 commits, an audit report, a security review, and a ready PR summary — visible
 at every step in your chat.
 
-→ [Full walkthrough](docs/getting-started.md)
-
-## How it works
-
 You ask. The crew routes automatically. **No agent names to memorize, no
 pipeline config to write.**
 
@@ -104,11 +124,41 @@ pipeline config to write.**
 - **Direct agent** when you know exactly what you need — say the name
 - **Slash commands** when you want to drive: `/mugiwara-plan`, `/mugiwara-review`, `/mugiwara-security`, `/mugiwara-ship`, `/mugiwara onboard`
 
-→ [Full workflow walkthrough](docs/concepts/workflow.md)
+→ [Full walkthrough](docs/getting-started.md) · [Full workflow walkthrough](docs/concepts/workflow.md)
+
+## What Mugiwara does
+
+### All features
+
+| Feature                  | What you get                                                                                    |
+| ------------------------ | ----------------------------------------------------------------------------------------------- |
+| **Lane sizing**          | Work auto-sized from `git diff`. Typo = instant fix. Auth migration = full pipeline.            |
+| **Evidence trail**       | `.mugiwara/` workspace: plans, audit reports, quality reports, review findings, blocker ledger. |
+| **Self-healing**         | Brook reads all failures at once, fixes root causes, re-runs verification. ≤3 cycles.           |
+| **Resume from anywhere** | Session lost? Rebuilds from `.mugiwara/state.json`. Continues, never restarts.                  |
+| **12 platforms**         | Claude Code, opencode, Copilot, Gemini, Codex, Cursor, Kimi, Pi, Antigravity + CLI.             |
+
+→ All 19 features, with how-to-use + scenarios: [Every feature](docs/concepts/features.md) · [Full pipeline](docs/concepts/workflow.md) · [Lanes](docs/concepts/lanes.md) · [Modes](docs/concepts/modes.md) · [Config](docs/concepts/config.md) · [Audit trail](docs/concepts/audit-trail.md) · [Cost](docs/concepts/cost.md)
+
+## The pipeline
+
+```mermaid
+flowchart TB
+    L0["Luffy - Triage"] --> L1["Usopp - Brainstorm"] --> L2["Nami - Plan"] --> L3["Zoro - Execute"] --> L4["Chopper - Audit"]
+    L4 --> L5["Sanji - Quality"] --> L6["Franky - Gates"]
+    L6 --> L7R["Robin - Review"]
+    L6 --> L7J["Jinbe - Security"]
+    L7R --> L8["Brook - Heal"]
+    L7J --> L8
+    L8 --> L9["Luffy - Closure"]
+    L8 -. "heal ≤3 cycles" .-> L4
+```
+
+→ [Full pipeline details](docs/concepts/workflow.md)
 
 ## The crew
 
-12 user-facing specialists (+3 internal). Each has role boundaries — auditors
+12 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   |
@@ -123,7 +173,7 @@ 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 — 10Q guided setup, writes config                                     |       —       |
+| `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):
@@ -136,21 +186,15 @@ and reviewers are read-only. Call them by name or let the pipeline auto-route.
 
 → [Agent details: summoning, boundaries, parameters](docs/concepts/agents.md)
 
-## How much it costs
-
-Mugiwara itself is free. Token usage depends on mission lane:
+## When not to use Mugiwara
 
-| Lane                | Waves | Typical tokens |
-| ------------------- | :---: | :------------: |
-| Direct (typo)       |   0   |       ~0       |
-| Lean (small bug)    |   2   |      ~4k       |
-| Standard (feature)  |  5–7  |      ~10k      |
-| Full (architecture) | 9–11  |      ~20k      |
-
-Usage tracked in `.mugiwara/state.json` per mission. Budget warns at 1.5×,
-pauses at 3×.
-
-→ [Full cost model](docs/concepts/cost.md)
+- **Prototyping or spikes** — use Lane 4, or skip mugiwara entirely.
+- **Unattended multi-hour runs** — the crew runs inline so you can interrupt it.
+  If you want to walk away, superpowers' subagent-driven-development is built
+  for that.
+- **Solo scripts with no review path** — the audit trail has no audience.
+- **Harnesses without agent dispatch** (Gemini, Codex, tier 3) — you get the
+  workflow and the trail, not enforced role boundaries.
 
 ## Configuration
 
@@ -209,6 +253,8 @@ Add to `opencode.json`:
 { "plugin": ["@ionivetech/mugiwara"] }
 ```
 
+Update: `rm -rf ~/.cache/opencode/packages/@ionivetech/mugiwara* && opencode plugin @ionivetech/mugiwara -g` ([details](docs/install/opencode.md#update))
+
 Uninstall: remove `"@ionivetech/mugiwara"` from `opencode.json` plugins array
 
 </details>
@@ -315,20 +361,29 @@ Uninstall: `mugiwara uninstall`
 
 </details>
 
-All platforms get the full crew — 12 agents, 26 skills (+3 internal agents).
-No per-platform feature gaps.
+All platforms get the full crew — 12 agents (+3 internal), 26 skills.
+Enforcement depth varies by harness; see the [harness matrix](docs/reference/harness-matrix.md).
 
 → [Per-platform guides](docs/install/index.md)
 
 ## Update
 
 ```bash
-npm update @ionivetech/mugiwara                           # npm-based
-/plugin update mugiwara                                   # marketplace-based
-# Reinstall with same install command                     # GitHub-based
+# opencode — clear the pinned cache, then reinstall (npm update alone does NOT work)
+rm -rf ~/.cache/opencode/packages/@ionivetech/mugiwara* && opencode plugin @ionivetech/mugiwara -g
+
+# Claude Code — marketplace
+/plugin update mugiwara
+
+# CLI — npm global
+npm i -g @ionivetech/mugiwara@latest
 ```
 
-→ [Full update reference](docs/install/index.md)
+OpenCode pins the resolved version in its own package cache, so `npm update`
+never touches it. Reinstall with the same command for GitHub-based plugins
+(Gemini, Codex, Copilot, Cursor, Kimi, Pi, Antigravity).
+
+→ [Per-platform guides](docs/install/index.md)
 
 ## CLI
 

package/content/agents/luffy-orchestrator.md

@@ -25,20 +25,30 @@ Owns the whole mission flow end to end: triage routing, wave transitions, inter-
 ## Rules
 
 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).
+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.
 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.
-6. At closure run `mugiwara-ship` for the GO/NO-GO verdict, write the closure report to `.mugiwara/results/<mission>/06-closure.md`, then delete unused `.mugiwara/` md files (superseded results, review, issues, and the decision log).
+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.
-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 delete unused `.mugiwara/` md files.
+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.
 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`.
 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
+    to the owning role — never execute source yourself, never answer as a
+    generic assistant. The main thread embodies roles; it is never "plain
+    Claude" mid-mission.
+17. Write-scope awareness: your frontmatter `write-scope: artifacts` means edit
+    deny outside `.mugiwara/**`. A source-edit task is Zoro's or Brook's — say
+    "Delegating to Zoro" and dispatch immediately; never probe permissions,
+    never explore capabilities, never attempt the edit yourself. Brook heals
+    only — general source edits go to Zoro.
 
 ## Output
 

package/content/agents/onboarding-guide.md

@@ -1,37 +1,33 @@
 ---
 name: onboarding-guide
-description: Persona for using-mugiwara. Onboarding wizard: asks 10 questions, processes answers into config. No network.
+description: Persona for using-mugiwara. Onboarding wizard: host-native question flow, writes config only. No network.
 skills: using-mugiwara, mugiwara-orchestration
 write-scope: artifacts
 permissions: read-only
 ---
-
 # Onboarding Guide
-
 ## Role
 
-Interactive onboarding agent — runs 10 predefined questions (no network), generates `.mugiwara/config` and `.mugiwara/onboard.json`.
-
-## Experience
-
-First-run specialist who sets up Mugiwara for new projects. Knows the full config surface and explains each option inline during the wizard.
-
-## When dispatched
-
-- `/mugiwara onboard` command
-- First-run detection: no `.mugiwara/config` file at project root
-- Re-onboard: config exists but user wants to reset
+Runs the onboarding wizard via host-native question tool (opencode `question`,
+Claude Code `AskUserQuestion`, Copilot `askQuestion` when present), or plain
+conversation otherwise. Writes `.mugiwara/config` only. No network. First-run
+specialist; knows the full config surface, explains each option inline.
+Dispatched by `/mugiwara onboard`, first-run detection, or re-onboard reset.
 
 ## Rules
 
-1. Never modify the 10 questions — they are fixed and validated.
-2. Never skip a question. Every question must be answered before writing config.
-3. Display questions in batch-form with options, one phase at a time.
-4. Write `.mugiwara/config` and `.mugiwara/onboard.json` only after all 10 answers collected.
+1. Never modify the questions — fixed and validated (9 questions).
+2. Never skip a question; all 9 answered before writing config.
+3. Host question tool when present (opencode `question`, Claude Code `AskUserQuestion`,
+   Copilot `askQuestion`): one per call, options + free-type, next-next until done.
+   No tool → conversation: numbered choices + "type your own answer".
+4. Write `.mugiwara/config` only after all 9 answers. Never write
+   `.mugiwara/onboard.json`; delete a stale copy if one exists.
 5. Print a config summary after completion so user can verify.
-6. All prompts are static — no network, no LLM-generated questions.
+6. All prompts static — no network, no LLM-generated questions.
+7. CLI users: point to `bun scripts/onboard.ts` (terminal wizard for non-interactive hosts).
 
-## The 10 Questions
+## The 9 Questions
 
 ### Phase 1: Project Context
 
@@ -91,20 +87,14 @@ First-run specialist who sets up Mugiwara for new projects. Knows the full confi
 [3] auto — full auto-pilot
 ```
 
-**Q7 — Agents to enable (comma-separated list or `all`):**
-```
-Available: brainstorm, plan, execute, checkpoint, quality, gates, review, security, healing
-Default: all
-```
-
-**Q8a — Code review depth:**
+**Q7 — Code review depth:**
 ```
 [1] full — breaking-change map, five-axis review, ≤3 cycles
 [2] standard — five-axis review, 1 cycle
 [3] quick — diff-only, no caller-map
 ```
 
-**Q8b — Quality check depth:**
+**Q8 — Quality check depth:**
 ```
 [1] full — format, lint, typecheck, test, build
 [2] standard — lint, typecheck, test
@@ -118,28 +108,17 @@ Default: all
 [3] custom — enter your own values
 [4] none — 0/0, no coverage enforcement
 ```
-
-**Q10 — Commit style:**
-```
-[1] Conventional Commits (feat:, fix:, chore:, docs:)
-[2] Semantic (type(scope): message)
-[3] Free-form
-```
-
 ## Output
 
-After all 10 answers collected, writes two files:
-- `.mugiwara/config` — machine-readable config (mode, branch, coverage, commit, review_depth, quality_depth, enabled_agents)
-- `.mugiwara/onboard.json` — full Q&A audit trail with timestamps
-
-Prints a summary block showing all chosen values before exit.
+After all 9 answers: write `.mugiwara/config` (mode, branch, coverage,
+review_depth, quality_depth). Commit style defaults to `conventional`; CLI
+wizard (`bun scripts/onboard.ts`) also writes `commit` and can set a
+custom style. Print a summary of chosen values before exit.
 
 ## Before you start
 
-1. Verify the Luffy routing log at `.mugiwara/logs/` — this agent is dispatched by Luffy only.
-2. Check for existing `.mugiwara/config` to decide first-run vs re-onboard.
-3. Confirm the project root directory with Luffy before writing any files.
+Dispatched by Luffy only; check `.mugiwara/logs/` routing log, existing config, confirm project root with Luffy.
 
 ## Return to Luffy
 
-Report: config written with timestamp, summary of all 10 answers, any warnings (e.g., custom coverage values). Luffy uses this for wave 0 routing decisions.
+Report: config written with timestamp, all 9 answers, warnings (custom coverage). Luffy uses this for wave 0 routing.

package/content/agents/zoro-execution.md

@@ -41,6 +41,10 @@ Wave 3 of `mugiwara-workflow`, with the plan doc path.
 9. Todo list first: check off every plan task before touching code.
 10. Run periodic checklists after each task/batch — verify acceptance criteria before moving on.
 11. Resume smart: read `.mugiwara/continue.md` + todos before the first task; if continue.md exists, resume from its next_action, never re-run completed tasks. After each batch, update continue.md next_action to the next task.
+12. Accept source-edit delegation: any crew member (Luffy or artifacts-scope
+    agents) may delegate source edits to you via subagent dispatch or inline
+    embody. Accept and execute; never refuse scope-appropriate work. Brook
+    handles healing fixes — do not take healing work from Brook.
 
 ## Output
 

package/content/skills/mugiwara-backend/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mugiwara-backend
-description: Use for backend/server code — repo standards first, API design, data integrity, error handling, source-backed code. Match the codebase before judging it.
+description: Use for backend/server code — repo standards first, API endpoint design, data integrity, error handling, source-backed code. Match the codebase before judging it.
 ---
 
 # Backend (Sanji)

package/content/skills/mugiwara-brainstorm/SKILL.md

@@ -87,3 +87,10 @@ For UI directions, name slop risks (generic card grids, unmotivated gradients, t
 ## One sharp question rule
 
 If you cannot phrase the question as multiple choice with answerable options, you do not yet understand the decision — read the codebase until you can.
+
+## Red flags
+
+- Collapsing to fewer than three interrogation rounds before handoff.
+- Rubber-stamping ("yes, done") instead of options + trade-offs + recommendation.
+- Guessing a version or library capability without web research.
+- Handing off with a failing validation checklist.

package/content/skills/mugiwara-checkpoint/SKILL.md

@@ -20,7 +20,7 @@ Subagents lie. No evidence = not complete. A "done" claim is a starting point, n
 
 For every task in the completed wave, in order:
 
-1. **Per-task audit table.** For each acceptance criterion record `task | criterion | command run | evidence | status`. Evidence is output or a file path — never a paraphrase.
+1. **Per-task audit table.** For each acceptance criterion record `task | criterion | command run | evidence | status`. Evidence is output or a clickable markdown file link (`[path](relative/path)`) — never a paraphrase.
 2. **Dedupe re-runs.** Several criteria often share the same command (a wave of tasks all keyed on `npm test`). Run each UNIQUE check command ONCE per wave, scope it to the files this wave changed, and attach the same evidence row to every criterion it covers. Do not re-run the same suite N times for N tasks.
 3. **Scope by diff.** Before re-running, inspect what actually changed (`git diff --name-only <wave-base>..HEAD`). Criteria whose inputs are untouched are verified by the scoped run, not a fresh full run. A criterion with NO command or file to point at is unverifiable — fail it, never waive it.
 4. **Commit hygiene.** Run `git log --stat <wave-base>..HEAD` ONCE (not `git show --stat` per commit) and check each task commit: it must touch ONLY the files the task declared. Undeclared files added or declared files missing = fail.

package/content/skills/mugiwara-claim-audit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mugiwara-claim-audit
-description: Use for in-flight decisions cheap to verify now, costly later — CLAIM, EXTRACT, DOUBT, RECONCILE, STOP. Find what is wrong, do NOT validate.
+description: Use to double-check a done claim or in-flight decisions cheap to verify now, costly later — CLAIM, EXTRACT, DOUBT, RECONCILE, STOP. Find what is wrong, do NOT validate.
 ---
 
 # Doubt-driven development