docs(skill): a carry orphans its source, and splitting a rate needs a correction - #363
Merged
Merged
Conversation
… correction Four sections. A carry re-cut onto a fresh base has a new tree and a new patch-id, so no content route connects it back and the bee's original branch becomes permanent debt - read the commit message instead, which L1 makes load-bearing. The landing rule had a second copy in close-done that never learned any of it. A conflict says two sides touched the same lines and says nothing about which side is behind: rebasing browseros-ai#1302 would have deleted landed work and reintroduced an L3 violation, so measure how far the base has moved instead. And splitting a rate by category is several tests at once - four groups at 95% each carry a 19% chance of a false alarm, which is how a dashboard earns the right to be ignored. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
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.
Four sections from the round that unjammed the landing pipeline. See the commit message.