Repository navigation
[autopilot] skills: sync-jobs backfill entry point for trailing-window syncs - #179
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a short section to the sync-jobs skill. Pattern: an incremental sync that only fetches a trailing window can never recover older history, and the full-history fetcher often exists but is wired only to a different path, so the primary source has no way to reach it. The section covers an opt-in full-history mode that reuses the same checkpointing and merge, verifying routing with a stubbed remote, and deciding the recovery story when a destructive-rebuild guard rejects scheduled-run scaffolding. Also adds a checklist item.