Explain raw test log whitespace preservation

2026-09-12 15:58:25 -07:00
parent 2488ee5955
commit 0eca66f669
1 changed files with 4 additions and 0 deletions
@@ -9,3 +9,7 @@ All three failures of the [older source](README.md) now pass. The passing run in
 The one ignored case is `app::source_symbols::tests::source_symbols_100_modules_1000_definitions_10000_uses`, explicitly a manual latency/process-memory trial intended to run alone. This result does not establish its performance threshold or large-model native responsiveness. The host also ran an independent core compilation and Capella startup during portions of execution; elapsed time here is not a comparative performance benchmark.

 Core-specific outline tests and strict lint are separate gates. A matching GUI build and native acceptance of the corrected source remain pending. The process/scenario free-editing requirements are still unfinished, and Linux/WSL remains paused by the user.
+
+## Raw-log preservation
+
+The evidence commit preserves the test output byte for byte, including its terminal blank line. The unrestricted Git whitespace check reports that blank line at `correction-tests.log:910`; it is an intentional raw-evidence exception. The same check excluding this exact raw log passes for the report, receipt and manifest changes. This does not change the successful source whitespace check recorded in the correction handoff.