Skip to content

[Release] Resume public development from latest private main - #342

Merged
yangzhuxinyzx merged 5 commits into
mainfrom
codex/v100-publicize-private-main-20260827-142404
Aug 27, 2026
Merged

yangzhuxinyzx merged 5 commits into
mainfrom
codex/v100-publicize-private-main-20260827-142404

Conversation

@yangzhuxinyzx

Copy link
Copy Markdown
Contributor

Purpose

Resume public development after leadership approval while preserving the v1.3.0 release tag and all public history.

  • Revert only the public-tree freeze introduced by [Release] Restore public source snapshot to v1.3.0 #329.
  • Restore the exact pre-freeze development tree.
  • Import the three accepted private-main changes: exact DFlash2 long-context verification, stable D256 GQA prefill through 256K, and exact PP2 x TP4 decode optimizations.
  • Do not force-push or rewrite public history.

Integration contract

  • Public base: f4c3451
  • Private source: d63e949
  • Candidate tree: bc484b5838c843aea00214100577d2bcdc52127a
  • Private source tree: bc484b5838c843aea00214100577d2bcdc52127a
  • The v1.3.0 tag remains unchanged at tree 4373fb80cf67164be8354c8ac098a63ec56200c3.

Test Plan

This is a history-preserving publication change. Validate exact tree identity and reuse the focused source, numerical, and operator gates already recorded for the three accepted private changes. Do not repeat expensive end-to-end runs.

Test Result

  • Candidate tree equals private main tree exactly.
  • Reverting [Release] Restore public source snapshot to v1.3.0 #329 reproduces the pre-freeze public-main tree exactly.
  • git diff --check: passed.
  • Imported DFlash2 and D256 changes passed their focused static, policy, numerical, and V100 gates before private merge.
  • Imported PP2 x TP4 routes passed Ruff 0.16.4, clang-format 21, git diff --check, 39 CPU/policy tests with 4 skips, and the recorded matching-extension suite with 41 passes.
  • No model or checkpoint identity dispatch was added; accepted routes use runtime and tensor contracts with rollback.

Risk and rollback

The displayed diff is intentionally large because #329 replaced the development tree with the v1.3.0 snapshot. This PR reverses that snapshot commit through ordinary history and then imports the audited private main. The v1.3.0 tag and release artifacts remain intact.

AI assistance was used for repository inventory, exact-tree verification, and preparing this publication PR. Human review remains required before promotion.

Signed-off-by: yangzhuxinyzx 153831768+yangzhuxinyzx@users.noreply.github.com

Source-audited against private main b06f54c. Includes strict route/shape admission, bitwise-equivalent long-context kernel optimizations, static-gate fixes, default-on promotion, and explicit rollback.

Signed-off-by: yangzhuxinyzx <153831768+yangzhuxinyzx@users.noreply.github.com>
Extends the quality-valid max-aware D256 GQA architecture to KV256K, removes the rejected raw-logit half2 experiment, preserves explicit rollback, and retains the recorded exact output hash with 19.5% prompt-throughput gain.

Signed-off-by: yangzhuxinyzx <153831768+yangzhuxinyzx@users.noreply.github.com>
Default the audited non-fused shared-gate QPN8 and exact TP4 six-route MXFP4 QPN M1 paths with explicit rollback and old-extension fallback.

Preserve the recorded PP2 x TP4 endpoint, rejected-path evidence, and long-context design scope.

Tests: Ruff 0.16.4; clang-format 21; git diff --check; 39 passed, 4 skipped policy tests; recorded matching-extension suite 41 passed.

Signed-off-by: yangzhuxinyzx <153831768+yangzhuxinyzx@users.noreply.github.com>
This reverts commit f4c3451.

Signed-off-by: yangzhuxinyzx <153831768+yangzhuxinyzx@users.noreply.github.com>
Signed-off-by: yangzhuxinyzx <153831768+yangzhuxinyzx@users.noreply.github.com>
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