SuperSeller fal Discipline

The fal SDK and direct REST calls are tenant-blind. They read process.env.FAL_KEY, which is the SuperSeller-paid account key. Yoram has his own fal BYOK key stored in ig_bot_config that the worker code is currently ignoring — every fal call for Yoram is silently billed to SuperSeller. This skill fixes that.

Sibling discipline skills — different provider, same gate philosophy:

• superseller-kie-discipline — every paid Kie.ai call (Schwed BYOK, Tax4US BYOK)
• superseller-higgsfield-discipline — every Higgsfield gen (Elite Pro, internal)

When to invoke

Triggers (any of):

• About to call fal.run(...), fal.subscribe(...), @fal-ai/client, or fetch https://fal.run/...
• User asks: "lipsync via fal", "sync.so v3", "fal seedance", "fal kling", "fal wan", "fal kontext", "fal flux"
• Bash session about to curl https://fal.run/...
• Worker code path includes process.env.FAL_KEY and a tenant is involved

If a sub-skill or worker job is about to fire fal for a tenant, the pre-flight checks below must run first.

Gate 1 — BYOK / tenant routing (HARD HALT if violated)