@maestrofrontier/frontier 1.4.5 → 1.5.0

package/integrations/README.md

@@ -1,111 +1,111 @@
-# Maestro integrations — slash commands for other CLIs
-
-The Claude Code plugin ships Maestro's slash commands (`/maestro:*`) plus
-enforcement hooks and auto-run. Codex CLI/Desktop can install Maestro as a
-native plugin from the repo marketplace; after the Maestro Codex plugin is
-installed, enabled, and trusted, Frontier can auto-route normal Codex prompts
-when you arm a project/workspace scope. Other agent CLIs mostly support
-**custom slash commands** as prompt templates: they inject
-instruction text, but do not run wrapper logic, gate tools, or auto-run every
-prompt. Those ports are shortcuts around the portable `maestro frontier ...`
-CLI, not plugin equivalents.
-
-Portable integrations include `/frontier` and `/update`; Codex also installs
-`maestro-frontier`, `maestro-settings`, `maestro-terse`, and `maestro-update`
-skills. `/frontier` drives the portable engine (`maestro frontier ...`);
-`/update` refreshes the install. `context-bar` is Claude Code-specific, while
-settings and terse are available through Codex skills or the portable CLI. The
-orchestration doctrine itself needs no command — it lives in `AGENTS.md` and
-loads on demand.
-
-## Placement
-
-| Runtime | Source in this repo | Install to | Invoke |
-|---|---|---|---|
-| Cursor | `integrations/cursor/commands/frontier.md` | `.cursor/commands/frontier.md` (per-repo) or `~/.cursor/commands/` (global) | `/frontier` |
-| Codex (CLI + Desktop) | `skills/maestro-frontier/SKILL.md` in the plugin; `integrations/codex/skills/` mirrors the same files for portable installs | bundled by the `maestro@maestro` Codex plugin; portable fallback copies to `.agents/skills/<name>/SKILL.md` | ask for the Maestro skill |
-
-After adding a file, restart the tool or open a new chat so it loads.
-
-Use an explicit `--scope` flag when the runtime cannot autodetect one. Codex
-plugin contexts resolve a project/workspace scope automatically (`codex-<8hex>`),
-which is the recommended default for repo installs. For manual Codex commands,
-use `--scope codex-project` from the repo root to target that same active scope:
-
-```bash
-maestro frontier status --scope codex-project
-maestro frontier mode fusion --preset chatgpt-duo --scope codex-project
-maestro frontier mode fusion --preset frontier-trio --judge chatgpt --synth chatgpt --scope codex-project
-maestro frontier mode off --scope codex-project
-```
-
-Global/user scope is optional and should be intentional. Cursor uses
-`--scope cursor`, Cline uses `--scope cline`, Gemini uses `--scope gemini`, and
-Windsurf/Devin use `--scope windsurf`.
-
-## Updating portable installs
-
-Portable installs have no plugin system. Update = refresh the copied files from
-latest `main`.
-
-**If you cloned the Maestro repo:**
-
-```bash
-git -C <path-to-maestro-clone> pull
-```
-
-Then re-copy `frontier/` and the integration command files into your project.
-
-**If you copied files manually** (no clone), re-download from latest `main` and
-overwrite the copies in your project:
-
-```bash
-curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/AGENTS.md
-curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/frontier/cli.cjs
-curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/bin/maestro.cjs
-# Also re-copy the integration command file(s) you installed.
-```
-
-A `/update` shortcut command ships for each runtime — install it once and future
-updates are a single invocation:
-
-| Runtime | Source in this repo | Install to | Invoke |
-|---|---|---|---|
-| Cursor | `integrations/cursor/commands/update.md` | `.cursor/commands/update.md` (per-repo) or `~/.cursor/commands/` (global) | `/update` |
-| Codex (CLI + Desktop) | `integrations/codex/skills/maestro-update/SKILL.md` | `.agents/skills/maestro-update/SKILL.md` (project/workspace) or `~/.agents/skills/maestro-update/SKILL.md` (global/user) | ask for `maestro-update` |
-
-**Version model:** Maestro pins no version for portable files. Fetching from
-latest `main` always resolves the newest committed code — no manual version bump
-needed per release.
-
-## Caveats
-
-- **Auto-run parity varies.** Claude Code and Codex can auto-route after a mode is
-  armed. Cursor, Gemini, Cline, and Windsurf/Devin command ports are manual
-  shortcuts unless those runtimes add an equivalent trusted hook surface. Use
-  `maestro frontier run "<prompt>" ...` there for one-off panels.
-- **Codex uses plugin-bundled skills, not prompts.** Install the marketplace
-  once with `codex plugin marketplace add mbanderas/maestro`, then install
-  `maestro@maestro` with `codex plugin add maestro@maestro`. The portable
-  fallback `maestro install --target codex` still copies the
-  `maestro-frontier`, `maestro-terse`, `maestro-settings`, and
-  `maestro-update` skills to `.agents/skills/<name>/SKILL.md`
-  (project/workspace) or `~/.agents/skills/<name>/SKILL.md` (global/user).
-  Deprecated `~/.codex/prompts/*.md` prompt files remain compatibility bridges
-  only.
-- **Codex per-repo skill path:** `.agents/skills/<name>/SKILL.md` is the
-  repo-scoped option for Codex skills. The global path is
-  `~/.agents/skills/<name>/SKILL.md`.
-- **Maestro Frontier ON indicator (Codex only).** When
-  `maestro frontier status --scope codex-project` reports mode != off, the `maestro-frontier` skill
-  instructs Codex to lead its reply with `Maestro Frontier ON (<label>)` —
-  `single · <model>` or `fusion · <preset>`. When mode is off, no indicator line
-  appears. This is Codex-scoped only and has no effect on Claude Code.
-- **Engine location.** Plugin installs run the bundled engine from the
-  installed plugin; portable/manual installs run `maestro frontier ...` (or
-  `node bin/maestro.cjs frontier ...`) from the repo root, so the engine must
-  have been copied in during install.
-- **Windows + Gemini judge/synth.** `gemini` is fine as a panel member, but a poor
-  `--judge`/`--synth` on Windows (its arg-passing rejects the newline-bearing
-  judge/synth prompts, so the stage degrades). Use `opus` or `gpt-5.5` for
-  judge/synth on Windows.
+# Maestro integrations — slash commands for other CLIs
+
+The Claude Code plugin ships Maestro's slash commands (`/maestro:*`) plus
+enforcement hooks and auto-run. Codex CLI/Desktop can install Maestro as a
+native plugin from the repo marketplace; after the Maestro Codex plugin is
+installed, enabled, and trusted, Frontier can auto-route normal Codex prompts
+when you arm a project/workspace scope. Other agent CLIs mostly support
+**custom slash commands** as prompt templates: they inject
+instruction text, but do not run wrapper logic, gate tools, or auto-run every
+prompt. Those ports are shortcuts around the portable `maestro frontier ...`
+CLI, not plugin equivalents.
+
+Portable integrations include `/frontier` and `/update`; Codex also installs
+`maestro-frontier`, `maestro-settings`, `maestro-terse`, and `maestro-update`
+skills. `/frontier` drives the portable engine (`maestro frontier ...`);
+`/update` refreshes the install. `context-bar` is Claude Code-specific, while
+settings and terse are available through Codex skills or the portable CLI. The
+orchestration doctrine itself needs no command — it lives in `AGENTS.md` and
+loads on demand.
+
+## Placement
+
+| Runtime | Source in this repo | Install to | Invoke |
+|---|---|---|---|
+| Cursor | `integrations/cursor/commands/frontier.md` | `.cursor/commands/frontier.md` (per-repo) or `~/.cursor/commands/` (global) | `/frontier` |
+| Codex (CLI + Desktop) | `skills/maestro-frontier/SKILL.md` in the plugin; `integrations/codex/skills/` mirrors the same files for portable installs | bundled by the `maestro@maestro` Codex plugin; portable fallback copies to `.agents/skills/<name>/SKILL.md` | ask for the Maestro skill |
+
+After adding a file, restart the tool or open a new chat so it loads.
+
+Use an explicit `--scope` flag when the runtime cannot autodetect one. Codex
+plugin contexts resolve a project/workspace scope automatically (`codex-<8hex>`),
+which is the recommended default for repo installs. For manual Codex commands,
+use `--scope codex-project` from the repo root to target that same active scope:
+
+```bash
+maestro frontier status --scope codex-project
+maestro frontier mode fusion --preset chatgpt-duo --scope codex-project
+maestro frontier mode fusion --preset frontier-trio --judge chatgpt --synth chatgpt --scope codex-project
+maestro frontier mode off --scope codex-project
+```
+
+Global/user scope is optional and should be intentional. Cursor uses
+`--scope cursor`, Cline uses `--scope cline`, Gemini uses `--scope gemini`, and
+Windsurf/Devin use `--scope windsurf`.
+
+## Updating portable installs
+
+Portable installs have no plugin system. Update = refresh the copied files from
+latest `main`.
+
+**If you cloned the Maestro repo:**
+
+```bash
+git -C <path-to-maestro-clone> pull
+```
+
+Then re-copy `frontier/` and the integration command files into your project.
+
+**If you copied files manually** (no clone), re-download from latest `main` and
+overwrite the copies in your project:
+
+```bash
+curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/AGENTS.md
+curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/frontier/cli.cjs
+curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/bin/maestro.cjs
+# Also re-copy the integration command file(s) you installed.
+```
+
+A `/update` shortcut command ships for each runtime — install it once and future
+updates are a single invocation:
+
+| Runtime | Source in this repo | Install to | Invoke |
+|---|---|---|---|
+| Cursor | `integrations/cursor/commands/update.md` | `.cursor/commands/update.md` (per-repo) or `~/.cursor/commands/` (global) | `/update` |
+| Codex (CLI + Desktop) | `integrations/codex/skills/maestro-update/SKILL.md` | `.agents/skills/maestro-update/SKILL.md` (project/workspace) or `~/.agents/skills/maestro-update/SKILL.md` (global/user) | ask for `maestro-update` |
+
+**Version model:** Maestro pins no version for portable files. Fetching from
+latest `main` always resolves the newest committed code — no manual version bump
+needed per release.
+
+## Caveats
+
+- **Auto-run parity varies.** Claude Code and Codex can auto-route after a mode is
+  armed. Cursor, Gemini, Cline, and Windsurf/Devin command ports are manual
+  shortcuts unless those runtimes add an equivalent trusted hook surface. Use
+  `maestro frontier run "<prompt>" ...` there for one-off panels.
+- **Codex uses plugin-bundled skills, not prompts.** Install the marketplace
+  once with `codex plugin marketplace add mbanderas/maestro`, then install
+  `maestro@maestro` with `codex plugin add maestro@maestro`. The portable
+  fallback `maestro install --target codex` still copies the
+  `maestro-frontier`, `maestro-terse`, `maestro-settings`, and
+  `maestro-update` skills to `.agents/skills/<name>/SKILL.md`
+  (project/workspace) or `~/.agents/skills/<name>/SKILL.md` (global/user).
+  Deprecated `~/.codex/prompts/*.md` prompt files remain compatibility bridges
+  only.
+- **Codex per-repo skill path:** `.agents/skills/<name>/SKILL.md` is the
+  repo-scoped option for Codex skills. The global path is
+  `~/.agents/skills/<name>/SKILL.md`.
+- **Maestro Frontier ON indicator (Codex only).** When
+  `maestro frontier status --scope codex-project` reports mode != off, the `maestro-frontier` skill
+  instructs Codex to lead its reply with `Maestro Frontier ON (<label>)` —
+  `single · <model>` or `fusion · <preset>`. When mode is off, no indicator line
+  appears. This is Codex-scoped only and has no effect on Claude Code.
+- **Engine location.** Plugin installs run the bundled engine from the
+  installed plugin; portable/manual installs run `maestro frontier ...` (or
+  `node bin/maestro.cjs frontier ...`) from the repo root, so the engine must
+  have been copied in during install.
+- **Windows + Gemini judge/synth.** `gemini` is fine as a panel member, but a poor
+  `--judge`/`--synth` on Windows (its arg-passing rejects the newline-bearing
+  judge/synth prompts, so the stage degrades). Use `opus` or `gpt-5.5` for
+  judge/synth on Windows.

