Document architecture checkpoint and restore original task callback order

This commit is contained in:
UnixNight committed 2026-10-25 12:56:17 -04:00
1 parent 69d0187a21
commit 531883aaac
45 files changed
+2935 -43

No files matched your search

+25
View File
@@ -0,0 +1,25 @@
# Preserved playable baseline
Baseline: `69d0187a2178deab1edff961d5126dad1cce3a05`, clean source tree at checkpoint
entry, local annotated tag `baseline-re-checkpoint-2026-10-25`. Existing Linux and
Windows packages were copied, without hard links, to
`artifacts/re-checkpoint/baseline/{linux-x64,win-x64}`. Their BuildInfo records
identify69d0187 and clean source. These ignored local copies are comparison tools;
subsequent builds must not overwrite them.
`artifacts/re-checkpoint/original-preservation-start.log` verifies all539 original
files against `docs/original-manifest.json`. Originals were read, never modified or
executed in place. All work remains local. A pre-existing `Gitea` Git remote is
configured; it was not contacted or changed. No fetch/push/remote-service operation
was performed. Older notes saying the repository has no remotes are stale.
The user has traversed lab → tutorial → lab → outside in their Windows build.
Earlier Linux managed, GPU and SDL tests demonstrate port behavior; package
cross-compilation and Wine checks do not establish native Windows verification.
No usable running-original gameplay capture exists. Static code evidence and
isolated DLL probes must not be reported as original end-to-end verification.
Modern authorized baseline policies include F1/F2 diagnostics, persistent SDL/Vulkan
presentation across level changes and uniform widescreen UI. They are not claims
about the original. Fixed60Hz simulation, provisional player capsule/feet grounding,
grouped system phases and duration-driven camera completion remain fidelity gaps.