[ci]: make priority:develop:sync reuse attached clean develop worktrees

[svelderrainruiz]

Summary

priority:develop:sync still fails on current develop when the local develop branch is already attached to another clean worktree, even after the helper-delegation slice from #1704 landed.

Live evidence

Command:
node tools/npm/run-script.mjs priority:develop:sync

Observed failure on 2026-03-21 from the root checkout:

• root branch: issue/origin-1352-delivery-control-plane-recovery
• failure: git checkout develop
• stderr: fatal: 'develop' is already used by worktree at 'C:/dev/compare-vi-cli-action.template-agent-verification-clean'

Why this matters

• Sagan depends on priority:develop:sync to keep fresh work lanes moving.
• An attached clean develop worktree should be reusable signal, not a hard failure.
• This currently creates avoidable continuity drag right at lane-refresh time.

Expected behavior

• if develop is already attached to a clean helper worktree, reuse or delegate to it
• do not fail just because root cannot git checkout develop
• emit a machine-readable receipt showing which helper worktree satisfied the sync

Related

• follow-up to #1704
• older family: #1412, #1504, #1517, #1615

[svelderrainruiz]

Live repro on current develop is now fixed in the work lane.

Evidence before the patch:

• priority:develop:sync delegated into C:/dev/compare-vi-cli-action.template-agent-verification-clean
• that helper was on develop but ahead 1, behind 40 and dirty
• the sync then failed on git pull --ff-only upstream develop

Evidence after the patch in E:\comparevi-lanes\compare-vi-cli-action-1751:

• node tools/npm/run-script.mjs priority:develop:sync
• result: command exits 0
• report: tests/results/_agent/issue/develop-sync-report.json
• execution mode now degrades safely to ref-refresh
• execution reason: dirty-develop-helper

Focused validation:

• node --test tools/priority/__tests__/develop-sync.test.mjs

[svelderrainruiz]

Completed via #1753.\n\nWhat landed:\n- priority:develop:sync now prefers clean attached develop helpers only\n- dirty/diverged attached develop helpers now degrade safely to
ef-refresh instead of failing the work-branch sync\n\nLive proof:\n-
ode tools/npm/run-script.mjs priority:develop:sync now exits cleanly from the #1751 lane\n- receipt: ests/results/_agent/issue/develop-sync-report.json\n- key evidence: �xecution.reason = dirty-develop-helper, �xecution.mode = ref-refresh, status = ok\n

[svelderrainruiz]

Fresh repro on current develop while prewarming #1497.
ode tools/npm/run-script.mjs priority:develop:sync still fails when it tries git checkout develop and a clean attached develop worktree already owns that branch (C:/dev/compare-vi-cli-action.template-agent-verification-clean). Evidence from 2026-03-22: atal: 'develop' is already used by worktree at 'C:/dev/compare-vi-cli-action.template-agent-verification-clean'. Sagan degraded to a direct git worktree add ... upstream/develop to keep the standing lane moving, but the helper itself still needs to fail closed or reuse that attachment correctly.

[svelderrainruiz]

Current fresh-worktree evidence on priority:develop:sync:

• node tools/npm/run-script.mjs priority:develop:sync -- --report tests/results/_agent/issue/develop-sync-report.json exits 0 in E:\comparevi-lanes\develop-sync-1751.
• The generated report records status=ok, syncMode=ref-refresh, syncReason=dirty-work-branch, and execution.reason=dirty-develop-helper.
• That means the helper is already failing closed instead of dying on git checkout develop.

I also verified the attached develop worktree currently shows a dirty report artifact, so this lane does not currently reproduce a clean-helper reuse case.

Focused validation:

• node --test tools/priority/__tests__/develop-sync.test.mjs