package/integrations/cline/skills/frontier/SKILL.md

@@ -1,75 +1,75 @@
----
-name: frontier
-description: Maestro Frontier local multi-CLI fusion engine — switch mode, or run a prompt through the panel
----
-
-Drive the **Maestro Frontier** engine — a zero-dependency local multi-CLI fusion
-engine (a parallel panel of local CLIs → a judge model's analysis → a grounded
-synthesis). It is the same engine the Claude Code plugin ships; here it runs
-through the `maestro` CLI with `--scope cline`.
-
-**Install path (pick one):**
-
-- Project-scoped: `.cline/skills/frontier/SKILL.md`
-- Global: `~/.cline/skills/frontier/SKILL.md`
-
-**This is a typing shortcut, not the Claude Code plugin.** Cline has no prompt
-hook, so arming a mode does **not** auto-run the engine on later prompts — it
-only persists the mode. To actually fuse a prompt, invoke `run` explicitly
-(step 3).
-
-When the user invokes this skill, map their request to one engine CLI call and
-run it in the terminal (Cline will request approval before executing). Do not
-edit the engine's state file by hand.
-
-## 1. Switch mode
-
-Persists to `~/.config/maestro/frontier-state.cline.json`; default `off`.
-`--scope cline` keeps Cline's armed mode independent from Claude Code, Codex,
-Cursor, and Gemini on the same machine:
-
-```bash
-maestro frontier mode off --scope cline
-maestro frontier mode single --model <model> --scope cline
-maestro frontier mode fusion --preset <preset> --scope cline
-maestro frontier mode fusion --preset custom --models <a,b,c> --scope cline
-maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope cline
-```
-
-Models: `opus` (Claude Opus 4.8, needs `claude`), `gpt-5.5` (needs `codex`),
-`gemini` (needs `gemini`). Presets: `opus-duo`, `opus-gpt`, `gpt-duo`,
-`frontier-trio`, `custom`. Judge + synth default to Opus; `--judge`/`--synth`
-override for any preset (e.g. `--judge opus --synth gpt-5.5`). `gpt-duo` runs
-judge + synth on GPT-5.5 — a Codex-only fusion that needs no `claude`.
-
-## 2. Show current mode/preset
-
-```bash
-maestro frontier status --scope cline
-```
-
-## 3. Run a prompt through the current mode
-
-This is the action that actually fuses, since nothing auto-runs here. Set a
-mode first (step 1), then:
-
-```bash
-maestro frontier run "<prompt>" --scope cline
-```
-
-- `off`: prints a notice, spawns nothing.
-- `single`: dispatches the one selected CLI, prints its answer.
-- `fusion`: runs the panel in parallel → judge → synthesizer; prints the final
-  answer (a one-line run meta goes to stderr). Report stdout verbatim.
-
-On error the engine prints `ERROR [<reason>]: <detail>` to stderr and exits
-non-zero — relay the reason.
-
-## Notes
-
-- Real `single`/`fusion` runs spawn local CLIs and cost tokens; use small prompts.
-  `off` is free.
-- Each model's CLI must be on `PATH`, or point at a specific build with
-  `MAESTRO_CLAUDE_BIN` / `MAESTRO_CODEX_BIN` / `MAESTRO_GEMINI_BIN`.
-- Requires `maestro` on `PATH` (installed during Maestro setup). If it is missing,
-  install Maestro first.
+---
+name: frontier
+description: Maestro Frontier local multi-CLI fusion engine — switch mode, or run a prompt through the panel
+---
+
+Drive the **Maestro Frontier** engine — a zero-dependency local multi-CLI fusion
+engine (a parallel panel of local CLIs → a judge model's analysis → a grounded
+synthesis). It is the same engine the Claude Code plugin ships; here it runs
+through the `maestro` CLI with `--scope cline`.
+
+**Install path (pick one):**
+
+- Project-scoped: `.cline/skills/frontier/SKILL.md`
+- Global: `~/.cline/skills/frontier/SKILL.md`
+
+**This is a typing shortcut, not the Claude Code plugin.** Cline has no prompt
+hook, so arming a mode does **not** auto-run the engine on later prompts — it
+only persists the mode. To actually fuse a prompt, invoke `run` explicitly
+(step 3).
+
+When the user invokes this skill, map their request to one engine CLI call and
+run it in the terminal (Cline will request approval before executing). Do not
+edit the engine's state file by hand.
+
+## 1. Switch mode
+
+Persists to `~/.config/maestro/frontier-state.cline.json`; default `off`.
+`--scope cline` keeps Cline's armed mode independent from Claude Code, Codex,
+Cursor, and Gemini on the same machine:
+
+```bash
+maestro frontier mode off --scope cline
+maestro frontier mode single --model <model> --scope cline
+maestro frontier mode fusion --preset <preset> --scope cline
+maestro frontier mode fusion --preset custom --models <a,b,c> --scope cline
+maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope cline
+```
+
+Models: `opus` (Claude Opus 4.8, needs `claude`), `gpt-5.5` (needs `codex`),
+`gemini` (needs `gemini`). Presets: `opus-duo`, `opus-gpt`, `gpt-duo`,
+`frontier-trio`, `custom`. Judge + synth default to Opus; `--judge`/`--synth`
+override for any preset (e.g. `--judge opus --synth gpt-5.5`). `gpt-duo` runs
+judge + synth on GPT-5.5 — a Codex-only fusion that needs no `claude`.
+
+## 2. Show current mode/preset
+
+```bash
+maestro frontier status --scope cline
+```
+
+## 3. Run a prompt through the current mode
+
+This is the action that actually fuses, since nothing auto-runs here. Set a
+mode first (step 1), then:
+
+```bash
+maestro frontier run "<prompt>" --scope cline
+```
+
+- `off`: prints a notice, spawns nothing.
+- `single`: dispatches the one selected CLI, prints its answer.
+- `fusion`: runs the panel in parallel → judge → synthesizer; prints the final
+  answer (a one-line run meta goes to stderr). Report stdout verbatim.
+
+On error the engine prints `ERROR [<reason>]: <detail>` to stderr and exits
+non-zero — relay the reason.
+
+## Notes
+
+- Real `single`/`fusion` runs spawn local CLIs and cost tokens; use small prompts.
+  `off` is free.
+- Each model's CLI must be on `PATH`, or point at a specific build with
+  `MAESTRO_CLAUDE_BIN` / `MAESTRO_CODEX_BIN` / `MAESTRO_GEMINI_BIN`.
+- Requires `maestro` on `PATH` (installed during Maestro setup). If it is missing,
+  install Maestro first.

