@elevasis/sdk 1.44.2 → 1.45.0

package/reference/claude-config/sync-notes/2026-06-06-om-build-systems-scaffold.md

@@ -1,47 +0,0 @@
-# /om build system scaffold added to tenant template
-
-## Why this note exists
-
-The monorepo added a guided `/om build` operation (Steps 2-3 of the Building-Systems Scaffold
-task) that sequences the full platform runbook for authoring an Organization Model System end
-to end. This train mirrors a thinner, Codify-ceremony-framed variant of that operation into the
-tenant template. Tenant projects author OM via the Codify ceremony (not the platform PR-review
-runbook), so the tenant variant is scoped accordingly.
-
-Changes in this train:
-
-- New operation file `.claude/skills/om/operations/build.md` (Codify-framed, 8 phases).
-- `metadata.promptSignals` in `.claude/skills/om/SKILL.md` extended with four build-intent
-  phrases: `build a system`, `design a system`, `create a system that`, `system architecture`.
-- `## Operations` table added to `.claude/skills/om/SKILL.md` with the `build` EXECUTE row.
-- Build-intent routing branch added to the Decision Tree section of `SKILL.md` so free-text
-  build intent routes to `/om build` before the 5-bucket read/write buckets.
-
-## Applies to
-
-- All template-derived projects that ship the `om` skill (`.claude/skills/om/SKILL.md`).
-- Any project where an agent might express intent to build or design a new System.
-
-## Required actions
-
-1. Pull template changes so the new `build.md` operation file and the updated `SKILL.md` are
-   present in `.claude/skills/om/`.
-2. No package baseline bumps required -- this is a pure agent-scaffold change (no published
-   package version involved).
-3. No `pnpm install` needed unless the `/git-sync` pull also brings unrelated baseline changes.
-
-## Verification
-
-- `.claude/skills/om/operations/build.md` is present.
-- `.claude/skills/om/SKILL.md` contains the `build` row in the `## Operations` table.
-- `.claude/skills/om/SKILL.md` `metadata.promptSignals.phrases` includes `build a system`,
-  `design a system`, `create a system that`, and `system architecture`.
-- Saying "build a system for lead gen" in chat triggers `/om` and routes to `/om build` without
-  requiring the explicit `/om build` subcommand.
-
-## Not handled by /git-sync
-
-- No dependency bumps or `pnpm install` required for this change alone.
-- Any project-local documentation that references how to add a new System should be updated by
-  the maintainer to point at `/om build` as the guided entry point rather than manual Codify
-  Level-A alone.

package/reference/claude-config/sync-notes/2026-06-06-om-item-copy-references.md

@@ -1,50 +0,0 @@
-# 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.

package/reference/claude-config/sync-notes/2026-06-08-knowledge-base-page-not-found-fix.md

