🚀

2026-07-19 20:30:34 -05:00
commit 5852f2ed4f
59 changed files with 6056 additions and 0 deletions
@@ -0,0 +1,26 @@
+---
+description: Install and verify the fusion-harness toolchain (pi, just, jq, uv, API keys)
+---
+
+# Purpose
+
+Install everything the fusion-harness needs and verify the harness launches.
+
+## Workflow
+
+1. Check each prerequisite binary and install the ones that are missing:
+   - `pi` — `npm install -g @earendil-works/pi-coding-agent`
+   - `just`, `jq`, `uv` — `brew install just jq uv` (macOS) or the user's package manager
+2. Check that `.env` exists at the repo root and contains non-placeholder values for
+   `ANTHROPIC_API_KEY` (architect) and `OPENAI_API_KEY` (builder). If it is missing or
+   holds placeholders, ask the user for keys — never invent or commit them. Note the
+   gotcha: `just`'s dotenv-load does NOT override variables already exported in the
+   shell, so a stale exported key silently wins over `.env`.
+3. Confirm the extension file loads by checking the entry point exists:
+   `extensions/fusion-harness/fusion-harness.ts` plus its sibling `SYSTEM_PROMPT_*.md`
+   and `USER_PROMPT_*.md` prompt files (the extension throws at load time if any prompt
+   file is missing).
+4. Tell the user to launch with `just fh-workhorse` (cheap test pair) and confirm the
+   ＦＵＳＩＯＮ ＨＡＲＮＥＳＳ boot banner renders. `just fh-sota` is the frontier
+   pair and costs real money.
+5. Report what was installed, what was already present, and anything still blocking.
@@ -0,0 +1,18 @@
+---
+description: Prime with foundational context for the fusion-harness Pi extension repo
+---
+
+# Purpose
+
+Orient yourself in fusion-harness: a clean-room Pi coding-agent extension that fuses two
+frontier models (ARCHITECT plans/fuses/validates, BUILDER builds) behind three slash
+commands, with a strict two-column output DX.
+
+## Workflow
+
+1. Run `git ls-files | sort` to see the full tree
+2. Read `README.md` for the repo-level overview — it covers the commands, flags, host-as-builder architecture, gate loop, and the two-column DX contract
+3. Note `extensions/fusion-harness/` is RUNTIME ONLY: the .ts plus the prompt files it loads. Docs live at the root README
+4. Read `justfile` for the run recipes and model configuration (WORKHORSE test pair vs SOTA fable/sol pair)
+5. Glob `extensions/fusion-harness/*_PROMPT_*.md` and skim 1-2 to see how default prompts are externalized with `{{VAR}}` interpolation
+6. Summarize your understanding of the project: purpose, stack, structure, key files, and entry points