package/integrations/codex/prompts/frontier.md

@@ -1,70 +1,70 @@
----
-description: Maestro Frontier local multi-CLI fusion engine — arm, disarm, inspect, or debug-run the panel
-argument-hint: "<off | single <model> | fusion <preset> | status | run <prompt>>"
----
-
-Drive the **Maestro Frontier** engine — a zero-dependency local multi-CLI fusion
-engine (a parallel panel of local CLIs → a judge model's analysis → a grounded
-synthesis). It is the same engine the Claude Code plugin ships; here it runs
-through the `maestro` CLI, installed into this repo during setup.
-
-When the Maestro Codex plugin hook is installed, enabled, and trusted, arming a
-non-`off` mode makes ordinary later Codex prompts auto-run through Frontier
-until disabled. Manual `run` remains available for advanced/debug one-offs.
-
-Requested action: `$ARGUMENTS`
-
-Map it to one engine CLI call and run it from the repo root. Do not edit
-the engine's state file by hand.
-
-1. Switch mode. Project/workspace scope is the default recommendation. Run from
-   the repo root with `--scope codex-project`; the CLI expands it to the same
-   `codex-<8hex>` scope the trusted Codex hook uses:
-
-   ```bash
-   maestro frontier mode off --scope codex-project
-   maestro frontier mode single --model <model> --scope codex-project
-   maestro frontier mode fusion --preset chatgpt-duo --scope codex-project
-   maestro frontier mode fusion --preset frontier-trio --judge chatgpt --synth chatgpt --scope codex-project
-   maestro frontier mode fusion --preset custom --models <a,b,c> --scope codex-project
-   ```
-
-   Models: `opus` (Claude Opus 4.8, needs `claude`), `gpt-5.5` (needs `codex`),
-   `gemini` (needs `gemini`). Presets: `opus-duo`, `opus-gpt`, `gpt-duo`,
-   `frontier-trio`, `custom`. Judge + synth default to Opus; `--judge`/`--synth`
-   override for any preset (e.g. `--judge opus --synth gpt-5.5`). `gpt-duo` runs
-   judge + synth on GPT-5.5 — a Codex-only fusion that needs no `claude`.
-   Friendly aliases are accepted: `chatgpt` -> `gpt-5.5`, and `chatgpt-duo` ->
-   `gpt-duo`.
-
-2. Show the current mode/preset:
-
-   ```bash
-   maestro frontier status --scope codex-project
-   ```
-
-3. Normal use after arming: type ordinary Codex prompts. The trusted hook
-   auto-runs Frontier and injects the synthesized answer as context.
-
-4. Advanced/debug one-off run:
-
-   ```bash
-   maestro frontier run "<prompt>" --scope codex-project
-   ```
-
-   - `off`: prints a notice, spawns nothing.
-   - `single`: dispatches the one selected CLI, prints its answer.
-   - `fusion`: runs the panel in parallel → judge → synthesizer; prints the final
-     answer (a one-line run meta goes to stderr). Report stdout verbatim.
-
-On error the engine prints `ERROR [<reason>]: <detail>` to stderr and exits
-non-zero — relay the reason.
-
-Notes:
-
-- Real `single`/`fusion` runs spawn local CLIs and cost tokens; use small prompts.
-  `off` is free.
-- Each model's CLI must be on `PATH`, or point at a specific build with
-  `MAESTRO_CLAUDE_BIN` / `MAESTRO_CODEX_BIN` / `MAESTRO_GEMINI_BIN`.
-- Requires `maestro` on `PATH` (installed during Maestro setup). If it is missing,
-  install Maestro first.
+---
+description: Maestro Frontier local multi-CLI fusion engine — arm, disarm, inspect, or debug-run the panel
+argument-hint: "<off | single <model> | fusion <preset> | status | run <prompt>>"
+---
+
+Drive the **Maestro Frontier** engine — a zero-dependency local multi-CLI fusion
+engine (a parallel panel of local CLIs → a judge model's analysis → a grounded
+synthesis). It is the same engine the Claude Code plugin ships; here it runs
+through the `maestro` CLI, installed into this repo during setup.
+
+When the Maestro Codex plugin hook is installed, enabled, and trusted, arming a
+non-`off` mode makes ordinary later Codex prompts auto-run through Frontier
+until disabled. Manual `run` remains available for advanced/debug one-offs.
+
+Requested action: `$ARGUMENTS`
+
+Map it to one engine CLI call and run it from the repo root. Do not edit
+the engine's state file by hand.
+
+1. Switch mode. Project/workspace scope is the default recommendation. Run from
+   the repo root with `--scope codex-project`; the CLI expands it to the same
+   `codex-<8hex>` scope the trusted Codex hook uses:
+
+   ```bash
+   maestro frontier mode off --scope codex-project
+   maestro frontier mode single --model <model> --scope codex-project
+   maestro frontier mode fusion --preset chatgpt-duo --scope codex-project
+   maestro frontier mode fusion --preset frontier-trio --judge chatgpt --synth chatgpt --scope codex-project
+   maestro frontier mode fusion --preset custom --models <a,b,c> --scope codex-project
+   ```
+
+   Models: `opus` (Claude Opus 4.8, needs `claude`), `gpt-5.5` (needs `codex`),
+   `gemini` (needs `gemini`). Presets: `opus-duo`, `opus-gpt`, `gpt-duo`,
+   `frontier-trio`, `custom`. Judge + synth default to Opus; `--judge`/`--synth`
+   override for any preset (e.g. `--judge opus --synth gpt-5.5`). `gpt-duo` runs
+   judge + synth on GPT-5.5 — a Codex-only fusion that needs no `claude`.
+   Friendly aliases are accepted: `chatgpt` -> `gpt-5.5`, and `chatgpt-duo` ->
+   `gpt-duo`.
+
+2. Show the current mode/preset:
+
+   ```bash
+   maestro frontier status --scope codex-project
+   ```
+
+3. Normal use after arming: type ordinary Codex prompts. The trusted hook
+   auto-runs Frontier and injects the synthesized answer as context.
+
+4. Advanced/debug one-off run:
+
+   ```bash
+   maestro frontier run "<prompt>" --scope codex-project
+   ```
+
+   - `off`: prints a notice, spawns nothing.
+   - `single`: dispatches the one selected CLI, prints its answer.
+   - `fusion`: runs the panel in parallel → judge → synthesizer; prints the final
+     answer (a one-line run meta goes to stderr). Report stdout verbatim.
+
+On error the engine prints `ERROR [<reason>]: <detail>` to stderr and exits
+non-zero — relay the reason.
+
+Notes:
+
+- Real `single`/`fusion` runs spawn local CLIs and cost tokens; use small prompts.
+  `off` is free.
+- Each model's CLI must be on `PATH`, or point at a specific build with
+  `MAESTRO_CLAUDE_BIN` / `MAESTRO_CODEX_BIN` / `MAESTRO_GEMINI_BIN`.
+- Requires `maestro` on `PATH` (installed during Maestro setup). If it is missing,
+  install Maestro first.

