[loom-fleet-dispatch]

Loom-Resync-Host: loom-worker-4
Loom-Resync-Version: 0.19.1250

The default branch refused a direct push (error: GH006: Protected branch update failed for refs/heads/main.), so the resync is proposed here.

[loom-fleet-dispatch]

PR #248's loom:reviewing claim is held by the judge of sweep step-judge-248-1793578820 on host host-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assigned updated_at, renewed while the judge works and released when it is done. Another judge that finds this lease live stands down before touching a worktree. See defaults/docs/lease-record.md § "PR-phase leases".

[loom-fleet-dispatch]

✅ Approved! Loom resync to v0.19.1250: vendored role docs, .loom/docs, scripts and tests only; install-metadata.json version, commit and installed_files list are consistent (new test file is registered). The merge-pr.sh change is a one-line --script-dir addition. Not measured: I did not run the resync test scripts, since CI is green on this head. I ran bash -n over every changed .sh and they all parse. Spec: no linked issue; the PR body states the resync reason. Formal reviews and inline threads: none (check-review-feedback CLEAR). Test plan: none in the PR body.

loom dashboard

[loom-fleet-dispatch]

PR #248's (no label: the lease is the claim) claim is held by the champion of sweep step-champion_merge-248-1793578939 on host host-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assigned updated_at, renewed while the champion works and released when it is done. Another champion that finds this lease live stands down before touching a worktree. See defaults/docs/lease-record.md § "PR-phase leases".

[loom-fleet-dispatch]

Champion: Holding for Human Merge

Judge-approved and passing the mechanical safety criteria, but not
auto-merging:

• Blast radius / kept set: changes .loom/scripts/merge-pr.sh (a --script-dir addition) and Champion's own prompts (champion-pr-merge.md, champion-critical-file-hold.md, champion-reference.md). The merge gate cannot vouch for a change to itself, and the resync waiver (#13096) does not apply because these are merge-gate paths (#12945).

Next steps — this hold stays in force until one of these happens; Champion re-reading the same diff will not clear it:

• A human releases it: gh pr edit 248 --remove-label "loom:blocked". Champion merges on its next tick unless it finds a concern this notice does not name; or run ./.loom/scripts/merge-pr.sh 248 yourself after removing it (merge-pr.sh refuses loom:pr + loom:blocked together, #8112)
• Or applies loom:auto-merge-ok to override the hold; Champion merges on the next tick
• Or comments here to clear it explicitly — start the comment with the instruction: clear the hold — <why>, cleared: <why>, override: <why>
• Or the situation actually changes: a new push that narrows the concern, or a deeper Judge re-review

Whichever path releases it, Champion will post a comment naming what changed before it merges.

Keeping loom:pr. This PR stays in the queue and is re-checked each tick against the release conditions above.

---

Automated by Champion role

loom dashboard

[loom-fleet-dispatch]

Superseded by #250 (v0.19.1251); this host now runs v0.19.1251. Closing the resync to v0.19.1250.