# SDK Ready Release Train

## Why this note exists

This release train carries SDK CLI, Organization OS/Knowledge scaffold, shared UI, and external template guidance changes from the monorepo into template-derived projects. Downstream projects need an operative sync note because the train includes `external/_template/.claude/**`, package baseline cascades, and generated/reference surfaces that are not handled by ordinary git merge alone.

## Applies to

- Template-derived external projects, including `external/ZentaraHQ` when its local worktree is ready for reconciliation.
- Managed Claude skill/rule/registry surfaces under `.claude/**`.
- Package dependency baselines for `@elevasis/core`, `@elevasis/ui`, and `@elevasis/sdk` after the publish stages complete.

## Required actions

- Run the prepared `/external sync --all` scope from `_external-sync-prep.json` after `/sdk ship` completes publish and deploy stages.
- Preserve project-owned files such as tenant `CLAUDE.md`, operations runtime code, and knowledge nodes unless the sync manifest marks a path as managed.
- Reconcile dirty tenant worktrees before applying managed `.claude` skill/rule writes.

## Verification

- Run the external sync planner/verify flow for each target project before applying writes.
- Confirm queue, schedule, note, Knowledge, and Organization OS guidance renders in the downstream `.claude` command/skill surfaces.
- Regenerate downstream knowledge/scaffold artifacts where the sync report requires generated freshness.

## Not handled by /git-sync

- Publishing `@elevasis/core`, `@elevasis/ui`, or `@elevasis/sdk`.
- Deploying the SDK resources bundle.
- Tenant-specific conflict resolution in dirty external project repositories.
- Manual review of project-owned `CLAUDE.md`, operations source, and knowledge content.
