# Knowledge nested-group routing fix

## Why this note exists

`@elevasis/ui` now exports `findOmTreeGroup` (and `OM_NESTED_TREE_GROUPS`) from `@elevasis/ui/knowledge`. The Knowledge Base `$nodeId` route must use `findOmTreeGroup` to resolve `group:` nodes instead of the direct `OM_TREE_GROUPS.find`. Without this, clicking the nested **Profile** and **Business Model** subgroups under Organization renders "Page Not Found", because those keys live in nested subgroups (not in the top-level `OM_TREE_GROUPS` list).

## Applies to

- Any project whose `ui/src/routes/knowledge/$nodeId.tsx` resolves `group:` route params against `OM_TREE_GROUPS`.
- Projects on `@elevasis/ui` < `2.44.0`.

## Required actions

1. Bump `@elevasis/ui` to `^2.44.0` and install.
2. In `ui/src/routes/knowledge/$nodeId.tsx`:
   - Replace the `OM_TREE_GROUPS` import from `@elevasis/ui/knowledge` with `findOmTreeGroup`.
   - Replace `OM_TREE_GROUPS.find((candidate) => candidate.key === groupKey)` with `findOmTreeGroup(groupKey)`.

## Verification

- `pnpm -C ui check-types` passes.
- `pnpm -C ui build` succeeds.
- In the running app, the Knowledge Base **Profile** and **Business Model** rows under Organization open a describe view instead of "Page Not Found".

## Not handled by /git-sync

`/git-sync` does not edit project route source. The `$nodeId.tsx` swap to `findOmTreeGroup` is a manual route edit (or applied via `/external sync` route-baseline merge); `/git-sync` only surfaces this note and installs the bumped dependency.
