Establish host-security boundaries for tests #15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "security/host-test-safeguards"
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?
Scope
Add an
AGENTS.mdpolicy requiring explicit approval for host-interacting Windows tests, prohibiting security-control workarounds and unsafe generated PowerShell, and stopping on unexpected failures or endpoint-security events.Verification
Static diff and independent read-only review only. No tests, PowerShell, Windows interop, or trust-store operations are authorized for this incident task.
The Bitdefender incident's cause remains unverified. This change does not modify PR #14, its worktree, or repository branch policy.
Base:
8d4179b3197d0a3026c68951671980b97a1c7eb0.Independent static-only agent review of head
4a008b1a2ad6c1c26037f38ef693a87004c765a7against base8d4179b3197d0a3026c68951671980b97a1c7eb0: no findings. An initial review identified ambiguous scope for the hold on generated PowerShell; the follow-up commit clarified it and the final head was re-reviewed. No tests, PowerShell, Windows interop, or trust-store operations were run for this PR. This comment records an agent review; it is not a separate Forgejo-account approval. Applicable owner/merge authority remains to be confirmed.