# Clients Domain Release Train

## Why this note exists

The clients domain release train adds client-management surfaces across the shared platform packages and updates template-facing project guidance. Template-derived projects need the new package baselines and guidance before they rely on the clients CLI, published clients UI feature exports, or project skill client-linkage instructions.

## Applies to

Template-derived projects that consume `@elevasis/core`, `@elevasis/ui`, or `@elevasis/sdk`, especially projects that expose client management in UI shells or use the SDK CLI for project/client linkage.

## Required actions

- Pull the updated template dependency baselines for `core/package.json`, `ui/package.json`, and `operations/package.json` after the release stages publish new package versions.
- Review project-local usage of project/client CLI flags and prefer `--client` / `--clear-client` for client linkage; keep `--client-company-id` only for the legacy company field.
- If the project maintains local Claude skill guidance, reconcile the project skill client-linkage wording with the updated template baseline.
- Smoke the clients UI route only after the project has the updated `@elevasis/ui` baseline.

## Verification

Run the package-specific checks after sync:

```bash
pnpm -C core check-types
pnpm -C operations check-types
pnpm -C ui check-types
```

For projects adopting the clients UI immediately, also open the clients list and detail routes and verify the route renders with the current organization selected.

## Not handled by /git-sync

`/git-sync` can propagate template baselines and guidance, but it does not publish packages, deploy the SDK resources bundle, decide project-specific client data migration policy, or validate tenant-specific WorkOS/Supabase data availability.
