docs(M03): hand off WMO scene resource cache state

This commit is contained in:
2026-07-17 01:19:36 +04:00
parent c83929428d
commit ff4f320412
@@ -82,14 +82,30 @@ version validation.
## Status ## Status
- State: claimed - State: ready for integration
- Done: lifecycle and four negative-cache sources identified - Done: state holder implemented; loader lookup/request/drain/reset/metrics
- Next: implement state holder, migrate loader adapters, verify and document adapters migrated; shutdown regression and required documentation updated
- Next: integrate and run post-merge smoke on master
- Blocked by: - Blocked by:
## Handoff ## Handoff
- Commit: - Commit: `c839294`
- Results: - Results: scene cache-state PASS (`cases=11`, `iterations=100`,
- Remaining risks: `elapsed_ms=40.768`; initial direct cold run `43.636ms`); render cache-state,
- Documentation updated: WMO queue/planner/registry/resolver/material/shutdown plus 18 adjacent
M2/terrain/facade/scheduler/streaming/coordinate regressions PASS;
documentation and coordination gates PASS; checkpoint dry-run PASS `7/7`.
- Remaining risks: accepted PackedScenes remain strongly referenced until full
shutdown release; ResourceLoader/FileAccess I/O, cache-validation probes and
live fallback remain in loader; no proprietary stale/oversize fixture,
asset-backed traversal/leak run, p95/p99 or original-client paired evidence.
The extracted scene state passed cold; full loader cold execution still needs
editor class registration for pre-existing focus/coordinate global classes.
- Documentation updated: inline public API; new
`docs/modules/wmo-scene-resource-cache-state.md`; render-cache spec, module
registry, world renderer and `RENDER.md`; data-flow/state/sequence diagrams,
ownership, threading, file-size/cache-version boundary, failure/recovery and
source map included.
<!-- OPENWC_HANDOFF:READY:M03-RND-WMO-SCENE-RESOURCE-CACHE-001:c839294 -->