Fr0zkaandClaude Opus 5
a7b8d10de6
Tools/VoxelForgeTest.ps1 runs scenarios (canonical, owner, probe, perf, tests, parity) with the known-good flag sets, isolated user/config dirs, serialized launches, an owner-process guard, and a compact result.json + summary.txt instead of 300 MB logs that Codex has to stream. Answers the owner's question 'can the commandlet reflect in-game behaviour': -gameconfig=1 makes the commandlet use the authored settings, and the parity scenario compares per-tile geometry hashes between the commandlet export and the game's streaming path. Parity PASS: 64 commandlet tiles vs 810 game records, no differing tile. First run of the tests scenario: 44 tests, 28 pass, 16 fail (8 composer, 6 op-stack equivalence, PassageLandsInOpenSpace, StrateParamBlendCoverage). Triage is the next round: stale expectations from the floor removal and the degrees change, versus real defects, especially the legacy-vs-op-stack equivalence ones. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MmSoF64BbRFmk9C3p1VsBJ
20 lines
334 B
Plaintext
20 lines
334 B
Plaintext
# Ignore everything
|
|
*
|
|
|
|
# But keep this gitignore file
|
|
!.gitignore
|
|
|
|
|
|
# Keep Source folder and its contents
|
|
!/Source/
|
|
!/Source/**
|
|
|
|
# The guarded single-entry test harness is source, not generated output.
|
|
!/Tools/
|
|
!/Tools/**
|
|
|
|
!VoxelForge.uplugin
|
|
|
|
# Keep every design / doc markdown at any depth (AUDIT P1 — these were untracked)
|
|
!*.md
|