Enhance release process with Vercel redirects and semantic versioning

[logusivam]

Summary

Enhance release process with Vercel redirects and semantic versioning.

Type of Change

• Bug fix (non-breaking)
• New feature (non-breaking)
• Breaking change (requires version bump + CHANGELOG entry)
• Refactor (no behaviour change)
• Documentation update
• CI / tooling change

Security Checklist

• No secrets, API keys, or credentials added to source
• Input validation added/updated for new endpoints
• RBAC permissions verified for new/changed routes
• Rate limiting considered for new public endpoints
• Audit log event added for new auth actions
• Cookie options unchanged (httpOnly, Secure, SameSite)
• No token data exposed in URLs, logs, or response bodies

Testing

• Unit tests added / updated
• Integration tests added / updated
• All existing tests pass (npm test)
• Coverage threshold maintained (≥80%)

Documentation

• JSDoc added for public functions / classes
• docs/api-reference.md updated if endpoints changed
• docs/rbac-model.md updated if permissions changed
• CHANGELOG.md entry added (or handled by semantic-release)
• .env.example updated if new env vars added

Linked Issues

Closes #16

Screenshots / Logs (if UI or behaviour change)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
tokenforge-dev	Ignored		Aug 1, 2026 1:13pm

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!