release: create and maintain v1 major version tag

[wishket-pjw]

Summary

GitHub Actions convention is to maintain a major version tag (e.g., v1) that always points to the latest v1.x.x release. This allows consumers to reference JeremyDev87/leonidas@v1 and automatically receive patch/minor updates.

The README already documents @v1 usage but the tag does not exist yet.

Scope (SRP)

This issue covers only the v1 major version tag creation and documentation of the update process for future releases.

Acceptance Criteria

• v1 tag created pointing to the same commit as v1.0.0
• Tag pushed to remote
• Verify JeremyDev87/leonidas@v1 resolves correctly
• Document the tag update process for future releases (e.g., git tag -fa v1 v1.0.1)

Blocked By

• release: create v1.0.0 git tag and GitHub Release #204 (v1.0.0 tag and GitHub Release — must exist first)

Blocks

• release: prepare and publish v1.0.0 #172 (v1.0.0 release — final verification)

Priority

HIGH — README references @v1 which currently doesn't exist.

Notes

• The v1 tag should be a lightweight tag, not annotated
• On future v1.x.x releases, this tag must be force-updated: git tag -f v1 v1.x.x && git push -f origin v1

[JeremyDev87]

v1 lightweight tag created pointing to v1.0.0 (SHA: 4e16671). JeremyDev87/leonidas@v1 resolves correctly.