Skip to content

cbz: exercise exact Atlas source bridge - #772

Merged
d6g8k5htny-coder merged 2 commits into
mainfrom
codex/cbz-atlas-source-bridge-current-20261109
Nov 9, 2026
Merged

d6g8k5htny-coder merged 2 commits into
mainfrom
codex/cbz-atlas-source-bridge-current-20261109

Conversation

@d6g8k5htny-coder

@d6g8k5htny-coder d6g8k5htny-coder commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

CBZ scope

Exact Atlas source-bridge browser closure for the public-site manifest profile only. This delivery does not change theorem statements, mathematical bounds, kernel evidence, authorship, scientific review, or acceptance.

Exact Git identity

  • base: 1046e3aceb869617efa349f94e48638bb5ceb030
  • hosted head: 1cc79287cd6455f8f4b3a6aade19d081609b8f2d
  • hosted head tree: 3f615867f7d04f2b3e772760c25af479d26c7948
  • first hosted commit/tree: 2429c5fcd2eed458824a5cba71d09d7ef7be0e0f / 486183f13aa93bdbec703bbb44fd243f23b8bf4b
  • equivalent local commits: cf3c8d1b86a513372b565d0d1568e56419a6a95d, then c78baf323f3962e136a3fac22ebe8e6037d9281a
  • each local and hosted tree matches exactly
  • fresh CAS read immediately before readiness: Main remains exact base; branch remains exact hosted head

Observed defect and repair

The pre-repair browser command failed before browser launch because docs/site/current.json pins exact public-site manifest blob 8d43188691c695f66e233727322484da22662a58, while the bridge generator, checked-in module, and browser runner admitted only the earlier exact profiles.

The exact 8d43 profile was recovered from native commit b7deb198722582df191006e4f47238f92e6e543d. Its delta is limited to two documentation files and one manifest metadata field, with zero control changes, no target-annotation changes, and all 15 formal files identical. The bridge remains identity/custody evidence only; it does not transfer execution, review, or scientific meaning.

The first hosted run also exposed stale transitive site-release pins. That red was preserved, reproduced, and fixed by deterministic tools/site_asset_release.py; the five generated import/query pins now bind the new bridge module hash.

Actual focused local verification

  • focused Python custody/control suite: 67/67 normal and 67/67 optimized
  • Node source-bridge suite: 20/20
  • adverse mutations: 3/3 killed in normal and 3/3 killed in optimized
  • site asset release: exact check passes; 46/46 normal and 46/46 optimized controls pass
  • exact G11 census: unresolved executable tools reduced 25 → 24; the source-bridge browser tool is no longer unresolved
  • unknown, resized, duplicate, renamed, forged, and resigned profiles remain refused
  • final local worktree is clean at tree 3f615867...

Exact-head hosted qualification

All eight PR workflows completed SUCCESS at hosted head 1cc79287...:

  • public-shop run 42547003551, including actual-browser Atlas exact historical source bridge, runner adverse controls, both-mode focus/reader regressions, and preserved result frames
  • workspace-landing run 42547003622, including Lean build, leanchecker, axiom audit, negative controls, receipt binding, and restricted-container architecture controls
  • Research navigation and public source checks 42547003736
  • Current research site 42547003639
  • CBZ federation drift 42547003570
  • CBZ G11 auditor component self-tests 42547003668
  • Museum conditional source route 42547003599
  • Node status 42547003657

Local full-suite boundary (preserved, not relabelled)

This managed executor forbids local Chromium's singleton socket (socket() failed: Operation not permitted). Consequently:

  • normal discovery at the final tree exited 1; direct normal-mode reproduction identifies the same Chromium-startup denial
  • optimized discovery ran 2,459 tests in 933.609s and exited 1 with exactly 2 errors and 23 skips
  • the two optimized errors were test_atlas_focus_geometry and test_atlas_reader_scroll, both before page work at browser launch
  • direct normal and optimized test_atlas_reader_scroll reproductions fail at the same launch boundary
  • the corresponding actual hosted focus/reader/browser steps all passed

These local failures are preserved as environment-bound observations, not manufactured green evidence and not source-test failures.

Claim boundary

No final same-pass federation G0–G11 qualification is claimed. This PR is not CBZ-0 and not a terminal Partial Baseline.

@d6g8k5htny-coder
d6g8k5htny-coder marked this pull request as ready for review November 9, 2026 01:59
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-09T02:00:36.902421Z 1cc7928 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@d6g8k5htny-coder
d6g8k5htny-coder merged commit 6deca31 into main Nov 9, 2026
21 checks passed
@d6g8k5htny-coder
d6g8k5htny-coder deleted the codex/cbz-atlas-source-bridge-current-20261109 branch November 9, 2026 01:59

Copy link
Copy Markdown
Owner Author

Durable CBZ contribution checkpoint v134 is published under the stable identities:

  • status: libfile_9551d0182bcc819188edfe9f998165b3, version 134, 532600 bytes, SHA-256 a33611e2434f508e249c4effed5cbd33380c6b2bcc894ab6222cbe25101d8d5c
  • evidence: libfile_1f9ec8ce62708191972f9e2bf6295816, version 134, 358562188 bytes, SHA-256 f99bcae69fd7ae7d6117e66ba6454cae6423647d32c926b8a60e518f9c854e30

Readback was byte-identical. The evidence ZIP passes compressed-data validation, contains 13106 unique members with no duplicate names, and retains all 13102 prior v133 non-status members byte-identically.

The native ledger records Main #772 merged normally as signed/valid 6deca3198c4b11b2d1208df904f5b942cd3e4bfb (tree 3f615867f7d04f2b3e772760c25af479d26c7948) from exact head 1cc79287cd6455f8f4b3a6aade19d081609b8f2d, followed by Workspace #46 merged normally as signed/valid a3d4c50b8b94ae1e02a032f68c5411007d695fa0 (tree a9f007b18fe496c63c74680a2005acb5766535cd) with the Main gitlink exactly at 6deca3198c4b11b2d1208df904f5b942cd3e4bfb. The final sequential organization-visible open-PR search returned zero.

Boundary: G11 remains red with 24 unresolved executable tools. Full local Main discovery is not green: the managed executor denied Chromium singleton-socket creation; optimized discovery observed 2459 tests, 2 errors, and 23 preserved skips. No full-regression-100%, final G7, same-pass G0–G11, Lean/kernel replay, CBZ-0, mathematical acceptance, or scientific-review claim is made. Historical mathematics, authorship, outcomes, and failures remain unchanged.

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