Add a security.txt file per RFC 9116

[Akatenvictor]

Problem / Context

There is no machine-readable security contact file at the well-known location for security researchers.

Proposed approach

Add a security.txt (or .well-known/security.txt equivalent, adapted for an API-only service) pointing to docs/SECURITY_POLICY.md.

Acceptance criteria

• File follows RFC 9116 format
• Contact/policy link is current

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[drips-wave]

@Akatenvictor This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets