docs(upstream): sync round 2026-05-18 — advance baseline to 3b7e0ba3#85
Merged
Conversation
Fifth sync round. Largest commit count to date (137 between baseline
`f7315016` and HEAD `3b7e0ba3`) but very little portable surface,
because the two EGC-authored PRs that would normally be this round's
top targets — workflow-security validator hardening and
ecc-metrics-bridge cost-reporting fixes — were opened upstream during
round 4 and merged during this round. They ARE the backport, in the
other direction.
Of the 137 commits:
- 10 are EGC-authored, integrated into ECC main this window:
7f971b7e, cdbc925d, e06d0382, 7bb31720 (= ECC PR #1970)
4f21ed2a, 63c9788f, 086e44c9, 2de0ce45, 4cafdb83, 9b1d8918 (= ECC PR #1971)
- ~42 are ECC-Tools / AgentShield / Linear roadmap sync logs — skip.
- ~50 are rc1-readiness / catalog / billing / readiness-dashboard
telemetry — skip.
- ~15 are a Japanese localization batch (ja-JP) — defer to its own
focused round; new locale needs install scripts, upstream mirror,
etc.
- ~6 are net-new community skills (uncloud, recsys-pipeline-architect),
a Thai locale, an installer --locale flag — defer.
- ~6 are dependency bumps (TypeScript 6, @types/node 25) — defer.
- The remainder (~6) sit outside EGC's port surface (`ecc-context-monitor`,
`gh-token-monitor`, supply-chain IOC scanner, Zed install target) —
skip per the same exclusion as rounds 1–4.
The note's narrative role stays separable from the baseline flip so the
next commit can advance both `upstream/.upstream-sync.json` and the
`upstream/README.md` baseline lines atomically (the validator requires
both files to agree on the SHA).
Move the recorded ECC baseline forward from `f7315016` (2026-05-15) to `3b7e0ba3` (2026-05-18) now that round 5's triage is recorded in `upstream/sync-rounds/2026-05-18.md` (previous commit). Both files atomically: - `upstream/.upstream-sync.json` — `lastSyncedSha`, `lastSyncedAt`, `notes` (links to the new round note, calls out the round-5 outcome pattern: EGC-authored PRs already in ECC main, remaining ECC drift outside EGC port surface). - `upstream/README.md` — baseline badge, "Last-synced upstream commit" link, "Last-synced date", and the round-notes pointer list (latest round first, all four prior rounds listed in reverse-chronological order). The CI validator (`scripts/ci/validate-upstream-sync.js`) requires the SHA in both files to match, so this commit updates them together. Verified: `OK — both files reference 3b7e0ba`. Localised mirrors (`upstream/ko-KR/README.md`, `upstream/zh-CN/README.md`) are not updated in this commit, matching the round-3/4 policy. They are scoped for a focused translation follow-up rather than the per-round baseline flip. This advance also closes the rolling `🔄 Upstream Sync` tracker [issue #77](#77) on the next `upstream-drift.yml` cron tick.
|
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 (3)
WalkthroughThis PR records the completion of Round 5 upstream sync. It updates the baseline commit SHA and sync date in ChangesRound 5 Upstream Sync Recording
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 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 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
Fifth upstream sync round. Inventories 137 commits between baseline
f7315016(2026-05-15) and ECC HEAD3b7e0ba3(2026-05-18) and advances the baseline files.Full per-commit table in
upstream/sync-rounds/2026-05-18.md.What's notable
No new EGC-authored ECC PR opens this round. The two PRs that would have been this round's top targets — workflow-security validator hardening +
ecc-metrics-bridgecost-reporting — were opened upstream during round 4 and merged during this round's window. They ARE the backport, in the other direction.The remaining 127 commits split into ECC operations log (no EGC analogue), substantial deferred candidates (ja-JP locale, new skills, installer
--localeflag), and out-of-port-surface ECC hooks (ecc-context-monitor,gh-token-monitor, supply-chain IOC scanner, Zed install target).Commit layout
Same shape as round 4: two commits so the narrative artefact and the baseline flip stay separable.
docs(upstream): add sync round note for 2026-05-18— adds the new round file only.docs(upstream): advance baseline to 3b7e0ba3 (2026-05-18)— flipsupstream/.upstream-sync.jsonANDupstream/README.mdatomically (the validator requires the SHA to match).Validation
node scripts/ci/validate-upstream-sync.js→OK — both files reference 3b7e0banpm run lint— cleannpm testunaffectedCloses #77 on the next
upstream-drift.ymlcron tick.Deferred net-new ECC features (carry forward)
New to the queue from this round:
uncloudskill (community contribution)recsys-pipeline-architectskill (community contribution)th) README + docs localeja-JP) full documentation translation--localeflag for selective translated-docs installation@types/node25 toolchain bumpsPlus all items already deferred from rounds 1–4.
Test plan
validate-upstream-sync.jsconfirms both files reference the same SHAupstream/README.mdshows the new SHAupstream-drift.ymlrunSummary by cubic
Advances the upstream baseline to 3b7e0ba3 (2026-05-18) and records the round‑5 inventory to keep EGC in sync with ECC. Updates
upstream/.upstream-sync.jsonandupstream/README.md; addsupstream/sync-rounds/2026-05-18.md; no code changes.Written for commit 2a11811. Summary will update on new commits. Review in cubic
Summary by CodeRabbit
Chores
Documentation