One focused Farcaster integration repair for one codebase. TLMNT reproduces the failure, confirms the boundary before access, and requests 79 USDC on Base only after you verify the fix.
The Doctor checks public Farcaster surfaces without a wallet or repository access. A scan is evidence for scoping; it is not a purchase, runtime guarantee, or release approval.
The repair is deliberately narrow. If reproduction shows that the problem belongs to a different layer, no payment is due and no repository access is requested.
Repair one reproducible manifest fetch, JSON, schema, hostname, or account-association failure. A decoded payload is not treated as cryptographic verification.
Verification: exact production bytes, final URL, schema result, and the repaired association check.Repair one broken fc:miniapp card, launch action, preview target, MIME mismatch, or role-specific icon, screenshot, hero, or OG image defect.
Verification: the affected metadata and asset roles pass their documented checks on the deployed URL.Repair one client launch blocker involving sdk.actions.ready(), splash dismissal, viewport, safe areas, scrolling, keyboard, or touch behavior.
Verification: the original client failure no longer reproduces in the agreed test flow.Repair one bounded saved-app, webhook configuration, event-handling, or notification delivery failure when the failing layer can be reproduced.
Verification: one agreed event or delivery path completes with sanitized before-and-after evidence.Included: one reproduced Farcaster Mini App integration blocker, one codebase, one bounded repair cycle, and verification evidence.
Excluded: new product features, smart contracts, wallet custody, full redesigns, growth work, fake engagement, unrelated hosting failures, and any request for seed phrases or private keys.
If the failure depends on private infrastructure or a platform decision TLMNT cannot verify, the result remains unverified and no repair payment is requested.
The request form creates a private status page. It does not connect a wallet, grant access, or authorize a payment.
Provide the public URL, the exact broken flow, and a public reply channel. The form authorizes neither access nor payment.
TLMNT reproduces the failure and states the one repair that fits before requesting any repository or deployment access.
Grant only the minimum access needed. The 24-hour repair window starts after reproduction and required access are ready.
Review the before-and-after evidence first. A private order page requests 79 USDC on Base only after you approve the fix.
Initial scope reply within two hours. The 24-hour repair window starts only after the failure and minimum access are ready. No verified fix means no payment.