Repository navigation
Conversation
…n types and canonical schema fields
…hema fields, and templates
…trict risk coverage
fraware
marked this pull request as draft
October 12, 2026 02:24
fraware
force-pushed
the
fix/cli-optional-pcs-lazy-imports-20261011
branch
from
October 12, 2026 14:11
e1c332e to
909eaa4
Compare
This branch has not been deployed
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.
Draft — engineering repairs validated; PCS evidence gate still red
This branch fixes optional PCS imports at CLI startup, an obsolete PCS benchmark checkout, the wheel's pytest-timeout environment, a stale security-suite fingerprint, the coordination-risk evidence schema, and the audit scanner. At head
e1c332e0697f, Audit self-check, Wheel smoke, Risk coverage (PR), and Release fixture verify all pass.The independent PCS QC-release workflow run 38183451993 still fails with committed runtime-receipt and certified-bundle digest inconsistencies, handoff input hash mismatches, and the release fixture contract. These are substantive evidence-integrity obligations and must not be resolved by skipping tests or relabeling claims. The earlier checkout/packaging/paths failures have been repaired. This PR is draft until the PCS contracts and artifacts are reconciled with an authoritative reproduction.
For review: the branch also contains the temporary pinned PCS metadata workaround. Replace with an upstream distributable package when available. Do not merge by bypassing the PCS check.