From f8194dbf92f46f9a4018fa60d007f27de1ffccaf Mon Sep 17 00:00:00 2001 From: Fr0zka Date: Mon, 27 Jul 2026 02:07:49 +0200 Subject: [PATCH] docs: correct an inaccurate claim in an earlier progress entry The "starting Phase 0.5" entry said the ClassifyTile test self-skips when the fixture fails to build. It does not -- all four tests fail loudly with a message identifying it as a fixture failure. Corrected by appending, since the log is append-only. Co-Authored-By: Claude Opus 5 --- OPSTACK-PROGRESS.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/OPSTACK-PROGRESS.md b/OPSTACK-PROGRESS.md index dc2c6a2..4325115 100644 --- a/OPSTACK-PROGRESS.md +++ b/OPSTACK-PROGRESS.md @@ -164,3 +164,14 @@ fixture's `TSoftObjectPtr` → transient-`UVoxelStrateDefinition` resolve has ne `OPSTACK-DECOMPOSITION.md §11`, then port Maze. Do not write more plugin C++ before the build. --- + +## 2026-07-27 — correction to the 3rd entry above + +The entry *"starting Phase 0.5"* says the `ClassifyTile` test **self-skips** if the fixture's +`TSoftObjectPtr` resolve fails headless. That was the plan; it is **not** what was written. All four +tests call `AddError(World.WhyInvalid())` and FAIL, with a message that says explicitly it is a +fixture failure and not a density bug. Failing is the right behaviour — a skip that reads as a pass +is exactly what hides bugs — but the earlier entry describes code that does not exist, so it is +corrected here rather than edited (this log is append-only). + +---