Repository navigation
docs: clarify Recycler recovery phases and Cooking provider requirement - #239
Merged
Merged
Conversation
ryanbarlow97
changed the title
ryanbarlow97
marked this pull request as ready for review
October 14, 2026 06:40
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.
When an older JAR has delivered a retained legacy file, recovery now checks the migration journal's phase before restoring it. The cancellation-and-restore procedure applies only to
moved;plannedandpublishedkeep the legacy file absent and preserve journals, copies and receipts for manual reconciliation with Paper stopped. The guide explains the duplicate-return and recurring-hold risks and prohibits resetting the phase or deleting history to force recovery.Cooking's migration and estate paragraphs now identify TLibs 2.6.0 and earlier as the JVM-error partial-commit boundary and document the published 2.6.1 rollback behavior. Operators must verify loaded 2.6.1 before ownership migration, while the compilation pin remains 2.6.0. Existing partial rows still need staff repair using preserved evidence; the guide retains the uncertain-rollback restart and separate inventory/world-effect limits.
These follow the resumed Opus Recycler round 2 D1 phase counterprobes and TLibs round 2/Cooking round 2 D1 provider guidance. Related merged changes: Recycler #36, Docs #233, TLibs #47, Cooking #78 and Docs #227. A fresh review will assess both complete current project guides at this head.
Validation after both corrections: 5 documentation tests; 933 local links and anchors in 230 pages plus project navigation; strict CoreProtect MkDocs;
git diff --check. Recycler, Cooking and TLibs source/build files remain byte-identical. Read-only artifact checks bind the published 2.6.1 SQLite class and all 345 Cooking 0.5.0 production classes to the frozen approved builds.