# SDK CLI `om:*` tenant Organization Model loader fix

## Why this note exists

The `@elevasis/sdk` CLI `om:*` read commands could return an empty model in standard
template-derived pnpm-workspace projects even when `core/config/organization-model.ts`
contained real systems and resources. The loader resolved `esbuild` and external
package imports from the project root, but template projects install SDK runtime
dependencies under `operations/`.

This train publishes an SDK loader fix. Tenant source does not need to change, but
`operations/package.json` must pick up the new `@elevasis/sdk` baseline.

## Applies to

- Template-derived projects that run `elevasis-sdk om:ls`, `om:search`, `om:describe`,
  `om:cat`, `om:graph`, or `om:skills` from `operations/`.
- Projects whose `om:*` output is unexpectedly empty despite a valid
  `core/config/organization-model.ts`.

## Required actions

1. Accept the `operations/package.json` `@elevasis/sdk` baseline bump delivered by
   `/external sync`.
2. Run the operations install after the sync so the published CLI binary is updated.

## Verification

Verify the tenant model loads from the published CLI:

```bash
pnpm -C operations exec elevasis-sdk om:ls /all-systems
```

The command should list the tenant's authored systems instead of returning an empty
result.

## Not handled by /git-sync

`/git-sync` pulls template guidance into a derived project. It does not publish the SDK,
install dependencies inside every standalone project, or redeploy any project. Run the
project-local install and deployment steps after accepting the sync.