@@ -1,76 +0,0 @@
-# Knowledge Base "Page Not Found" hardening (KB `$nodeId` route)
-
-## Why this note exists
-
-The Knowledge Base detail route (`ui/src/routes/knowledge/$nodeId.tsx`) could render a
-terminal full-pane **"Page Not Found"** screen for node ids it could not resolve. Two
-distinct gaps caused it:
-
-1. **No `folder:` branch.** Selecting a KB **folder** node (e.g. the `KNOWLEDGE > All`
-   folder) navigates to `/knowledge/folder:knowledge:all`. The route matched none of the
-   `domain:` / `group:` / `item:` prefixes, resolved to no graph node, and fell through to
-   a bare `<PageNotFound />`. The folder routing (`folder:` → `FolderDetailView`) was
-   missing from the template route entirely.
-2. **Two hard-404 landmines.** The `!group` and `!node` fall-through branches returned
-   `<PageNotFound />`, so any stale bookmark, renamed ontology id, or snapshot drift
-   dead-ended the whole content pane.
-
-This train delivers the hardened route that **always renders browsable content** for any
-node id. There is **no package bump** — the fix consumes only `@elevasis/ui` exports your
-project already has at `@2.49.0+` (`KnowledgeBrowser`, `buildKnowledgeOmTreeData`,
-`findKnowledgeTreeNodeByValue`, `KnowledgeTreeNodeData`).
-
-## Applies to
-
-- Every template-derived project whose `ui/src/routes/knowledge/$nodeId.tsx` is still the
-  pre-fix version (no `folder:` branch, bare `PageNotFound` returns). If your KB renders
-  "Page Not Found" when the `All` (or any) folder node is selected, you are affected.
-- No action is required for projects that have already customized this route to handle
-  folders and avoid hard 404s — the sync is a `merge-baseline` that **preserves your local
-  route edits** (`external-sync-feature-route-baseline`, `sync_lane_severity:
-optional-feature-selection`).
-
-## Required actions
-
-`/git-sync` / `/external sync` delivers the hardened route as a baseline merge and surfaces
-this note. The route is project-owned baseline content under the route-preservation lane,
-so it is **merged, not force-overwritten** — review the merge if you carry local
-customizations.
-
-1. **Pull and review.** Run `/git-sync` (or `/external sync`) and review the merge into
-   `ui/src/routes/knowledge/$nodeId.tsx`. Accept the two changes: the new `folder:` →
-   `FolderDetailView` branch, and the replacement of both `<PageNotFound />` returns with a
-   `KnowledgeNodeFallback` (a subtle "not available" `Alert` plus the full
-   `KnowledgeBrowser`).
-2. **No dependency change.** `@elevasis/ui` does **not** need bumping for this fix; the
-   required exports are already published. Do not add a package bump to this sync.
-3. **Type-check, then boot.** Run `pnpm -C ui lint` (`tsc --noEmit`), then start the UI.
-
-## Verification
-
-```bash
-# 1. The route must no longer return a bare PageNotFound
-grep -n "PageNotFound" ui/src/routes/knowledge/$nodeId.tsx
-#   Expect: no terminal `return <PageNotFound />` in the content branches
-#   (a folder: branch + KnowledgeNodeFallback should be present instead)
-
-# 2. Required @elevasis/ui exports are present at your installed version
-grep -n "KnowledgeBrowser\|buildKnowledgeOmTreeData\|findKnowledgeTreeNodeByValue" \
-  ui/src/routes/knowledge/$nodeId.tsx
-
-# 3. Template-family coherence
-pnpm -C ui lint
-```
-
-In the running app, select the `KNOWLEDGE > All` folder node (and any other folder/group
-node): the content pane must render browsable Knowledge content, never a full-pane
-"Page Not Found".
-
-## Not handled by /git-sync
-
-- `/git-sync` / `/external sync` deliver and merge the route baseline plus this note, but
-  they do **not** redeploy your UI. Reaching your live app requires your own UI **redeploy**
-  after the sync merge is accepted.
-- Local customizations to `ui/src/routes/knowledge/$nodeId.tsx` are preserved by the
-  `merge-baseline` lane — if you maintain a forked KB route, reconcile the `folder:` branch
-  and the `KnowledgeNodeFallback` into your version by hand rather than discarding your edits.

package/reference/claude-config/sync-notes/2026-06-09-agent-sessions-public-agent-chat-route.md

