You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prose-skill spawns are routed by role, and reviews have a lean default depth.interlock limits now prints a routing: table (the model and effort for each spawn role) and a review depth: table (each depth's dimensions and skeptics), and --json carries them. The new interlock routing [<role>] [--depth lean|strict] prints one role's model and effort, or every role and the depth's review shape, with inherit for an unset value and the EFFORT ROUTING OVERRIDDEN and MODEL ROUTING OVERRIDDEN banners when an environment override is set. Five prose sites read it instead of choosing their own: the explore investigators, the review dimensions, the review skeptics, the settle fixer and the settle conformance worker. A review runs the lean default depth; --strict runs the wider set. Skeptics are spawned per review, not per finding. interlock review --carry <file> appends an earlier record's findings from dimensions this review did not run, marked (carried), so a scoped re-review still reads the whole pull request. settle remediate-brief and fixer-result take --previous <file> and defer two kinds of finding, one on a protected test path and one the earlier round's fixer declined; they stay open at their band, and when only those remain the loop stops with STOP: nothing fixable remains. remediate-brief --out <file> keeps the round's briefing record, and fixer-result --brief <file> checks the fixer's result against the ids that record lists, so the deferrals are never worked out a second time from a profile the fixer could have changed. The review depth is on the record and in the evidence, interlock doctor's claude-env row says whether per-call effort is applied on this host, and the skeptic effort now applies on the settle path.
Changed
BREAKING: the pull request skill is renamed settle, and no MR naming is left./interlock:mr (shipped in 1.8.0) is now /interlock:settle, the interlock mr family (1.9.0) is now interlock settle with the same sub-verbs, and interlock pipeline --gitlab-mr and --mr are now --gitlab-pr and --pending. The loop's work directory is .claude/ship/settle/ and its local artifact is settle-summary.md. The old names have no alias, shim or fallback: interlock mr exits 1 as an unknown subcommand, and files at the old paths are not read. Prose that said "MR" or "merge request" says "pull request" or "PR" in the skill, the CLI help, the docs and the site. "Settled at the checkpoint" now reads "decided", so the verb settle means one thing.
Upgrading
Run /interlock:settle where you ran /interlock:mr, and interlock settle where you ran interlock mr. Rename --gitlab-mr to --gitlab-pr and --mr <file> to --pending <file> in any script that calls interlock pipeline. Delete .claude/ship/mr/ and any mr-summary.md: nothing reads them now, and the next pass writes .claude/ship/settle/ and settle-summary.md afresh.