6.3 KiB
Ordinary compact source and Text workspace integration
This proposal composes ordinary source-default omission with the published Text workspace. It does not replace the release owner's branch or establish release acceptance. Issue 11 owns this contribution; issue 27 retains release integration. Source-8 analysis composition and Linux verification remain outside this candidate; Linux work is paused at the user's instruction.
Source composition
Production commit d7c065991d3f63cc41341d23a546739de8837ac3 applies the exact
14-file ordinary code/test delta from 74cc0e09119f9fa9e1287988bdd98c4cbf9db79e
to 3d067041d1c8b62bc4b2bd1e2ae81eb2713bf4e2 onto published Text/root
136ed6e5868200165fbb1c2ae8a7230067bf9c1e. Thirteen preimages match, including
seven paths absent on both bases. The only other preimage difference is
lib.rs's independent pub mod analysis_numeric;, retained with the new private
mod source_defaults;. Thirteen resulting files match the ordinary head exactly;
the combined lib.rs additionally retains the numeric module. The original
145,928-byte patch has SHA-256
e319a5151b7e6713880eaaab632f3f1c01aee6df3cd534d85a1c099fb501dcb7.
Follow-up e624d5b9c4f848eff3fba2ed83f9decf959e14d8 brings over the ordinary
normative language-contract delta and regenerates the current teaching example.
The full core run identified the latter dependency: its exact generated-source
assertion still expected verbose defaults. The documented generator produced
30 source files and four JSON files. Twenty-nine source files changed, removing
514 default-field lines; the root entry, all four JSON files, and all 68 historical
trace baseline blocks remained byte-identical. Generation asserts complete
decoded Project equality. The test assertion was preserved.
Strict Docutils 0.23 rendering exposed an existing one-character-short underline on the focused diagram removal heading. Repairing it allowed warning-free HTML generation. Regeneration also restores the root's existing allocation/removal sections that were missing from its previous HTML. No semantic prose from those sections changed.
Verification to date
Windows toolchain: Rust/Cargo 1.98.1, stable-x86_64-pc-windows-gnullvm, LLVM-MinGW
20260826 UCRT, one build job, CARGO_INCREMENTAL=0. Each Cargo run captures its
707 source inputs before and after, including all 71 vendored Iced widget files,
raw logs, process identity, and executable artifact hashes. A captured HEAD with
local deltas is not represented as a clean-commit run.
- The initial combined-consumer attempt stopped before compilation because
num-bigintwas absent from the offline cache. A locked Windows-target fetch installednum-bigint 0.5.1andnum-integer 0.1.47; sources and lock stayed unchanged. - Full core at clean
d7c0659: 536 passed, one failed, one existing opt-in scaling probe ignored, across 46 result summaries. The sole failure wasrelease1_teaching_regeneration_and_shipped_source_are_exact_with_one_intentional_warning. The source-transaction panic messages are deliberate interruption injections in passing recovery tests. - The documented teaching generator completed successfully against the same production inputs, writing to a separate scratch folder. All 34 generated files were compared with the repaired shipped fixture.
cargo test --locked --offline -p oa-core --test release1_teachingagainst the repaired fixture: four passed, including exact source/JSON parity and the one intentional coverage warning. This run capturedd7c0659plus the 29 fixture changes subsequently committed ine624d5b; production was unchanged.- Strict language HTML generation: passed with an empty warning log.
- CLI/HTTP consumers: 12 CLI and 51 HTTP passed, no failed or ignored
cases. The HTTP preservation witness exercises an actual move and server
restart with an explicitly authored empty port-anchor list. The two Windows
storage-refusal messages are expected from atomic-storage failure tests.
This run started at
d7c0659plus the 31 fixture/documentation changes now ine624d5b; all 707 captured inputs remained unchanged through execution.
Actual desktop listing admission, desktop execution, strict workspace Clippy, matching Windows binaries, and native combined-workflow acceptance are not established by the results above. Earlier ordinary-only native and automated evidence remains scoped to its original published inputs.
Independent review
Astra review checked exact Git-blob composition and the source-preserving updater, raw diagnostic coordinates, source publication ordering, warning authority after recovery, rename/history/save ownership, schema-7 boundary, and historical payloads. No actionable source defect was found. Separate follow-up review confirmed all 34 regenerated files and 68 unchanged historical blocks, then checked the scoped reST delta, preserved root sections, generated HTML, and strict-render receipts.
A source-pinned checklist identifies 150 critical desktop declarations: all 89 imported desktop additions, both later recovery-warning fixes, retained selection and departure cases, additional recovery/Save As/rename/navigation controls, and six explicitly ignored probes. This is expected membership only; lexical counts are not executable admission or passing runtime results.
Portable closed-run checkpoint
The evidence package
contains the eight closed captures described above, including failed runs, exact
input snapshots, raw generated outputs, and the source-admission checklist.
Its ZIP contains 81 members with three distinct input manifest/archive pairs:
8,584,848 bytes, SHA-256
f220433f8f6fe99cea762aca98ee471c14411b5f6762745cf91432e6bfaca440.
Run the package's verify.py with Python 3.10 or newer; it requires only the
standard library and the five adjacent package files. It verifies integrity and
receipt relationships without executing archived code or consulting this machine.
The README records provenance limitations and the absence of runtime binaries.
All 707 consumer inputs were independently compared with committed Git blobs at
e624d5b9c4f848eff3fba2ed83f9decf959e14d8 and matched exactly.