docs: sync upstream baseline to e9c88458#70
Merged
Conversation
Final PR of the 2026-05-12 upstream sync round. Advances the recorded baseline from 9db98673 (2026-02-09) to e9c88458 (2026-05-11) — the upstream HEAD at triage time and the last commit *evaluated* in this round. The round shipped three port PRs and a per-commit audit log: - #67 port: skill curation updates from ECC - #68 port: hook + validator fixes from ECC - #69 port: plan command graceful degradation - audit log: upstream/sync-rounds/2026-05-12.md The baseline reflects what was evaluated, not what was ported. Of the 159 commits in the focused range, 9 ported, 5 evaluated inline, 3 deferred as net-new skills, 142 skipped with rationale. Architectural-mismatch skips (session-start additional_context, observe-runner relocation, MCP-disable Claude-only guidance) are documented in the audit log and the relevant PR descriptions so the precedent is auditable. Files updated: - upstream/.upstream-sync.json — lastSyncedSha + lastSyncedAt + round notes pointing at the audit log. - upstream/README.md — baseline badge, Last-synced commit, date, and a round-notes pointer. - upstream/ko-KR/README.md and upstream/zh-CN/README.md — same three updates mirrored. Expected post-merge behaviour: the next scheduled run of the upstream-drift workflow (or a manual dispatch) will compute the delta against ECC's current HEAD (~820e07f at the time of this PR), find a small drift covering only the new commits ECC merged in the last ~36 hours, and update issue #60 with the new (much smaller) count. Issue #60 will not auto-close because ECC continues to merge upstream commits faster than EGC catches up; that is exactly the "best-effort, surface drift" policy at work. validate-upstream-sync passes locally: "OK — both files reference e9c8845". Lint clean. 279/279 tests pass. Doc-only.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughUpdates the upstream synchronization baseline commit from 9db9867 to e9c88458 (dated 2026-05-13) across the configuration file and localized README documentation, advancing the recorded baseline to reflect Round 2 sync audit completion. ChangesUpstream Sync Baseline Advance to Round 2
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
This was referenced May 13, 2026
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.
Summary
Final PR of the 2026-05-12 upstream sync round. Advances the recorded baseline from
9db98673(2026-02-09) toe9c88458(2026-05-11) — the upstream HEAD at triage time and the last commit evaluated in this round.What landed in this round
upstream/sync-rounds/2026-05-12.md)Of the 159 commits in the focused range (4e66b288..e9c88458):
The 142 skips are dominated by ECC-runtime-only surfaces (
loop-status,gateguard,insaits-security-*, ECC'scursor/codex/opencodeinstall targets,ecc2RC1 work) and Claude-Code-specific session-start / observe-runner / MCP-disable changes.Files updated (4)
upstream/.upstream-sync.json—lastSyncedSha+lastSyncedAt+ round notes pointing at the audit log.upstream/README.md— baseline badge, Last-synced commit, date, and a round-notes pointer.upstream/ko-KR/README.md+upstream/zh-CN/README.md— same three updates mirrored.Why the baseline is the evaluated SHA, not ECC HEAD
ECC has continued to merge commits since triage (~820e07f at the time of this PR). The sync policy explicitly chooses to advance the baseline to the last commit actually evaluated rather than the current upstream HEAD — see
upstream/README.md→ Recording a sync. Lying about the SHA would close issue #60 prematurely and hide unevaluated drift.Expected post-merge behaviour
validate-upstream-sync.js) passes — the prose SHA and JSON SHA agree one9c8845.upstream-driftworkflow run will compute the delta against ECC's current HEAD, find a small drift (only the ~1–2 days of new ECC commits sincee9c88458), and update issue Upstream sync: 1526 new commits in ECC since 9db9867 #60 with the new (much smaller) count.Test plan
node scripts/ci/validate-upstream-sync.js— "OK — both files reference e9c8845"npm run lint— cleannpm test— 279/279sync-rounds/2026-05-12.mdRound end
This PR closes the round. Future rounds will start fresh with a new triage file under
upstream/sync-rounds/.Related to / will eventually close #60 once ECC's commit cadence catches down (or, more realistically, the next round).
Summary by cubic
Advances the recorded upstream baseline to e9c88458 (2026-05-11), the last commit evaluated in the 2026-05-12 sync round, and points docs to that round’s audit log. Updates
upstream/.upstream-sync.json,upstream/README.md,upstream/ko-KR/README.md, andupstream/zh-CN/README.mdwith the new SHA, date, and notes; the next drift run will recalc against ECC’s current HEAD and shrink the count in issue #60.Written for commit b18af8f. Summary will update on new commits.
Summary by CodeRabbit
Chores