Fix fail-open config propagation for protected-content pins #47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/protected-content-config"
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?
Confirmed P1: defaultConfig omitted protectedContent, dropping manifests loaded from harness.yaml and silently disabling verification. Preserve the manifest in effective config. Regression covers defaults plus YAML load to integrity check, matching/mutated/missing files; failed before fix. 306 tests, typecheck and build passed. Fresh review 07071fcfec5d837aceed525258239ec610bc16c4324a27664e57416da3c6627a: no findings. Operator authorized push, PR and merge after local-only correction. No deployment claim.