# Current staged checkpoint: bounded independent integration review

Reviewed the staged checkpoint on 2026-09-06, observing 287 changed files. This is a consequential integration, reproducibility and accidental-disclosure review, not a claim to have reviewed every changed line or accepted the release objective. No production files were changed and no Cargo or native tests were run for this review.

## Findings

No material defect found within the checks below.

| Check | Observed result |
|---|---|
| Staged fixture inventory integrity | All **65** entries in the five inventories below match SHA-256 of their exact staged Git blob bytes, including inventoried generators and READMEs. No stale digest was found. |
| Byte-preserving checkout/staging | All **145** tracked files beneath the three explicitly protected path families have identical staged and working-tree bytes. `.gitattributes` disables text normalization for these exact source/recovery/history oracles. |
| Packaged teaching inputs | All **30** current teaching `.arcadia` files are tracked. `scripts/package-windows.ps1:125` enumerates tracked `docs`, `examples` and `deployment` inputs and therefore includes the complete teaching folder, including its evidence files. This checks input reachability; it does not rerun packaging. |
| Staged local/runtime data | The staged filename inventory contains no `.local`, build target, runtime executable/DLL, credential/key or environment-secret files. The source-5 recovery JSON is deliberately synthetic: its adjacent generator uses fixed test identities, `origin: None`, fabricated source and invalid raw drafts. |
| Credential-pattern scan | Zero matches in staged added lines for private-key headers, AWS access keys, GitHub/OpenAI token patterns or credential-bearing URLs. This bounded pattern scan cannot establish the absence of every possible secret. |
| Version boundary | Staged `crates/oa-core/src/model.rs` still declares schema **6**. The contextual-chain and interface-operation material is design/probe evidence; source/schema 7 is not implemented by this checkpoint. |
| Platform dependency boundary | The new direct `libc` dependency is scoped to Linux in `oa-core/Cargo.toml`; it does not introduce a Windows runtime dependency. Runtime correctness remains covered by the separate platform evidence, not by this manifest inspection. |

The checked inventories are `harness/fixtures/interface-operation-probe/hashes.json`, `harness/fixtures/release1-native/artifacts/semantic-artifacts.hashes.json`, `harness/fixtures/release1-native/communication-means/hashes.json`, `harness/fixtures/release1-native/semantic-attachments.hashes.json`, and `harness/fixtures/release1-native/semantic-batch.hashes.json`. The attachments inventory retains original absolute task-local paths as provenance; its tracked files were resolved by their unique basenames in the inventory directory and hashed from the index. No runtime data at those original paths was staged.

The byte-protected path families are `harness/fixtures/release1-native/**`, `harness/fixtures/interface-operation-probe/**`, and `harness/history/2026-09-06-ledgers-before-consolidation/**`. The existing exact upstream license whitespace must likewise remain unchanged; whitespace cleanup is not a substitute for a byte oracle.

## Reproduction and limits

Enumerate the candidate with `git diff --cached --name-only`. Hash the bytes emitted by `git cat-file blob :<path>` with SHA-256 and compare each manifest entry. For the protected path families, compare `git hash-object --no-filters -- <paths>` against object IDs from `git ls-files --stage -- <paths>`; all 145 matched in this review. The ignored detailed hash result is `.local/checkpoint-hash-audit-current.json`.

Root separately reports the latest strict Clippy pass (28.26 seconds); this audit neither reran that command nor extends its result to subsequent changes. Native verification of the newest semantic-review navigation binary remains a separate gate. Source-7 contract decisions and implementation, and the remaining objective gates recorded in the current ledger, remain unfinished. A reproducible checkpoint is not a feature-complete release claim.