# Mixed CLI runtime review

Final source: `f10490b13bb3332ff60c2372d554e276f6f44959`. Parent ran the independent data reader once with exit0; this reviewer inspected its completed readback and selected raw logs/streams without rerunning the checker, Cargo or product binaries. Readback `MIXED-CLI-RUNTIME-READBACK.json` SHA256 `1b02b0eb3870cbc4074542467ef527acb7b13e9956674115484ebc82d3a5d97b`; checker SHA256 `42dc33fbdcc17331c13995c9b3202c10ecc010635f6de07aaeb52cef2c8086c4`; plan SHA256 `b43452757ed101484863ab97b4ea210469ab203bfd0d2f7344d7562a5efeebf0`.

No unresolved runtime discrepancy was found within this checkpoint's scope.

## Final outcomes

- Core302/302, preserving all299 baseline named passes and adding exactly the three discovery tests. The focused discovery run passes the same three names. Full log SHA256 `7328cd7bf0b86db45a2bed68e4a99f73f4859917d7dc3156ca89c1e1aaf8102e`.
- Eleven integration list/run pairs pass98 named tests: mixed filesystem5, new mixed CLI6, existing source_cli12, public mixed-read10, and the seven selected ordinary suites65. The12 source_cli names were compared against baseline source; their prior successful execution was never claimed.
- Three doctests pass in groups1+2. The two exact CheckedMixed compile-fail runtime suffixes are reconciled to their listed names by the reviewed recorder mapping; raw names remain preserved. Current recorder verification succeeds, unlike the historical public-read spelling refusal. Doc log SHA256 `85d55fbea6963e6c3e1108a10f84e4d2e9cd5a7a8d094d3b7e6a68a43ed93ac5`.
- Strict all-target core+CLI Clippy exits0. Formatting still exits1 with byte-identical inherited log SHA256 `c1c6b12861c8117ce6ffc6d6742ebf92618aafb10160ec6f99d370ca72ebab2d`; it is not reported as a formatting pass.
- Five additional actual CLI invocations meet their literal oracles: ordinary check and rename preview, mixed valid JSON, unresolved JSON and valid human output. They share the recorded build artifact. Whole reports, exits, raw streams, original file bytes and complete fixture directory inventories match. The unresolved reference remains `sub/f.arcadia`, bytes208..215, line3/column154; valid human output is exactly `checked: mixed source8 check; no files changed` plus newline on stderr, with empty stdout.

The readback reconciles30 final Cargo receipts, six preserved initial Cargo receipts and five CLI receipts:41 total records. Final records bind567 declared inputs to Git/current bytes, exact reviewed launcher/command/environment, artifact origins and clean post-run source. Baseline is public-read bab6f96a, archive SHA256 `1c20b7bffdaee9b1139b0e922d4366f6ac739f8567040e8f4723dc19e3974656`.

Final core executable:43,394,560 bytes, SHA256 `cc940d9e50873cda3470d2fdf381b2b9b73221399b70cf2e0e26b6aecda71f38`. Final CLI executable:23,530,496 bytes, SHA256 `54d4c9ec305e9330b3c5a81905129e47db52a4ef459a8bbe663986208d1730dd`. These are debug verification artifacts, not a packaged release claim.

## Preserved initial findings

Initial f232482 passed the new core filesystem5 and mixed CLI6 tests but emitted the Command glob-shadow warning. Its existing source_cli run passed10 and failed2: `complete_alarm_example_preview_then_write_and_fixed_point` and `rename_shows_missing_identity_and_separate_source_migration`. Their stale schema7 destination expectations were corrected to current schema8 without production changes. The complete stripped-byte comparison,40 identities, preview/write/fixed-point/model checks remain; the warning repair only aliases the process-command import. All six original list/run receipts and failure/warning logs remain preserved, separately from final results.

Initial566-input manifests omitted the actual include_str alarm fixture under `harness/experiments/textual-authoring-20260911/alarm-response.arcadia`. Final recorder15d3bae6 adds that exact path, yielding567 inputs. Its initial/final Git blob SHA256 is identically `d5e75f60081a7d99b0e10387c5d722064abbe022a022f376d7bf742ac0d69b0b`; this does not retroactively prove initial raw capture. The omission and repair are explicit in the readback, source review and launcher review.

## Scope

All eleven exact existing core stack controls and the selected structural-writeback integration control pass. These qualify their exercised worker paths only; no universal stack headroom, all-allocation/RSS, Linux or broad depth128 guarantee follows. Discovery and complete checking remain two separately bounded passes. This verifies explicit read-only mixed filesystem/CLI validation and ordinary regressions, not mixed editing/save/history/GUI adoption or an atomic snapshot against concurrent writers. Parent owns final integration, publication and stopping work.