Skip to content

t1k:marketing:store:manifest

FieldValue
Modulestore
Version0.14.9
Effortmedium
Tools—
/t1k:marketing:store:manifest

One file per game, stores/<slug>/store-manifest.json, says what the Play and App Store Connect listings should say. The legacy *.play.json and *.game.json + studio-base.json become DERIVED output of this file; the engines keep reading them unchanged. This skill is the data layer: it never calls a store, needs no credentials and writes nothing but the files you name with --out. The store gate (plan, approval, apply) and the two engines import its libraries.

bun scripts/manifest.cjs <command> (from this skill directory; dependency-free Node).

CommandDoesExit
validate <path> [--root dir] [--check-files]schema + rules S1-S12; one line per error <JSON pointer>: <rule>, warnings <pointer>: W<n> <text>; --check-files also requires every referenced file, checks real paths, and checks the play.release artifacts the Play engine reads (regular file; aab/nativeSymbols are zips; mapping is text). migrate warns (W8, exit 0) on a missing or wrong-kind artifact0 ok (warnings allowed), 1 errors
derive <path> --store play|asc [--out f] [--root dir]the legacy config shape for one store, paths rewritten ABSOLUTE; validates first0, 1 invalid
migrate --play f --asc-game f [--base f] --slug s --display-name n --out p [--report f] [--allow-unmapped] [--year YYYY]legacy files to a manifest; see references/migration.md0, 1 blocked
hash <path> [--root dir]sha256(canonical(MERGED manifest)), the manifestSha256 of the gate; validates first0, 1 invalid

Usage errors exit 2. --root is the store root (default: the nearest ancestor directory named stores, else the manifest’s directory); extends may point anywhere inside it, nowhere outside.

schema/store-manifest.schema.json is the SSOT (never copy a value out of it: lib/limits.cjs reads limits from it, lib/schema.cjs interprets it). Top level: schema, extends?, app (slug, displayName), stores (play, asc), listings, graphics, category, rating, privacy, iap[], play, asc. Unknown keys are rejected at every level. Field table, omitted-key semantics and rules: references/manifest-spec.md. Template: templates/store-manifest.json.

KindMeaning
sharedlistings.<loc>.title (Play title, ASC name, 30) and fullDescription (4000) feed both stores; play.title, asc.name, play.fullDescription, asc.description override for ONE store
storeone store only (play.shortDescription 80, asc.subtitle 30, asc.keywords 100, …); shortDescription and subtitle are different fields and are never merged
manualcategory.play, rating.play, privacy.asc: "manual": true plus the expected value; no API, so never a writable op, only a checklist
passthroughplay.release, play.regionsVersion, asc.settings, asc.reviewDetails, iap[].play: values carried whole, KEYS allow-listed

A locale reaches a store only when that store is in listings.<loc>.stores (default both). Every write-shaping publish option is a play.release field (sendForReview, cancelInReview, track, aab, userFraction, releaseNotes, mapping, nativeSymbols), never a CLI flag.

  • derive is a pure function of the merged manifest: no network, no clock, no environment; an absent section gives an absent key, never an empty default; it never emits _ keys.
  • hash is stable across key order and whitespace, and is taken over the MERGED manifest, so a changed studio default moves it and a whitespace-only edit does not. Canonical form is RFC 8785 with keys sorted by UTF-16 code unit; ONLY the top-level planId / createdAt plan-envelope fields are ever excluded from a hash, a store attribute named createdAt at depth stays in.
  • Length limits count UTF-16 code units (String.length, what Play and ASC count): a 30-emoji title is 60 units and is rejected.
  • A literal secret is rejected (demoAccountPassword, any string under a key ending in password, secret, token, privateKey, apiKey, credential, auth); secrets are env var NAMES in *Env keys.
  • A path may not be absolute, climb out of its declaring directory, or resolve through a symlink out.
  • Play category and content rating (IARC) are manual: never a writable op. ASC App Privacy is a checklist only (no API).
  • null clears a value (C11) only on the fields listed in references/clearable-fields.md; it is a type error everywhere else (e.g. app.slug). The schema, not the spec prose, is the SSOT.
  • derive output paths are ABSOLUTE; compare golden files after relativising them against the output root.
  • migrate needs --slug and --display-name (no legacy file has them) and writes --out next to the assets: legacy paths are relative to the legacy file, manifest paths to the manifest.
  • {{YEAR}} does not exist in /1: migrate freezes it (--year, default the current year) and says so.
  • S13 (contact needs defaultLanguage) is NOT implemented: it applies only if the Play engine keeps PUT details, which Phase 8 decides.
  • Offline validate warns W7 (not an error) for a scoped locale with no title; the engine makes it an error at plan time when the locale does not exist live.

validate, hash, derive and migrate are deterministic scripts; only choosing per-game values (slug, display name, copy) is judgment (routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”).

StepAgent
Run manifest.cjs validate or hash on a named file and report the outputt1k-fact-fetcher

The engines and the gate import scripts/lib/* through a sibling-skill path (see references/engine-contract.md): engine-contract.cjs (typed exits, log routing, store-diff/1 check, op ids, hashes), canonical.cjs, and the manifest API of scripts/manifest.cjs (references/manifest-api.md).

  • references/manifest-spec.md: fields, omitted-key semantics, rules S1-S12, extends, paths, secrets
  • references/clearable-fields.md: the fields where null clears a value (C11), and the op each becomes
  • references/migration.md: migrate flags, mapping rules, report format
  • references/engine-contract.md: the engine-side API and the store-diff/1 contract
  • references/manifest-api.md: the manifest library API