fix: restore beta package Telegram validation#108566
Merged
Merged
Conversation
* fix(qa): keep packaged entry off private transport * fix(qa): lazy-load private transport runtime * fix(qa): pass relative package artifact path * fix(qa): isolate packaged bus protocol * fix(qa): mount package scenario catalog
openclaw-barnacle
Bot
added
scripts
Contributor
Author
|
Land-ready proof for exact head
Known gap: none for landing this internal QA/package-harness backport. Full release validation will run against the landed beta SHA. |
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.
Related: #108499
What Problem This Solves
Fixes an issue where the 2026.7.2 beta release validation could not complete package acceptance because the packaged Telegram QA harness crossed four invalid package and container boundaries.
Why This Change Was Made
Backports the exact repair already landed and proven on main in #108499. The QA harness now defers private runtime loading, writes artifacts through container-valid absolute paths, implements the small protocol surface locally with parity tests, and mounts the required scenarios into the package-test container.
No version, tag, publication, registry, deployment, or release mutation is included.
User Impact
Maintainers can run the beta package acceptance and Telegram scenario lanes against the actual packaged artifact. Runtime product behavior is unchanged.
Evidence