Skip to content

docs: sync upstream baseline to 393d397#76

Merged
Jamkris merged 1 commit into
mainfrom
docs/advance-upstream-baseline-393d397
May 13, 2026
Merged

docs: sync upstream baseline to 393d397#76
Jamkris merged 1 commit into
mainfrom
docs/advance-upstream-baseline-393d397

Conversation

@Jamkris
Copy link
Copy Markdown
Owner

@Jamkris Jamkris commented May 13, 2026

Summary

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 this round.

Round 3 PRs

  • #74 — triage / audit log (upstream/sync-rounds/2026-05-13.md)
  • #75 — port: code-reviewer guardrails + prompt defense baselines

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.jsonlastSyncedSha + 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

  • The validator passes — the prose SHA and JSON SHA agree on 393d397.
  • Next scheduled or manually-dispatched upstream-drift workflow run will compute the delta against ECC's current HEAD. If ECC has moved past 393d397 (likely — they merge daily), issue #71 updates with the new (small) count. If no new ECC commits since 393d397, #71 auto-closes.

Test plan

  • node scripts/ci/validate-upstream-sync.js — "OK — both files reference 393d397"
  • npm run lint clean
  • npm test 279/279
  • Manual link check — README baseline → ECC commit, audit log links → 2026-05-13.md + 2026-05-12.md

Round end

This PR closes round 3.

Related to #71.

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.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 13, 2026

Walkthrough

Updated upstream synchronization metadata: .upstream-sync.json records a new evaluated commit SHA and "Round 3" sync-round outcomes; the baseline badge hash and sync-round file references are propagated across primary and localized README documentation.

Changes

Upstream sync metadata round 3 update

Layer / File(s) Summary
Sync metadata source and primary documentation
upstream/.upstream-sync.json, upstream/README.md
.upstream-sync.json updated with new lastSyncedSha and "Round 3 sync" notes; baseline badge SHA and "Round notes" link updated in primary README to reference the latest 2026-05-13 sync-round file.
Localized documentation updates
upstream/ko-KR/README.md, upstream/zh-CN/README.md
Baseline badge hash and sync-round metadata references synchronized across Korean and Chinese localized README files to match the primary English documentation updates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

Possibly related PRs

  • Jamkris/everything-gemini-code#70: Both PRs update the same upstream sync metadata (upstream/.upstream-sync.json and baseline hashes in README files) to a newer evaluated upstream commit.
  • Jamkris/everything-gemini-code#74: Main PR updates sync metadata to point to the upstream/sync-rounds/2026-05-13.md file created in the retrieved PR.
  • Jamkris/everything-gemini-code#66: Main PR updates sync-round references in .upstream-sync.json and README pointers that directly connect to the upstream audit log added in the retrieved PR.

Suggested labels

docs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and specifically describes the main change: syncing the upstream baseline to commit 393d397, which aligns with all four files updated in this PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/advance-upstream-baseline-393d397

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 4 files

@Jamkris Jamkris merged commit a343f3a into main May 13, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant