Skip to content

[codex] prepare the Oh site StyleX native baseline - #55

Draft
0thernet wants to merge 6 commits into
mainfrom
codex/stylex-oh-site-20260909
Draft

0thernet wants to merge 6 commits into
mainfrom
codex/stylex-oh-site-20260909

Conversation

@0thernet

@0thernet 0thernet commented Sep 10, 2026

Copy link
Copy Markdown
Member

Outcome

Prepare a takeover-ready native baseline collector before migrating the Oh website to compiled StyleX. This draft adds only seven verification files. It does not change product source, CSS, package pins, the CLI, public specification, release metadata, or deployment configuration. The legacy native baseline and migration are still pending.

The collector binds exact legacy commit f185ca6, the complete tracked source and installed dependency inventories, and explicit runtime/browser identities. It owns one ordinary site production build and its loopback server. Its 58 layout/media cells each have JavaScript-enabled and JavaScript-disabled observations (116 observations), covering breakpoints, light/dark, forced colors, coarse pointer, reduced motion, print, and the actual 404.

Native coverage includes keyboard skip/focus/hit testing, all eight FAQ disclosures, both install commands, authored link/action/header states, sticky/static behavior, overflow, complete computed and pseudo paint, and strict screenshot/media/readiness fences. Terminal receipts separate work failure from original-probe/resource/process/EOF/listener collection. There is no screenshot masking, injected styling, HMR claim, install fallback, or deadline waiver.

Contract impact

None to persisted or exchanged product bytes. This introduces a verification-only baseline protocol. Prior preparation commits remain in history. Benchmark-only main updates through PR #54 were integrated normally before any native run, with complete site, manifest, lockfile and governing instruction bytes unchanged. The source-equivalent frozen install is retained, not repeated.

The collector's clean child environment now preserves the exact eight inherited scheduler worker limits and two opaque custody bindings. It neither invents worker budgets nor copies arbitrary environment, provider or session values. Receipts contain only byte counts and hashes for the private custody bindings; scheduler authentication remains owned by the schedulers.

Verification

  • Independent surface/paint and runtime/custody static reviews are green, including the incremental scheduler environment repair.
  • Current focused pure evidence: 18 contract tests and 23 resource/custody tests pass with Bun 1.3.14. These are injected controls, not native evidence.
  • All authored modules pass the applicable Node 24.18.1 syntax checks. Repository CI uses Node 24.19.0; native toolchain identity remains explicit and separate.
  • The first frozen bun install --frozen-lockfile --ignore-scripts passed through both schedulers: 419 packages, existing Next 16.3.3 and React/React DOM 19.2.6. Product, package and lockfile bytes are unchanged.
  • Collector head 0c7aa01 passed CI run 34422814257. Current head 1a76453, including the independently reviewed strict listener parser repair, passed CI run 34423535492: Ubuntu and macOS CLI checks and Site are green.
  • The first collector-owned invocation completed the ordinary build and its 12 site tests (125 assertions), then stopped before browser launch because the PID-only listener parser rejected macOS lsof's mandatory file-descriptor records. The failed receipt is retained; original operations were collected, no owned processes/listener survived, and source/install/build hashes were preserved.
  • The parser now requires complete unique PID/descriptor groups, rejects unknown/orphan/duplicate/malformed records, and preserves the existing positive root/descendant ownership proof for every listener. Independent review and all 23 changed-area pure tests pass.
  • The fresh current-head invocation completed the ordinary build and all 12 site tests (125 assertions), proved the server listener, and launched the pinned browser. It stopped during the first JavaScript-enabled home cell's native snapshot settlement, before accepting any observation. The absolute five-second bound was not widened. The failed receipt retains the timeout and original probe rejection, zero owned survivors/pending resources/probes, child exit/close/EOF, closed loopback ports, browser disconnect, and unchanged source/install/toolchain/served-output hashes. Snapshot/transport diagnosis is in progress; this is not a no-JavaScript failure or an accepted baseline.
  • Remaining: complete legacy native evidence; immutable compatible shared compiler adoption; actual StyleX migration and parity; final current-head checks, merge and deployment proof.

