test(#69): build regression test suite

[Cbiux]

Summary

• Adds a dedicated *.regression.spec.ts suite covering webhook status sync, validation, status transitions, activity logging, and API edge cases — each test cites its originating issue/PR.
• Documents the policy that bug-fix PRs are not done without a regression test (CONTRIBUTING.md + docs/integration-tests.md index).
• Specs are independent (mocked Supabase/TW) and run via existing pnpm test / CI (testRegex: .*\.spec\.ts$).

Closes #69

Regression index (test → issue/PR)

Spec	Guards	Issue / PR
webhook-status-mapping.regression.spec.ts	escrow.released → completed	#52 / PR #54
dispute-percentages.regression.spec.ts	percentages must sum to 100	#12 / PR #49
stellar-address.regression.spec.ts	invalid Stellar address rejected	#27
status-transitions.regression.spec.ts	illegal transitions blocked	#59 / #67 · PR #110 / #76
agreement-activity.regression.spec.ts	dispute/status → agreement_activity + states	#58 / #61 · PR #100 / #104
api-edge-cases.regression.spec.ts	invalid JWT / 404 / unauthorized by-wallet	#15 / #51 · PR #57

Policy

• CONTRIBUTING.md — “bug fixes require a regression test”
• docs/integration-tests.md § Regression Test Suite

Test plan

• pnpm exec jest regression --runInBand — 6 suites / 12 tests green
• Specs pass in reverse file order (independence)
• pnpm exec jest --runInBand — full suite 26 / 596 green (local)
• Confirm CI Test job green on this PR

Local CI-equivalent output (excerpt)

Test Suites: 6 passed, 6 total
Tests:       12 passed, 12 total
Ran all test suites matching regression.

Test Suites: 26 passed, 26 total
Tests:       596 passed, 596 total
Ran all test suites.

[vercel]

@Cbiux is attempting to deploy a commit to the ManuelJG's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Kalchaqui]

Review — request changes (CI Format/Lint)

Thanks @Cbiux — solid work on #69. The regression convention, docs/policy, and issue/PR-traced specs look good. Scope is right.

Blocker before merge

CI is currently red:

• Format fails (prettier --check)
• Lint fails on the new *.regression.spec.ts files (and a few annotations in related specs)

Please run locally and push:

pnpm run format
pnpm run lint
pnpm exec jest regression --runInBand

Once Format + Lint + Test are green on this PR, happy to merge. (Vercel deploy authorization is unrelated and not a blocker.)

Non-blocking nits

• Fix the CONTRIBUTING path typo if still present (src/<feature>/*.regression.spec.ts).
• Optional later: shared buildDb helper across regression files.

Looking forward to the CI-green follow-up — nice foundation for the regression policy.

[Cbiux]

Pushed a CI follow-up: chore: fix regression suite format and lint for CI

Local verification (same commands as CI):

• pnpm run format:check — green
• pnpm run lint:check — 0 errors (warnings only, pre-existing / non-blocking)
• pnpm exec jest regression --runInBand — 6 suites / 12 tests green

Also updated CONTRIBUTING naming to src/<feature>/*.regression.spec.ts.

[Kalchaqui]

Re-review (c59d6ca) — LGTM

Thanks @Cbiux — the Format/Lint follow-up addresses the previous blocker.

Verified locally on this tip

• pnpm run format:check — green
• pnpm run lint:check — 0 errors (warnings only, pre-existing)
• pnpm exec jest regression --runInBand — 6 suites / 12 tests green
• CONTRIBUTING naming updated to src/<feature>/*.regression.spec.ts
• No merge conflicts with current main

Verdict

LGTM — mergeable. Nice foundation for the #69 regression policy.

Maintainer: fine to merge when ready.

[Kalchaqui]

Merging

Format/Lint blocker cleared — verified locally and merging now. Thanks @Cbiux for the #69 regression suite + policy.