Stats
Actions
Tags
From omni-link-hustlexp
Use when preparing HustleXP for public beta launch, verifying launch readiness, or determining what blockers remain before going live
How this skill is triggered — by the user, by Claude, or both
Slash command
/omni-link-hustlexp:beta-launch-runbookThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The scorecard reads 100/100 — the journeys work. That is necessary but not sufficient. Five hard gates must clear before a single beta user touches real money. Work through them in order. Do not skip gates or reorder them.
The scorecard reads 100/100 — the journeys work. That is necessary but not sufficient. Five hard gates must clear before a single beta user touches real money. Work through them in order. Do not skip gates or reorder them.
When asked about beta launch readiness, beta blockers, or "what do we need to do to launch":
Nothing ships until every item below is complete. Legal documents are in HUSTLEXP-DOCS/. Six documents have unfilled placeholders.
[State] in ALL 6 documents — governing jurisdiction. California requires separate counsel review: triggers PAGA exposure and AB5/Dynamex independent contractor complications. Do not default to California without explicit legal sign-off.[Effective Date] in all 6 documents:
[Address] — HustleXP legal department mailing address in Arbitration Agreement Sections 3.2 and 5.1https://hustlexp.com/legal/cancellation-fees — Poster Agreement Exhibit A references this URL live; the page must exist before any Poster Agreement is executeddashboard.checkr.com (account: "hustlr", email: [email protected])Real money transactions must not occur with these bugs. The platform earns $0 and/or charges users incorrectly until both are fixed.
File: hustlexp-ai-backend/src/services/StripeService.ts line 162
Problem: application_fee_amount is not set correctly — platform earns $0 on every transaction
Fix: Use the hustlexp-revenue-fixer skill — it contains the exact patch
Test: After fix, create a test charge and verify application_fee_amount appears non-zero in Stripe dashboard
File: hustlexp-ai-backend/src/services/EscrowService.ts line 337
Problem: grossPayoutCents = task.price — should be escrow.amount
Impact: Fee calculation is based on task listing price, not actual escrowed amount — these can diverge
Fix: Change task.price → escrow.amount on line 337
Test: Create escrow with a different amount than task.price, verify fee is calculated from escrow.amount
Users cannot file disputes without this. A fake success response means disputes are silently dropped.
File: hustlexp-ios/HustleXP/Screens/Shared/DisputeScreen.swift lines 73–85
Problem: Dispute submission uses DispatchQueue.main.asyncAfter(deadline: .now() + 2) — simulates a 2-second delay then shows fake success. No dispute is stored in the database.
Fix: Replace the fake async block with a real tRPC call via TRPCClient.shared. Use the ios-tRPC-wirer skill for the wiring pattern.
Test: File a dispute in the app, verify a row appears in the disputes table in the database
These do not block financial transactions but will cause user-facing failures visible to beta testers.
SquadService.swift lines 151–171 — getSquadTasks(), acceptSquadTask(), and getLeaderboard() are all hardcoded mock returns, not real API callsProofSubmissionViewModel.swift lines 280–284 — returns a mock response, not the real API result; users see false success on biometric proof submissionHUSTLEXP-DOCS submodule pointer in HUSTLEXPFINAL1 — git status shows the HUSTLEXP-DOCS submodule has new commits not reflected in the parent repo. Fix: cd /Users/sebastiandysart/HustleXP/HUSTLEXPFINAL1 && git add HUSTLEXP-DOCS && git commit -m 'chore: update docs submodule to HEAD'zod-audit skill to identify unvalidated mutations and add .input(z.object(...)) schemas.security.ts middleware covers all 139+ mutation routes. Run a route count to confirm no mutations bypass the rate limiter.Run all 6 journeys manually before launch day. Do not skip any. Record pass/fail for each step.
J1 — Hustler Earn
application_fee_amount non-zero in Stripe dashboardJ2 — Poster Help
J3 — Messaging
J4 — Trust
J5 — Disputes
LOCKED_DISPUTE → correct terminal stateJ6 — Admin
Run these in order on launch day. All three must pass before opening beta invites.
# 1. Backend test suite — must show 0 failures and ≥ 88.88% coverage
cd /Users/sebastiandysart/Desktop/hustlexp-ai-backend
npx vitest run --coverage 2>&1 | tail -5
# 2. Ecosystem health — must show 100/100 overall
node /Users/sebastiandysart/omni-link-hustlexp/dist/cli.js health
# 3. Payload drift — must be ≤ 11 (the irreducible floor; anything above 11 is a regression)
node /Users/sebastiandysart/omni-link-hustlexp/dist/cli.js authority-status
Interpreting payloadDrift: The floor is exactly 11. These are irreducible Swift↔TypeScript type-representation differences (named enums vs string literals, [String:Bool] vs Record<string,boolean>, named structs vs inline objects). They are not real field mismatches. Do not attempt to fix them. If drift reads >11, a real regression has been introduced — stop and investigate before proceeding.
Check each of these within the first 24 hours of accepting beta users:
| Check | What to Look For | Tool |
|---|---|---|
| Stripe platform fee | application_fee_amount > 0 on all charges | Stripe dashboard → Payments |
| Dispute storage | Disputes filed by users appear in disputes table | Supabase / DB query |
| Server errors | Monitor for 500s in Hono server logs | Backend logs |
| Escrow fee accuracy | Spot-check 3 completed tasks: escrow.amount used for fee (not task.price) | DB query |
These items are B3 (post-beta). Do not let anyone pull you onto these during the beta sprint.
| Gate | Type | Status |
|---|---|---|
| Gate 1: Legal documents | HARD BLOCK | Open — placeholders unfilled |
| Gate 2: Revenue bugs (StripeService + EscrowService) | HARD BLOCK | Open — 2 bugs confirmed |
| Gate 3: DisputeScreen fake success | HARD BLOCK | Open — bug confirmed |
| Gate 4: iOS feature parity | Required | Partial — 3 items |
| Gate 5: Backend security | P1 | Partial — Zod at 79% |
| 6-Journey smoke test | Pre-launch | Not yet run |
Do not launch until Gates 1, 2, and 3 are all closed.
npx claudepluginhub sebdysart/omni-link-hustlexp --plugin omni-link-hustlexpProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.