@dotobokuri/fleet-cli 1.4.0 → 1.5.0

package/README.md

@@ -27,7 +27,7 @@ After installation, run `fleet` from any directory.
 ## Session Plugins
 
 Dedicated Claude and Codex sessions receive Fleet context through generated plugin assets rendered under `~/.fleet/marketplace/plugins/fleet`.
-The Fleet system prompt is injected at CLI launch time via temporary prompt files for Claude and a dedicated Codex profile, while provider-shared skill files and Claude subagent definitions are generated inside the plugin bundle from packaged assets. Built-in skills include Fleet Wiki usage plus the four protocol-mode skills used by the Admiral protocol gate: `fleet-protocol-trivial`, `fleet-protocol-standard`, `fleet-protocol-high-risk`, and `fleet-protocol-multi-agent`.
+The Fleet system prompt is injected at CLI launch time via temporary prompt files for Claude and a dedicated Codex profile, while provider-shared skill files and Claude subagent definitions are generated inside the plugin bundle from packaged assets. Built-in skills include Fleet Wiki usage plus the four protocol-mode skills used by the Admiral protocol gate: `protocol-baseline`, `protocol-midline`, `protocol-redline`, and `protocol-frontline`.
 The carrier and wiki MCP servers are not rendered into the plugin bundle; they are injected at spawn time as launch arguments (`--mcp-config` for Claude and `-c mcp_servers.*` for Codex).
 
 Claude launches with `--plugin-dir ~/.fleet/marketplace/plugins/fleet` and discovers enabled carrier agents from plugin `agents/*.md`.

package/assets/skills/{fleet-assumption-audit → assumption-audit}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: fleet-assumption-audit
+name: assumption-audit
 description: Resolve decision-shaped Context Confidence gate failures one blocking gap at a time before the active protocol re-applies its planning boundary.
 ---
 

package/assets/skills/{fleet-protocol-trivial → protocol-baseline}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: fleet-protocol-trivial
+name: protocol-baseline
 description: Use the compact Fleet protocol mode for simple, reversible, single-surface work.
 ---
 
-# Fleet Protocol: Trivial
+# Fleet Protocol: Baseline
 
 Use this mode only for simple, reversible, single-surface operational work.
 
@@ -11,7 +11,7 @@ At any point during the work, if a Downward Guard trigger appears, stop and re-c
 
 ## Checkpoints
 
-None. Selecting trivial implies Mission Anchor Compact Mode.
+None. Selecting baseline implies Mission Anchor Compact Mode.
 
 ## Reporting Cadence
 

package/assets/skills/{fleet-protocol-multi-agent → protocol-frontline}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: fleet-protocol-multi-agent
+name: protocol-frontline
 description: Use the coordinated Fleet protocol mode for multi-carrier or parallel ownership work.
 ---
 
-# Fleet Protocol: Multi-Agent
+# Fleet Protocol: Frontline
 
-Use this mode when operational work requires multiple Carriers, independent parallel workstreams, cross-carrier review loops, or file ownership coordination. If the work is high risk but single-owner, use `fleet-protocol-high-risk` instead.
+Use this mode when operational work requires multiple Carriers, independent parallel workstreams, cross-carrier review loops, or file ownership coordination. If the work is high risk but single-owner, use `protocol-redline` instead.
 
 ## Checkpoints
 

package/assets/skills/{fleet-protocol-standard → protocol-midline}/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: fleet-protocol-standard
+name: protocol-midline
 description: Use the normal Fleet protocol mode for bounded operational work without downward-guard triggers.
 ---
 
-# Fleet Protocol: Standard
+# Fleet Protocol: Midline
 
 Use this mode for ordinary bounded operational work.
 

package/assets/skills/{fleet-protocol-high-risk → protocol-redline}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: fleet-protocol-high-risk
+name: protocol-redline
 description: Use the risk-controlled Fleet protocol mode for irreversible, structural, multi-module, or prompt-policy work.
 ---
 
-# Fleet Protocol: High Risk
+# Fleet Protocol: Redline
 
-Use this mode for irreversible operations, structural/API changes, cross-module edits, doctrine or prompt-policy edits, security-sensitive work, or any operational request needing explicit risk controls. Escalate to `fleet-protocol-multi-agent` when multiple Carriers or parallel ownership boundaries are required.
+Use this mode for irreversible operations, structural/API changes, cross-module edits, doctrine or prompt-policy edits, security-sensitive work, or any operational request needing explicit risk controls. Escalate to `protocol-frontline` when multiple Carriers or parallel ownership boundaries are required.
 
 ## Checkpoints
 
@@ -27,7 +27,7 @@ Confirm each readiness check below before the Workflow. Work through them in ord
 - [ ] **Impact radius** — flag public-surface or API impact, irreversibility, and any security-sensitive surface. → report `impact: <…>`
 - [ ] **Rollback** — identify a rollback-safe checkpoint and any Admiral of the Navy approval point before execution begins. → report `rollback: <…>`
 - [ ] **Isolation** — confirm a working branch or worktree isolates the change; no direct work on the default branch. → report `isolation: <branch>`
-- [ ] **Escalation** — if multiple carriers or parallel ownership boundaries are required, re-classify under multi-agent. → report `escalation: clear`
+- [ ] **Escalation** — if multiple carriers or parallel ownership boundaries are required, re-classify under frontline. → report `escalation: clear`
 
 ## Workflow