v0.96.0

Breaking

• Old watchers and v1 helper tools are gone from the image - orchestrator-watch.sh, pipeline-watch.sh, callum-flow-regate, callum-flow-fix-linkage and callum-flow-design-route are removed, and synced settings no longer allow them. callum-flow-merge-guard keeps only its --patch mode: --run and --update-behind now exit 2 with a usage line. Nothing the factory loop runs used them. (#1314)

New

• Merge train (off by default) - With the new mergeTrain setting on, the merge queue tests the next approved PR on a factory-train/* branch while the head is still in CI, and merges it right after the head with no update and CI run of its own, as long as the tested tree still matches. Any mismatch drops the train and the PR takes the usual path. With the setting off, the queue behaves as before. (#1321)

Upgrade

• Plugin: run npx callum-dev update, commit the .claude/settings.json it produces, then restart the container or run dev-init --plugins. A loop workspace on the orchestrator-loop template picks up the plugin only after that template is pushed at this release (coder/push.sh orchestrator-loop).
• CLI and templates: npm update @callum/dev-system && npx callum-dev update (drops the removed tools from the synced allowlist).
• Base image: rebuild or re-pull the dev container to get image 2.75.0. Scripts that call the removed tools or callum-flow-merge-guard --run / --update-behind must move to --patch.
• Merge train: to turn it on, first turn off "Require branches to be up to date before merging" in main's branch protection while keeping the ci check required, then set "mergeTrain": true in .claude/factory-loop.json (or /factory config set mergeTrain true). /factory config shows mergeTrain on.

Technical changes

Maintenance

• Release v0.96.0 (image 2.75.0) (#1323)
• Merge queue: test the next PR on a train, merge it right after the head (#1321)
• Remove the old watchers and helper tools; the merge guard keeps only --patch (#1314)