zwitschi/gig-line
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

qa(diag): gate setup logs behind gigline.SetupLogs cvar (#14)

Browse Source 
Merged PR #14: gate setup logs behind cvar

Co-authored-by: Zwitschi <zwitschi82@gmail.com>
This commit was merged in pull request #14.
This commit is contained in:
zwitschi authored and zwitschi committed 2026-11-08 15:01:33 +01:00
1 parent 71acffec12
commit 31f073d608
4 files changed
+48 -14
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

MEMORY.md
+12
View File
@@ -319,3 +319,15 @@ Scope: facts and traps that cost time to establish. Planned work lives in [TODO.
at t=2s with "ShotActor: done (4 shots)" + RequestExit).
- Results on packaged build: walk 761cm/2s, reset 0cm, pause/unpause, transect
0 holes, wall 0/35 -> all PASS. Evidence recorded in Docs/release-checks.md.
## 2026-11-08 — setup logs gated behind a cvar (diagnostics item)
- The remaining spawn/input setup logs (settle-timer "start captured", "GigLine
IN:" pushed/bound/errors) are now gated behind `gigline.SetupLogs`
(TAutoConsoleVariable, default **0** via `DefaultEngine.ini [ConsoleVariables]`).
Re-enable at runtime: `gigline.SetupLogs 1`.
- The `-qaselftest` QA logs stay ungated (deliberate release-check feature per
Docs/release-checks.md). Verified packaged build: 0 setup-log lines, QA suite
still all PASS (walk/reset/pause/transect 0 holes/wall 0-35).
- Branch qa-diagnostics-0.1.0. SIM/GROUND probes were removed earlier in the
DefaultKeyMappings fix (PR #8).