Without --config=production the CLI fell back to shopify.app.toml, whose
client_id points at the Solora dev app in another org — every Space build
died on a 403 "not a member of the requested organization".
fix: shorten short_description to meet HF 60-char limit
The Space was created and named jay-hank/mixly, on a different HF
account than Tierly's (solora-hq). Update all URLs, the S3 endpoint
namespace, the first-time-setup steps (Space already exists), and the
HF_SPACE_ID / sync-env.mjs default-value mismatches vs the in-code
defaults. Add a risk note about HF Storage Bucket availability on a
free, non-Pro account and the ephemeral-filesystem data-loss exposure
that follows if it is unavailable.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Modelled on Host-Tierly. Adapted after verifying against Mixly's
actual source (scripts/restore-db.mjs, src/lib/backup.ts, src/lib/s3.ts,
src/instrumentation.ts, src/lib/env.ts, shopify.app.toml):
- DB path /data/mixly.db, bucket Mixly-storage, snapshot prefix mixly-
- Space solora-hq/Mixly, GitHub source phamdung2209/Mixly
- Kept Prisma Studio proxy (Mixly has src/lib/ops/studio-proxy.ts)
- Dropped Crisp build secret (no Crisp integration in Mixly)
- Dropped --config=production (only a default shopify.app.toml exists)
- Scopes/API version taken from Mixly's own shopify.app.toml