The collector README documents the exact command and acceptance boundaries. This PR remains draft.

@vercel

vercel Bot commented Sep 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
oh-computer Ready Ready Preview Sep 10, 2026 2:33am UTC

Request Review

@0thernet

Copy link
Copy Markdown
Member Author

Takeover checkpoint: lossless native snapshot transport

Pushed 5b8d77200b015b80833c2942de37cd09cefd011b, tree 3a63ee2c6c972c7191a0115f0235c585f084073c, on codex/stylex-oh-site-20260909. The checkout is clean. This remains a draft: independent review of this incremental codec and a fresh complete native baseline are pending. No legacy baseline or StyleX product migration is accepted.

Only four verification files changed in this commit (+217/-6). The original native capture, all 58 cells / 116 JS and no-JS observations, three-equal-snapshot five-second settlement, per-case and total deadlines, screenshot/media/focus/resource/custody checks remain unchanged. A sample-local dictionary removes repeated property names from the wire representation; decoding restores the entire snapshot before its existing assertions. Exceptional numeric values, undefined, sparse entries and literal collision-like keys are covered. No product source, manifest, lockfile, provider or release changes.

Evidence

  • Focused shared HRA/Jungle session 65694: bun test site/verification/stylex-native/transport.test.mjs5 passed, 0 failed, 282 ms. Both schedulers released.
  • Genuine Node 24.18.1 --check passed for the transport, its test and the changed collector.
  • The retained real snapshot round-trips by deep equality and identical original JSON bytes: 350 nodes, 665,000 declarations, 18,386,116 bytes before and 8,227,222 wire bytes after. Local encode/decode measurements were 107/292 ms; these are not browser timing guarantees. Wire SHA-256: 7d5142e91c3371ca40ad2db81685e70670fe530d5ed444d963eef8f4d47d6796.
  • Prior complete native invocation 9047 remains red at first JS home settlement, with zero accepted observations. Its ordinary build and 12 existing site tests / 125 assertions passed. Original operations, browser, server, listeners and resources were collected; inputs and served outputs were unchanged.
  • Authorized retained-build-only diagnostic 72362 is diagnostic-complete, accepted=false. Same first-cell snapshot: native capture 875.60 ms; same-object structured transfer 3,070.99 ms; JSON-string transfer 871.38 ms. All fields were equal, no unsupported JSON values were present, zero errors/survivors/pending operations remained. No rebuild or baseline acceptance occurred in that diagnostic.

Exact retained inputs and artifacts

Source checkout: /Users/benguo/Documents/oh-stylex-site-20260909.

  • Legacy baseline anchor remains f185ca670af0e04ae9786ade50ed436634cb7fb5; new remote main was observed at 53ae5032ab5a1c789b898bdd2751eb8d51c9b627 during checkpoint preflight. That delta has not been joined or relabeled. Resolve it before the next baseline invocation if the governed main join is required.
  • Failed full receipt: /private/tmp/oh-site-legacy-native-lsof-20260909.kCKhnY/run/receipt.json, SHA-256 1d2f4b3956a2c98389d55ae68453129e3494434ac159e6a110264a82ba6e3d62.
  • Diagnostic source: /private/tmp/oh-snapshot-diagnosis-20260910.gEYlD7/diagnose.mjs, SHA-256 5152b56d9dc6b5d141216d88dd8034de3c34ab427388d20ab42860bb9adc1b25.
  • Diagnostic receipt: /private/tmp/oh-snapshot-diagnosis-20260910.gEYlD7/run/receipt.json, SHA-256 eeb5f6762d9b6d15f1465e73da200f7e74055bc83261b587bb2c4b5be1d9d266.
  • Original complete snapshot: /private/tmp/oh-snapshot-diagnosis-20260910.gEYlD7/run/diagnostic-snapshot.json, SHA-256 bc94bfaecdf469ca64d855315d69ba10b8a99a7d1eec1084f2e41b2fe989e8eb.
  • Preserved source census SHA-256 e71d6618a7deb7471a464e29f2e75827b0b27aa5efe1703b172d6c574896bf13; served build 448dda9fec2ac63a094ea85b1168d0e47b424b83bb0134ea6541d6926f8f7b9e.

