@ionivetech/mugiwara 0.5.4 → 0.6.0

package/docs/getting-started.md

@@ -1,158 +0,0 @@
-# Getting Started
-
-Install the crew, run your first mission, and understand what you're looking at
-in the chat.
-
-## 1. Install
-
-Pick your harness — every major one is supported. The two easiest:
-
-**opencode** — add the plugin to `opencode.json`:
-
-```json
-{ "plugin": ["@ionivetech/mugiwara"] }
-```
-
-**Claude Code** — via the marketplace:
-
-```bash
-/plugin marketplace add ionivetech/mugiwara
-/plugin install mugiwara
-```
-
-| Harness | Install command |
-|---------|----------------|
-| Claude Code | `/plugin marketplace add ionivetech/mugiwara` then `/plugin install mugiwara` |
-| opencode | `{ "plugin": ["@ionivetech/mugiwara"] }` in `opencode.json` |
-| GitHub Copilot | `copilot plugin marketplace add ionivetech/mugiwara` then `copilot plugin install mugiwara` |
-| Gemini CLI | `gemini extensions install https://github.com/ionivetech/mugiwara` |
-| Codex | `codex plugin marketplace add ionivetech/mugiwara` then `codex plugin add mugiwara@mugiwara` |
-| Cursor | `/add-plugin mugiwara` |
-| Kimi Code | `/plugins install https://github.com/ionivetech/mugiwara` |
-| pi | `pi install git:github.com/ionivetech/mugiwara` |
-| Windsurf, Cline, Kilo, Antigravity | `npx @ionivetech/mugiwara@latest --project . --target <id> --yes` |
-
-Or the CLI for any target:
-
-```bash
-npx @ionivetech/mugiwara@latest --project ./my-app --target all --yes
-```
-
-Requires **Node.js >= 20.11**. Bun is optional (build-from-source only).
-
-## 2. Start a mission
-
-The workflow **auto-activates** at session start. The crew announces itself,
-then give any non-trivial request.
-
-### Small: lane 0–1
-
-```
-> fix the date formatting bug in src/utils/format.ts
-```
-
-Luffy routes it to **Lane 1** (Lean). Zoro reproduces and fixes, Sanji runs
-format + lint + tests. Two waves, visible as compact checkpoint reports. No
-nine-wave ceremony for a one-file bug.
-
-That's lane sizing: the process scales to the work. A typo (Lane 0) runs zero
-waves — the fix happens directly.
-
-### Medium: lane 2
-
-```
-> add a search bar to the products page
-```
-
-Touches frontend + API. Luffy routes to **Lane 2** (Standard). Nami plans 1
-wave with 3-5 tasks, Zoro executes test-first, Chopper audits every criterion,
-Sanji and Franky gate, Robin and Jinbe review.
-
-### Large: lane 3
-
-```
-> add role-based access control to the API
-```
-
-Touches auth — Luffy routes to **Lane 3** (Full). All 9 waves run. Nami plans
-the migration, Zoro executes, Chopper audits, Sanji tests, Franky gates, Robin
-reviews the diff with a breaking-change map, Jinbe runs STRIDE + OWASP, Brook
-heals any failures (max 3 cycles), Luffy closes with a mission report + push +
-ready PR summary.
-
-```
-  Wave 0  Luffy   triage → route: full pipe (auth/ touched)
-  Wave 2  Nami    plan   → .mugiwara/plans/2026-08-10-rbac.md (2 waves, 5 tasks)
-  Wave 3  Zoro    execute→ 5 tasks, evidence per task
-  Wave 4  Chopper audit  → PASS: all criteria met, commit hygiene clean
-  Wave 5  Sanji   quality → PASS: lint 0, 312 tests green
-  Wave 6  Franky  gates  → PASS: new 94%, modified 87%, build green
-  Wave 7  Robin   review → 2 minor findings (batched)
-  Wave 7  Jinbe   security→ PASS: STRIDE clean, 0 high
-  Wave 9  Luffy   closure→ mission report + push + ready PR summary
-```
-
-The crew runs **inline** in your main conversation — every wave reports as a
-compact checkpoint. Subagents only for parallel task batches.
-
-Prefer to drive stages yourself? Every stage has a slash command:
-`/mugiwara-plan`, `/mugiwara-execute`, `/mugiwara-review`,
-`/mugiwara-security`, `/mugiwara-heal`, `/mugiwara-ship`. Jump into any stage.
-
-## 3. What you do during a mission
-
-Almost nothing in `guided` mode:
-
-- Answer Nami's clarifying questions (one batched round before planning).
-- Give the plan an explicit GO when presented.
-- Review Brook's rollback note if a risky fix is proposed.
-- In every mode, **open the PR at the end** — the crew pushes the branch and
-  hands you a verdict file with a ready PR summary. The crew never creates a
-  PR, merges, or deploys.
-
-Switch to `semi` or `auto` if you want the crew to self-manage branch, commits,
-and ambiguities. See [modes](modes.md).
-
-## 4. The `.mugiwara/` workspace
-
-Every mission writes to `.mugiwara/` at the repo root:
-
-```
-.mugiwara/
-├── config          # mode, branch, commit, base, coverage thresholds
-├── state.json      # computed at every wave boundary by scripts/savepoint.sh
-├── spec/           # brainstorm output
-├── plans/          # clean execution plan (source of truth from Wave 2)
-├── results/        # audit, quality, gate, closure reports + evidence logs
-├── reports/        # human-readable mission reports
-├── review/         # review + security findings
-├── issues/         # blocker ledger
-├── refs/           # full skill/agent bodies for glob-loading harnesses
-└── logs/           # decision log + cross-mission lessons
-```
-
-**Savepoint** runs at every wave boundary — `state.json` carries lane, wave,
-files, blockers, heal cycle, and token budget. Resume reads one file instead of
-six. See [audit-trail.md](audit-trail.md) for the full artifact map.
-
-## 5. Configuration
-
-`.mugiwara/config` (project) overrides `~/.mugiwara/config` (global):
-
-| Key | Default | What it controls |
-|-----|---------|-----------------|
-| `mode` | guided | Autonomy: guided/semi/auto |
-| `branch` | `feature/{type}-{issue}-{slug}` | Branch naming pattern |
-| `commit` | conventional | Commit style: conventional/gitmoji/plain |
-| `base` | main | PR target branch |
-| `coverage_new` | 90 | Coverage % for new files |
-| `coverage_modified` | 80 | Coverage % for modified files |
-
-## 6. Next steps
-
-- Meet the [crew](agents.md) — 14 agents with permission boundaries.
-- Browse the [skills](skills.md) — 26 skills with the 3-layer disclosure model.
-- Understand the [lanes](lanes.md) — how work is sized before it runs.
-- Set your [mode](modes.md) — guided/semi/auto.
-- Read the [audit trail](audit-trail.md) — every artifact and how to review it.
-- See the [compliance matrix](compliance-matrix.md) — rule compliance per model.

