repo-refresh-skill

A repository refresh prevents incorrect or unverified worktrack outputs from being blindly copied into repo-level truth by updating slow variables exclusively from gate-validated findings and baseline-traced checkpoints.

Baseline tracing in repository state transitions enforces strict provenance from close handoff evidence, blocking any unverified or non-traceable write target updates to maintain repo-level truth integrity.

Generate an approval-ready handover report by running the repo refresh process, which writes a structured, programmer-reviewable handover documenting the transition from worktrack loop to repo loop using verified evidence.

During a worktrack closure handoff, you can update the milestone backlog file and mark completions, but the actual milestone status updates are deferred to the next observe phase in the control loop.

A repo refresh handles unverified write paths by strictly blocking them, ensuring that repository-level evaluations and slow variables only update from gate-validated findings and baseline-traced checkpoints.

You need to refresh repo-level slow variables in a control loop when the WorktrackScope has finished and RepoScope must update before the next repo action, marking the end of the worktrack loop.