Changed source SHA-256 values:

File under site/verification/stylex-native/ SHA-256
transport.mjs 8dae9a1db3707ff8640a39c52c8ade137e74402604279e2316a55b67bd7f3cdb
transport.test.mjs b192eb1bea4442427b87c2f8158604d1a0993fdbf17f4012148b0e729c724ed0
collect.mjs 0b507d758595db51938ec80c917ef8f15f98b428adcf85ccf34852663f286c9f
README.md 692ad2f285702b4300669aff57ad18a67c3750de8a943d21c7320f03492b41db

Next operation, only after review and source/ownership preflight

Revalidate immutable browser/runtime bytes, scheduler owners, shared-volume reserve, the exact clean source and applicable main join. The current-head CI and incremental independent review remain required. Then allocate a fresh private evidence parent and run one complete invocation through both schedulers; it includes the ordinary build once. Do not rerun the old diagnostic as an acceptance substitute, reuse its output directory, skip the build, or expand deadlines.

oh_evidence_directory=$(mktemp -d /private/tmp/oh-site-legacy-native-transport-20260910.XXXXXX)
cd /Users/benguo/Documents/jungle
/Users/benguo/.bun/bin/hra-host-run --mode=exclusive --lane=browser-auth --label=Oh-legacy-native-lossless-transport -- \
  /Users/benguo/.bun/bin/bun run check:resources:exclusive -- \
  /Users/benguo/.nvm/versions/node/v24.18.1/bin/node \
  /Users/benguo/Documents/oh-stylex-site-20260909/site/verification/stylex-native/collect.mjs \
  --repo /Users/benguo/Documents/oh-stylex-site-20260909 \
  --expected-head 5b8d77200b015b80833c2942de37cd09cefd011b \
  --output "$oh_evidence_directory/run" \
  --bun /Users/benguo/.bun/bin/bun \
  --node-sha f480e325ee0ca9cb9eef00b5ca6057a2a104807a1b073f1bc373a55c67facff5 \
  --playwright /Users/benguo/Documents/ui-stylex-property-validation-20260909/node_modules/playwright-core/index.mjs \
  --chromium '/private/tmp/atet-playwright-1234-a794119.ikI4ol/browsers/chromium-1234/chrome-mac-arm64/Google Chrome for Testing.app/Contents/MacOS/Google Chrome for Testing' \
  --chromium-sha a596b1cfc6353e987fcec8d71a23a28cd6a9e7a6b4e20b908e4c4fcffe51158e \
  --chromium-version 151.0.7922.34

If an authorized main join changes the collector commit, update the explicit expected head only after its new source/anchor review and relevant focused evidence. Preserve every failed receipt, the ordinary install and source/build evidence; do not clean protected artifacts.

@0thernet

Copy link
Copy Markdown
Member Author

The coordinator independently reviewed the complete four-file 5b8d772 codec checkpoint: GREEN, no P0–P2 findings. The complete source capture and acceptance/deadline contracts are unchanged. The exact-head CI run 34429879062 is now successful on Ubuntu, macOS and Site; CodeQL and Vercel preview are also green. CI uses Node 24.19.0; the separately qualified native command retains Node 24.18.1.

The coordinator also compared f185ca6 to remote main 53ae503: 24 benchmark/script/test paths only, no site/product/package/lock/native-verifier changes. The upcoming result is therefore explicitly a baseline of the preserved historical f185ca6 source, not current-main migration acceptance. A later normal main integration remains separate.

I own one newly authorized complete native invocation, using exactly the command in the preceding checkpoint comment at clean 5b8d77200b015b80833c2942de37cd09cefd011b. Its newly allocated private output is /private/tmp/oh-site-legacy-native-transport-20260910.f6o1L6/run. HRA exclusive/browser-auth and Jungle exclusive remain mandatory; the ordinary build runs once inside this invocation. The scheduler session and terminal result will be posted here. It is not yet a browser pass, and no product migration will begin without the accepted baseline.

@0thernet

Copy link
Copy Markdown
Member Author

