Repository navigation
Sync speed: 35-second sync check, Test Web on 4 runners, Mac build during sync CI - #57
Merged
Merged
Conversation
…ring sync CI - sync-upstream.sh check runs knip, vp check and typecheck side by side, then the web build; the touched tests are gone (CI runs every test). It fails when the fork edits a native mobile file. Measured 22 s for the side-by-side part against 20-30 min before. - ci.yml: Test Web splits over 4 runners (it took 8-11 min on one); sync/upstream-* branches skip the macOS lint, whose runner queued 10+ min in 3 of 3 runs on 2026-11-03. - web browser tests retry a failed test once in CI: the split showed one flaky browser test in 2 of 3 runs, each passing alone. - custom-mac-build.yml also builds sync/upstream-* branches, so a fast-forward merge finds its build ready. Measurements: ziyadakl/tokenmaxxing#107, branch proto/sync-speed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…guard, run_parallel keeps exit codes and logs - CUSTOM.md: a sync merges by fast-forward when CI is green and Ziyad says merge; the retry seam names apps/web/vite.config.ts and records Ziyad's 2026-11-03 sign-off (AGENTS.md bans retries otherwise). - sync-upstream.sh: check fails when MOBILE_NATIVE in ci-changes.cjs no longer matches the fork's copy; run_parallel writes each status under set -e and keeps the logs of a failure. - ci.yml: the Test Web shard count has one source (strategy.job-total). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… still on Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Makes a sync (bringing Upstream into the Fork) faster with today's safety. Measured on the 2026-11-03 trial merge: ziyadakl/tokenmaxxing#107, branch
proto/sync-speed.Not ported from the prototype on purpose: the split Test job and 10 one-runner server shards. Upstream edited
ci.yml20 times in the last 30 days, and the Fork's diff there was 28 lines. The extra jobs also queued for runners: the second prototype shape ended at 331 s, against 346 s for the first.The 22-second figure Ziyad picked is the side-by-side part. The web build runs after it, because its probe config would show up in knip and
vp check, so the whole check takes about 35 s.The companion change in ziyadakl/tokenmaxxing makes
switch-build.shinstall a build whose commit is on custom-v2.Evidence
check, as documented, took 20-30 min. Test Web took 489 s and 683 s in runs 41601964186 and 41600312661.After: the new
checkran on today's real merge (cefb544 into custom-v2, commit 57236a8) on affinity-vps in 35 s, exit 0. Timings: knip 23 s, vp check 13 s and typecheck 5 s side by side, then the web build.bash scripts/custom/sync-upstream.test.sh: 22 ok, all passed. New cases:fork_native_files: the Fork's own native file, an Upstream native file the Fork edits, and a bad ref.native_rule_matches: the realci-changes.cjs, and a widened one.run_parallel: the order of results, a failure's output, kept logs, exit codes underset -e, and that the commands run at the same time.vp check,vpr typecheckandknip:checkpass on this branch.Merge Danger
Door: two-way
Every change is in CI config, the Fork's own sync script and one test-config line. Reverting the PR restores the old behaviour. Nothing touches the built app or user data.
Blast Radius: CI
sync/upstream-*branches.checkfails if the Fork ever edits a native mobile file, or if Upstream changes the native-file rule.🤖 Generated with Claude Code