[HedgeWonder]

Summary

This pull request closes four issues by adding CLI test execution to CI, a scenario testing the 28-byte UTF-8 memo boundary, a root check command for deterministic package checks, and a comprehensive release checklist.

Changes

Issue #167: Text memo at 28-byte UTF-8 boundary

• Add `esure-backend/scenarios/text-memo-28-byte-boundary.yaml` scenario
• Tests payment with a memo exactly at the 28-byte UTF-8 maximum boundary
• Verifies memo is correctly stored and retrieved from Testnet

Issue #168: Execute CLI test suite on pull requests

• Add `npm run test` step to CLI CI job in `.github/workflows/ci.yml`
• CLI tests now run for every pull request, preventing test regressions
• Tests already exist and pass in `esure-cli/test/`

Issue #169: Root command for deterministic package checks

• Create `package.json` at repository root with npm workspaces
• Define `npm run check` command that runs checks across all three packages
• Enables single command for developers: `npm run check` from root

Issue #170: Release checklist for three application packages

• Add `esure-docs/RELEASE_CHECKLIST.md` with detailed release procedures
• Covers backend (@esure/backend), frontend (@esure/frontend), and CLI (@esure/cli) packages
• Includes pre-release verification, release steps, rollback procedures, and post-release notes

Test plan

• Scenario file is valid YAML and conforms to schema v1
• Memo is exactly 28 bytes (verified programmatically)
• CI workflow syntax is valid
• Root package.json declares correct workspaces
• Check command can be verified locally
• Release checklist is complete and actionable

Notes

All four issues are now complete and ready for merge.

Closes #167 Closes #168 Closes #169 Closes #170

[vercel]

@Akanimoh12 is attempting to deploy a commit to the Favour Chigozirim's projects Team on Vercel.

A member of the Team first needs to authorize it.