Track canonical Core main for development and CI - #45
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.
Development and CI currently fix Core at a released version. Declare canonical Core
main, refresh that package during development/CI setup, and run tests without re-syncing the old lock. CI verifies the current Core API and records its resolved commit; README documents the same refresh flow.The lock retains the exact tested resolution as evidence. Every non-Amplifier package entry in the lock remains identical, and third-party requirement constraints are unchanged.
Validation on Python 3.13.11:
e2cf2a6f1ff1aa2082b3b849b10f7e99e700bdd2; provenance assertion and ContextLengthError import passed.git diff --checkpassed.