@@ -1,75 +0,0 @@
-# Agent Sessions and public agent chat route
-
-## Why this note exists
-
-This train makes `Agent Sessions` the canonical internal full-page chat surface and
-introduces the browser-safe public agent chat substrate. Public browser clients use
-platform-issued access grants and short-lived capability tokens; they must not call
-server-to-server session APIs with platform API keys.
-
-The shared public chat UI is published from `@elevasis/ui/features/public-agent-chat`.
-The tenant route is authored after the UI package publish, then propagated through the
-strict manifest sync.
-
-The template Organization Model now also declares the `operations-sessions` navigation
-surface (`/operations/sessions`). That lets template-derived tenants inherit the
-standard Agent Sessions page or opt into the same surface from their own OM navigation
-without hand-authoring a route.
-
-## Applies to
-
-- Template-derived projects that want public or code-gated agent chat links.
-- Projects syncing the template route baseline after the `@elevasis/ui` package baseline
-  is bumped.
-- Projects that want the internal Agent Sessions page exposed through OM-authored
-  navigation.
-
-## Required actions
-
-1. Accept the package baseline updates for `@elevasis/core` and `@elevasis/ui`.
-2. Accept the new public chat route baseline once it appears in
-   `ui/src/routes/chat.$slug.tsx` and any root-shell adjustment needed to keep that route
-   outside the authenticated app shell.
-3. If your project customizes `core/config/organization-model/navigation.ts`, merge the
-   `operations-sessions` surface into the Operations group:
-
-```ts
-'operations-sessions': {
-  type: 'surface',
-  label: 'Agent Sessions',
-  path: '/operations/sessions',
-  surfaceType: 'list',
-  order: 30
-}
-```
-
-4. Run the project UI install and typecheck/build after sync:
-
-```bash
-pnpm -C ui install
-pnpm -C ui check-types
-pnpm -C ui build
-```
-
-5. Configure platform-side public agent access grants before sharing a public chat URL.
-
-## Verification
-
-After sync, verify the OM exposes the Agent Sessions navigation surface:
-
-```bash
-grep -n "operations-sessions\\|Agent Sessions\\|/operations/sessions" core/config/organization-model/navigation.ts
-pnpm -C core test
-```
-
-## Security notes
-
-- Browser code must use the public grant/capability-token flow.
-- Do not expose `ELEVASIS_PLATFORM_KEY` or operations API keys in browser code.
-- Public turns use the public WebSocket route backed by a capability token.
-
-## Not handled by /git-sync
-
-`/git-sync` does not create production access grants, choose which agents are public,
-merge project-owned OM customizations automatically, or redeploy tenant UIs. Those are
-project/operator decisions after the code and package baselines are accepted.

package/reference/claude-config/sync-notes/2026-06-09-sdk-cli-load-org-model-resolution.md

@@ -1,42 +0,0 @@
-# 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.

package/reference/claude-config/sync-notes/2026-06-12-agent-grants-visualizer-operations.md

@@ -1,30 +0,0 @@
-# Agent grants, execution visualizer, and Operations sidebar release train
-
-This train publishes coordinated platform updates across `@elevasis/core`, `@elevasis/ui`,
-and `@elevasis/sdk`, then syncs the external template baseline.
-
-## What changes for tenant projects
-
-1. `@elevasis/sdk` adds `grant:list`, `grant:create`, and `grant:disable` for
-   managing public/code-gated agent access grants through the platform API.
-2. `@elevasis/ui` adds shared agent public/private controls and improves the
-   agent execution visualizer with per-iteration tool activity.
-3. `@elevasis/core` adds the grant audit activity contract used by platform
-   activity feeds.
-4. The template `.claude/registries/skill-coverage.json` now explicitly waives
-   the `grant` CLI domain as operator-facing access-management tooling.
-
-## Operator action
-
-- Run the prepared external sync manifest from the SDK ship artifact.
-- Verify each derived project updates `.claude/registries/skill-coverage.json`.
-- After package baselines are bumped, verify derived package manifests point at
-  the newly published `@elevasis/core`, `@elevasis/ui`, and `@elevasis/sdk`
-  versions selected by the release steps.
-
-## Manual-review exclusions
-
-Operations sidebar root-route parity for `external/nirvana-marketing` and
-`external/ZentaraHQ` is intentionally excluded from this ship train. Their
-root routes are project-specific merge-managed surfaces and should be reviewed
-manually before adopting the template Operations manifest mount.

package/reference/claude-config/sync-notes/2026-06-14-session-ux-and-project-cli-json.md

