# SDK Boundary Consolidation Release Train

## Why this note exists

This train publishes the SDK boundary consolidation work and updates the template to consume more of the published Elevasis SDK family instead of carrying local boilerplate. It also carries the Organization Model bridge retirement and typed-contract hardening that the ship train depends on.

## Applies to

- Template UI shells derived from `external/_template/ui`.
- Template operations packages that depend on `@elevasis/sdk`.
- Template core packages that depend on `@elevasis/core`.
- Projects that still carry copied `.claude/rules/*.md` files instead of SDK reference pointers.

## Required actions

- Refresh package baselines after publishing `@elevasis/core`, `@elevasis/ui`, and `@elevasis/sdk`.
- Adopt `ElevasisAuthenticatedShell` from `@elevasis/ui/app` in template-derived root routes.
- Replace local UI test/store/query-client helpers with `@elevasis/ui/test-utils`, `@elevasis/ui/test-utils/setup`, `createElevasisAppStore`, and `createElevasisQueryClient`.
- Keep project-specific Claude guidance as compatibility stubs that point at `@elevasis/sdk/reference/rules/`.
- Treat `System.ontology.catalogTypes` and `System.config` as canonical Organization Model authoring surfaces; do not reintroduce `System.content`.

## Verification

- `pnpm sdk:verify-release`
- `pnpm scaffold:verify`
- `pnpm verify:scaffold-reference`
- `pnpm sync:verify`
- `pnpm org-os:verify`
- Template UI typecheck and tests from the source workstream.

## Not handled by /git-sync

`/git-sync` does not publish npm packages, deploy the operations resource bundle, or decide whether project-owned files should adopt a template baseline. Those steps remain owned by `/sdk ship` and the prepared external-sync manifest.
