Repository navigation
docs: correct D1 baseline CLI coverage - #71
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
The D1 transport matrix now describes its actual historical
f58880dfCLI baseline: nine fixed commands and no genericcall. It distinguishes internal discovery from exposed commands and records broader CLI parity as proposed at that baseline. Later implemented CLI behavior and current product acceptance remain intact.The original correction is composed with product main
ab2ca5ba225ae6f8fa91ce7dd743ba1e48ea72a0at head87c4f61b23df1c1999e6eee25c46745c74e0dbd5. The ledger conflict preserves the complete dated October 15 correction followed by every later October 16 implementation and acceptance entry. Only the original two documentation files differ from main. The user's October 16 PR cleanup authorization supersedes the original no-auto-merge hold; the dated historical ledger remains unchanged.Validation:
No application, model, migration or runtime behavior changes.