Repository navigation
Establish the clean v1 licensing baseline - #63
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
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.
License, trial and usage-recovery grants now use only v1. The server and SDK share the current feature set, including additive purchases, separate trial/paid usage, signed offline limits and operator-approved recovery. Removed old protocol parsers, adoption paths, old database tables/migrations, hash-only key re-entry and obsolete public fixtures.
This deliberately requires a fresh development database and SDK installation state; old development grants and state are rejected. Ed25519 keys and signature encoding remain unchanged. SDK 0.2.0 marks the breaking baseline; compatible scaffolders are prepared as create-keyforge 1.0.3 and create-keyforge-client 0.2.0.
Validation: local check/build pass, current public vectors and negative old-version tests pass, and SQLite, PostgreSQL, browser and package suites are being verified alongside CI. Production deployment is explicitly excluded.