fix(staging): add _A2A_BOUNDARY_START/_END aliases + fix tier-check lint ref #934
No reviewers
Labels
No Label
merge-queue
merge-queue
merge-queue
merge-queue-hold
release-blocker
release-test
security
test-label-sre
tier:high
tier:low
tier:medium
triage-test
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: molecule-ai/molecule-core#934
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/staging-python-test-and-tier-check-lint"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
workspace/_sanitize_a2a.py: export_A2A_BOUNDARY_STARTand_A2A_BOUNDARY_ENDconvenience aliases.test_a2a_sanitization.pyimports them but the module only had the underlying_A2A_RESULT_FROM_PEERconstant — blockingCI / Python Lint & Test..gitea/workflows/sop-tier-check.yml: updatecontinue-on-errortracker reference frominternal#189(404, deleted) tointernal#343(open, same scope) — fixinglint-continue-on-error-tracking.Why
Both are pre-existing staging blockers preventing PR#927 from passing CI. These two checks (Python Lint and lint-continue-on-error-tracking) fail on every staging PR until this is fixed.
Test plan
CI / Python Lint & Testpasseslint-continue-on-error-trackingpasses/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack five-axis-review
/sop-ack memory-consulted
orchestrator LGTM — staging fix only, tier:low