# 2026-05-09 -- Command System SDK Release Train

## Why this note exists

This train adds SDK CLI catalog, acquisition CLI read, API-key external route, and deterministic knowledge-routing changes to the existing SDK release queue. It publishes updated `@elevasis/core` and `@elevasis/sdk` baselines, then syncs the template dependency pins to derived projects.

## Applies to

- Template-derived projects consuming `@elevasis/core` or `@elevasis/sdk`.
- Operators using `elevasis-sdk cli`, `acquisition:list:*`, `acquisition:deal:*`, `client:*`, or generated `/knowledge` routing guidance.
- Projects that rely on API-key-gated SDK CLI access to platform external routes.

## Required actions

1. Pull the synced template changes through `/git-sync`.
2. Accept the package baseline bumps published by this train:
   - `core/package.json`: `@elevasis/core`
   - `operations/package.json`: `@elevasis/core` and `@elevasis/sdk`
3. Verify local `operations` commands still have the expected platform key environment variables before using SDK CLI API calls.
4. Review local operator guidance if the project documents SDK CLI command discovery or acquisition/client/deal command usage.

## Verification

- `pnpm -C operations check`
- `pnpm -C operations check-types`
- `pnpm -C operations test`
- `pnpm -C core test`

## Not handled by /git-sync

- Platform API route deployment remains an Elevasis monorepo/API deployment concern.
- Tenant-specific platform keys and API base URLs remain project-owned secrets and environment configuration.
- Project-authored knowledge nodes and routing guidance remain project-owned content.
