[ethenotethan]

What

Fork-diff page (op-geth style, via protolambda/forkdiff). fork.yaml at the root names the upstream commit this fork sits on and groups every file the fork changes into a described section:

• Metal eval: use-after-free with mid-eval synchronization (fix(metal): use-after-free in gpu::eval for primitives that synchronize mid-eval #5)
• Sorted expert-tile quantized matmul, Gemma 4 E=128 / Qwen 3.5–3.6 E=256, with C-ABI diagnostics and the quantized bias-sum promotion
• GPT-OSS MXFP4 decode: masked-tail gathered qmv on M4 Max (perf: accelerate GPT-OSS MXFP4 decode on M4 Max #14)
• Coherent allocator accounting for admission control (Expose coherent allocator accounting and correct quantized bias sums #15)
• FP32 partial sums in two-pass vector SDPA (Preserve FP32 partial sums in two-pass vector SDPA #16)
• Declared-mutable inputs for Metal custom kernels (Track declared mutable inputs in Metal custom kernels #18)
• Cross-thread compile-cache cleanup (chore: upgrade core to MLX 0.32.2 #10)
• Upstream v0.32.2 sync carried in PR chore: upgrade core to MLX 0.32.2 #10 — 131 of the 166 changed files are byte-identical to upstream v0.32.2 (CUDA backend, Python tests, repo CI/templates, AGENTS.md/CLAUDE.md, …). They show up as fork changes only because chore: upgrade core to MLX 0.32.2 #10 applied upstream's delta instead of merging it; the page says so rather than crediting the fork with them. This section vanishes once the fork rebases onto a commit at or past v0.32.2.

.github/workflows/forkdiff-pages.yml renders it on every push to main and deploys to GitHub Pages → https://layr-labs.github.io/mlx/.

Enforcement gate. scripts/check_forkdiff.py runs on every PR and push (forkdiff-check.yml) and fails when:

Drift	Check
rebase onto newer upstream	base.hash ≠ git merge-base HEAD upstream/main, or not an ancestor of upstream main
new fork change nobody described	a path in git diff base.hash..HEAD matches no section glob / global ignore
section describing code the fork no longer carries	a glob matches nothing

It also renders the page, so a fork.yaml forkdiff rejects can't merge; the deploy workflow runs the same check first, so a stale page is never published. FORKDIFF.md documents the day-to-day and how to bump after a rebase; the README links the page.

Base

77a0c1e8ae16eb781a79e2b7134ba84b2ee7b597 = upstream main at 2026-08-14 (the merge-base). Fork diff against it: 166 files (172 including this PR's own), all described.

One-time admin step

GitHub Pages is not enabled on this repo and the workflow token cannot enable it (configure-pages enablement needs an admin token). Until an admin sets Settings → Pages → Source: GitHub Actions, the deploy workflow builds the page, keeps it as the forkdiff-page artifact and exits with a notice rather than failing. The existing documentation.yml is workflow_dispatch-only, so nothing contends for the Pages site.

Verification

• Gate on this branch against a real upstream/main fetch: changed files 172 described 172, exit 0.
• Page rendered locally with go run github.com/protolambda/forkdiff@v0.1.1: 1.3 MB, all sections present, nothing unmatched.
• This PR exercises the CI path itself: Fork Diff Check fetches upstream, runs the gate and renders the page as an artifact.

🤖 Generated with Claude Code