# Knowledge Browser item copy-references now resolve via `om:describe item:<domain>:<id>`

## Why this note exists

The Knowledge Browser used to copy an unresolvable `graph:<kind>:<uuid>` shorthand for
domain items (clients, roles, policies, customers, offerings, goals). Pasting that to an
agent led to dead ends — the OM resolver had no mount for it and `om:describe` rejected the
id. This train (published `@elevasis/core`, `@elevasis/sdk`, `@elevasis/ui` + the bundled
`om` skill) standardizes domain-item copy references on `item:<domain>:<id>`, which resolves
to the rich profile plus its location and governing knowledge. The `om` skill's read-folder
table and CLI invocation guidance changed, so derived projects must pick up the new skill
text and package baselines.

## Applies to

- All template-derived projects that ship the `om` skill (`.claude/skills/om/SKILL.md`).
- Any project whose Knowledge Browser surfaces domain items (clients, roles, policies,
  customers, offerings, goals).
- Agents that consume copied Knowledge Browser references.

## Required actions

1. Pull template changes and bump the published package baselines to the versions shipped by
   this train: `@elevasis/core`, `@elevasis/sdk`, `@elevasis/ui` (run `pnpm install` after the
   baseline bump so the new SDK CLI and UI copy behavior are present).
2. Adopt the refreshed `.claude/skills/om/SKILL.md` read-folder table. It now documents
   `item:<domain>:<id>` (resolves via `om:describe item:<domain>:<id>`), the `/by-domain/<domain>`
   and `/by-item/<domain>/<id>` `om:ls` mounts, `group:` / `domain:` / `folder:` as
   browser-overview references, and a legacy `graph:client:<uuid>` bridge note pointing to
   `om:describe item:clients:<uuid>`.
3. Use the corrected SDK CLI invocation at a project root: `pnpm elevasis-sdk om:describe …`
   (root script alias) or `pnpm -C operations exec elevasis-sdk om:describe …`. The old
   `pnpm exec elevasis-sdk …` at the project root fails in a multi-package tenant — replace it.

## Verification

- `pnpm elevasis-sdk om:describe item:clients:<id>` returns the client profile, its location
  (domain + graph id + `contains` parentage), and any governing knowledge — no dead ends.
- A bare/legacy `om:describe client:<uuid>` still resolves (back-compat for already-copied
  references).
- `pnpm sync:verify -- <project>` shows the `.claude/skills/om/SKILL.md` write applied and no
  remaining `om`-skill drift.

## Not handled by /git-sync

- The published-package baseline bumps (`@elevasis/core` / `@elevasis/sdk` / `@elevasis/ui`)
  and the subsequent `pnpm install` are manual — `/git-sync` does not bump dependencies.
- Any project-local documentation that hand-copied the old `pnpm exec elevasis-sdk` root
  invocation or the old `graph:<kind>:<uuid>` copy vocabulary must be corrected by the
  maintainer; `/git-sync` stops before touching project-owned surfaces.
