- All 5 walker hashes are recomputed client-side on save from the local
CompartmentsDatabase + CompartmentDefinitionDto (same build => byte-identical
hashes; no per-walker secret). Wiping any/all hashes loads/opens/edits fine;
one in-editor save regenerates everything (+ new file UUID & UniqueId).
- VERSION flag (WalkerBlueprintContainer.ValidateVersion) depends only on the
structural Compartments/Connections hashes, not the Definition hashes; ERRORS
is a separate structural check. Hashes = integrity/version-staleness markers,
not security. Server upsert validation still untested.
- Document the 5-hash table (3 top-level + 2 per-part) and offline-computability
in docs/TRAMPLER.md + CLAUDE.md; include experiment artifacts + baseline.
