fix: Add a release checklist for TeachLink Web

[Muyideen-js]

Summary

Implemented the governance gap from issue #1537 by adding a release checklist for TeachLink Web, scoped to exactly two files, both inside Governance/.

Files added

1. Governance/templates/RELEASE_CHECKLIST.md — a fillable release checklist template that documents:

   • Pre-release steps: scope freeze, release branch creation, version proposal, required checks (type-check, lint, build, test + UI/web3 validate jobs), security audit, deprecation announcements, documentation updates, release notes, issue references, and a known rollback path.
   • Sign-off gates: the three required sign-offs (Lead Maintainer with final authority, QA Lead, Product Manager) plus the code review, security scan, documentation, and freeze gates, matching Governance/processes/RELEASE_SIGNOFF.md.
   • Post-release steps: deployed-version and core-flow verification, error tracker and performance-budget checks, recording the verification result, closing the tracking issue, filing follow-ups, and unblocking the next train.
   • Plus Purpose, Scope, How-to-Use, Release Identification, Ownership, Success, and Revision history sections, following the house documentation style (max 82-column lines, cross-references to the cadence, sign-off, versioning, backport, deprecation, hotfix, and performance-budget documents).

2. Governance/templates/RELEASE_CHECKLIST.test.ts — regression tests (vitest) that pin the template's guarantees so they cannot silently regress: document structure/section order, the three required areas, absence of unresolved authoring markers, line-width, the specific pre-release/sign-off/post-release items, and consistency with the referenced governance documents (which are also asserted to exist).

Scope compliance: only two files changed, both under Governance/; no application code, workflows, or tests outside the Governance folder were touched. The change is documented within the template itself (Purpose/Scope/Revision history), and Governance/README.md does not enumerate individual template files, so no README edit was needed.

Changed files

• Governance/templates/RELEASE_CHECKLIST.md
• Governance/templates/RELEASE_CHECKLIST.test.ts

Test plan

CI will run the existing test suite (vitest), which discovers Governance/templates/RELEASE_CHECKLIST.test.ts alongside the existing Governance/policies/DEPRECATION.test.ts. Expected: all new tests pass — they read the checked-in RELEASE_CHECKLIST.md, assert its section structure and required pre-release/sign-off/post-release content, verify no unresolved TBD/TODO/FIXME/XXX markers, check the 82-column line width, and confirm the referenced governance documents (RELEASE_CADENCE.md, RELEASE_SIGNOFF.md, VERSIONING.md) exist. Lint/type-check/build should be unaffected since only Markdown and a test file were added.

This PR was created as a draft by the issue solver bot. It will remain a
draft until repository CI passes.

Closes #1537

[drips-wave]

@Muyideen-js 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

[RUKAYAT-CODER]

Thank you for contributing to the project.