@@ -1,33 +0,0 @@
-# Session UX fixes + project CLI `--json`
-
-## Why this note exists
-
-This train bumps both `@elevasis/ui` and `@elevasis/sdk` with several tenant-facing changes beyond the shared `SessionConversationView` adoption (see the companion `2026-06-14-shared-session-conversation-view.md` note):
-
-- **Lazy agent-session creation** (`@elevasis/ui`) — the Agent Sessions surface and the public agent-chat surface no longer create a `sessions` row on open/mount. The row is created on the first message-send ("create-on-first-turn"), so opened-then-abandoned chats no longer leave phantom "0 turns" rows.
-- **Agent Sessions list refresh-after-delete fix** (`@elevasis/ui`) — a query-key factory bug (`sessionsKeys.sessions` appended a literal `undefined`) broke partial-match invalidation, so delete/create/archive left the list stale until a manual reload. Fixed; the list now refreshes automatically.
-- **Project milestone progress badge fix** (`@elevasis/ui`) — the `/projects` milestone header badge counted the milestone's own (empty) checklist, showing `0/0 COMPLETE`. It now counts completed child tasks, with a checklist fallback for task-free milestones.
-- **`project:*` CLI `--json` flag** (`@elevasis/sdk`) — every `project:*` command (project/task/milestone/note) now accepts `--json` for clean machine-parseable output, matching `grant:*`/`session:*`. The `/project` skill SKILL.md gains an Output Flags reference and the canonical `pnpm -s elevasis-sdk … --json` parse recipe (auto-propagated as a managed `.claude` write).
-
-## Applies to
-
-- All template-derived projects that expose the agent-sessions page (`ui/src/features/operations/sessions/`) or the public agent-chat surface.
-- All projects that drive work via the `elevasis-sdk project:*` CLI or surface the `/projects` delivery page.
-
-## Required actions
-
-- Bump `@elevasis/ui` to `^2.55.0` and `@elevasis/sdk` to `^1.36.5` (or later) and install. The ship train's `external-sync` stage does this automatically via the package-cascade baselines — manual `pnpm update` is not required.
-- No source changes are required to receive the lazy-session, delete-refresh, or milestone-badge fixes — they ship inside `@elevasis/ui`.
-- Agents may now invoke `pnpm -s elevasis-sdk project:<cmd> … --json` for clean JSON; the propagated `/project` SKILL.md Output Flags table documents the parse recipe.
-
-## Verification
-
-- `pnpm -C ui check-types` passes against `@elevasis/ui@^2.55.0`.
-- Open an agent-session chat without sending → no new `sessions` row appears in the list; send one message → exactly one row with `1 turn`.
-- Delete a session → the list refreshes without a manual reload.
-- `pnpm -s elevasis-sdk project:task:list --project <id> --json` exits 0 with parseable JSON and no `unknown option` error.
-
-## Not handled by /git-sync
-
-- `/git-sync` surfaces this note and pulls the propagated `/project` SKILL.md baseline, but it does not run the `@elevasis/ui` / `@elevasis/sdk` install for you when reconciling manually outside the ship train.
-- The lazy-session change does NOT retroactively clean up pre-existing "0 turns" rows; those are left in place by design.

package/reference/claude-config/sync-notes/2026-06-14-shared-session-conversation-view.md