package/docs/git-strategy.md

@@ -1,62 +0,0 @@
-# Git Strategy
-
-Commits, branches, save-points — and why the executor commits, not the closer.
-
-## Who commits and when
-
-**Zoro commits during execution, per logical task.** The executor is the one
-making the changes, so it commits at the moment each unit of work passes its
-acceptance criteria. This gives:
-
-- **Save-points** — rollback is one `git reset --hard <save-point>` away.
-- **Reversibility** — every commit is one logical change you can name.
-- **Bisectability** — a regression points at the exact commit that introduced it.
-
-Luffy does NOT re-commit at closure. The closer pushes the mission branch and
-writes the PR verdict — re-slicing history at the end means one giant diff, no
-save-points, and a painful bisect.
-
-## Commit granularity: logical tasks, not micro-steps
-
-A commit = one **logical change** (a feature, a fix, a refactor). The plan's
-tasks are sized at that granularity — see `mugiwara-planning`.
-
-- Adjacent trivial changes (typo, formatting, one-line tweak) fold into the
-  neighboring logical task's commit.
-- Never one commit per keystroke; never a wave of micro-commits.
-- If the plan slices finer than a logical change, group adjacent tasks into one
-  commit and note the grouping in the execution report.
-
-## The rules (from `mugiwara-git`)
-
-1. **Atomic commits.** One logical change per commit; each commit compiles and
-   passes the relevant checks — never commit a broken tree.
-2. **Exact staging.** `git add` specific files and paths, never `git add -A`
-   sweeping an unrelated commit.
-3. **Save-points before risky work.** Commit the working state with a naming
-   intent message (`checkpoint: before renderer migration`) before refactors,
-   migrations, or merges.
-4. **Match repo style.** Inspect `git log --oneline -20` before the first
-   commit and copy the observed conventions (prefix style, case, body usage).
-5. **Never commit secrets.** Scan for `.env*`, keys, tokens before every
-   commit. A secret already committed = treat as compromised, rotate, purge,
-   file a security finding.
-
-## Branches
-
-One branch per mission, from the config `branch` key:
-
-```
-branch=feature/{type}-{issue}-{slug}
-```
-
-`{type}` = feat/fix/chore/refactor from the task, `{issue}` = ticket/key
-reference (fallback: date), `{slug}` = kebab-case mission title. Created before
-the first task commit; never force-push once pushed. No mugiwara-prefixed
-branch names.
-
-## Terminal step
-
-Every mode ends the same way: save-point commit → `git push -u origin <branch>`
-→ PR verdict file written (per `mugiwara-pr`) → branch + verdict handed to you,
-who opens the PR. The crew never creates a PR, merges, or deploys.

