docs(render): finalize Campaign AR machine-local gate

This commit is contained in:
Erik 2026-08-22 14:14:40 +02:00
parent d78ce100d6
commit d84edf0ceb
3 changed files with 53 additions and 24 deletions

View file

@ -1,9 +1,9 @@
# Campaign AR Stage 2 connected and closeout gate
**Date:** 2026-08-22
**Verdict:** PASS for every machine-local Stage 2 row; external hardware,
second-client remote-player evidence, and final project-owner acceptance remain
explicit gates
**Verdict:** PASS for every machine-local Stage 2 row that the available
credentials and hardware can exercise; a distinct-account remote-player row,
external hardware, and final project-owner acceptance remain explicit gates
## Scope and evidence boundary
@ -113,28 +113,53 @@ Every process connected, entered world, captured its render-pack metadata,
disconnected, and exited with code zero. Failure rows created no half-active
pack and recovery required an explicit corrected selection.
## Remote-player gate availability
The connected remote-player gate was exercised on exact commit `a861510a`:
[`artifacts/atmospheric-rendering/connected-remote-player-20260822-140355/report.json`](../../artifacts/atmospheric-rendering/connected-remote-player-20260822-140355/report.json).
The observer entered the world and moved at the target location. The concurrent
primary client then timed out waiting for `CharacterList`: ACE did not permit a
second simultaneous character from the same account. Both clients were closed
cleanly, and the failed row is not represented as renderer evidence.
The gate now accepts a separate observer account and password, keeps credentials
out of its report, fails fast on session failure, and records whether distinct
accounts were configured. The authoritative nonzero `RemotePlayers` caster row
and visible moving remote-player shadow therefore require only access to a
second account; no missing renderer or test-harness implementation remains.
## Final automated gate
On clean exact code commit `f92479ac`:
On clean exact code commit `d78ce100`:
- managed shader regeneration compiled **24/24** Vulkan pairs and produced no
tracked SPIR-V difference;
- forced locked restore passed;
- the complete Release solution built with **0 warnings and 0 errors**; and
- the repository-owned fresh-process gate passed **15,178/15,178** tests with
zero skips or failures across 14 assemblies. App contributed **5,950/5,950**.
- the repository-owned fresh-process gate passed **15,179/15,179** tests with
zero skips or failures across 14 assemblies. App contributed **5,951/5,951**.
The complete logs, TRX files, environment inventory, hashes, and aggregate
summary are under
[`artifacts/atmospheric-rendering/stage2-closeout-release-gate-f92479ac/`](../../artifacts/atmospheric-rendering/stage2-closeout-release-gate-f92479ac/).
[`artifacts/atmospheric-rendering/stage2-closeout-release-gate-d78ce100/`](../../artifacts/atmospheric-rendering/stage2-closeout-release-gate-d78ce100/).
An earlier rerun exposed that the dense-shadow allocation assertion had only a
single warmup frame and could include tiered-JIT work under full-suite parallel
load. Commit `d78ce100` changes that test fixture only: it performs a complete
64-frame dense warm window before measurement. The focused test passed 12
fresh-process repeats, the complete App assembly passed, and the final gate
above is the authority; production renderer behavior was not changed by this
hardening.
## Remaining external gates
Campaign AR is not declared shipped by this report. Three evidence classes are
not available to this machine-local run:
1. A second connected client/account must produce a nonzero authoritative
`RemotePlayers` caster row and a visible moving remote-player shadow.
1. A second connected client using a distinct account must produce a nonzero
authoritative `RemotePlayers` caster row and a visible moving remote-player
shadow. The connected gate is implemented; the available single account was
rejected by ACE for concurrent play as recorded above.
2. Supported physical GPU classes other than the installed Radeon RX 9070 XT
and integrated AMD adapter must repeat the required pack-off/Low/Medium/
High/Auto resolution and pacing rows. The integrated adapter currently