@@ -1,26 +0,0 @@
-# Shared Session ConversationView
-
-## Why this note exists
-
-`@elevasis/ui` now ships a shared `SessionConversationView` component (WebSocket-backed session-detail chat body). The template's session-detail page previously filled the `renderConversationView` slot with a local stub (`ui/src/features/assistant/components/ConversationView.tsx`) that returned `null`, so the agent-sessions chat page (`/operations/sessions/$sessionId`) rendered blank and the `DISCONNECTED` badge never cleared. The template `SessionChatPage` now renders the shared component directly, so derived projects get a working session chat with no local implementation.
-
-## Applies to
-
-- All template-derived projects that expose the agent-sessions page (`ui/src/features/operations/sessions/SessionChatPage.tsx`).
-- Any project still carrying the `null`-returning `ConversationView` stub in `ui/src/features/assistant/components/`.
-
-## Required actions
-
-- Bump `@elevasis/ui` to `^2.55.0` (or later) in `ui/package.json` and install. (The ship train's `external-sync` stage does this automatically via the package-cascade baseline; manual `pnpm update` is not required.)
-- Adopt the new `SessionChatPage` slot wiring: render `<SessionConversationView apiUrl={API_URL} sessionId={...} ... />` from `@elevasis/ui/features/operations`, reading `API_URL` from `@/lib/constants/api`, instead of the local `ConversationView` stub.
-- The local `ConversationView` stub is now unused by the session page. It remains a generic placeholder for an AI-assistant feature; keep it only if you are building such a feature, otherwise it can be removed.
-
-## Verification
-
-- `pnpm -C ui check-types` passes against `@elevasis/ui@^2.55.0`.
-- The session-detail chat page renders history + live messages and the `DISCONNECTED` badge clears (connects) once `apiUrl` is wired.
-
-## Not handled by /git-sync
-
-- `/git-sync` surfaces this note and pulls the template `SessionChatPage` baseline, but it does not delete the now-unused local `ConversationView` stub. Remove it manually if you do not intend to build an assistant feature.
-- `/git-sync` does not run the `@elevasis/ui` install for you; run the install after the baseline bump if you are reconciling manually outside the ship train.

package/reference/claude-config/sync-notes/2026-06-15-session-chat-zero-wiring.md

@@ -1,46 +0,0 @@
-# Session Chat Zero-Wiring Default Slot
-
-## Why this note exists
-
-`@elevasis/ui` (>= 2.56.0) makes `SessionChatPage`'s `renderConversationView` slot
-optional and self-defaulting: when omitted, the page renders the shared
-`SessionConversationView` itself, resolving `apiUrl` from the service context
-(now exposed on `ElevasisServiceContextValue`). The template `SessionChatPage`
-now mounts the shared page with NO slot, and the orphan null-stub
-`ui/src/features/assistant/components/ConversationView.tsx` is deleted. Projects
-that omit the slot get a working session chat out of the box; customization stays
-opt-in via the same prop. Backward-compatible: hosts that still pass the slot are
-unaffected.
-
-## Applies to
-
-- All template-derived projects with the agent-sessions page
-  (`ui/src/features/operations/sessions/SessionChatPage.tsx`).
-- Any project still wiring a local `ConversationView` stub
-  (`ui/src/features/assistant/components/ConversationView.tsx`) -> these render
-  a blank chat with a stuck `DISCONNECTED` badge until reconciled.
-
-## Required actions
-
-- Bump `@elevasis/ui` to `^2.56.0` (or later) and install. (The ship train's
-  `external-sync` stage does this automatically via the package-cascade baseline;
-  manual `pnpm update` is not required.)
-- Drop the explicit `renderConversationView={...}` slot from your
-  `SessionChatPage.tsx` and remove the local stub import, relying on the new
-  default. (To keep a custom body, keep passing the slot.)
-- Delete the now-unused local null-stub
-  `ui/src/features/assistant/components/ConversationView.tsx`.
-
-## Verification
-
-- `pnpm -C ui check-types` passes against `@elevasis/ui@^2.56.0`.
-- The session-detail chat page (`/operations/sessions/$sessionId`) renders
-  history + live messages and the `DISCONNECTED` badge clears, with NO slot wired.
-
-## Not handled by /git-sync
-
-- `/git-sync` surfaces this note and pulls the template `SessionChatPage`
-  baseline, but the diverged tenant copy is preserved (merge-managed) -- you must
-  manually drop the explicit slot.
-- `/git-sync` does NOT delete the local `ConversationView` stub
-  (`delete_policy: none`); remove it manually.

package/reference/claude-config/sync-notes/2026-06-17-agent-session-ux-features.md

@@ -1,34 +0,0 @@
-# Agent session UX features (End Conversation, intake form, session naming)
-
-## Why this note exists
-
-This train bumps `@elevasis/core` and `@elevasis/ui` with three tenant-facing agent-session features that ship entirely inside the published packages (no template source edit, package-cascade-only):
-
-- **End Conversation** (`@elevasis/ui`) — both the internal Agent Sessions surface (`features/operations/sessions/SessionDetailsPanel`) and the public agent-chat surface (`features/public-agent-chat/PublicAgentChat`) now render an "End conversation" control. Ending preserves history and blocks new turns (distinct from Delete, which removes). The public composer locks out after end with a "This conversation has ended" placeholder.
-- **Welcome intake form** (`@elevasis/ui` + `@elevasis/core`) — the public chat intro screen renders an optional intake form driven by the grant's `capture_fields` column (now typed as `CaptureField[]` in `@elevasis/core`'s public-agent-chat schema). Collected values flow into `session.metadata`. All fields are optional.
-- **Session naming from intake** (`@elevasis/ui` + platform API) — sessions are titled from the collected `name` (server-side, with a first-user-message fallback), and the Agent Sessions list now renders `session.title` as the row label.
-
-The session `session:end` / `session:ended` WebSocket messages, the internal `POST /sessions/:id/end` route, and server-side title derivation live in the Elevasis-deployed platform API — tenants receive that behavior automatically; the package bump only delivers the frontend.
-
-## Applies to
-
-- All template-derived projects that expose the Agent Sessions page (`ui/src/features/operations/sessions/`) or the public agent-chat surface (`ui/src/features/public-agent-chat/`).
-- Projects that configure public agent grants and want to collect intake fields (Name plus arbitrary configurable fields) on the public intro screen.
-
-## Required actions
-
-- Bump `@elevasis/core` to `^0.52.0` and `@elevasis/ui` to `^2.59.0` (or later) and install. The ship train's `external-sync` stage does this automatically via the package-cascade baselines — manual `pnpm update` is not required.
-- No source changes are required to receive End Conversation, the intake form, or title-in-list — they ship inside `@elevasis/ui` / `@elevasis/core`.
-- To enable an intake form on a public agent, populate the grant's `capture_fields` (array of `{ key, label, type?, required? }`). There is no Command Center editor for `capture_fields` yet — configure it via a grant write. Leaving `capture_fields` empty renders the intro exactly as before (no form).
-
-## Verification
-
-- `pnpm -C ui check-types` passes against `@elevasis/ui@^2.59.0`.
-- Open the public agent chat for a grant with `capture_fields` set → the intro renders the configured fields; entering a name and starting the session titles the session by that name in the Agent Sessions list.
-- With no `capture_fields` → the intro renders unchanged; the session is titled from the first user message.
-- Click "End conversation" on either the public header or the internal session detail panel → the session ends, history is preserved, and a new turn is rejected ("Session has ended").
-
-## Not handled by /git-sync
-
-- `/git-sync` surfaces this note and pulls the propagated package baselines, but it does not run the `@elevasis/core` / `@elevasis/ui` install for you when reconciling manually outside the ship train.
-- The intake/title and End features depend on the Elevasis-deployed platform API (`session:end` handling, `/sessions/:id/end`, server-side title derivation). They are not part of a tenant's own backend and require no tenant action — but they only work once the platform API carrying them is deployed.

