t1k:marketing:store:manifest
| Field | Value |
|---|---|
| Module | store |
| Version | 0.14.9 |
| Effort | medium |
| Tools | — |
How to invoke
Section titled “How to invoke”/t1k:marketing:store:manifestStore Manifest (store-manifest/1)
Section titled “Store Manifest (store-manifest/1)”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.
Commands
Section titled “Commands”bun scripts/manifest.cjs <command> (from this skill directory; dependency-free Node).
| Command | Does | Exit |
|---|---|---|
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 artifact | 0 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 first | 0, 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.md | 0, 1 blocked |
hash <path> [--root dir] | sha256(canonical(MERGED manifest)), the manifestSha256 of the gate; validates first | 0, 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.
Shape and field kinds
Section titled “Shape and field kinds”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.
| Kind | Meaning |
|---|---|
| shared | listings.<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 |
| store | one store only (play.shortDescription 80, asc.subtitle 30, asc.keywords 100, …); shortDescription and subtitle are different fields and are never merged |
| manual | category.play, rating.play, privacy.asc: "manual": true plus the expected value; no API, so never a writable op, only a checklist |
| passthrough | play.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.
Guarantees (each has a test)
Section titled “Guarantees (each has a test)”deriveis 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.hashis 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-levelplanId/createdAtplan-envelope fields are ever excluded from a hash, a store attribute namedcreatedAtat 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 inpassword,secret,token,privateKey,apiKey,credential,auth); secrets are env var NAMES in*Envkeys. - A path may not be absolute, climb out of its declaring directory, or resolve through a symlink out.
Hard rules
Section titled “Hard rules”- Play category and content rating (IARC) are manual: never a writable op. ASC App Privacy is a checklist only (no API).
nullclears a value (C11) only on the fields listed inreferences/clearable-fields.md; it is a type error everywhere else (e.g.app.slug). The schema, not the spec prose, is the SSOT.deriveoutput paths are ABSOLUTE; compare golden files after relativising them against the output root.migrateneeds--slugand--display-name(no legacy file has them) and writes--outnext to the assets: legacy paths are relative to the legacy file, manifest paths to the manifest.{{YEAR}}does not exist in/1:migratefreezes it (--year, default the current year) and says so.- S13 (
contactneedsdefaultLanguage) is NOT implemented: it applies only if the Play engine keepsPUT details, which Phase 8 decides. - Offline
validatewarns 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.
Executed by
Section titled “Executed by”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”).
| Step | Agent |
|---|---|
Run manifest.cjs validate or hash on a named file and report the output | t1k-fact-fetcher |
Libraries other skills import
Section titled “Libraries other skills import”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
Section titled “References”references/manifest-spec.md: fields, omitted-key semantics, rules S1-S12,extends, paths, secretsreferences/clearable-fields.md: the fields wherenullclears a value (C11), and the op each becomesreferences/migration.md:migrateflags, mapping rules, report formatreferences/engine-contract.md: the engine-side API and thestore-diff/1contractreferences/manifest-api.md: the manifest library API