Prepare explicit Next static-export production profile - #72
Draft
0thernet wants to merge 1 commit into
Draft
Conversation
Member
Author
|
Exact checkpoint 330f565: CI run 34719210936 is terminal red at committed-output parity after inventory, strict TypeScript, and canonical package build passed. The build changed only dist/build/next.js and dist/stylex-manifest.json. Generated output was deliberately deferred from this source-only draft and remains a required coordinated join; no CI or native acceptance is claimed. CodeQL passed. Local focused profile/custody/process evidence and independent review remain as recorded. The public static-export path is still disabled. No unchanged CI rerun was requested. |
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.
Status
Draft source checkpoint for a separately opted-in Next.js production static-export profile. Public execution is still disabled. This checkpoint does not qualify a static export, a release, or a deployment.
Source boundary
.nextorigin from discovery evidence retained under a fresh attempt. A one-use, root-bound token requires successful child and process-group collection before capture.O_NOFOLLOW | O_NONBLOCKand positively verify the opened file type. A deterministic real-FIFO control confirms rejection and handle collection.Package version, lockfile, public exports, generated output, production UI runtime, and CSS are unchanged.
Evidence
Base:
8626e82f9aeed4de085e418e6cae4e7dc3d8e80f.Checkpoint:
330f56537a7213aa209be01a88299c4d6484512f, tree22605b3aad3a96bfb9141e682fd6f03f8497f07c.Commands used Bun 1.3.14, genuine Node 24.18.1, and both required shared schedulers:
bun test build/next-export-profile.test.ts: four tests passed.bun test build/next-export-custody.test.ts: seven tests passed, including the native FIFO control.build/next-process.test.ts: four tests passed, including descendant collection.bun run typecheck: passed after the final custody correction.Earlier focused failures are retained in the task evidence: an empty assertion-message argument, an unescaped Unicode regex delimiter, and a platform-specific human-readable EBADF message. Those test plumbing errors were corrected; no acceptance rule was relaxed.
Remaining implementation and gates
output: "export".No merge or publication is requested by this draft checkpoint.