package/reference/claude-config/sync-notes/2026-06-25-shared-page-scroll-contract-guard.md

@@ -1,52 +0,0 @@
-# Shared Full-Height Page Scroll Contract + Canonical headerActions Pattern
-
-## Why this note exists
-
-`@elevasis/ui` (>= 2.61.2) hardens the shared full-height page scroll contract and
-the template now demonstrates the safe customization pattern for it.
-
-- `SubshellContentContainer` (the root of the lead-gen list-detail, CRM/delivery/
-  clients detail pages, etc.) is a `flex:1 / overflowY:auto / minHeight:0` scroll
-  container that only bounds correctly as a **direct flex child** of the shell's
-  height-bounded region. Wrapping a shared page in a layout element (e.g. a Mantine
-  `<Stack>`, which is `flex:0 1 auto` with no `min-height:0`) breaks the height
-  chain: the page balloons to content height and its internal scroll never engages.
-- The package now ships a **dev-only runtime guard** that logs a console warning when
-  it detects an unbounded `SubshellContentContainer`, so this mistake is caught while
-  authoring a route instead of shipping a silently broken page. No-op in production.
-- The template `lead-gen/lists.$listId.tsx` now injects a `ListExportButton` through
-  the page's **`headerActions` slot** (not a wrapper) as the canonical reference for
-  customizing a shared full-height page.
-
-## Applies to
-
-- All template-derived projects that render shared full-height pages
-  (`LeadGenListDetailPage`, CRM/delivery/clients detail pages).
-- Any project that wrapped a shared page in a `<Stack>` (or similar) to bolt on
-  extra UI -> that page's scroll is broken; switch to the page's slot props.
-
-## Required actions
-
-- Bump `@elevasis/ui` to `^2.61.2` (or later) and install. (The ship train's
-  `external-sync` stage does this automatically via the package-cascade baseline;
-  manual `pnpm update` is not required.)
-- If any route wraps a shared full-height page, remove the wrapper and pass the
-  extra UI through the page's slot props (`headerActions` / `tabs` / `footer`). The
-  template `lead-gen/lists.$listId.tsx` is the canonical reference.
-- Heed the new dev console warning if it appears; do not silence it.
-
-## Verification
-
-- `pnpm -C ui check-types` passes against `@elevasis/ui@^2.61.2`.
-- Open a shared detail page (e.g. `/lead-gen/lists/:listId`): the page scrolls
-  internally, the bottom is reachable, and no scroll-contract console warning fires.
-- Wrapping the page in a `<Stack>` produces the dev warning (negative check).
-
-## Not handled by /git-sync
-
-- `/git-sync` surfaces this note and pulls the template `lists.$listId.tsx` +
-  `ListExportButton` baseline, but a diverged tenant copy is preserved
-  (merge-managed) -- you must manually remove any page wrapper and adopt the slot
-  pattern.
-- The dev guard ships inside `@elevasis/ui`; no tenant source change is required to
-  receive it beyond the dependency-baseline bump.

