fusionlisted

# Fusion — Claude + Codex (PLAN before code) ## Storage Run content (the brief, both leg reports, and the plan — draft first, the final version overwrites it) lives in one SQLite DB at `~/.fusion/fusion.db`; nothing is written into the project directory. Talk to it only through the bundled CLI `bun "${CLAUDE_SKILL_DIR}/fusion.ts" <command>` (`${CLAUDE_SKILL_DIR}` is supplied by Claude Code): - `start --title "<concise task title>"` — run the GPT preflight gate, then create the run; read `runId` from its JSON (`--title` is optional at the CLI boundary, but the workflow always supplies it). - `put --run-id <id> --type <brief|claude_report|codex_report|plan> --file <path>` — save content. - `get --run-id <id> --type <...>` — read content back (JSON `content` field). - `relay --run-id <id>` — launch the external Codex leg. - `finish --run-id <id>` — mark the run completed (after the final plan is saved). - `export --run-id <id> --type plan --out docs/X.md` — write ONE committed doc, on demand. - `list` — JSON of interrupted runs (status `running`) across all projects, newest first, each with which artifacts exist + any GPT drop reason. Powers RESUME. - `status --run-id <id>` — the same record for a single run (any status). - `abort --run-id <id>` — mark an interrupted run aborted (when the user gives up on it). - `dashboard` — run-history UI. > On success every command prints one JSON line on stdout (progress on stderr); on failure the > error goes to stderr and the command exi