Squadra 3+ 3.10.3

Squadra 3+ 3.10.3: the final block becomes the default way a squad builds and reads a release, and long tasks resume from a small context packet.

The CLI commands and the registry format do not change. Active squads keep the mode they recorded until they switch.

What changes

• The final block is the default. The coordinator agrees the shared contract and the seams before any lane starts. Lanes merge into the integration as they deliver, each with its own green proof, and a delta ledger records every change with the readers planned for it. A frozen candidate then gets one Claude and one Codex read by non-authors, split so nobody reads their own work. One fix round follows, then one re-read block of only the fix deltas. Per-lane reads remain an option the owner can choose. Workflow
• Only grave findings block. One decision records the non-grave findings as carry-over tasks created at the next milestone's kickoff, each with an owner and an acceptance check.
• Proofs bind the release head. Required runtime or native proofs run on the exact sources being released, not only on lane heads.
• Coordinator reads stay honest. The coordinator may read through a fresh-context subagent and must check the subagent's main claims itself before recording the verdict.
• No challenge agreements for re-read fixes. A fix covered by the re-read block is delivered with its normal proof and its red-to-green evidence in the task output.
• Smaller context for long tasks. squadra context --task ID prints a bounded, read-only resume packet (task, scope, candidate, latest proof and verdict, pending acknowledgements, open questions, resources), so an agent can continue from references instead of full conversation dumps. See context and native compaction.
• Usage keeps its scope. The Usage view keeps the project scope and its boundary warnings in view.
• Plugins: the memoranda bridge accepts the reviewed 3.10.3 registry reader.

Used on a real project

The ReverseAI squad (one Claude coordinator, one Claude builder and reader, two Codex builders and readers) built three releases this way, M2a, M2b and M3a. Each closed after one fix round and one re-read block, and each final block found real defects at the seams between lanes, which were then fixed in that single round.

Updating

• In Claude Code run /plugin marketplace update squadra, then /plugin update squadra@squadra; in Codex run codex plugin marketplace upgrade, then codex plugin add squadra@squadra. For a standalone install run git pull and the installer with a new backup folder. Then restart the windows.
• 3.10.2 and 3.10.3 windows can share a registry while you update them; nothing is converted.
• Before you update, the coordinator saves the squad: squadra save --actor <coordinator> --to <a new folder>.