chore: drop chainwatch check; simplify pkg comments; doc polish - #2
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.
What
Housekeeping and doc polish:
chainwatchfrom the companion-tool checks; keepancc.pkg/package-level doc comments to describe the public API as being for "external consumers" generically. Comment text only — no API, types, or logic change.launchpipeline's per-operation.bakfiles are cleared whenclean,fix, andrewirerun in sequence, so the checkpoint is the restore point for a full run.Why
chainwatchis no longer a companion tool this project checks for. The doc changes keep the public API description neutral and make thelaunchbackup behavior explicit.