Skip to content

Verify recovered Experiment 2 evidence and current TLS/runtime behavior - #20

Merged
k2jac9 merged 1 commit into
mainfrom
fix/issues-17-18-20261116
Nov 16, 2026
Merged

k2jac9 merged 1 commit into
mainfrom
fix/issues-17-18-20261116

Conversation

@k2jac9

@k2jac9 k2jac9 commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Problem and resulting behavior

The recovered Experiment 2 archive needs an independently checkable link to its published aggregates, and the historical TLS failure has no recoverable runtime. This change adds a bounded offline archive verifier and a read-only TLS diagnostic, records what the recovered files establish, and refreshes the expired runtime selections.

Task and architectural contract

  • Task: follow-ups Recover and verify the original Experiment 2 evidence #17 and Diagnose the local TLS trust-store discrepancy without weakening pinning #18; offline evidence verification and runtime qualification.
  • Reviewed commit: 06499e76828292339b696faa6e933c2f7d323115, based on 2160a55324404d6bf9d35d5c7f7132607bbe590f.
  • Owned paths: scripts/verify_experiment2_archive.py, scripts/diagnose_tls_roots.py, tests/test_experiment2_archive.py; the runtime matrix and two dated receipts under ci/; data/README.md, build/runtime reports, and the two dated investigation reports.
  • Preserves ADR-0001/0002/0006/0010/0012, historical archives/aggregates and production TLS assertions. No ADR change is proposed.

Verification evidence

  • The archive verifier checks 77 member hashes, 41,995 prompt/receipt bindings across 14 runs, and 46 frozen-count comparisons; 20 mutation/behavior tests pass.
  • Local full suite: 399 tests on the current Python 3.15.2 host and each of seven pinned Python runtimes. Five viewer tests pass on each of five pinned Node runtimes.
  • Python lanes also pass submission verification, task validation/planning and a scripted demo. Exact local artifact, executable, code and log hashes are in ci/runtime-validation-20261116.json.
  • Focused TLS checks pass with ordinary and isolated startup; initial roots are empty on the current host. Existing root, hostname, untrusted-certificate and environment-control assertions remain active.
  • Initial local timeout/launcher failures and inherited SQLite ResourceWarnings are retained. Corrected launch setup was followed by complete reruns.
  • Hosted Ubuntu CI passed all 13 jobs (selection plus 12 lanes) in both the PR run and push run. Each run passed 399 tests per Python lane and five tests per Node lane. All 24 uploaded artifacts were downloaded, digest-checked, and checked against the exact runtime, lockfile, matrix and source identities.
  • The PR tested merge commit 2b65343f5dcf3199ce302e7922dd4597f2220676; its Git tree f66c121004fa05c962053536bd9748887d21e56c exactly matches reviewed head 06499e7. Existing SQLite ResourceWarnings remain visible. No deployment or rollback qualification is claimed.

Review and limitations

Independent code and evidence reviews found no remaining findings. The owner authorized integration after hosted checks pass. Paired inputs, experimental data and production TLS code are unchanged.

Refs #17 and #18; this PR does not close them. Private-original preservation, a second person's fresh-checkout reproduction, missing stopped-run records and external billing/authenticity remain separate requirements. The unavailable Python 3.12.14 environment's extra trust root remains unexplained.

AI assistance / prior-work provenance: Codex assisted implementation, regression tests, diagnostics and documentation; a separate review agent checked code and evidence. The existing archive published in #19 was read without modification. No paid model call or new credential was used.

Integration result

Merged as e48a75a331b61cfa7f0b861805f485a0e5c47bc5. The repository's automatic Codex code review completed on 06499e7 with no findings. The post-merge main workflow passed all 13 jobs, and all twelve uploaded runtime artifacts were independently checked against the merged commit, exact runtime/lockfile/matrix identities and full test results. The merged tree is identical to the reviewed/tested tree. Local main was fast-forwarded and is clean; existing worktrees and WIP were preserved. Issues #17 and #18 remain open for the historical requirements above.

Add bounded offline archive checks and regression coverage, plus a read-only
TLS root diagnostic. Refresh exact runtime pins and record successful local
validation across all twelve lanes, retaining historical evidence limits.

Refs #17, #18
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 16, 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-16T09:23:06.916122Z 06499e7 PR opened
ℹ️ 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.

@k2jac9
k2jac9 merged commit e48a75a into main Nov 16, 2026
26 checks passed
@k2jac9
k2jac9 deleted the fix/issues-17-18-20261116 branch November 16, 2026 10:13
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