Repository navigation
fix: verify configs and preserve metadata - #5
Open
waynesutton wants to merge 1 commit into
Open
waynesutton wants to merge 1 commit into
waynesutton wants to merge 1 commit into
Conversation
This was referenced Oct 4, 2026
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.
Verification now recognizes versioned plugin entries in valid JSONC, including comments and trailing commas. Live sync and CLI backfill read nested model/provider metadata with legacy flat-field fallbacks; idle sync also preserves the local session directory.
Five tests pass, including the built plugin with synthetic local files and mocked fetch. Build, TypeScript and targeted lint pass.
Refs #1 and #3. Keep both open until a package is published. Source main reports 0.3.6 while npm has 0.3.7, so reconcile versions before publishing. This excludes the separate unpublished SQLite/SDK work and does not change existing credentials or HTTP endpoints.