#1741 add daemon cutover readiness summary#20
Conversation
…mmunity-CI-CD#1735) docs: record print proof finalization contract (LabVIEW-Community-CI-CD#1726) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1738) feat: add Docker cutover contract to lane planning (LabVIEW-Community-CI-CD#1737) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1739) Make burst lane roots deterministic for LabVIEW-Community-CI-CD#1727 Co-authored-by: Agent Runner <agent@example.com>
…VIEW-Community-CI-CD#1740) Co-authored-by: Agent Runner <agent@example.com>
…abVIEW-Community-CI-CD#1734) docs: add security alert reconciliation register for LabVIEW-Community-CI-CD#1426 Co-authored-by: Agent Runner <agent@example.com>
…-Community-CI-CD#1467) (LabVIEW-Community-CI-CD#1742) * Add payload finalization helper for native print authoring (LabVIEW-Community-CI-CD#1624) * docs: tighten print seed evidence trail (LabVIEW-Community-CI-CD#1467) * test: align print payload proof contracts (LabVIEW-Community-CI-CD#1467) --------- Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1747) LabVIEW-Community-CI-CD#1744 Force router refresh after standing sync Co-authored-by: Agent Runner <agent@example.com>
…cutter surface (LabVIEW-Community-CI-CD#1748) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1746) * LabVIEW-Community-CI-CD#1743 Pin template dependency and add cookiecutter conveyor * LabVIEW-Community-CI-CD#1743 Fix cookiecutter bootstrap workflow YAML * LabVIEW-Community-CI-CD#1743 Map cookiecutter container user onto hosted Linux * LabVIEW-Community-CI-CD#1743 Route cookiecutter home into writable run root * LabVIEW-Community-CI-CD#1743 Expand cookiecutter bootstrap trigger coverage * LabVIEW-Community-CI-CD#1743 Bridge cookiecutter project paths back to host * LabVIEW-Community-CI-CD#1743 Align template verification artifact paths --------- Co-authored-by: Agent Runner <agent@example.com>
…orktrees (LabVIEW-Community-CI-CD#1749) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1750) docs: make queue refresh receipt operation explicit (LabVIEW-Community-CI-CD#1397) Co-authored-by: Agent Runner <agent@example.com>
…ring develop sync (LabVIEW-Community-CI-CD#1753) fix: prefer clean develop helpers in develop sync (LabVIEW-Community-CI-CD#1751) Co-authored-by: Agent Runner <agent@example.com>
…unity-CI-CD#1754) LabVIEW-Community-CI-CD#1741 clarify jarvis daemon cutover actions Co-authored-by: Agent Runner <agent@example.com>
…lper roots (LabVIEW-Community-CI-CD#1755) LabVIEW-Community-CI-CD#1744 Route priority sync through clean helper roots Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1756) docs: make burst-root defaults explicit (LabVIEW-Community-CI-CD#1727) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1757) docs: expose concurrent plan provenance in status (LabVIEW-Community-CI-CD#1482) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1758) ci: gate downstream scorecard on template verification (LabVIEW-Community-CI-CD#1497) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1759) docs: document concurrent plan provenance in status (LabVIEW-Community-CI-CD#1482) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1760) ci: bridge onboarding scorecard through manifest (LabVIEW-Community-CI-CD#1497) Co-authored-by: Agent Runner <agent@example.com>
…D#1762) LabVIEW-Community-CI-CD#1741 document jarvis cutover operator loop Co-authored-by: Agent Runner <agent@example.com>
…ity-CI-CD#1763) Co-authored-by: Agent Runner <agent@example.com>
…mmunity-CI-CD#1764) LabVIEW-Community-CI-CD#1741 gate stale host-signal status Co-authored-by: Agent Runner <agent@example.com>
…unity-CI-CD#1765) feat(queue): add queue:update alias Co-authored-by: Agent Runner <agent@example.com>
…W-Community-CI-CD#1766) Honor LabVIEW-Community-CI-CD#1741 manager-filtered Jarvis host runtime evidence Co-authored-by: Agent Runner <agent@example.com>
…ty-CI-CD#1767) Add LabVIEW-Community-CI-CD#1741 host-signal mode aliases Co-authored-by: Agent Runner <agent@example.com>
| import { parseGitWorktreeListPorcelain } from './develop-sync.mjs'; | ||
|
|
||
| const WORK_BRANCH_PATTERN = /^(issue\/|feature\/|release\/|hotfix\/|bugfix\/)/i; | ||
| const MODULE_DIR = path.dirname(fileURLToPath(import.meta.url)); |
Check notice
Code scanning / CodeQL
Unused variable, import, function or class Note
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 months ago
In general, the correct fix for an unused variable is to remove its declaration (and any associated computation) when it has no side effects and is not required for API compatibility. Here, MODULE_DIR is a simple computed constant with no side effects; removing it will not change runtime behavior, because it is never read.
The best fix is therefore to delete the line that declares MODULE_DIR on line 10 in tools/priority/run-sync-standing-priority.mjs. No other changes are needed: imports remain the same, and no additional methods or definitions are required. This keeps functionality identical while improving clarity and avoiding the unused-variable warning.
| @@ -7,7 +7,6 @@ | ||
| import { parseGitWorktreeListPorcelain } from './develop-sync.mjs'; | ||
|
|
||
| const WORK_BRANCH_PATTERN = /^(issue\/|feature\/|release\/|hotfix\/|bugfix\/)/i; | ||
| const MODULE_DIR = path.dirname(fileURLToPath(import.meta.url)); | ||
| const SYNC_SCRIPT_RELATIVE_PATH = path.join('tools', 'priority', 'sync-standing-priority.mjs'); | ||
|
|
||
| function runGitText(spawnSyncFn, cwd, args, env) { |
Add a compact manager-status summary for daemon cutover readiness and runner-service isolation, derived from existing raw fields in Manage-UnattendedDeliveryAgent.ps1 status output.\n\nFocused contract coverage added in tools/priority/tests/delivery-agent-manager-contract.test.mjs.