CRT
710c3a53d0
README is a short front page (about 120 lines) with one real visual per section; every former section moved unchanged into docs/*.md with a docs/README.md index (journey, rejections, getting-started, commands, growth, studios, store-art, listing-languages, api, skills, mcp, safety, faq, project). The site tells the same story on one page: the teaser in the hero, real CLI output as text, the desktop app as a section with light/dark captures of eight screens and the per-system downloads (desktop/latest.json); /desktop/ redirects to /#download. New capture tools: tools/site-desktop-shots.ts (fixture-mode desktop frames) and tools/site-term-shots.ts (real CLI output as text and WebP). tests/docs-links.test.ts checks README, docs and site links resolve.
15 lines
1.1 KiB
Text
15 lines
1.1 KiB
Text
$ storebound check
|
|
[check] config ok: storebound.config.ts
|
|
[check] play listing: 2 languages
|
|
[check] hint: the App Store name is "Example App" in every locale: App Store names are unique, so if it is taken App Store Connect refuses the record ("already being used"). Then set apple.name with a short suffix, e.g. "Example App: <tagline>" (30 characters at most); app.name stays the Play and on-device name
|
|
[check] appstore listing: 2 locales
|
|
[check] data safety: 768 CSV rows
|
|
[check] shots copy: 2 languages x 4 scenes
|
|
[check] hint: Play App category "Productivity" (apple.info.categories (PRODUCTIVITY)) is a console step, not an API one: `storebound console plan play-store-settings`
|
|
[check] WARN 31 Play App content answer(s) are not in the config: ask the owner in one batch at the start (`storebound console plan play-app-content` lists them), then write them into the config
|
|
- App Review needs a demo account (sign-in required) · add reviewDemoAccount to .storebound/credentials.json · review-access skill
|
|
- missing file: store/icon/icon.png
|
|
- missing file: store/icon/foreground.png
|
|
- missing file: store/icon/background.png
|
|
|
|
error: 4 problems
|