Record verified ordinary source8 compatibility and CLI evidence

This commit is contained in:
2026-09-24 21:09:28 -07:00
parent 763e6d8256
commit e79645a0ec
17 changed files with 2437 additions and 3 deletions
+24
View File
@@ -733,3 +733,27 @@ behavior. Preserve the initial two incorrect empty-warning expectations and thei
independent full-warning correction. A raw build-target path spelling difference
requires only a named exact-pair checker amendment, not weakened failure or source
comparison. All earlier outcomes remain preserved; public integration is next.
## 2026-09-25 — restore ordinary schema8 compatibility before mixed adoption
Current formatters already emit schema8, while the ordinary reader previously
rejected it. Admit that version through the existing ordinary grammar and model
validation, preserving migration, complete source indexes, identity stabilization,
updates and checked saves. Keep typed and long analysis-constructor refusals;
ordinary acceptance does not qualify missing typed formatting or mixed editing.
The [contract and independent comparison](ordinary-source8-compatibility-contract-20260925.md)
reject replacing compile_bundle with an incomplete read-only index.
[Windows evidence](experiments/ordinary-source8-20260925/README.md) exercises the
previously blocked nested/transaction workflows, complete ordinary OA/SA and
historical trace round trips, relevant integration tests and actual read-only CLI
commands. Preserve the initial example-trace assumption failure, four obsolete
private header-rejection assertions and the historical JSON oracle's missing
empty definitions catalog. Correct their expectations explicitly while retaining
whole-model and typed-refusal checks; two test renames have exact inventory maps.
Reuse the source-identical core, other integration and CLI evidence after the last
three-line migration-test correction. Verify the entire successor diff and every
other declared input, rerun the affected target plus all-target Clippy/format, and
identify each tested code version. No Linux, GUI or release qualification follows
from these core/CLI results. Publication remains blocked by server disk exhaustion.