t1k:unity:mobile:release-phase-config
| Field | Value |
|---|---|
| Module | mobile |
| Version | 3.65.6 |
| Effort | medium |
| Tools | — |
Keywords: firebase, phase-config, release-phase, release-phases, remote-config, rollout-phase
How to invoke
Section titled “How to invoke”/t1k:unity:mobile:release-phase-config[--dry-run] [--manifest <path>] [--checklist [--phase <id>]]T1K — Release-Phase Config (Firebase Remote Config)
Section titled “T1K — Release-Phase Config (Firebase Remote Config)”The user triggers this by hand. The skill asks which release phase to apply with AskUserQuestion, then writes that
phase’s values into the live remote-config template through the existing deploy pipeline. Nothing is published
without the deploy skill’s step-8 gate. The phase list lives in release-phases.json; this file names no phase.
Pipeline SSOT: t1k-unity-mobile-remote-config-deploy/SKILL.md, cited below by step number, never restated.
Manifest + CLI contract: references/manifest-contract.md. Exit-2 table, gotchas, rollback: references/runbook.md.
--checklist selects the read-only checklist mode (the Checklist mode section); without it the apply flow below runs unchanged.
- In scope: choosing a phase, writing its values onto keys already live, verify, gated publish.
- Out of scope: authoring Firebase conditions or A/B tests (A/B:
t1k-unity-mobile-ab-test), adding keys (run the deploy skill first), cohort targeting (an apply is global), editingPackages/com.gdk.3rdor the deploy skill’s scripts.
Constants
Section titled “Constants”<skill> = .claude/skills/t1k-unity-mobile-release-phase-config. CLI: bun <skill>/scripts/release-phase.cjs.
Stdout is JSON only. Exit 0 ok, 1 usage/invalid manifest, 2 a human decision is needed and nothing was written.
Work dir <w> = ${TMPDIR:-/tmp}/rc-<project>-phase/.
Workflow
Section titled “Workflow”Deploy step 2 (generator run, Editor) is skipped on purpose: a phase edits values already live, nothing is generated.
- Resolve — deploy steps 1, 3, 4. Step 3 is check-only here: a missing
firebase.jsonor.firebasercis reported and the run stops, nothing is recreated or committed. Thenbun <skill>/scripts/release-phase.cjs validate --manifest release-phases.json --json(exit 1 = fix the manifest). - Fetch + back up — deploy steps 5, 6 (live template to
${TMPDIR:-/tmp}/rc-<project>-live.json, backup before anything else). Record the liveversionNumber. - Detect —
bun <skill>/scripts/release-phase.cjs detect --manifest release-phases.json --live <live> --json. Tell the user which phase(s) are live now (matches), or theclosestphase and itsdifferingKeys. - Pick —
bun <skill>/scripts/release-phase.cjs list --manifest release-phases.json --json, thenAskUserQuestion. Options come ONLY from that output (label+description), never from a literal. A question holds at most 4 options: show 3 phases plusMorewhile more remain, and page until the user chooses. - Adapt —
bun <skill>/scripts/release-phase.cjs adapt --manifest release-phases.json --phase <chosen> --live <live> --out-dir <w> --json. Exit 2: renderrefused[]through the runbook table and STOP. - Merge — deploy step 7, written out in full:
bun .claude/skills/t1k-unity-mobile-remote-config-deploy/scripts/merge-remote-config.cjs --generated <w>/phase-generated.json --live <w>/phase-live.json --out <repo-root>/remoteconfig.template.json(--dry-run:--out ${TMPDIR:-/tmp}/rc-<project>-phase.json). Exit 2 = deploy collision procedure, STOP. - Verify —
bun <skill>/scripts/release-phase.cjs verify --manifest release-phases.json --phase <chosen> --live <live> --template <template> --json. Exit 2 = STOP: only the managed values may differ from live. - Gate — deploy step 8
AskUserQuestion, extended with: phase id, project id,adapted[](from -> to),shadowedByConditions[](a conditional value can still win for that cohort) and the rollback version number. - Dry-run — deploy step 9 (server
validateOnlywhen the MCP exposes it; else report “server validation not run (local verify only)”). - Re-fetch + verify again — fetch the live template FRESH into
<w>/live-fresh.jsonright before publishing, then runverifyof step 7 against it (--live <w>/live-fresh.json). A console edit between the two human gates would otherwise be erased by the FULL-REPLACE publish. Exit 2 = STOP and restart from step 2.force:trueis forbidden unless this second verify passed. - Publish + verify — deploy steps 10, 11. Step 11 also runs
detecton the re-fetched template and requiresmatchesto INCLUDE the chosen phase id (identical phases are all listed). Report the rollback version.
--dry-run
Section titled “--dry-run”Run steps 1-9, then stop after deploy step 9: the publish steps are never reached, and no re-fetch is needed. The
merged template goes to ${TMPDIR:-/tmp}/rc-<project>-phase.json, not the repo-root remoteconfig.template.json.
The dry run changes no tracked file; the untracked backup and ${TMPDIR} are its only writes. It proves the local
artifact, and the report says so.
Checklist mode
Section titled “Checklist mode”Triggered by --checklist. Read-only: no live template, no MCP, no Jenkins, nothing is written, nothing is evaluated.
- Locate the manifest
release-phases.json(or--manifest <path>). No fetch, no back-up, no apply steps. - Offer the phases with
AskUserQuestion(skip when--phase <id>was given), built ONLY from the output ofbun <skill>/scripts/release-phase.cjs list --manifest release-phases.json --json: 3 phases plusMore, paged as in the apply flow’s picker. - Fetch the cumulative list with
bun <skill>/scripts/release-phase.cjs checklist --manifest release-phases.json --phase <chosen> --json. Exit 2: renderrefused[]through the runbook table and STOP, showing the exactproject/publisherSymbolssnippet to add torelease-phases.json(the skill never writes the manifest). - Render the
items[]grouped by originphase, earliest first, one line each:[ ] check <text>or[ ] note <text>, with itshowunderneath, thenskipped[]with reasons and thecounts. Print this header first: “Checklist for
how paths are relative to the Unity project root (the directory holding ProjectSettings/), not necessarily the git
root. Define lists: the Jenkins job parameter PARAM_UNITY_SCRIPTING_DEFINE_SYMBOLS is the source of truth.
Executed by
Section titled “Executed by”The six release-phase.cjs subcommands are mechanical: t1k-fact-fetcher may run them and relay their JSON. The picker, the
step-8 gate and the publish stay in the main session, operator-confirmed.
Hard rules
Section titled “Hard rules”Detail and the exit-2 table are in references/runbook.md. The ones that bite:
- A later plain
remote-config-deploymerge resets managed keys to the asset defaults: rundetectfirst. - An apply is global to all clients; clients take the values on their next fetch (default minimum interval 12 h).
- A running A/B experiment can make a publish report success without advancing the version (deploy step 10 guard).
.claude/remote-config-backups/is NOT gitignored: nevergit addit blindly.
References
Section titled “References”references/manifest-contract.md— manifest schema, CLI and exit codes (SSOT, read-only).references/runbook.md— exit-2 table, gotchas, rollback.references/release-phases.example.json— copy to the repo root asrelease-phases.jsonand edit.