@maestrofrontier/frontier 1.4.4 → 1.5.0

package/integrations/gemini/commands/frontier.toml

@@ -1,76 +1,76 @@
-# Maestro Frontier — Gemini CLI custom command
-#
-# Install path (pick one):
-#   Project-scoped : <project>/.gemini/commands/frontier.toml
-#   Global         : ~/.gemini/commands/frontier.toml
-#
-# Once installed, invoke with `/frontier <args>` inside the Gemini CLI.
-# This command arms or queries the Maestro Frontier engine with
-# `--scope gemini`, keeping Gemini's state independent from Claude Code,
-# Codex, and Cursor on the same machine.
-#
-# Requires `maestro` on PATH (installed during Maestro setup).
-
-description = "Maestro Frontier local multi-CLI fusion engine — switch mode, or run a prompt through the panel"
-
-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 with `--scope gemini`.
-
-**This is a typing shortcut, not the Claude Code plugin.** Gemini CLI 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).
-
-Requested action: {{args}}
-
-Map it to one engine CLI call and execute it. Do not edit the engine's state
-file by hand.
-
-1. Switch mode (persists to `~/.config/maestro/frontier-state.gemini.json`; default `off`).
-   `--scope gemini` keeps Gemini's armed mode independent from Claude Code, Codex,
-   and Cursor on the same machine:
-
-   !{maestro frontier mode off --scope gemini}
-   !{maestro frontier mode single --model <model> --scope gemini}
-   !{maestro frontier mode fusion --preset <preset> --scope gemini}
-   !{maestro frontier mode fusion --preset custom --models <a,b,c> --scope gemini}
-   !{maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope gemini}
-
-   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 the current mode/preset:
-
-   !{maestro frontier status --scope gemini}
-
-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:
-
-   !{maestro frontier run "{{args}}" --scope gemini}
-
-   - `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`.
-- On Windows, `gemini` is a poor `--judge`/`--synth` choice: judge/synth prompts
-  contain newlines that the win32 arg-safety guard refuses. Use `opus` or `gpt-5.5`
-  for judge/synth on Windows.
-- Requires `maestro` on `PATH` (installed during Maestro setup). If it is missing,
-  install Maestro first.
-"""
+# Maestro Frontier — Gemini CLI custom command
+#
+# Install path (pick one):
+#   Project-scoped : <project>/.gemini/commands/frontier.toml
+#   Global         : ~/.gemini/commands/frontier.toml
+#
+# Once installed, invoke with `/frontier <args>` inside the Gemini CLI.
+# This command arms or queries the Maestro Frontier engine with
+# `--scope gemini`, keeping Gemini's state independent from Claude Code,
+# Codex, and Cursor on the same machine.
+#
+# Requires `maestro` on PATH (installed during Maestro setup).
+
+description = "Maestro Frontier local multi-CLI fusion engine — switch mode, or run a prompt through the panel"
+
+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 with `--scope gemini`.
+
+**This is a typing shortcut, not the Claude Code plugin.** Gemini CLI 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).
+
+Requested action: {{args}}
+
+Map it to one engine CLI call and execute it. Do not edit the engine's state
+file by hand.
+
+1. Switch mode (persists to `~/.config/maestro/frontier-state.gemini.json`; default `off`).
+   `--scope gemini` keeps Gemini's armed mode independent from Claude Code, Codex,
+   and Cursor on the same machine:
+
+   !{maestro frontier mode off --scope gemini}
+   !{maestro frontier mode single --model <model> --scope gemini}
+   !{maestro frontier mode fusion --preset <preset> --scope gemini}
+   !{maestro frontier mode fusion --preset custom --models <a,b,c> --scope gemini}
+   !{maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope gemini}
+
+   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 the current mode/preset:
+
+   !{maestro frontier status --scope gemini}
+
+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:
+
+   !{maestro frontier run "{{args}}" --scope gemini}
+
+   - `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`.
+- On Windows, `gemini` is a poor `--judge`/`--synth` choice: judge/synth prompts
+  contain newlines that the win32 arg-safety guard refuses. Use `opus` or `gpt-5.5`
+  for judge/synth on Windows.
+- Requires `maestro` on `PATH` (installed during Maestro setup). If it is missing,
+  install Maestro first.
+"""

package/integrations/windsurf/workflows/frontier.md

