Lovable burned credits, ignored valid JSON, and now locks live deployments behind a paywall

[mikeyapina]

📝 Description: We’ve uploaded verified, structured JSON for four live athlete records — each fully compliant, using MXN, no demo_tag, and containing months of stipend + merit data. This includes:

Michael Pina – not created despite valid file

Abraham Garcia – returned “success” but showed blank screen

Rafa Garcia – mislabeled, then confirmed

Victor Hugo – confirmed but timeline cut off mid-year

We followed every instruction. Your system ignored fields, ran unrelated “security scans,” and burned dozens of prompts without execution. Then it blocked us behind a $294/month paywall right as we tried to finalize onboarding.

📊 Historical Evidence: Files: *_live_mxn.json (uploaded repeatedly)

Emails: [email protected], [email protected], [email protected], [email protected]

Timestamps: Abraham stipend from 2022; Rafa loan since April 2025

Proof of prompt exhaustion from security scans + token logs

Screenshots: Admin panel failure, system auto-bypass, paywall trigger

🎯 Ask: Re-credit all wasted prompts

Unlock access to create [email protected]

Acknowledge this is live production QA, not user error

Fix the token consumption logic (you’re draining before delivering)