Validate the Classic source export separately from retained Modern history (by Codex)

This commit is contained in:
Codex committed 2026-10-30 15:50:36 +01:00
1 parent 8ee062ea46
commit 3cce6465d0
2 files changed
+8 -1

No files matched your search

+4
View File
@@ -11,3 +11,7 @@ Status: implementation candidate, not final-release acceptance.
- Author defect reference: original hash and all 1,084 listed original/changed bytes checked. All 33 defects are tracked privately; source inspection is not regression acceptance.
Still required: dedicated original-game/GUI/save roundtrips, completing the original-defect audit, per-edition gameplay review, Windows/macOS native checks and release-package acceptance. No final 1.0 tag is justified by these checks alone.
## Source export versus retained history
The restored Classic tree passes the source-only guard. The retained 0.2/0.3 history still contains launcher artwork and editor QA screenshots, which the old Classic guard classifies as binary content; this is not a clean all-history audit. CI checks the current tree actually exported by the source-package tool. The stricter `check_public_tree.py --history` command remains available for a separate repository-history audit. No history has been rewritten and no historical assets are added to the Classic source archive.