# 2026-05-06 -- SDK Changes Release Train

## Why this note exists

This train coordinates the Google Calendar integration, list-builder OM Spine cleanup, and OM Spine documentation/skill surfaces into one package and external-sync release. It publishes updated `@elevasis/core`, `@elevasis/ui`, and `@elevasis/sdk` baselines, then syncs template Claude guidance and package versions to derived projects.

## Applies to

- Template-derived projects consuming `@elevasis/core`, `@elevasis/ui`, or `@elevasis/sdk`.
- Projects using the list-builder workflow factory or custom lead-gen build-state UI.
- Projects relying on tenant Claude guidance for `/knowledge`, `/project`, `/tutorial`, or ambient `vibe` behavior.

## 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`
   - `ui/package.json`: `@elevasis/ui`
   - `operations/package.json`: `@elevasis/core` and `@elevasis/sdk`
3. Review local list-builder customizations against the OM-owned stage vocabulary and SDK `listBuilderWorkflow(...)` factory.
4. Review any local tenant guidance overrides before accepting the synced `.claude/rules/vibe.md` and `.claude/skills/{knowledge,project,tutorial}/SKILL.md` changes.

## Verification

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

## Not handled by /git-sync

- Project-authored list-builder workflow registrations remain project-owned code.
- Google Calendar OAuth configuration remains an Elevasis platform/admin responsibility, not a tenant scaffold migration.
- Manual browser smoke for authenticated calendar views is not automated by template sync.
