Repository navigation
Conversation
|
Independent exact-final-source review request — v0.13 T04 risk-3, 1 Nov 2026. Authoritative integration HEAD is |
…th verified cross-platform regression
|
@codex review Please perform a fresh independent diagnostic code/security/architecture review of authoritative draft PR #92 at exact commit |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 26de8b3575
ℹ️ 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".
…tore recovery (H80)
|
@codex review Request fresh independent diagnostic code/security/architecture scrutiny of exact v0.13 T04 integration SHA |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d8b1e7e02e
ℹ️ 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".
|
Exact-source independent review request — v0.13 T04 risk-3 (1 Nov 2026). Current authoritative integration SHA: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: bf0cbcb959
ℹ️ 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".
| const loadedSnapshot = loadStateSnapshot(rootDir, { rebuildIfNeeded }); | ||
| if (!loadedSnapshot && !rebuildIfNeeded) return null; | ||
| const snapshot = loadedSnapshot ?? emptySnapshot(); | ||
| const paths = statePaths(rootDir); |
There was a problem hiding this comment.
Disable bootstrap recovery in read-only index preflight
If an initializer publishes a bootstrap hard link and exits between the snapshot read and this second path lookup, loadStateIndex(rootDir, { rebuildIfNeeded: false }) still mutates recovery evidence because statePaths() defaults to enabling bootstrap recovery. Reproduced on Linux against the requested tree: initialize an empty layout, remove index.db, then have a child publish its bootstrap index link and exit before unlinking the staging name during the snapshot read. The read-only index lookup succeeds, deletes the staging entry, and reduces the canonical link count from two to one. Unlike the corrected scale-context GET path, this public index reader therefore retains a recovery-enabled preflight. Pass recoverBootstrapIfNeeded: rebuildIfNeeded here so the read-only call fails closed without consuming the interrupted initializer's evidence.
Useful? React with 👍 / 👎.
DKF130-T04 — State Engine V2
First v0.13 priority, rebased from the released v0.12.1 line.
Scope
Preserved
All released v0.12.1 T01–T03/T05–T10 semantics remain in place. Historical v0.12 State Engine branches are source material only.
Explicitly not claimed yet
This PR is not accepted merely because CI passes. T04 remains risk level 3 and requires independent code, architecture, and security review plus security-control evidence bound to the exact reviewed source.
Deferred/out of scope