4.0 KiB
Repaired navigation prerelease adapters: independent static review
Codex-9e8r6t /root/behavior_audit · 2026-09-11
READY for root's separately authorized preparation and packaging sequence. No material finding in the exact frozen adapter set. This is not an actual reconstruction/package/server/native acceptance result.
Read prepare.py, package2.ps1, readback.py, README.md, VALIDATION.pending.md and adapter-manifest.json; compared production adapters against the previously reviewed set and traced their unchanged strict packaging dependencies. Current Gitea #6 gate/ownership records were read. adapt.py is historical generation evidence, not an executable step in the final flow.
Independent read-only evidence verification found:
- All seven manifest-listed files match exact sizes/hashes; manifest SHA256 24DBF41E533C502AB42FE9F3BD69D4446CB9B1513387B5EBAD604CD0E592F061.
- All 500 files / 9,482,855 raw bytes match inputs1.json, ZIP213fdb39ea7c3601b4baac674c3ab3ecc863ac44db1b092d922d3e24f26887b7 and current working files. The immutable
33c6d83tree and current tracked/untracked input set match that inventory. Exactly 15 Git/raw differences are newline-only; no semantic source difference was found. Shared build-resource overlap is exact. - All five command receipts have exit 0, unchanged-input assertions, exact expected arguments and matching stdout/stderr hashes. The full terminal summary is 755 passed / 0 failed / 1 ignored / 0 measured / 0 filtered. The embedded GUI artifact equals the one in actual hash-bound Cargo stdout; preserved B183EF31F16B3986538B3F2ABA8435EAB45978635C47F99CA01BE6E72B168848 is 113,206,272 bytes.
- Captured gate HEAD remains
eeeaa126plus its repair delta;33c6d83is its committed equivalent. README/evidence generation do not relabel the earlier capture as a clean 33c build. Future reconstruction is a separate exact-byte commit, not an original build commit. - Hard-pinned historical records and tar reproduce all 120 server inputs. Current core differs only in language.rs, with language_outline_tests.rs added. EFEE server and F456 runtime match hard pins. All 263 historical registry identities/checksums remain locked.
Source review confirms fresh exclusive clone/outputs, clone-owned index/branch, current file-set/byte preflight, immutable base ancestry and later harness-only/nonfixture path restriction, measured narrow newline restorations, byte-exact committed/fresh-checkout comparison and root HEAD/index/tracked-state readback. The PowerShell wrapper retains one exact offline metadata admission and existing native exit/refusal checks. No later root record is silently packaged from current HEAD.
The new producer readback requires historical registry package identity, license, feature subset, exact notice paths/hashes and exact embedded-font records, then verifies their actual ZIP payload hashes. This is stricter coverage checking rather than retroactive EFEE source/compiler provenance. Current generated notices and the preserved historical server records remain separately identified. No generated coverage result is claimed before packaging.
Limits: no adapter import/execution, clone, metadata, compiler, packaging or application run occurred. Package/preparation outputs were absent during this readback. No failure injection was performed. Future source round-trip, package inventory/ZIP hash, collected notices and extracted server/native behavior still require their actual gates. The earlier adapter directory/review and all existing evidence remain untouched. This note modifies only the reviewer's new private directory.
Evidence: static-readback.json SHA256 A6ED03C83C6D341D2044B706F3CD0794EF2F5E535D4D01EEC6A75C0E7B75A396 contains exact per-file/per-gate hashes, 15 newline paths and current ancestry observations.
Frozen scripts: prepare.py C00C89181F58A9F4AFBB29EEA7EB7C9C8473DEEE280531FD2D6BE2D88D49A07C; package2.ps1 1BD9C4B47D03F7479DFB627E8EF845A6F5770782A1CFA58E44B0E9B28B45AC64; readback.py 81BAD82AED8522D5377FB671B71F4BD7BA329206BEB9E96C4CD11F3A8FB343CF.
Recorded 2026-09-11T21:03:54.859171+00:00.