[Bug] Claude 4.7 refuses authorized security tooling work that 4.6 handles

Bug Description
Since the release of 4.7, ive had issues where the guardrails appear to be raised for code I have been working on with 4.6. Some of this involves EDR bypasses, shellcode, c2 implants etc. As part of the Cyber Verification Program with my team account, this shouldnt be a problem. You can see within this session that 4.7 assumes my codebase breaks its usage policy, where 4.6 is willing to continue its development with me. Would it be possible to look in to this for me and let me know if this is a bug or simply 4.7 not retaining memory from built up conversations

Environment Info

• Platform: darwin
• Terminal: WarpTerminal
• Version: 2.1.114
• Feedback ID: ba02ea9e-045f-4379-9528-bab5dc511f13

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/<user>/.local/share/claude/versions/2.1.114 (expected in multi-process scenarios)\n    at sd_ (/$bunfs/root/src/entrypoints/cli.js:2751:2177)\n    at WH8 (/$bunfs/root/src/entrypoints/cli.js:2751:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-19T17:27:39.317Z"}]