refactor(ci): compose shared Python package Legos - #47
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WhrjTokoEF6Zax8EASdGsv
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.
TL;DR: compose edgeproc-core CI/candidate verification with Foundation and the shared Python-package Lego at exact central SHA 95c72573, while preserving the existing source-free PyPA publisher bridge byte-for-byte.
Why: the repository duplicated source/history/scanner/build/archive validation locally. The adapter now binds the exact caller snapshot and green workflow identity, uses the shared locked candidate boundary, then projects the authenticated artifact subtree into the existing release/dist handoff.
No package version, tag, release trigger, publish workflow, registry, secret, environment, or product code changes. No release is performed.
Proof: module 10/10; repository 303/303 at 99.28%; workflow 8/8; Ruff, strict mypy, Xenon A, actionlint, locks, schema, real build/Twine proof, and independent review green. Exact current-main candidate correctly fails closed because v0.4.2 is tagged to an older commit.