doc-catch-up-worker-skill

Documentation sync writes only already-validated implementation facts into the correct long-term doc layer, preventing stale references in future worktracks. It enforces strict evidence-to-field mapping and blocks unverified or improperly attributed updates.

Preventing stale documentation references requires a version fact sync mode that updates release channel and governance docs using strict evidence. This distinguishes source version, published version, and docs freshness to eliminate mismatched context.

Scope-aware doc baseline alignment targets the minimal outdated doc ranges, such as entry pages, command matrices, and directory structure references. It updates only the specific outdated facts without unnecessarily rewriting entire narratives.

No, updating published version and dist-tag changes requires strict evidence. The sync workflow blocks any unverified or improperly attributed updates, ensuring only validated release lifecycle facts are promoted to long-term documentation.

Documentation catch-up is needed during worktrack closeout to synchronize verified facts and align the baseline. It is triggered by harness observation and publish lifecycle checkpoints to ensure subsequent worktracks use accurate context.

Documentation shows pending ideas because the sync workflow keeps unverified plans marked as pending rather than promoting them to long-term truth. Only validated implementation facts are written into the permanent documentation layer.