Fix fail-open config propagation for protected-content pins #47

Merged
severus-snape merged 1 commit from fix/protected-content-config into main 2026-10-24 19:48:26 +00:00
Collaborator

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.

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.
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harness/core!47
No description provided.