Conversation
perf(web): preserve home and marker identity with measured swipe caches
…60927 sync: bring main ancestry into develop for protected promotion
promote: rendering performance from develop to data
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Promote the measured rendering candidate from
datatomainafter #3056, the ancestry-only sync #3058, and #3057. The verified tree contains the home provider, Google marker, swipe cache and initial admin-loading changes, with laboratory measurements and limitations inapps/web/performance/render-delivery-20260925/REPORT.md.The feature PR and
develop → dataPR passed all reported checks. Local exact-dependency unit tests, lint, TypeScript parity, production build, and real Naver desktop/mobile browser interaction passed. The current production rollback target is Vercel deploymentdpl_BzV4NmXYxVzd8z5fKrprKvfsVbN6, Git SHA255309357342dc8963b00cf2767379c21ef5fdf0; live/api/healthagreed before promotion. Merge alone does not prove deployment. After merge, update the production approval SHA for this exactmaincommit, redeploy its Git-integrated deployment, and read back the Vercel deployment identity, Git SHA, live URL, and health.