package/reference/claude-config/sync-notes/2026-06-26-leadgen-overview-om-telemetry.md

@@ -1,47 +0,0 @@
-# Lead Gen Overview — OM-derived telemetry (NaN fix)
-
-## Why this note exists
-
-The published `@elevasis/ui` Lead Gen **Overview** page previously hardcoded the
-pre-migration canonical pipeline stage keys (`populated, extracted, qualified,
-discovered, verified, personalized, uploaded`) in its telemetry reducer. Any tenant
-whose Organization Model declares a different stage set got `undefined` stage reads
-and rendered `NaN` in the header and the **Ready Contacts** stat card.
-
-`@elevasis/ui@2.62.0` (paired with `@elevasis/core@0.54.0`) makes the Overview render
-generically over the OM-declared stage catalog. Telemetry now derives entirely from
-`getLeadGenStageCatalog()` + `ListTelemetry.stageCounts`; an absent stage contributes
-`0`, never `NaN`. The "ready / next focus" backlog moved from hardcoded
-`personalized − uploaded` to a declared OM descriptor.
-
-## Applies to
-
-- Every template-derived project that consumes `@elevasis/ui` for the Lead Gen
-  Overview surface and whose pipeline diverges from the old canonical stage set.
-- This is a **package-cascade-only** change: no template SOURCE edits are required.
-  The fix is bundled in the published packages; tenants only need the new baselines.
-
-## Required actions
-
-- Take the dependency baseline bump propagated by this train:
-  - `@elevasis/core` → `0.54.0`
-  - `@elevasis/ui` → `2.62.0`
-- Reinstall so the new bundles are live (`pnpm install` in the project's `ui/`
-  workspace) and clear any stale Vite optimize cache
-  (`node_modules/.vite`) before restarting a running dev server.
-
-## Verification
-
-- After the baseline bump + install, open the Lead Gen Overview for a list on a
-  divergent pipeline: the header summary and the three stat cards render finite
-  numbers, with no `NaN` and no reference to retired stages.
-- `pnpm sync:verify -- <project>` confirms the project is on the new baselines.
-
-## Not handled by /git-sync
-
-- **Optional OM authoring (tenant-owned, NOT shipped here):** a tenant MAY declare
-  `readinessTarget: true` on one stage in its `core/config/organization-model.ts`
-  stage catalog to restore a semantic "Ready: \<stage\>" stat. Until declared, the UI
-  correctly falls back to a generic last-incomplete-stage backlog. This is an
-  enhancement done via a separate `/om` cycle, never auto-propagated.
-- The visual confirmation that `NaN` is gone on a running tenant page (a human check).

package/reference/claude-config/sync-notes/2026-07-21-agent-scaffold-hardening.md