@@ -1,70 +1,70 @@
-Maestro Frontier — drive the 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 windsurf`.
-
-**Install path (pick one):**
-
-- Project-scoped: `.windsurf/workflows/frontier.md`
-- Global: `~/.codeium/windsurf/global_workflows/frontier.md`
-
-Once installed, invoke with `/frontier <args>` inside Windsurf Cascade.
-
-**This is a typing shortcut, not the Claude Code plugin.** Windsurf Cascade 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 this workflow is invoked, map the requested action to one engine CLI call
-and run it in the terminal. Cascade will request approval before executing. Do
-not edit the engine's state file by hand.
-
-1. Switch mode (persists to `~/.config/maestro/frontier-state.windsurf.json`; default `off`).
-   `--scope windsurf` keeps Windsurf's armed mode independent from Claude Code,
-   Codex, Cursor, Gemini, and Cline on the same machine:
-
-   ```bash
-   maestro frontier mode off --scope windsurf
-   maestro frontier mode single --model <model> --scope windsurf
-   maestro frontier mode fusion --preset <preset> --scope windsurf
-   maestro frontier mode fusion --preset custom --models <a,b,c> --scope windsurf
-   maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope windsurf
-   ```
-
-   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 the current mode/preset:
-
-   ```bash
-   maestro frontier status --scope windsurf
-   ```
-
-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 windsurf
-   ```
-
-   - `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.
+Maestro Frontier — drive the 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 windsurf`.
+
+**Install path (pick one):**
+
+- Project-scoped: `.windsurf/workflows/frontier.md`
+- Global: `~/.codeium/windsurf/global_workflows/frontier.md`
+
+Once installed, invoke with `/frontier <args>` inside Windsurf Cascade.
+
+**This is a typing shortcut, not the Claude Code plugin.** Windsurf Cascade 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 this workflow is invoked, map the requested action to one engine CLI call
+and run it in the terminal. Cascade will request approval before executing. Do
+not edit the engine's state file by hand.
+
+1. Switch mode (persists to `~/.config/maestro/frontier-state.windsurf.json`; default `off`).
+   `--scope windsurf` keeps Windsurf's armed mode independent from Claude Code,
+   Codex, Cursor, Gemini, and Cline on the same machine:
+
+   ```bash
+   maestro frontier mode off --scope windsurf
+   maestro frontier mode single --model <model> --scope windsurf
+   maestro frontier mode fusion --preset <preset> --scope windsurf
+   maestro frontier mode fusion --preset custom --models <a,b,c> --scope windsurf
+   maestro frontier mode fusion --preset <preset> --judge <model> --synth <model> --scope windsurf
+   ```
+
+   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 the current mode/preset:
+
+   ```bash
+   maestro frontier status --scope windsurf
+   ```
+
+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 windsurf
+   ```
+
+   - `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/package.json

