[Anekenonso]

Summary

Adds the project-wide security policy and vulnerability disclosure process for Shade Protocol, defining clear reporting channels, response SLAs, emergency response mechanisms, safe harbor commitments, and bug bounty guidelines.

Type of Change

• Documentation update

Linked Issue

Fixes #510

Changes Made

• SECURITY.md: Created the root security policy defining in-scope components across the workspace contracts, reporting procedures (GitHub Private Vulnerability Reporting and encrypted email), SLAs (24h ack, 72h triage, 3–14 days fix timeline), emergency response protocols (Pausable contract, role revocation, WASM upgrade runbooks), safe harbor terms, and bug bounty framework.
• docs/security/README.md: Updated index to reference the newly introduced security policy and disclosure process.

Test Evidence

Documentation-only changes; no contract code modified.

• No est_snapshots/ file is staged in this PR
• Verified markdown syntax and internal documentation links

Documentation Updates

• This PR does not change a public interface, or the change needs no doc update (explain why below if not obvious).
• This PR adds/changes a docs/ page and satisfies the Documentation Style Guide's review checklist.

Changelog

• This PR needs no changelog entry (internal-only change; documentation policy only).

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• My changes generate no new warnings

[drips-wave]

@Anekenonso Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[Anekenonso]

Hi @codebestia, I've rebased this cleanly onto the latest \main\ branch and updated the PR according to the repository's template to complete assigned issue #510. It is ready for your review and merge. Thank you!