package/docs/harness-matrix.md

@@ -1,41 +0,0 @@
-# Harness Matrix
-
-What actually differs per harness tier. Every skill and agent file ships to every harness, but behavior differs in three tiers.
-
-| Tier | Harnesses | Skills | Agents | `references/` | Scope |
-|------|-----------|--------|--------|:---:|-------|
-| **1** | Claude Code, opencode | Native, auto-trigger per skill | Real, dispatchable | Yes | global + project |
-| **2** | Gemini, Codex, Copilot | Full body in rules dir + bootstrap pointer | Markdown only | Yes | project only |
-| **3** | Windsurf, Cline, Kilo, Antigravity | Stub; body in `.mugiwara/refs/` | Stub | Yes | project only |
-
-## Behavioral differences
-
-### Tier 1 — Full
-
-- Skills auto-trigger when `description` frontmatter matches the task.
-- Agents are dispatchable subagents with isolation.
-- Progressive disclosure works: description → body → `references/`.
-- Global scope supported — install once, use in every project.
-
-### Tier 2 — Skills only
-
-- Agent files are markdown — the main thread embodies the persona, no subagent dispatch.
-- Skills load as rules files; the model chooses which to read per task.
-- **Project scope only** — `generic.ts` throws on global scope.
-- `references/` files are copied to `.mugiwara/refs/` and reachable.
-
-### Tier 3 — Stubs
-
-- Rule directories get **stub files** — the frontmatter and a pointer to `.mugiwara/refs/`.
-- Full body is loaded only when the agent opens the reference file.
-- Saves ~40k tokens of glob-load. Trade: the model must decide to open the ref.
-- **Project scope only.**
-- `references/` files are copied to `.mugiwara/refs/` — depth is available, just not auto-loaded.
-- Wave-boundary state flush: savepoint writes `state.json` so the model has computed state to resume from.
-
-## What's the same everywhere
-
-- All 32 (→ 26) skill directories ship to every harness.
-- All 15 agent markdown files ship to every harness.
-- `references/` files are always copied.
-- The workflow, lane sizing, and evidence discipline are identical — the difference is in how the model loads them.

package/docs/index.md

@@ -1,56 +0,0 @@
-# Mugiwara Docs
-
-The Straw Hat crew of AI agents and skills. These docs cover what the crew is,
-how to adopt it, and how each harness installs it. The crew is markdown plus a
-small Node CLI (`mugiwara`) — no daemons, nothing to host. It ships **15
-agents** and **32 skills**, and the workflow **auto-activates** at session
-start — a non-trivial request runs the pipeline by itself, with
-`/using-mugiwara` as an optional explicit router. Work is **sized to a lane**
-before it runs: small fixes skip the pipeline, sensitive changes run the full
-nine waves, and every wave passes only on **evidence**, never on a spoken
-claim.
-
-## Start here
-
-| Doc | What it covers |
-|-----|----------------|
-| [Getting started](getting-started.md) | Install, first mission, what you see in the chat |
-| [Adoption guide](adoption-guide.md) | Pick the harness, pick the mode, fit the crew to your workflow |
-| [Modes](modes.md) | guided / semi / auto — the autonomy levels, what each asks you |
-| [Config](config.md) | Full reference for `.mugiwara/config` keys and commit styles |
-| [Auto-PR](pr-summary.md) | What the crew hands off at closure: push + a ready-to-paste PR summary (it never creates a PR) |
-| [The crew](agents.md) | All 14 agents and when to summon each |
-| [The techniques](skills.md) | All 32 skills and what each enforces |
-| [The wave pipeline](workflow.md) | How a mission flows Wave 0 → Wave 9 |
-| [Execution model](execution-model.md) | Inline-by-default: why the crew runs in your main conversation |
-| [Lanes & sizing](lanes.md) | How Luffy sizes work at triage: Lane 0–4, escalation, budget |
-| [Enforcement](enforcement.md) | Skip gates, evidence over claims, and capability tiers |
-| [Git discipline](git-strategy.md) | Commits, branches, save-points — and why the executor commits |
-
-## Install by harness
-
-| Harness | Guide |
-|---------|-------|
-| Claude Code | [claude-setup.md](claude-setup.md) |
-| opencode | [opencode-setup.md](opencode-setup.md) |
-| GitHub Copilot | [copilot-setup.md](copilot-setup.md) |
-| Gemini CLI | [gemini-setup.md](gemini-setup.md) |
-| Codex | [codex-setup.md](codex-setup.md) |
-| Cursor | [cursor-setup.md](cursor-setup.md) |
-| Windsurf | [windsurf-setup.md](windsurf-setup.md) |
-| Cline / Kilo / Antigravity | [rule-based-setup.md](rule-based-setup.md) |
-
-## Reference
-
-| Doc | What it covers |
-|-----|----------------|
-| [Skill anatomy](skill-anatomy.md) | How a mugiwara skill file is structured |
-| [Agent anatomy](agent-anatomy.md) | How a mugiwara agent file is structured |
-| [Troubleshooting](troubleshooting.md) | Common problems and how to fix them |
-| [Developer onboarding](developer-onboarding.md) | Repo layout, validation, tests, contributing |
-
-## Resources
-
-- GitHub: <https://github.com/ionivetech/mugiwara>
-- npm: <https://www.npmjs.com/package/@ionivetech/mugiwara>
-- License: MIT

