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

This commit is contained in:
2026-07-17 01:11:27 +04:00
parent d39f591e50
commit b4b94b3cbb
@@ -80,14 +80,30 @@ cache-format validation.
## Status ## Status
- State: claimed - State: ready for integration
- Done: scope and state transitions identified - Done: state holder implemented; loader cache/request/reset/metrics adapters
- Next: implement state holder, migrate loader adapters, verify and document migrated; shutdown regression and required documentation updated
- Next: integrate and run post-merge smoke on master
- Blocked by: - Blocked by:
## Handoff ## Handoff
- Commit: - Commit: `d39f591`
- Results: - Results: cache-state PASS (`cases=10`, `iterations=100`,
- Remaining risks: `elapsed_ms=58.727`); direct no-`.godot` cache-state run PASS (`45.361ms`);
- 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 Resources remain strongly referenced until full
shutdown release; cached-scene and ResourceLoader I/O seams remain in loader;
no proprietary corrupt-cache fixture, asset-backed WMO traversal/leak run,
p95/p99 or original-client paired evidence. Full loader cannot be used as a
direct empty-class-cache smoke because pre-existing typed global coordinate/
focus dependencies require editor class registration; the extracted service
itself passed cold and normal editor parse passed.
- Documentation updated: inline public API; new
`docs/modules/wmo-render-resource-cache-state.md`; module registry, WMO queue,
world renderer and `RENDER.md`; data-flow/state/sequence diagrams, ownership,
threading, cache-version boundary, failure/recovery and source map included.
<!-- OPENWC_HANDOFF:READY:M03-RND-WMO-RENDER-RESOURCE-CACHE-001:d39f591 -->