v2.1.3

Agent teams gain an authoritative mission brief so the lead builds what you actually asked for, plus a defense-in-depth guarantee that a specialist's disagreement with that brief can never be silently dropped.

Added

• create_team now takes a required brief. Previously the only intent channel was a short title, so the lead had to infer the architecture — and often invented one that drifted from the request. create_team now requires a full brief (the authoritative statement of what to build and why) alongside the title (now a hard-capped ≤200-char label). This is a breaking change: calls without a brief are rejected. The brief is seeded verbatim into an immutable mission-brief scratchpad section before any agent spawns, and the lead is gated — it cannot spawn a specialist until it has read mission-brief, so the authoritative intent always reaches the whole team. Every specialist prompt mandates reading mission-brief first.
• Brief-conflict escalation. A specialist that finds the lead's contract, its own task, or a peer's work in conflict with the mission-brief must HARD STOP and call the new team_flag_brief_conflict tool instead of proceeding on a guess. The lead reconciles via team_request_revision (fix the work) or the new team_resolve_brief_conflict (dismiss with a written rationale) — and when the fork is genuinely one the brief doesn't settle, the lead escalates it to you via AskUserQuestion rather than choosing for you.

Fixed

• A flagged brief conflict can never be silently dropped. Three independent guarantees: synthesis is mechanically blocked while any conflict is open (team_synthesize_result is rejected); every completion path funnels through one terminal method that prepends a prominent "⚠️ UNRESOLVED BRIEF CONFLICTS" block and persists an audit record if the team ever finishes with an open conflict (e.g. via Escape/cancel); and a lead that ends its turn with an open conflict gets a bounded re-nudge (max 2 delivered) to reconcile. The nudge budget counts delivered nudges, so a conflict resolved in-flight doesn't starve a later, distinct conflict of its re-engagement. None of this extends the team's keep-alive, so it can't hang.