@@ -1,75 +0,0 @@
-# Agent Scaffold Hardening — deploy default, rule paths, ownership split
-
-## Why this note exists
-
-Three corrections in this train change guidance agents were previously following
-incorrectly. The first is safety-relevant and is the reason this note exists.
-
-**1. Plain `deploy` targets PRODUCTION, not dev.** `resolveApiUrl` in the SDK CLI
-falls through to `https://api.elevasis.io` unless `NODE_ENV === 'development'` is
-set. The template `CLAUDE.md` Commands table and the bundled `deployment.md` both
-stated that plain `deploy` targeted dev. Both were wrong, and every derived project
-inherited the wrong statement. The full resolution order is now documented:
-`--api-url` > `--prod` > `ELEVASIS_API_URL` > `NODE_ENV === 'development'` >
-production fallthrough. `resolveApiKey` follows a separate rule and is documented
-alongside it.
-
-If your project has no `NODE_ENV=development` in its environment, it has **no
-working dev target** — `deploy` and `deploy:prod` resolve to the same production
-API. Verify before your next deploy rather than assuming.
-
-**2. Bundled rule paths were wrong fleet-wide.** Every drill-down pointer said
-`node_modules/@elevasis/sdk/reference/...`. The SDK actually installs at
-`operations/node_modules/@elevasis/sdk/reference/...`; the project root has no
-`@elevasis` packages at all.
-
-**3. `ui.md` documented three import surfaces that do not exist.**
-
-| Was documented                                               | Actual                                                    |
-| ------------------------------------------------------------ | --------------------------------------------------------- |
-| `useApiClient` from `@/lib/hooks/useApiClient`               | `@elevasis/ui/api`, and it takes `API_URL` as an argument |
-| `ProtectedRoute` from `ui/src/features/auth/`                | `@elevasis/ui/auth` — that directory does not exist       |
-| `sseConnectionManager` from `@/lib/sse/SSEConnectionManager` | `@/lib/sse` (`ui/src/lib/sse.ts`)                         |
-
-## Applies to
-
-- Every template-derived project. All three corrections ship inside the
-  `@elevasis/sdk` reference bundle, so they arrive with the dependency baseline —
-  no source edits required to receive them.
-- `CLAUDE.md` also changed shape this train. Template-structural guidance (project
-  structure, stack, commands, slash-command surface) moved into
-  `.claude/Overview.md`, which is replace-managed and propagates by sync.
-  `CLAUDE.md` is now project-owned identity only and remains never-touch.
-
-## Required actions
-
-- Take the `@elevasis/sdk` dependency baseline bump propagated by this train, then
-  reinstall in `operations/` so `reference/rules/` carries the corrected canon.
-- Read the new `OPERATIONS.md` at your project root. It is tenant-owned, never
-  synced, and is the sanctioned home for operational facts that contradict generic
-  guidance — starting with your real deploy target.
-- Once this train's `.claude/Overview.md` has landed, remove template-structural
-  prose from your project's `CLAUDE.md`. Keep your identity sections verbatim.
-
-## Verification
-
-- `grep -n "elevasis/ui/api" operations/node_modules/@elevasis/sdk/reference/rules/ui.md`
-  returns a match, and `@/lib/hooks/useApiClient` returns none.
-- The bundled `deployment.md` leads with a Dev vs Prod section stating the
-  production default.
-- `.claude/Overview.md` contains Project Structure, Stack, and Commands sections.
-- `pnpm sync:verify -- <project>` confirms the project is on the new baseline.
-
-## Not handled by /git-sync
-
-- **The `CLAUDE.md` migration is manual and tenant-specific.** The file is
-  never-touch by design, so nothing overwrites it. Lifting stale template prose out
-  while preserving your identity sections is a per-project edit.
-- **Literal `{CLIENT_CONTEXT}` / `{USER_PREFERENCES}` placeholders must stay
-  literal** if setup has not run for your project. Setup only fills them while they
-  are still literal; replacing them with stub prose permanently marks an
-  unconfigured project as configured.
-- **One-time EOL renormalization.** This train adds `.gitattributes` (LF in-repo).
-  After it lands, run `git add --renormalize .` once in your project repo. Until
-  then the CRLF/LF false-drift persists in existing checkouts — it accounted for
-  roughly 95% of apparent `.claude/` drift before this change.