The sole fresh native wrapper is session 81923, queued and not yet admitted. Exact clean head 5b8d77200b015b80833c2942de37cd09cefd011b; output /private/tmp/oh-site-legacy-native-transport-20260910.f6o1L6/run. One owner will collect its terminal result; no duplicate gate or baseline-success claim.

@0thernet

Copy link
Copy Markdown
Member Author

Additional independent peer review is now GREEN on the exact pushed four-file codec (8dae9a1d / b192eb1b / 0b507d75 / 692ad2f2): no P0–P2 findings, no reviewer edits or duplicate execution. This joins the coordinator review and focused/retained-snapshot equality evidence. Native session 81923 is still the sole pending run; no native acceptance is claimed.

@0thernet

Copy link
Copy Markdown
Member Author

Native session 81923: terminal red, collected

The one queued complete invocation admitted after 2,695.4 seconds and exited 1. HRA and Jungle both released their exclusive lanes. It ran the exact clean pushed collector 5b8d77200b015b80833c2942de37cd09cefd011b, tree 3a63ee2c6c972c7191a0115f0235c585f084073c, against the explicitly historical legacy source f185ca670af0e04ae9786ade50ed436634cb7fb5. Receipt interval: 2026-09-10 03:23:17.682–03:23:53.210 UTC.

The ordinary build passed: 12 existing site tests / 125 assertions, Next 16.3.3 webpack compilation, native TypeScript, five generated static pages and build tracing. The browser then stopped on the first cell's initial paint:

AssertionError [ERR_ASSERTION]: Native settlement deadline exceeded
contract.mjs:150 (post-operation deadline check)
collect.mjs:326 (initial paint)

Zero complete observations were accepted; the baseline remains failed. The receipt contains two propagated copies of this same first failure, not two independently diagnosed causes. All original native probes resolved, with zero pending probes and zero probe failures. The receipt does not identify which capture iteration crossed the unchanged five-second bound. The codec's focused tests and retained-snapshot equality remain valid, but they did not establish sufficient native end-to-end performance. No deadline, assertion, property inventory or acceptance condition was relaxed.

Cleanup and identity evidence:

  • Original operations, context, browser and browser server collected; browser disconnected.
  • Build exited 0, the intentionally stopped production server exited 143, Chromium exited 0; each has close and stdout/stderr EOF evidence.
  • Zero pending resource requests/tasks, 12 recorded responses, zero owned survivors.
  • Listener ports 54601 and 54609 absent; a fresh bounded postflight found none of the 25 recorded process IDs present.
  • Tracked source remains clean at the pushed commit. Package/lock, production CSS, collector, installed dependency, executable and served-output preservation checks passed. No cleanup or provider action was performed.
  • Settled free-space readings were 244,955,992 and 244,948,152 KiB.

Retained evidence:

Artifact SHA-256
/private/tmp/oh-site-legacy-native-transport-20260910.f6o1L6/run/receipt.json ea0fff78685ce429c3eec77a080f7ee0e6da1fb1ad5522dbc89035b06ffab816
Source census 7798eed37defcbad0755dd1c9f2887307ae9a9bf04a3ab154e1e679bc9625935
Served build inventory e6d391ef5d8f5f8908bcb6129b40e1e494dd01fcd757f6628d87087b8ac32619
Installed dependency inventory 89b8e6ceaad3d5b816de1796ae50631728f987b42a72a0788ea1d7757d5fc445
Propagated errors 4f090549e148fd4ea5fb99c7d736538fb6a86b4fc1a2ef7ded94d4482f401dbf
Cleanup evidence 42aefbcfb705c50a211694a15653db764377ef8255d4551aca4c07881fb04f2e

The full build log and all earlier failed/diagnostic receipts remain intact. The coordinator has separately reported newer main 678cd458525239c75854b20fa315fdcf2fceaf08, including hosted-embedding specification changes. This historical attempt does not qualify that newer source, and its baseline anchor was not relabeled.

Stopped at the first red result. There is no native run left queued or owned from this invocation. No duplicate, rerun, source edit, migration, merge or deployment was performed. A bounded diagnosis and independently reviewed repair are required before another native invocation; the prior next-command example is not authority to rerun unchanged inputs.

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