Runtime Context

Before any subcommand, resolve paths:

PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$(ls -d "$HOME/.claude/plugins/cache/ops-marketplace/ops"/*/ 2>/dev/null | sort -V | tail -1)}"
STATUSLINE_CMD="$HOME/.claude/statusline-command.sh"
STATUSLINE_CFG="$HOME/.claude/statusline.config.json"
THEMES_FILE="${PLUGIN_ROOT}templates/statusline/themes.json"
SETTINGS_FILE="$HOME/.claude/settings.json"
SUGGEST_BIN="${PLUGIN_ROOT}bin/ops-statusline-suggest"

---

OPS ► STATUSLINE

Load ops-rules before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If AskUserQuestion / Workflow are missing, follow Rule 10 in ops-rules (Hermes: numbered options / two-turn Telegram card; delegate_task).

Manages the Claude Code cockpit statusline, a 3-line terminal status bar showing context-window health, quota gauges, burn rate, git branch, fleet state, sys metrics, and per-project ops badges.

Parse $ARGUMENTS and route:

Argument (first word)	Action
preview or empty	Render a sample output at current terminal width
config	Re-run the wizard: preset, theme, projects, gauge widths
theme <name>	Switch theme in config
doctor	Validate config, settings.json wiring, renderer path
reset	Restore default config from template
(anything else)	Show help + current status

---

Subcommand: preview

Render the statusline using the current config against a built-in sample payload. Never touches real config or settings files.

Step 1, Build sample payload