package/integrations/codex/prompts/update.md

@@ -1,39 +1,39 @@
----
-description: Update Maestro portable files to the latest committed code
-argument-hint: ""
----
-
-Refresh the Maestro portable install in this repository to the latest committed
-code from <https://github.com/mbanderas/maestro>.
-
-Maestro has no version pin for portable installs — fetching the latest `main`
-always resolves the newest committed code.
-
-**If this repo contains a git clone of the Maestro source**, run:
-
-```bash
-git -C <path-to-maestro-clone> pull
-```
-
-Then re-copy `frontier/` and any integration command files you use into this project.
-
-**If you downloaded and copied files manually** (no clone), re-fetch and re-copy
-from latest `main`:
-
-```bash
-curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/AGENTS.md
-curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/frontier/cli.cjs
-curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/bin/maestro.cjs
-# Re-copy any integration command files you installed:
-#   integrations/codex/prompts/frontier.md -> ~/.codex/prompts/frontier.md
-#   integrations/codex/prompts/update.md   -> ~/.codex/prompts/update.md
-```
-
-After updating, run `node bin/maestro.cjs frontier status` to confirm the engine is present.
-For Codex skills, managed Maestro copies refresh automatically, user-edited
-copies are preserved with next-step output, and older exact unprefixed Maestro
-skills may be migrated to compatibility shims.
-
-Report what was refreshed and note any errors.
-
-Do not edit any other files.
+---
+description: Update Maestro portable files to the latest committed code
+argument-hint: ""
+---
+
+Refresh the Maestro portable install in this repository to the latest committed
+code from <https://github.com/mbanderas/maestro>.
+
+Maestro has no version pin for portable installs — fetching the latest `main`
+always resolves the newest committed code.
+
+**If this repo contains a git clone of the Maestro source**, run:
+
+```bash
+git -C <path-to-maestro-clone> pull
+```
+
+Then re-copy `frontier/` and any integration command files you use into this project.
+
+**If you downloaded and copied files manually** (no clone), re-fetch and re-copy
+from latest `main`:
+
+```bash
+curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/AGENTS.md
+curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/frontier/cli.cjs
+curl -O https://raw.githubusercontent.com/mbanderas/maestro/main/bin/maestro.cjs
+# Re-copy any integration command files you installed:
+#   integrations/codex/prompts/frontier.md -> ~/.codex/prompts/frontier.md
+#   integrations/codex/prompts/update.md   -> ~/.codex/prompts/update.md
+```
+
+After updating, run `node bin/maestro.cjs frontier status` to confirm the engine is present.
+For Codex skills, managed Maestro copies refresh automatically, user-edited
+copies are preserved with next-step output, and older exact unprefixed Maestro
+skills may be migrated to compatibility shims.
+
+Report what was refreshed and note any errors.
+
+Do not edit any other files.