Harden realm continuity and authority boundaries - #149
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
Interrupted WebView navigation or presentation changes could leave local interaction latches stale. Several authority paths also relied on upstream or operational bounds that were documented but not enforced at the nearest trust boundary. Exact Worker retries after a successful return could fail despite an authoritative receipt, encouraging unnecessary client ambiguity.
Impact
Players receive more reliable touch and embedded navigation, cleaner gathering controls, and fresher public identity presentation. Gateway, admission, and Worker paths fail closed under tighter bounded rules. This patch does not change admission decisions, ownership, balances, gathering rates, terrain, or persistent world data.
Validation
--maxWorkers=2)Honest residual risk
The deployed access-request v1 table still lacks an indexed review order. Alpha 0.3.29 prevents unbounded growth and unbounded administrative materialization, but a later additive queue revision should provide indexed pagination before admission opens at materially larger scale. Existing production chunk-size warnings also remain unchanged.