Natalie 4f6b0daba8 test(api/vip): cover the unlock loop end-to-end ... Integration test against a real Postgres exercising the full M1 flow: - methods list returns only vip_unlock_enabled rows and a sanitized shape (no legal-name / visibility / provider fields ever surface to the fan) - a method not enabled for unlocks is rejected (CashApp gating) - token header auth and service-token admin auth are enforced - intent creation returns awaiting_payment + memo code + handle instructions - admin confirm records exactly one paid ledger entry and is idempotent under a duplicate confirm (no double-bill) 6 tests, green in ~2s. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-06-21 23:19:39 -05:00
..
@features	test(api/vip): cover the unlock loop end-to-end	2026-06-21 23:19:39 -05:00
@packages	fix(i18n): declare i18next dep and add 'escort' to UserType	2026-06-19 05:53:02 -05:00
config.yaml
package.json
tsconfig.base.json