Maestro v1.15.0

Maestro 1.15.0 makes Frontier fusion the primary product surface and leaves the discipline layer optional and off by default.

Highlights:

• Adds Claude Opus 5 and the current Codex selector family: GPT-5.6 Sol, Terra, Luna, Codex Auto Review, GPT-5.5, GPT-5.4, GPT-5.4 Mini, and GPT-5.3 Codex Spark.
• Adds validated effort control across panel, judge, and synthesizer stages through --effort and frontier effort <level|auto>.
• Removes mandatory completion-status and human-review vocabulary from normal Maestro operation. Discipline and verify hooks remain opt-in.
• Makes portable installation Frontier-first. --with-discipline installs the independent policy layer; --remove-discipline removes managed doctrine safely.
• Fixes current Codex CLI argument ordering while preserving read-only sandboxing and never approval.
• Repairs npm package closure so configured hooks, telemetry support, and the Codex plugin icon ship correctly.
• Expands the explicit release smoke gate to every first-party Codex selector.

Release validation passed on Windows and Linux CI, the HOL plugin security scanner, package-install smoke, Opus 5 with explicit effort, Codex effort dispatch, and all eight live Codex selectors.

Maestro v1.14.2

Maestro 1.14.2 keeps the Terse artifact protection from 1.14.1 and limits Codex plugin metadata to three supported featured prompts. Codex can now load the default prompt list without discarding it.

Maestro v1.14.1

Maestro v1.14.1 keeps Terse mode scoped to agent narration. Requested artifacts retain their voice, genre, rhetoric, formatting, and necessary length unless the user explicitly asks for terse artifact copy.

• Reinforces the artifact boundary at SessionStart and every prompt reminder.
• Extends hook coverage for both the full ruleset and one-line reminder.
• Updates command guidance, documentation, and plugin metadata.

Maestro 1.14.0

Added

• Codex now ships a direct /maestro slash hub via the bundled maestro skill, so users can run /maestro frontier off, /maestro frontier fusion budget-trio, /maestro settings status, /maestro terse ultra, and /maestro update without any /prompts:* prefix.
• Portable Codex installs now copy the maestro hub alongside maestro-frontier, maestro-settings, maestro-terse, and maestro-update, while preserving user-edited skills and legacy migration behavior.
• README, Codex docs, integration docs, installer tests, and plugin metadata now document the direct Codex slash-command path.

Verification

• npm test
• npm run lint
• npm run bench-verify

Maestro 1.10.0 — verify-gate (S7.3) + orchestration-transfer F1–F6

Structural S7.3 verification enforcement for both Claude Code and Codex, plus the F1–F6 orchestration-transfer deltas (previously unreleased).

Added

• Verify gate (hooks/maestro-verify-gate.cjs) — a Stop hook that fires once when a session modified files but ran no checker (test/lint/tsc) AND stated no honest status token (UNVERIFIED/PENDING_REVIEW/FAIL). A VERIFIED claim with no checker still fires. Mode = MAESTRO_VERIFY_GATE env > config.json verifyGate > default warn: warn nudges (non-blocking), block blocks the Stop once, off disables. Block-once per session; respects discipline off; fails open.
• verify settings toggle (off/warn/block, default warn) — round-trips through node settings/cli.cjs set verify <mode> and the maestro-settings skill.
• Codex parity — the gate auto-detects and streams Codex rollout transcripts (content-detected, hundreds of MB never slurped), so block enforces S7.3 on the Codex Stop event too. New scripts/codex-telemetry.cjs brings Codex token telemetry to parity with the Claude SessionEnd path.

Changed

• Orchestration-transfer deltas F1–F6 — six transferable multi-agent orchestration patterns into doctrine + the Frontier engine (anti-anchoring, gate-vs-synthesis, per-step routing, S1 topology hint, isolate-within/share-across, dead-end escalation). Every engine change sits behind a config flag defaulting to current behavior.
• Gate telemetry now captures aggregate token usage (MAESTRO_TELEMETRY=1, local-only). Gate reminder trimmed to the live Frontier badge + verdict template + a pointer to cached AGENTS.md S1, cutting per-prompt overhead.
• Doctrine — S7.3 references the verify-gate hook; S1/S7.0 wording tightened; mirrored across doctrine copies.

Full notes: CHANGELOG.md. Tests: node scripts/run-hook-tests.cjs — all suites pass. Default behavior unchanged (verify defaults to warn; all F-delta engine flags default off).

Maestro 1.8.1 — further optimizations and compression for efficiency

Changed

• Always-on kernel S2-6 thinned to a pointer. The Multi-Agent Protocol body in AGENTS.md and .cursorrules is replaced by a compact stub — the irreducible chain (Planner first as a real subagent -> scoped manifests -> cross-talk check -> Staff Engineer PASS/FAIL, max 2 cycles) plus a pointer to docs/orchestration.md, where the full protocol already lives unchanged. Saves ~0.8 KB always-on across both kernel copies; the README kernel-size claim is updated to ~10 KB. S0/S1 and S7-S10 are untouched.

---

Published to npm with provenance: @maestrofrontier/frontier@1.8.1
Full changelog: CHANGELOG.md