chore: rename Tokens Studio test source to production-shaped layout (#5179)

Author: pomfrida

.github/workflows/tokens_studio_backup.yaml

@@ -88,9 +88,11 @@ jobs:
         working-directory: packages/eds-tokens
         run: ~/studio-cli/node_modules/.bin/studio tokens pull --ci --verbose
       # Aliases and output dirs are read from .studio.json so a config
-      # rename (e.g. the planned eds-test-3 → eds) never requires a
-      # workflow change. Each source lands at backup/<alias>/;
-      # --delete keeps removals visible in the diff
+      # rename (e.g. eds-test-3 → eds) never requires a workflow
+      # change — but removed aliases are never cleaned up; delete
+      # backup/<old-alias>/ on the backup branch manually. Each source
+      # lands at backup/<alias>/; --delete keeps removals visible in
+      # the diff
       - name: Sync pulled sources into the backup branch
         run: |
           jq -r '.configurations | to_entries[] | "\(.key)\t\(.value.output)"' packages/eds-tokens/.studio.json |

documentation/agent-instructions/TOKENS_STUDIO.md

@@ -134,4 +134,4 @@ studio
 └── flags       --host --json --no-color --verbose
 ```
 
-Known state in this repo at snapshot time: CLI installed as a devDependency of `packages/eds-tokens` and approved in `onlyBuiltDependencies`. `.studio.json` lives in `packages/eds-tokens` (single source alias `eds-test-3`, project `4952a007-699a-4124-a043-124e80cc28d6`, branch `main`, format raw — the test-phase alias/output is due a production-shaped rename). Two saved export configurations on the project: `EDS-CSS` (css, id `39d37416-632b-4f04-b49b-cfaec63e3baa`, prefix `eds`, split layout, density base comfortable) and `EDS-DTCG` (dtcg, id `019463d4-9bef-4e37-9425-6de80eec87c8`). CI auth is OIDC (`id-token: write` + `--ci`) — no service token stored. Two workflows use it: `tokens_studio_release.yaml` (release-triggered, § The release pipeline) and `tokens_studio_backup.yaml` (hourly cron, § Backup & recovery).
+Known state in this repo at snapshot time: CLI installed as a devDependency of `packages/eds-tokens` and approved in `onlyBuiltDependencies`. `.studio.json` lives in `packages/eds-tokens` (single source alias `eds`, project `4952a007-699a-4124-a043-124e80cc28d6`, branch `main`, format raw, output `src/tokens/raw`). Two saved export configurations on the project: `EDS-CSS` (css, id `39d37416-632b-4f04-b49b-cfaec63e3baa`, prefix `eds`, split layout, density base comfortable) and `EDS-DTCG` (dtcg, id `019463d4-9bef-4e37-9425-6de80eec87c8`). CI auth is OIDC (`id-token: write` + `--ci`) — no service token stored. Two workflows use it: `tokens_studio_release.yaml` (release-triggered, § The release pipeline) and `tokens_studio_backup.yaml` (hourly cron, § Backup & recovery).

packages/eds-tokens/.studio.json

@@ -1,13 +1,13 @@
 {
   "$schema": "https://tokens.studio/schema/cli",
   "configurations": {
-    "eds-test-3": {
+    "eds": {
       "project": "4952a007-699a-4124-a043-124e80cc28d6",
       "ref": {
         "type": "branch",
         "name": "main"
       },
-      "output": "src/tokens/eds-test-3",
+      "output": "src/tokens/raw",
       "format": "raw"
     }
   }

packages/eds-tokens/CLAUDE.md

@@ -4,7 +4,7 @@ Design tokens package — CSS variables, JSON, and JS/TS outputs consumed by EDS
 
 ## Two pipelines coexist
 
-The **legacy pipeline** below (Figma REST sync + Style Dictionary) still owns everything the package *publishes* (`build/`, the `exports` map). The **new Tokens Studio pipeline** writes generated output to `src/tokens/{<alias>,css,dtcg,ts}` via `.github/workflows/tokens_studio_release.yaml` — those directories are **generated, never edit them by hand**, and are not yet wired into the `exports` map. The TS modules are produced by `pnpm run generate:ts-tokens` (`scripts/generate-ts-tokens.mjs` — DTCG export for structure + CSS export for evaluated values; the script header documents the mechanics). Canonical pipeline doc: [`documentation/agent-instructions/TOKENS_STUDIO.md`](../../documentation/agent-instructions/TOKENS_STUDIO.md).
+The **legacy pipeline** below (Figma REST sync + Style Dictionary) still owns everything the package *publishes* (`build/`, the `exports` map). The **new Tokens Studio pipeline** writes generated output to `src/tokens/{raw,css,dtcg,ts}` via `.github/workflows/tokens_studio_release.yaml` — those directories are **generated, never edit them by hand**, and are not yet wired into the `exports` map. The TS modules are produced by `pnpm run generate:ts-tokens` (`scripts/generate-ts-tokens.mjs` — DTCG export for structure + CSS export for evaluated values; the script header documents the mechanics). Canonical pipeline doc: [`documentation/agent-instructions/TOKENS_STUDIO.md`](../../documentation/agent-instructions/TOKENS_STUDIO.md).
 
 ## Build Pipeline (3 steps)
 

packages/eds-tokens/src/tokens/README.md

@@ -8,7 +8,7 @@ changes. Fix token values in Tokens Studio instead.
 
 | Directory  | Content                                | Produced by                                     |
 | ---------- | -------------------------------------- | ----------------------------------------------- |
-| `<alias>/` | Raw token sets (JSON, with `{alias}`s) | `studio tokens pull` (sources in `.studio.json`) |
+| `raw/`     | Raw token sets (JSON, with `{alias}`s) | `studio tokens pull` (sources in `.studio.json`) |
 | `css/`     | CSS custom properties                  | `studio exports run` (EDS-CSS configuration)    |
 | `dtcg/`    | DTCG interchange JSON                  | `studio exports run` (EDS-DTCG configuration)   |
 | `ts/`      | TypeScript modules                     | `pnpm run generate:ts-tokens` (combines `dtcg/` + `css/`) |