docs: sync upstream baseline to 393d397#76
Merged
Conversation
Final PR of the 2026-05-13 upstream sync round. Advances the recorded baseline from e9c88458 (2026-05-11) to 393d397 (2026-05-12) — the upstream HEAD at triage time and the last commit evaluated in this round. The round shipped two port PRs and a per-commit audit log: - #74 docs: triage ECC upstream commits e9c8845..393d397 - #75 port: code-reviewer guardrails + prompt defense baselines - audit log: upstream/sync-rounds/2026-05-13.md Of the 67 commits in the focused range, 2 ported (code-reviewer agent + prompt defense baselines applied to GEMINI.md + 48 agents), 8 deferred as net-new feature additions (PRD command, network architect agents, motion skills, Quarkus, Django Celery, cost tracking, frontend design, homelab configs), 57 skipped with rationale. Files updated: - upstream/.upstream-sync.json — lastSyncedSha + lastSyncedAt + round notes pointing at the new audit log. - upstream/README.md — baseline badge, Last-synced commit, date, round-notes pointer (now references both 2026-05-13 and 2026-05-12). - upstream/ko-KR/README.md and upstream/zh-CN/README.md — mirrored. Expected post-merge behaviour: next scheduled or manually-dispatched upstream-drift workflow will compute the delta against ECC's current HEAD, update issue #71 with the new (small) count, and auto-close it if there's no drift since 393d397. validate-upstream-sync passes locally: "OK — both files reference 393d397". Lint clean. 279/279 tests pass. Doc-only.
WalkthroughUpdated upstream synchronization metadata: ChangesUpstream sync metadata round 3 update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related issues
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 docstrings
🧪 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 |
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.
Summary
Final PR of the 2026-05-13 upstream sync round. Advances the recorded baseline from
e9c88458(2026-05-11) to393d397(2026-05-12) — the upstream HEAD at triage time and the last commit evaluated this round.Round 3 PRs
upstream/sync-rounds/2026-05-13.md)Of 67 commits in the focused range: 2 ported, 8 deferred (net-new feature additions: PRD command, network architect agents, motion skills, Quarkus, Django Celery, cost tracking, frontend design, homelab configs), 57 skipped with rationale.
Files updated (4)
upstream/.upstream-sync.json—lastSyncedSha+lastSyncedAt+ round notes pointing at the new audit log.upstream/README.md— baseline badge, Last-synced commit, date, round-notes pointer (now references both 2026-05-13 and 2026-05-12).upstream/ko-KR/README.md+upstream/zh-CN/README.md— mirrored.Expected post-merge behaviour
393d397.upstream-driftworkflow run will compute the delta against ECC's current HEAD. If ECC has moved past393d397(likely — they merge daily), issue #71 updates with the new (small) count. If no new ECC commits since393d397, #71 auto-closes.Test plan
node scripts/ci/validate-upstream-sync.js— "OK — both files reference 393d397"npm run lintcleannpm test279/279Round end
This PR closes round 3.
Related to #71.