Repository navigation
Integration: reject protected-file-only change - #3
davidwilliam wants to merge 3 commits into
Conversation
|
ProofForge: payout-flagship REFUTED Reproduce: Proof check rejected:
|
|
ProofForge: payout-flagship REFUTED Reproduce: Proof check rejected:
|
|
ProofForge: payout-flagship REFUTED Reproduce: Proof check rejected:
|
|
Demonstration of the ProofForge pull request check, kept as evidence and closed without merging. The failing check is the intended outcome: the change edits only the protected specification, and the check rejects it. Recorded outcomes: reports/pr-integration/summary.json. |
|
ProofForge: payout-flagship REFUTED Counterexamples checked by the kernel: Reproduce: Proof check rejected:
|
Integration test: change only the protected specification, leaving candidate files untouched.
Expected result: the workflow runs and the tree check rejects the changed protected-file hash. The edit is a comment, deliberately demonstrating byte-level lock enforcement without introducing a new behavioral policy. This test PR is not intended to merge.