close-worktrack-skill

To safely close a worktrack without unauthorized PR merges, you perform a scoped closeout during the WorktrackScope.closing phase that intercepts execution. This prevents silent branch cleanup or repo truth updates by requiring staged evidence validation and explicit approval boundaries before any state advancement.

A repo refresh handoff is a structured output generated during worktrack closure that passes baseline traceability and node-policy alignment data to the next workflow step. It is needed during PR merge closure to explicitly flag required baseline branches and approval mismatches for downstream execution.

You generate a structured closeout report by initiating a scoped closure action within the closing state. The system validates staged evidence, checks node-policy traceability against the Worktrack Contract, and outputs a detailed report containing executed actions, pending approvals, and next-range recommendations.

Worktrack closure fails with missing baseline branch traceability because the system requires explicit baseline_branch sourcing from the Worktrack Contract to verify state. Without this checkpoint_policy_match validation, the process cannot confirm node-policy alignment and must block closure to prevent unauthorized repo refresh execution.

No, you cannot execute code cleanup or repo refresh directly within the worktrack closing scope. The closing phase strictly enforces permission boundaries to prevent drifting into implementation or unauthorized repo truth updates, meaning refresh actions must be handed off rather than executed inline.