Repository navigation
chore(standards): adopt shared Sheets vocabulary from Base 0.40.3 - #109
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.
Drive can now use the shared
insertandformatvocabulary from published cli-base 0.40.3. Pin the dependency exactly, retain compatible Core 0.307.0, and remove the last two Sheets naming exceptions without changing the lint baseline. The range recipe now points to the friendly tab/formatting workflow.Validation: 290 tests, 90.38% lines; ten CLI/MCP contracts; five prior-store upgrade cases; typecheck, lint, generation freshness, Markdown and no-leak checks pass. Command lint reports 20 existing baseline entries, one existing fact-verb override and zero new violations. Public-client Sheets checks pass eight cases with 18 in-memory SDK requests. Node/Bun installed-tarball acceptance passes with one physical Base instance. Compiled executable acceptance passes ten checks in 27 guarded CLI processes.
Source evidence: shared release, Sheets acceptance. No live Google validation or Drive registry release is claimed.