docs(devlog): record dev release readiness and the raw-bun-test harness trap

[lidge-jun]

Summary

Records that dev @ 4b95010 passes every repository gate, and documents a harness misuse that made the suite look broken when it was not.

An earlier full-suite run in this session invoked bun test directly and reported 122 failures. That count also appeared unchanged on the pre-session baseline, which is what first indicated it was not caused by any recent change.

bun test is not this suite's entry point. package.json maps test to scripts/test.ts, which builds an isolated environment per run — a mkdtemp root with HOME, USERPROFILE, OPENCODEX_HOME, and CODEX_HOME inside it, plus OCX_REAL_HOME captured before the rewrite. Run raw, none of that exists: suites that persist config resolved to the operator's real ~/.opencodex, and assertNotRealHomeUnderTest correctly refused the write. All 122 failures are that refusal surfacing downstream as empty usageRows(), a missing admissionKind, or a 503 where a 429 was expected.

The guard behaved exactly as designed. No product change was needed, and none is made here — this PR is documentation only.

Verification

Run on the Linux validation host against this exact head:

bun run test        12388 pass, 11 skip, 0 fail, 158046 expect() across 789 files (447.98s)
bun run typecheck   clean
bun run privacy:scan  Privacy scan passed
bun run build:gui   built, package prepared
bun run lint:gui    0 warnings, 0 errors

CI on 4b95010: ci, gates, test 1-4/4, macos, keyring (ubuntu/macos/windows), npm-global (ubuntu/macos/windows), storage policy, api usage — all success.

origin/dev, the local checkout, and the validation host all sit on 4b950101a1116d8bac4e479cb2dceca3bb80370e.

Corroboration that the failures were environmental: the same files pass in isolation, a six-file group of the heaviest offenders passes 216/216, and the full suite through the real entry point reports zero failures.

Checklist

• Documentation only; no runtime code changed
• Full suite, typecheck, privacy scan, GUI build and lint all green on this head
• No credentials, request bodies, or account identifiers recorded
• Makes no release claim — no version bump, tag, publish, or promotion

Summary by CodeRabbit

• Documentation
  • Added a release-readiness record documenting successful validation across tests, type checking, privacy checks, builds, linting, and continuous integration.
  • Documented validation alignment and clarified test results from the supported isolated test environment.
• Release Management
  • Confirmed that no release, version update, publication, or branch promotion was performed.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 380912e4-c27e-4ae6-89d5-4888de6eaf56

📥 Commits

Reviewing files that changed from the base of the PR and between 4b95010 and 188e021.

📒 Files selected for processing (1)

• devlog/_plan/260815_roadmap_closeout/110_release_readiness.md

---

📝 Walkthrough

Walkthrough

The PR adds a release-readiness record for dev. It documents validation results, test-environment safeguards, commit alignment, and the absence of release promotion actions.

Changes

Release readiness

Layer / File(s)	Summary
Release validation record devlog/_plan/260815_roadmap_closeout/110_release_readiness.md	Documents test, typecheck, privacy, GUI, and CI gate results. It distinguishes bun run test from raw bun test, records isolated test-environment protections, confirms commit alignment, and states that no release promotion occurred.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• lidge-jun/opencodex#899: Documents the CI gates and workflow outcomes covered by this release-readiness record.
• lidge-jun/opencodex#1759: Adds a separate documentation-only devlog record for execution and validation results.

Suggested reviewers: ingwannu, wibias

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-readiness-260815

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 188e0215cb

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Correct the raw bun test diagnosis

On this exact parent, a bare bun test still loads bunfig.toml, whose [test].preload points to tests/preload.ts; that preload calls createIsolatedTestEnvironment(), rewrites HOME, USERPROFILE, OPENCODEX_HOME, and CODEX_HOME, and arms the real-home guard (tests/preload.ts:14-34). The checked bun test --help describes the bare invocation as “Run all test files” and exposes no flag used here to bypass repository test configuration. Consequently, a normal raw invocation on this head cannot have resolved persistence to the operator's real home as claimed, so this record misattributes the 122 failures and could derail future triage. Correct the diagnosis or document the concrete invocation/environment that bypassed bunfig.toml.

Useful? React with 👍 / 👎.