feat(#245): add non-interactive CI smoke-test artifact validation for…

[Richardkingz2019]

… every release candidate

Create release-validation.yml CI workflow that validates release candidates by verifying: build success (native + WASM), all tests pass (unit + fuzz), lint/format compliance, WASM artifact hash determinism, and smoke-test expectations. Results are recorded in a reviewable artifact.\n\n- New workflow: .github/workflows/release-validation.yml with 7 validation steps\n- Updated SECURITY.md with comprehensive release validation checklist and promotion guide

Description

Brief description of the changes in this PR.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Related Issues

Fixes #(issue number) or relates to #(issue number)

Changes Made

Testing

Describe the testing performed to validate these changes:

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented complex logic
• I have updated relevant documentation
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• My changes do not introduce new warnings

Screenshots (if applicable)

Add screenshots or logs if applicable.

closes #245

[drips-wave]

@Richardkingz2019 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