package/docs/install-antigravity.md

@@ -1,45 +0,0 @@
-# Antigravity Install
-
-Mugiwara installs as an Antigravity plugin from this repo.
-
-## Prerequisites
-
-- [Antigravity](https://antigravity.google) installed
-
-## Install
-
-```bash
-agy plugin install https://github.com/ionivetech/mugiwara
-```
-
-## How it works
-
-Antigravity reads `.agents/plugins/marketplace.json` and installs the plugin
-from the repo root. Skills and agents are auto-discovered.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-Reinstall with the same command:
-
-```bash
-agy plugin install https://github.com/ionivetech/mugiwara
-```
-
-## Uninstall
-
-```bash
-agy plugin uninstall mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [docs/config.md](config.md).

package/docs/install-claude.md

@@ -1,75 +0,0 @@
-# Claude Code Install
-
-Mugiwara is a full Claude Code native plugin with agents, skills, and a
-session-start hook.
-
-## Prerequisites
-
-- [Claude Code](https://claude.ai/code) installed
-- Node.js >= 20.11
-
-## Install
-
-```bash
-/plugin marketplace add ionivetech/mugiwara && /plugin install mugiwara@mugiwara
-```
-
-## How it works
-
-Claude Code clones the repo and reads from:
-
-- `skills/` and `agents/` — symlinks to `content/skills/` and
-  `content/agents/`. Claude Code auto-discovers all 26 skills and 14 agents.
-- `hooks/hooks.json` — defines a SessionStart hook that runs
-  `hooks/session-start.ts`, injecting the crew announce header at every
-  session start.
-
-The hook announces: "Mugiwara crew available. The workflow auto-activates
-for non-trivial requests..."
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-Or start any task — the crew auto-activates at session start.
-
-## Update
-
-```
-/plugin update mugiwara
-```
-
-## Uninstall
-
-```
-/plugin uninstall mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [docs/config.md](config.md).
-
-Switch autonomy mode with `/mugiwara-mode guided|semi|auto`.
-
-## Troubleshooting
-
-### Plugin not showing up
-
-1. Verify marketplace is registered: `/plugin marketplace list`
-2. If not, re-run the marketplace add command
-3. Check Claude Code is up to date
-
-### Skills not found
-
-1. Check that `skills/` and `agents/` symlinks resolve correctly
-2. Reinstall: `/plugin uninstall mugiwara` then reinstall
-
-### Hook not running
-
-The session-start hook requires Claude Code plugin hook support. Ensure
-you're on a recent Claude Code version.

package/docs/install-cli.md

@@ -1,103 +0,0 @@
-# CLI Install (Windsurf, Cline, Kilo)
-
-These platforms don't have native plugin systems. Use the mugiwara CLI
-installer to copy files into the platform's config directory.
-
-## Prerequisites
-
-- Node.js >= 20.11
-
-## Install
-
-```bash
-npx @ionivetech/mugiwara@latest install --target <id> --yes
-```
-
-Replace `<id>` with one of: `windsurf`, `cline`, `kilo`.
-
-Or install globally first:
-
-```bash
-npm i -g @ionivetech/mugiwara
-mugiwara install --target <id> --yes
-```
-
-### What gets written
-
-| Target | Skills/agents | References | Bootstrap |
-|--------|---------------|------------|-----------|
-| Windsurf | `.devin/rules/*.md` (stubs) | `.mugiwara/refs/*.md` | — |
-| Cline | `.clinerules/*.md` (stubs) | `.mugiwara/refs/*.md` | — |
-| Kilo | `.kilo/rules/*.md` (stubs) | `.mugiwara/refs/*.md` | `kilo.jsonc` |
-
-Tier 3 targets use stubs (pointer + routing) to keep rule files small.
-Full skill bodies live in `.mugiwara/refs/` — the agent loads them on demand.
-
-### Interactive mode
-
-Drop `--yes` for the interactive wizard:
-
-```bash
-npx @ionivetech/mugiwara install
-```
-
-Pick scope (global/project), target(s), and confirm before writing.
-
-### Multiple targets
-
-```bash
-npx @ionivetech/mugiwara install --target windsurf,cline,kilo --yes
-```
-
-Or all available targets:
-
-```bash
-npx @ionivetech/mugiwara install --target all --yes
-```
-
-## Verify
-
-Ask your agent:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-```bash
-mugiwara update
-# or: npx @ionivetech/mugiwara@latest update
-```
-
-## Uninstall
-
-```bash
-mugiwara uninstall
-```
-
-## Global install
-
-```bash
-mugiwara install --global --target <id> --yes
-```
-
-Installs to `~/.devin/rules/` (Windsurf), `~/.clinerules/` (Cline), or
-`~/.kilo/rules/` (Kilo).
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [docs/config.md](config.md).
-
-## CLI reference
-
-```bash
-mugiwara install                                  # wizard (interactive)
-mugiwara install --project . --target all --yes   # non-interactive
-mugiwara update                                   # replace existing files
-mugiwara uninstall                                # remove what manifest recorded
-mugiwara list                                     # show installations
-mugiwara reset --keep-logs                        # wipe mission state, keep lessons
-mugiwara reset --force                            # override multi-actor guard
-```

package/docs/install-codex.md

@@ -1,44 +0,0 @@
-# Codex Install
-
-Mugiwara installs as a native Codex plugin.
-
-## Prerequisites
-
-- [Codex](https://github.com/openai/codex) CLI or app installed
-
-## Install
-
-```bash
-codex plugin marketplace add ionivetech/mugiwara && codex plugin add mugiwara@mugiwara
-```
-
-## How it works
-
-Codex reads `.codex-plugin/plugin.json` which references `content/skills/`.
-All 26 skills are auto-discovered. Agents come from `content/agents/` via the
-`agents/` symlink.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-```bash
-codex plugin update mugiwara
-```
-
-## Uninstall
-
-```bash
-codex plugin remove mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [docs/config.md](config.md).

package/docs/install-copilot.md

@@ -1,45 +0,0 @@
-# GitHub Copilot Install
-
-Mugiwara installs as a Copilot plugin directly from the GitHub repo.
-
-## Prerequisites
-
-- [GitHub Copilot](https://docs.github.com/en/copilot) extension installed
-
-## Install
-
-```bash
-copilot plugin install https://github.com/ionivetech/mugiwara
-```
-
-## How it works
-
-Copilot clones the repo and auto-discovers skills from `content/skills/`
-and agents from `content/agents/`.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-Reinstall with the same command:
-
-```bash
-copilot plugin install https://github.com/ionivetech/mugiwara
-```
-
-## Uninstall
-
-```bash
-copilot plugin uninstall mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [docs/config.md](config.md).

package/docs/install-cursor.md

@@ -1,45 +0,0 @@
-# Cursor Install
-
-Mugiwara installs through Cursor's plugin marketplace.
-
-## Prerequisites
-
-- [Cursor](https://cursor.com) installed
-
-## Install
-
-```
-/add-plugin mugiwara
-```
-
-## How it works
-
-Cursor reads `.cursor-plugin/plugin.json` and auto-discovers skills from
-`content/skills/`.
-
-## Verify
-
-Ask:
-
-```
-what mugiwara crew members are available?
-```
-
-## Update
-
-Re-run:
-
-```
-/add-plugin mugiwara
-```
-
-## Uninstall
-
-```
-/remove-plugin mugiwara
-```
-
-## Configuration
-
-After install, configure mugiwara in `.mugiwara/config` (project) or
-`~/.mugiwara/config` (global). See [docs/config.md](config.md).