Report blocks via existing connector /api/logs/log

[mariojgt]

Summary

• Persist the WP-format api_key from Pulse provision into .patchstackrc.json / PATCHSTACK_API_KEY.
• On enforced blocks, exchange client_credentials at /oauth/token and POST to existing /api/logs/log (same path as WordPress).
• Fail-open / fire-and-forget; dry-run detections are not reported; opt out with PATCHSTACK_TELEMETRY=off.

Depends on the SaaS PR that returns api_key + ensures a Pulse license.

Test plan

• npm test -- tests/protect/firewall-log.test.ts tests/config.test.ts
• Fresh scan saves apiKey into .patchstackrc.json
• With apiKey + enforcement block, a blocked exploit triggers /oauth/token then /api/logs/log from the server (not the browser)
• Without apiKey, blocking still works and no log API calls are made
• PATCHSTACK_TELEMETRY=off disables reporting

Made with Cursor

[coderbuds]

Cohesive firewall log reporting feature with thorough tests and documentation.

🎯 Quality: 95% Elite · 📦 Size: Large — consider splitting if possible

🛡️ Standards: no pre-flight fit check ran for this change — wire assess-change-fit into your coding agents to catch size before opening.

📈 This month: Your 82nd PR — above team average · Averaging Excellent

_{See how your team is trending →}

[mariojgt]

/review