chore: seed .upstream-provenance.json so the link-(a) drift check can run - #5
Merged
Merged
Conversation
… run The ClaudeCode maintainer's P2 vendor-sync pipeline has two links. Link (b) (fork -> vendored copy) started working for this tree at the 2026-07-29 re-vendor. Link (a) (true upstream -> fork) has never been runnable here, because it reads a root `.upstream-provenance.json` that this fork did not have — the other three org forks were seeded per ClaudeCode issue Egonex-AI#46 and this one was skipped, correctly, while it carried no divergence worth tracking. It carries divergence now (PRs #1-#4), so the marker is no longer a formality. `last_synced_upstream_sha` is the merge-base with upstream, measured rather than assumed: `Egonex-AI:main...CircuitBoardGames:main` reports merge_base 2cda14e (2026-07-25, upstream's own merge of Egonex-AI#598). At seed time the fork is 8 ahead / 2 behind, so link (a) will report drift on its first run — the two upstream commits are both docs-only, so nothing about that first drift is urgent. Co-Authored-By: Claude <noreply@anthropic.com>
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.
Seeds the root
.upstream-provenance.jsonmarker that the ClaudeCode maintainer agent's P2 vendor-sync pipeline reads (docs/agents/maintainer.mdPart A.6a).Why now
The pipeline has two links:
last_vendored_shastopped beingnull.The other three org forks were seeded per ClaudeCode issue Egonex-AI#46. This one was skipped deliberately and correctly: it carried no divergence, so there was nothing for link (a) to protect. That changed with PRs #1–#4, so the marker is now load-bearing rather than a formality.
The SHA is measured, not assumed
last_synced_upstream_shais defined as the fork's merge-base with upstream. Measured via:→
merge_base=2cda14e89535049e49120198886bc0b82e9e630f(2026-07-25), which is upstream's own merge of its PR Egonex-AI#598. Verified it resolves as a real upstream commit.At seed time the fork is 8 ahead / 2 behind. So link (a) will report drift on its very first run — that is expected and is the marker doing its job. Both pending upstream commits are docs-only (a Korean README formatting fix and its merge), so nothing about that first drift is urgent.
Two notes carried in the file itself
pnpm-lock.yaml, and a grammar re-resolving to a version with no musl prebuild turns a later install into a multi-MBg++compile. Review lockfile changes in a sync PR rather than waving them through.Keys match
claude-obsidian-OKFandwebobsidian-GitPusherexactly.🤖 Generated with Claude Code