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).