Repository navigation
docs: clarify estate retry and recovery boundaries - #238
Merged
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
1 participant
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.
Document the bounded estate retry for a vehicle whose metadata and registry row disappear after an earlier handover or save failure: three spaced hourly attempts lead to BLOCKED, with staff retry rereading the vehicle without recreating it.
Clarify the existing API versus vehicle-registry failure boundary, the exits from a pending personal-vehicle pause, the 4.1.0 rollback fields and cleanup replay behavior, and the distinction between held warbands with and without successfully saved state.
Source: TF-Minecraft/SimpleFactions#165
Validation: five Docs tests pass; 933 local links and anchors in 230 pages plus project navigation pass; the strict CoreProtect MkDocs build and whitespace checks pass. Source validation passes 8,041 tests at the unchanged zero missed-line gate.