@@ -1,55 +1,58 @@
-{
-  "name": "@maestrofrontier/frontier",
-  "version": "1.4.4",
-  "description": "Achieve Frontier AI performance in your CLI by fusing the model CLIs you already run. Maestro Frontier is an opt-in, zero-dependency local multi-CLI fusion engine for AI coding agents: fan a prompt across a panel of any 1 to 8 local model CLIs you pick, have a judge model and a synthesizer you choose read the answers into a structured analysis and write one grounded synthesis (default Opus 4.8, override either with --judge/--synth). On a 100-task benchmark every fusion panel outscored its individual member models. Three adapters ship today: Opus 4.8, GPT-5.5, Gemini 3.1 Pro, with Kimi, DeepSeek, GLM, and Qwen to follow. Off, single, and fusion modes switch via /maestro:frontier. Built on Maestro orchestration discipline: decision-gated routing, verified done-claims, surgical scope, and structural enforcement hooks.",
-  "keywords": ["multi-cli-fusion", "fusion-engine", "frontier", "multi-agent", "orchestration", "claude-code", "gemini", "codex", "agents", "hooks", "doctrine"],
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/mbanderas/maestro.git"
-  },
-  "engines": {
-    "node": ">=18"
-  },
-  "bin": {
-    "maestro": "bin/maestro.cjs"
-  },
-  "files": [
-    "bin/maestro.cjs",
-    "frontier/cli.cjs",
-    "frontier/config.cjs",
-    "frontier/dispatch.cjs",
-    "frontier/judge.cjs",
-    "frontier/run.cjs",
-    "frontier/schema.cjs",
-    "frontier/semaphore.cjs",
-    "frontier/synthesize.cjs",
-    "scripts/install.cjs",
-    "AGENTS.md",
-    "CLAUDE.md",
-    "GEMINI.md",
-    ".cursorrules",
-    "docs/orchestration.md",
-    "docs/codex.md",
-    "commands/",
-    "integrations/",
-    "hooks/frontier-autorun.cjs",
-    "hooks/hooks.json",
-    "hooks/maestro-doctrine-guard.cjs",
-    "hooks/maestro-gate-reminder.cjs",
-    "hooks/maestro-gate-telemetry.cjs",
-    "hooks/maestro-loop-guard.cjs",
-    "hooks/maestro-phase-scope.cjs",
-    "hooks/maestro-statusline-sync.cjs",
-    "hooks/maestro-subagent-guard.cjs",
-    "hooks/maestro-terse-mode.cjs",
-    "hooks/maestro-toolbudget-advisory.cjs",
-    "settings/cli.cjs",
-    "settings/config.cjs"
-  ],
-  "scripts": {
-    "test": "node scripts/run-hook-tests.cjs",
-    "lint": "npx --yes markdownlint-cli2",
-    "bench-verify": "node scripts/bench-verify.cjs"
-  }
-}
+{
+  "name": "@maestrofrontier/frontier",
+  "version": "1.5.0",
+  "description": "Achieve Frontier AI performance in your CLI by fusing the model CLIs you already run. Maestro Frontier is an opt-in, zero-dependency local multi-CLI fusion engine for AI coding agents: fan a prompt across a panel of any 1 to 8 local model CLIs you pick, have a judge model and a synthesizer you choose read the answers into a structured analysis and write one grounded synthesis (default Opus 4.8, override either with --judge/--synth). On a 100-task benchmark every fusion panel outscored its individual member models. Three adapters ship today: Opus 4.8, GPT-5.5, Gemini 3.1 Pro, with Kimi, DeepSeek, GLM, and Qwen to follow. Off, single, and fusion modes switch via /maestro:frontier. Built on Maestro orchestration discipline: decision-gated routing, verified done-claims, surgical scope, and structural enforcement hooks.",
+  "keywords": ["multi-cli-fusion", "fusion-engine", "frontier", "multi-agent", "orchestration", "claude-code", "gemini", "codex", "agents", "hooks", "doctrine"],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/mbanderas/maestro.git"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "bin": {
+    "maestro": "bin/maestro.cjs"
+  },
+  "files": [
+    "bin/maestro.cjs",
+    "frontier/cli.cjs",
+    "frontier/config.cjs",
+    "frontier/dispatch.cjs",
+    "frontier/judge.cjs",
+    "frontier/run.cjs",
+    "frontier/schema.cjs",
+    "frontier/semaphore.cjs",
+    "frontier/synthesize.cjs",
+    "scripts/install.cjs",
+    ".codex-plugin/",
+    ".agents/plugins/marketplace.json",
+    "skills/",
+    "AGENTS.md",
+    "CLAUDE.md",
+    "GEMINI.md",
+    ".cursorrules",
+    "docs/orchestration.md",
+    "docs/codex.md",
+    "commands/",
+    "integrations/",
+    "hooks/frontier-autorun.cjs",
+    "hooks/hooks.json",
+    "hooks/maestro-doctrine-guard.cjs",
+    "hooks/maestro-gate-reminder.cjs",
+    "hooks/maestro-gate-telemetry.cjs",
+    "hooks/maestro-loop-guard.cjs",
+    "hooks/maestro-phase-scope.cjs",
+    "hooks/maestro-statusline-sync.cjs",
+    "hooks/maestro-subagent-guard.cjs",
+    "hooks/maestro-terse-mode.cjs",
+    "hooks/maestro-toolbudget-advisory.cjs",
+    "settings/cli.cjs",
+    "settings/config.cjs"
+  ],
+  "scripts": {
+    "test": "node scripts/run-hook-tests.cjs",
+    "lint": "npx --yes markdownlint-cli2",
+    "bench-verify": "node scripts/bench-verify.cjs"
+  }
+}