Repository navigation
Open
Description
Merge-Risk Hold Digest
Auto-maintained by Champion's Held-PR Census (#6720, #6851, #7020). This
issue's body is overwritten in place every pass — it is never appended
to, and it is not a work item: do not curate, build, or promote it.
Last updated: 2026-11-19T22:52:23Z
Aggregate: Merge-risk holds: 46 open PR(s) — 14 conflicting, 2 out at Doctor, oldest 40d
Conflicting for at least 3 days: 0
Conflict count: The 14 conflicts above are among approved PRs. Both PRs out at Doctor also conflict.
Released, not yet merged: none
| PR | Hold reason | Status | Base |
|---|---|---|---|
| ⭐ #14545 | Blast radius: forge_verdict_cmd.rs::verdict_labels now uses the shared credential router to apply and remove Judge verdict labels. comment_trust/records.rs::fetch_comment_listing uses the same router to read the evidence behind those verdicts. A routing error could prevent Loom from recording or confirming approvals across PRs. Both paths are part of the merge gate and require an operator decision. |
MERGEABLE | CLEAN, drift risk: 1 overlapping files (possible structural overlap) |
| ⭐ #14619 | Blast radius: tokens_pool/private_workspace/dispatch.rs (Selection::prepare_with) changes which Codex account/seat a dispatch is bound to — the unconditional Err(error) => arm makes SeatPolicy::Existing walk to other seats too, for four callers (worker_spawn/mod.rs:824, private_workspace/transport.rs:60, role_runner/launch.rs:139, sweep_registry/private_dispatch.rs:98). That is credential/token selection on a shared runtime path (the Judge noted a diagnostic regression in transport.rs, the WRONG_CLONE bail, and that no live multi-seat run was done), so a regression would misroute or refuse dispatch fleet-wide, not in one feature. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #11305 | Blast radius: hyperparams.rs removes the LOOM_HYPERPARAMS tier from the shared configuration precedence used by dispatch, lifecycle and rework across all daemon consumers; a host still setting it will silently change behavior (warn + ignored). Shared config surface — operator decision needed on fleet impact. |
CONFLICTING since 2026-11-19T11:26:42Z, 0d | DIRTY — possible structural overlap (1 overlapping files) |
| #11717 | Critical File Exclusion Check: .github/workflows/ci.yml matches critical-file pattern .github/workflows/ |
CONFLICTING since 2026-11-19T11:26:43Z, 0d, out at Doctor | DIRTY — possible structural overlap (71 overlapping files) |
| #13582 | Blast radius: loom-daemon/src/cli/forge_identity_cmd.rs matches the *forge_identity* kept set. The PR changes when the promotion gate returns TRUSTED for an outside author's issue based on a maintainer's adoption. An incorrect trust or history decision can admit an issue the gate should hold. |
MERGEABLE | CLEAN, drift risk: 1 overlapping files (possible structural overlap) |
| #13997 | Blast radius / kept set (the merge gate itself): splits judge.md into a core plus 13 judge-* sub-skills across defaults/.claude/commands/loom/, defaults/.agents/skills/, defaults/roles/ and defaults/.claude/agents/loom-judge.md, and edits verdict, guard and lease tests. The Judge prompt writes the loom:pr approval, so it is the merge-gate entry of the kept set (*judge*, *verdict*, *guard* paths). The gate cannot vouch for a change to itself, and no standing authorization or self-release applies. |
CONFLICTING since 2026-11-19T11:26:44Z, 0d | DIRTY — possible structural overlap (5 overlapping files) |
| #14046 | Critical File Exclusion Check: Cargo.toml matches critical-file pattern Cargo.toml (workspace members edit; no standing class covers it). .github/workflows/ci.yml and .github/workflows/version-bump-on-merge.yml also match .github/workflows/. |
CONFLICTING since 2026-11-19T11:26:44Z, 0d | DIRTY — possible structural overlap (13 overlapping files) |
| #14078 | Blast radius / merge gate itself (kept set): edits defaults/.claude/commands/loom/champion-pr-merge.md, the Champion merge-gate prompt (kept-set entry "the merge gate itself": the gate cannot vouch for a change to itself). The hunks are confined to the Held-PR Census reporting block (HELD_AT_DOCTOR / RELEASED reads now raise HELD_STRUCTURAL_UNAVAILABLE) and do not touch the six criteria or the sticky-hold logic, but the path matches KEPT_SET_PATTERNS (*champion*), so the deterministic kept-set check stops self-release. |
CONFLICTING since 2026-11-19T11:26:44Z, 0d | DIRTY — possible structural overlap (2 overlapping files) |
| #14108 | Blast radius: loom-daemon/src/tokens_pool/private_workspace/forge_auth.rs config_dir_for decides which published owner gh config dir (and so which installation token) is forwarded into an exec. That is credential/token selection, a kept-set entry that stays red for an operator. Judge also records that the out-of-band check (in-container gh api repos/<owner>/<repo> returns 200 on a rolled worker) was not performed, and that the mtime-as-freshness assumption was not measured against non-Loom writers of hosts.yml. |
CONFLICTING since 2026-11-19T11:26:44Z, 0d | DIRTY — possible structural overlap (1 overlapping files) |
| #14136 | Blast radius / Revertability (kept set: installers/updaters): edits defaults/scripts/resync-installed.sh (new _gitignore_workspace_is_stub and _gitignore_source_stub_patterns feeding the #5294/#5991/#11323 stale-binary check that strips "extra" managed-block patterns). It is an installer/updater that rewrites installed files on roll, so a defect would rewrite .gitignore in every consumer repo on the next resync, and git revert would not undo what hosts already wrote. This path is on the kept set, so Champion never self-releases it at any confidence. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14181 | Blast radius: kept-set paths. The diff edits loom-daemon/src/tokens_pool/** (account_lifecycle.rs, codex_hooks*.rs, private_workspace/containment.rs, worker_setup.rs) and cli/accounts*.rs (credential/token and account-binding surface), and its load-bearing change adds a new admission path: enforcing() now accepts a "sealed" Codex hook registration without recorded trust, and the launch then passes --dangerously-bypass-hook-trust. That relaxes the guard-hook trust gate for private-clone sessions fleet-wide. Self-release is barred for kept-set paths at any confidence, so a human decides. |
CONFLICTING since 2026-11-19T11:26:45Z, 0d | DIRTY — possible structural overlap (7 overlapping files) |
| #14193 | Blast radius: kept-set entry the merge gate itself — the PR edits champion-pr-merge.md (the Held-PR Census RELEASED query and Step 1 ratification-reason rule) and champion-ratification-hold.md (the ratification hold notice text that the census parses). The gate cannot vouch for a change to itself, and this is not a byte-matching resync PR. |
MERGEABLE | CLEAN, drift risk: 3 overlapping files (possible structural overlap) |
| #14243 | Blast radius / Revertability: edits defaults/scripts/resync-installed.sh (new canonicalize_source_remote, called from restamp_metadata()), an installer/updater on the hardcoded kept set. It rewrites loom_source_remote in consumers' tracked .loom/install-metadata.json on every roll, which git revert does not undo. The change reads fail-open and well tested, but kept-set paths are never self-released at any confidence |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14253 | Blast radius: kept set, merge gate itself: loom-daemon/src/cli/champion_hold_cmd.rs (the champion-hold ratification verb that decides the ratification hold) and champion-ratification-hold.md (its tick table) decide whether a PR merges; the new unreachable! arm would panic the gate verb if the unreadable_candidates gate ever stops preceding scan. The gate cannot vouch for a change to itself. |
CONFLICTING since 2026-11-19T22:52:23Z, 0d, out at Doctor | DIRTY — possible structural overlap (2 overlapping files) |
| #14260 | Blast radius: changes which accounts a contained launch may draw (loom-daemon/src/tokens_pool/private_workspace/dispatch.rs, containment.rs, worker_spawn/mod.rs, sweep_registry/private_dispatch.rs), i.e. credential/token selection, a red entry in the blast-radius axis. A mistaken filter would stop contained launches drawing any account, or draw the wrong seat, across the fleet. |
CONFLICTING since 2026-11-19T11:26:45Z, 0d | DIRTY — possible structural overlap (12 overlapping files) |
| #14267 | Blast radius: the diff edits loom-daemon/src/worktree_ops/clean.rs (the loom-clean worktree/lock cleanup path) — clear_stale_spawn_loop_locks now judges a claim lock live via owner_pid_alive_since instead of bare liveness. This is the table's named loom-clean / worktree-deletion surface and matches the hardcoded kept-set (*worktree*, *loom-clean*), which is never self-released. Per the code's own doc comment, over-removal of these claim locks double-dispatches. The Judge's review is thorough (writer-side lock stamping, the 900 s skew, and the failing-at-base test were all checked) and I found no defect; this hold is a policy floor, not a defect finding. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14281 | Blast radius / kept set (merge gate + installers): the diff edits defaults/scripts/merge-pr.sh, defaults/.claude/commands/loom/champion-pr-merge.md, defaults/scripts/resync-installed.sh, defaults/scripts/lib/installed-file-guard.sh (including a user-facing BLOCKED message string) and defaults/scripts/check-main-freshness.sh. The hunks I read in those files are slug text only (comments and one message string), but the merge gate cannot vouch for a change to itself, and no standing authorization or resync waiver applies, so a human should merge this. |
CONFLICTING since 2026-11-19T11:26:45Z, 0d | DIRTY — possible structural overlap (33 overlapping files) |
| #14289 | Blast radius: edits loom-daemon/src/tokens_pool/bad_tokens.rs (the bad-token hold/cooldown reader now takes its evidence from the fleet-probe sidecar instead of only the local .ranking) and adds tokens_pool/fleet_probe.rs, so it changes credential/token selection on every worker that rolls to it. This is a kept-set entry (credential/token selection) and no confidence level can self-release it. |
MERGEABLE | CLEAN, drift risk: 14 overlapping files (possible structural overlap) |
| #14293 | Blast radius: edits champion-ratification-hold.md (and its test), the ratification tick of the merge gate itself: its release) branch decides whether the shared loom:blocked hold label is removed. This is the "merge gate itself" kept-set entry; the gate cannot vouch for a change to itself, and no standing authorization or self-release applies. The diff is also stacked on open PR #14215 (commit b15ab2d33, same kept-set surface), so merging this lands both changes. Judge's non-blocking finding (#14307: an unreadable comments read removes the label) concerns this same logic. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14330 | Blast radius: touches credential/token selection — credential_preflight.rs gains unregister_root_gh_config_dir (drops a root's per-owner GH_CONFIG_DIR registration, so its gh/git children fall back to the process-global credential), and the new credential_preflight/owner_drift.rs is driven from the primary refresh tick in github_app_refresh.rs to re-run cross_owner::establish_for_workspace and rewrite those registrations at runtime. A defect there changes which credential fleet gh calls carry (the credential/token-selection entry of the red set). |
MERGEABLE | CLEAN, drift risk: 4 overlapping files (possible structural overlap) |
| #14335 | Critical File Exclusion Check: .github/workflows/ci.yml (comment-only edit; WF_BLAST=red: head file contains / , no standing authorization covers it) matches critical-file pattern .github/workflows/ |
CONFLICTING since 2026-11-19T09:06:09Z, 0d | DIRTY — possible structural overlap (22 overlapping files) |
| #14366 | Blast radius / merge gate (kept set): reorders merge-pr.sh's --release-hold path (_release_champion_hold, new _apply_champion_hold_release, _check_required_checks exit-5 branch), so it changes the label/ordering guards that decide whether a PR merges. The gate cannot vouch for a change to itself. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14381 | Blast radius: edits loom-daemon/src/tokens_pool/check.rs (format_ranking_lines_with_preserve now skips the carry-forward for accounts with a permanent auth/malformed-timestamp mark), which decides what .ranking rows the token selector reads. That is the credential/token-selection entry of the kept set (*tokens*), which no self-release or standing authorization can waive. Judge approved and CI is green; the hold is for a human to confirm the change to selector inputs. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14384 | Blast radius: rewrites defaults/scripts/worktree.sh (+118/-9, worktree admission/discard paths, kept set: *worktree*), makes Builder setup fail closed on a new lease ensure --require-ownership result, and raises the installed-files daemon floor (SUPPORTS_INSTALLED/REQUIRES_DAEMON) to 0.19.1314, which refuses Builder dispatch on any host still running 0.19.1313 or older. A regression here damages the whole fleet's Builder path, not one feature; the floor also touches install/roll compatibility (installers/updaters entry), and ci-daily.yml changes alongside. The kept set disables self-release, so a human decides. |
CONFLICTING since 2026-11-19T09:06:09Z, 0d | DIRTY — possible structural overlap (12 overlapping files) |
| #14410 | Blast radius: kept set, merge gate itself: defaults/scripts/post-verdict.sh is a verdict writer (the new elif [[ -n "$RECONCILED" ]] branch changes what is posted on the changes-requested and gate-skipped approval paths), and the gate cannot vouch for a change to itself. Kept-set paths are never self-released. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14411 | Blast radius: this changes credential/token selection through loom-daemon/src/tokens_pool/check.rs::carries_forward and its ranking-writer caller. Preserving or replacing an exhausted row determines whether the selector hard-excludes that account. The installed Champion policy keeps credential/token selection for human release; all three changed paths match its hardcoded *tokens* kept-set pattern. That prevents Champion self-release. No applicable standing authorization or loom:auto-merge-ok override is present. |
MERGEABLE | CLEAN, drift risk: 1 overlapping files (possible structural overlap) |
| #14437 | Blast radius (kept set: the merge gate itself): the PR rewrites check-run classification in loom-daemon/src/merge_pr/check_runs_rollup.rs and changes how the merge queue's forge_merge_queue/group_run.rs (GhContextStates::states) decides a required context's state, turning stranded Pending rows into Failure. That output decides whether a merge-group PR merges. The diff also touches judge_backstop.rs (docs only). The gate cannot vouch for a change to itself, and the kept-set patterns *merge_pr* and *judge* match, so Champion's self-release does not apply. The PR body also says the merge-group path was only shown by fixture, never against a live merge_group commit. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14441 | Critical File Exclusion Check: .github/workflows/release.yml (and ci.yml, ci-daily.yml, ci-images.yml) match critical-file pattern .github/workflows/. The workflow carve-out (WF_BLAST) is red: release.yml's head contents hit the privileged-content list (release: trigger, workflow_run), and the diff changes the published image namespace. |
CONFLICTING since 2026-11-19T20:32:14Z, 0d | DIRTY — possible structural overlap (8 overlapping files) |
| #14452 | Blast radius / Revertability: rewrites an installer/updater that changes installed files on roll — defaults/scripts/resync-installed.sh (new held_back stamp and exit code 3) and loom-daemon/src/daemon_update/sync.rs (post-roll resync handling of exit 3). Kept-set entry (installers/updaters): git revert does not undo held_back stamps already written to hosts' install metadata, and no standing authorization or self-release can cover it. |
MERGEABLE | CLEAN, drift risk: 3 overlapping files (possible structural overlap) |
| #14470 | Blast radius / Revertability: credential_preflight/cross_owner.rs is credential selection (kept-set entry, never self-released or waived by a class). reap_stale_owner_credentials deletes by-owner writer credential files (hosts.yml, config.yml, identity.json) on every establishment pass, in the primary root and every managed root, once the daemon rolls to it. git revert does not restore the deleted files, and the no-plan arm decides "stale" from registry state, so a wrong call there removes a live cross-owner credential. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14478 | Blast radius (kept set: the merge gate itself): loom-daemon/src/cli/champion_hold_cmd.rs is the sticky-hold classifier and janitor (champion-hold classify, ratification). The diff reroutes its trusted-comment, label and PR-head reads through GhInvocation, adds run_with_gate and decline_gitea, and makes the command types pub. A regression there changes what the merge gate sees about holds and markers. The gate cannot vouch for a change to itself, and no confidence level releases a kept-set path. |
CONFLICTING since 2026-11-19T09:06:10Z, 0d | DIRTY — possible structural overlap (6 overlapping files) |
| #14498 | Blast radius: changes credential/token selection. tokens_pool/session_lifecycle/liveness.rs (is_unprovisioned_bare_seat, live_preferred) now narrows which Codex account seats the selector may draw, and the new tokens_pool/sandbox_seat_hold.rs writes a per-account cooldown into the shared account-health.json. A wrong inventory heuristic ("any enabled container seat makes the host a container host") would pass over a working bare-metal seat fleet-wide, and the Judge reports live behaviour on loom-worker-4 is unverified. |
CONFLICTING since 2026-11-19T20:32:14Z, 0d | DIRTY — possible structural overlap (5 overlapping files) |
| #14510 | Blast radius: changes credential/token selection — Codex seat draw and shared-account disable handling (loom-daemon/src/tokens_pool/account_registry.rs, account_scope.rs, cli/tokens/select_cmd.rs, runtime_preference/codex_guard.rs, sweep_registry/step_spawn.rs, defaults/scripts/spawn-codex.sh). A wrong draw there can assign or withhold seats fleet-wide. Kept-set entry: credential/token selection (self-release not available). |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14514 | Blast radius: The change routes branch-cleanup evidence through the new tools-mode forge reader. In maybe_delete_local_branch_with, that evidence can select force deletion of a local branch after the worktree has been removed. The existing default-branch and landed-head guards remain, and the worktree parity fixtures passed. The automatic merge criterion still places changes to this deletion decision behind operator review. Branch cleanup · Exact Judge approval |
CONFLICTING since 2026-11-19T11:26:49Z, 0d | DIRTY — possible structural overlap (5 overlapping files) |
| #14518 | Blast radius: edits defaults/scripts/verdict-staleness-guard.sh (Step 4b), which decides whether a Judge verdict is FRESH or STALE for the merge gate. This is the "merge gate itself" entry of the kept set (code that writes or invalidates a verdict label or marker), and the gate cannot vouch for a change to itself. The change reads as fail-closed (more STALE results, never fewer) and CI is green, but a human should make the call. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14532 | Blast radius: docs_only_fast_path_worklog_check() in defaults/.claude/commands/loom/judge.md and its generated skill changes which documentation PRs can receive Judge approval without full review. If the check misses a new WORK_LOG entry, a PR containing another repository’s history can take that path. Changes to the approval gate itself require operator review under Champion’s merge rules. |
MERGEABLE | CLEAN, drift risk: 5 overlapping files (possible structural overlap) |
| #14546 | Blast radius: changes the credential-resolution path in loom-daemon/src/tokens_pool/private_workspace/forge_auth.rs (ExecAuth::resolve / primary_root), which now asks the running daemon over its IPC socket for the primary workspace root and uses it to locate and read an owner's published GitHub App credential. That is credential/token selection, a kept-set entry that is never self-released. A regression there could hand a child exec the wrong or no installation token. The Judge's review is thorough and the design is a last-resort fallback behind the existing env and registration sources, but a human should own this call. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14576 | Blast radius: The installed pre-push and PR-open lease fence now reads ownership comments through the tools-mode credential route. sweep-lease-fence.sh uses that response to decide whether an overlapping claim prevents a push or PR opening. The existing ownership policy and the writer routes passed the three-mode parity tests. The automatic merge criterion requires operator review for this change to the fence's credential routing. Fence read at this head · Exact Judge approval |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14588 | Blast radius: edits install.sh and scripts/install-loom.sh, installers that write machine-level state on every roll (daemon, dispatcher, guard hooks, MCP registration). The new --repo-only path gates six of those provisioning steps in the default Full Install flow, so a regression in the gate condition would change what every host provisions. Installers are on the merge-risk blast-radius list and the kept set, which no standing authorization can waive. The other axes look fine: CI is green at this head, the Judge review is specific, and the change is flag-gated with 19 passing assertions. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14596 | Blast radius: the diff changes defaults/scripts/spawn-claude.sh (49+/10-), defaults/scripts/claude-wrapper.sh and loom-daemon/src/tokens_pool/{claude_seat,select}.rs. This is credential/token selection and Claude dispatch routing (OAuth token passed into persistent account seats), a kept-set entry. A regression could mis-route or expose pool credentials fleet-wide. The .github/workflows/ci.yml additions are test-step wiring only. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14597 | Blast radius: In tokens_pool/health.rs, select_healthy_for_class_at now narrows eligible Codex seats to those with the lowest measured weekly usage before round-robin selection. Every unpinned worker draw through that selector can change. An incorrect usage reading could repeatedly direct work to the same seat and exhaust its quota. Credential and token selection requires operator sign-off under the Champion merge criteria. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14620 | Blast radius: This changes acquire_lock in loom-daemon/src/cli/forge_verdict_cmd.rs. Judge’s post-verdict.sh relies on that lock to serialize verdict comments and label updates. A regression could block valid approvals or allow concurrent verdict writers. Champion reserves changes to this part of the merge gate for an operator. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14637 | Blast radius: forge_merge_queue/status_route.rs and gh_lifecycle.rs change how the shared merge-queue handoff chooses the command and trusted workspace for writing the required loom/merge-authorization status. The selection can decide whether an approved head receives the required status and enters the queue. This is the merge gate itself. The operator’s broker ruling establishes the Dashboard’s status route. The verified route and exact-head fixtures establish behavior within that policy. Review of this change to the shared gate still requires human release. |
MERGEABLE | CLEAN, base fresh for this PR’s files |
| #14650 | Blast radius: The merge-gate kept set applies. standing_auth_content_clear and standing_auth_eval in defaults/.claude/commands/loom/champion-pr-merge.md decide whether a workflow qualifies for standing authorization. ci_workflow_blast_eval uses the same new classifier when scoring workflow changes. Misclassifying an actual write-all permission as harmless would let that workflow pass both checks. |
MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
| #14653 | Blast radius / merge gate (kept set): edits defaults/.claude/commands/loom/judge.md and its generated copies (defaults/.agents/skills/loom-judge/SKILL.md, plus the Doctor counterparts). The Judge prompt is the merge-gate entry of the kept set (it writes the loom:pr verdict), and the gate cannot vouch for a change to itself. This changes the existing head-recovery path of Judge and Doctor (fetch, pin check, fast-forward, tracking repair) and is not a resync byte-match PR, so neither self-release nor a standing authorization applies. |
MERGEABLE | CLEAN, drift risk: 4 overlapping files (possible structural overlap) |
| #14662 | A failed or unavailable workflow lint check can trigger a blocking Judge verdict across repositories. | MERGEABLE | CLEAN, drift risk: 2 overlapping files (possible structural overlap) |
Automated by Champion role
Metadata
Metadata
Assignees
Labels
No labels
Activity
Champion: detect held-PR base staleness before merge time (#8552)
Champion: detect held-PR base staleness before merge time (#8552)
Champion: detect held-PR base staleness before merge time (#8552) (#8569
turian commentedon Sep 26, 2026
If the judge review is good, let's go!
rjwalters commentedon Oct 16, 2026
clear the hold — unblock for the next work described below.
Remove the operator hold from the digest itself; continue maintaining its rows and decide each real PR separately.
Pro: This is an auto-maintained informational digest, explicitly not a work item.
Con: Its row-level PR holds must remain authoritative and are not waived by clearing the digest's label.
Confidence: 96% in this disposition. Remove
loom:operatorandloom:blocked.Normal review, CI and ratification requirements still apply.
loom-fleet-dispatch commentedon Oct 16, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1792115310on hosthost-97b68aab. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".146 remaining items
loom-fleet-dispatch commentedon Nov 18, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1795032810on hosthost-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 18, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1795036895on hosthost-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 19, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1795115602on hosthost-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 19, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1795117516on hosthost-7ec0fa4c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 19, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1795124822on hosthost-7ec0fa4c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 20, 2026
PR #6877's
loom:curatingclaim is held by the curator of sweepstep-curator-6877-1795146531on hosthost-a6032f0c. This comment is a PR lease record (#9401): its liveness signal is its own forge-assignedupdated_at, renewed while the curator works and released when it is done. Another curator that finds this lease live stands down before touching a worktree. Seedefaults/docs/lease-record.md§ "PR-phase leases".loom-fleet-dispatch commentedon Nov 20, 2026
Curating this issue per user request.