Automated git backup of Tokens Studio tokens via studio CLI

[pomfrida]

Why

The Tokens Studio platform currently has no undo, rollback, or restore functionality — only a read-only version history of releases (version history docs). Designers have already made mistakes that were permanently applied, and since plugin changes push to Studio in real time, errors propagate immediately.

Until the platform ships undo, we need our own safety net outside the platform.

What

Set up a scheduled job that pulls all token sources from Tokens Studio into a git repository, so we get diffs, history, and recovery independent of the platform:

• studio tokens pull on a schedule (e.g. GitHub Actions cron), committing changes with a timestamped message
• Authentication via service account token or OIDC (--ci), see service account tokens — prefer OIDC, otherwise store the token in the CI provider's secret store
• Decide target: dedicated backup repo vs. a directory in this monorepo (note: .studio.json config model and safety rubric are documented in documentation/agent-instructions/TOKENS_STUDIO.md, added in chore: add tokens studio agent and cli setup #5151)
• Recovery path documented: how to restore token state in Studio from a given backup commit

Notes

• The CLI is installed as a devDependency of packages/eds-tokens (PR chore: add tokens studio agent and cli setup #5151)
• Related: token pipeline rebuild Establish a new Token build & publishing pipeline #5108
• Webhooks or studio tokens watch could make this event-driven later; a simple cron is enough as a first safety net

[claude]

These issues look related and may provide useful context for scoping this backup job:

• Establish a new Token build & publishing pipeline #5108 — Establish a new Token build & publishing pipeline (open): the rebuilt pipeline is explicitly "GitHub sync is pull-based (CI pulls via the Tokens Studio CLI)", so this scheduled backup is effectively a component of that effort (and is referenced by this issue).
• Pilot Tokens Studio migration for the EDS token system #5015 — Pilot Tokens Studio migration for the EDS token system (closed): established Tokens Studio as the source of truth this backup would protect; useful for understanding what token sources need pulling.
• Tokens Studio — exploration and evaluation #4822 — Tokens Studio — exploration and evaluation (closed): the umbrella exploration of how Tokens Studio fits the EDS workflow, including where it augments the existing pipeline.

This comment was generated by an LLM and may be inaccurate. Please verify that the linked issues are actually relevant.