Conversation
…_sync v2026.9.24 The catchup_in_progress block was a phantom: its PR Lexus2016#1641 merged 2026-08-04 and branch sync/upstream-catchup no longer exists on origin. Per the evolution-upstream-sync skill (release-track pre-flight step 4) it is removed so it cannot block the incremental cursor behind a catch-up that already landed. Release-track merges are tracked in the new release_sync block instead: latest upstream release v2026.9.24 (v0.21.5) is fully contained in main (main..v2026.9.24 = 0 commits), merged via PR Lexus2016#3436 on 2026-09-29.
This branch has not been deployed
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
1 participant
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.
What
State-file bookkeeping only — no code changes.
Why
catchup_in_progressremoved. The block referencedsync/upstream-catchup/ PR sync(upstream): catch up to v2026.7.30 — all 87 conflicted files integrated #1641, but PR sync(upstream): catch up to v2026.7.30 — all 87 conflicted files integrated #1641 merged 2026-08-04 and the branch no longer exists on origin. Per theevolution-upstream-syncskill (release-track pre-flight step 4) a merged catch-up must be cleared, otherwise it blocks the incremental cursor behind a phantom catch-up.release_syncblock records the release-track marker. Latest upstream published release v2026.9.24 (v0.21.5) is already fully contained inmain(git rev-list --count main..v2026.9.24= 0;git merge-base --is-ancestor v2026.9.24 origin/main= true), landed via PR merge upstream v2026.9.24 #3436 merged 2026-09-29T17:47:15Z. Release merges are tracked here, not insynced_through_commit(the incremental 25-commit cursor is not advanced by release merges).Verification
.evolution/upstream-sync-state.jsonparses as valid JSON;release_sync.integrated_tagancestry re-checked againstorigin/mainat run time.Notes
Pushed from the
Da-Mikeyfork because theDa-Mikeygh identity has no push access to Lexus2016/hermes-agent-evolution. Merge stays owner-gated.