@elevasis/sdk 1.34.0 → 1.34.1

package/reference/claude-config/skills/om/operations/build.md

@@ -0,0 +1,237 @@
+---
+name: build
+description: Guided Codify-ceremony runbook for building a new Organization Model System end to end in a tenant project — shell, ontology, resources, topology, knowledge node, and verify.
+allowed-tools: Read, Glob, Grep, Bash
+---
+
+# /om build (Tenant)
+
+Intent-driven runbook for authoring a complete Organization Model System in this tenant project.
+The **primary entry is intent**: `/om` routes free-text build intent here via `promptSignals` and
+the 5-bucket classifier whenever you describe a system you want to build. Manual `/om build` is a
+supported secondary entry.
+
+Every write runs through the Codify ceremony (snapshot → propose → confirm → write → validate →
+rollback). See the "Write Power" section in `SKILL.md` for the ceremony steps.
+
+**Tenant authoring files** (split layout):
+
+- `core/config/organization-model/systems.ts` — System entries and system-owned resources
+- `core/config/organization-model/navigation.ts` — sidebar wiring
+- `core/config/knowledge/nodes/` — knowledge node MDX files
+
+---
+
+## Phase 0 — Capture Intent
+
+Before writing anything, extract:
+
+1. **System name and dotted path** (`parent.child` format, e.g. `sales.crm`).
+2. **Kind**: `product`, `operational`, `platform`, or `diagnostic`.
+3. **What it does** — one sentence. This becomes the `description`.
+4. **What it owns** — objects, actions, catalogs, events (these become `system.ontology` entries).
+5. **What it calls or reacts to** — other systems, triggers, human checkpoints.
+6. **Whether it needs a UI route** — yes/no determines whether `system.ui` is authored.
+7. **Whether it adopts a platform API interface** — yes/no determines whether `system.apiInterface`
+   is authored (see "API Interface Readiness" in `SKILL.md`).
+
+Run a pre-flight read to ground id choices in current model state:
+
+```bash
+pnpm elevasis-sdk om:ls /all-systems
+```
+
+---
+
+## Phase 1 — System Shell (Codify Level-A)
+
+Use `om:scaffold:system` (dry-run first) or the Codify Level-A ceremony to add the `SystemEntry`
+to `core/config/organization-model/systems.ts`.
+
+**Dry-run:**
+
+```bash
+pnpm elevasis-sdk om:scaffold:system --dry-run
+```
+
+Minimum fields: `id`, `order`, `label`. Optional at this stage: `description`, `kind`,
+`lifecycle`, `responsibleRoleId`.
+
+**Validate after write:**
+
+```bash
+pnpm -C operations check-types
+pnpm -C operations check
+```
+
+---
+
+## Phase 2 — Ontology (`system.ontology`)
+
+Add owned ontology kinds inside the `ontology` field of the `SystemEntry` in `systems.ts`.
+
+Valid scope keys: `objectTypes`, `linkTypes`, `actionTypes`, `catalogTypes`, `eventTypes`,
+`interfaceTypes`, `valueTypes`, `sharedProperties`, `groups`, `endpoints`.
+
+All ids use the canonical format: `system.path:kind/local-id`
+(e.g. `sales.crm:object/deal`, `sales.crm:action/qualify-lead`).
+
+Apply via the Codify Level-A ceremony — read, propose diff, confirm, write, validate.
+
+**Validate after write:**
+
+```bash
+pnpm -C operations check-types
+pnpm -C operations check
+```
+
+---
+
+## Phase 3 — Resources (Codify Level-A + scaffold)
+
+Add resource entries to `systems.ts` (or the split `resources` section if your project uses one).
+Each resource carries `systemPath` (canonical system attachment) and `ontology` bindings.
+
+Use `om:scaffold:resource` for guided creation, or Codify Level-A for manual addition.
+
+**Dry-run:**
+
+```bash
+pnpm elevasis-sdk om:scaffold:resource --dry-run --system-path <your.system>
+```
+
+Key invariants:
+
+- `resource.systemPath` is the canonical attachment for `getResourcesForSystem()`.
+- Choose `systemPath` based on the business capability the resource operates, not its kind.
+- `primaryAction` must be a member of `resource.ontology.actions`.
+
+**Validate after write:**
+
+```bash
+pnpm -C operations check-types
+pnpm -C operations check
+```
+
+---
+
+## Phase 4 — Topology (optional)
+
+If the system reacts to events, calls other systems, or requires human checkpoints, author
+topology relationships. In a tenant project, topology lives alongside the System entries in
+`systems.ts` (or a dedicated `topology` field if your project uses the split layout with a
+separate topology section).
+
+Canonical relationship kinds:
+
+- `triggers` — event, webhook, or schedule fires a resource handler
+- `uses` — this system calls another system or integration
+- `approval` — a step requires human checkpoint before continuing
+
+Cross-system API handoff requires a `uses` edge with `systemInterfaceGrant` metadata — see the
+"API Interface Readiness" section in `SKILL.md`.
+
+Apply via Codify Level-A ceremony. Validate after each topology write.
+
+---
+
+## Phase 5 — Knowledge Node (optional)
+
+Author a governing knowledge node to make the system searchable via `/om` and surfaced in the
+knowledge browser.
+
+Use `om:scaffold:knowledge` for guided creation:
+
+```bash
+pnpm elevasis-sdk om:scaffold:knowledge --dry-run --system-path <your.system> --kind playbook
+```
+
+MDX frontmatter shape:
+
+```mdx
+---
+id: knowledge.my-system-playbook
+kind: playbook
+label: My System Playbook
+description: Rules and patterns for operating My System.
+governs:
+  - my.system
+---
+```
+
+After authoring, regenerate the knowledge index:
+
+```bash
+pnpm elevasis-sdk om:generate
+```
+
+---
+
+## Phase 6 — UI and Navigation (optional)
+
+If the system needs a sidebar entry, author `system.ui` and add a navigation surface entry.
+
+`system.ui` fields: `path`, `surfaces[]`, `icon`, `order`. Apply via Codify Level-A.
+
+Navigation wiring lives in `core/config/organization-model/navigation.ts`. Add the system's
+path to the relevant sidebar section. Validate after the navigation write.
+
+---
+
+## Phase 7 — apiInterface (API-backed systems only)
+
+`system.apiInterface` is adopt-only in tenant projects. Only add it when the system adopts a
+platform-provided API capability from the installed `@elevasis/core` / `@elevasis/sdk` version.
+Use only readiness profiles listed in
+`node_modules/@elevasis/sdk/reference/scaffold/reference/system-interface-capabilities.md`.
+
+The profile also fixes the required System path — do not invent a profile or repoint a cataloged
+profile to a custom path.
+
+Apply via Codify Level-A after confirming the readiness profile with the user:
+
+```bash
+pnpm -C operations check-types
+pnpm -C operations check   # conformance gate fires here if the marker is incomplete
+```
+
+---
+
+## Phase 8 — Full Verify
+
+Run both validation gates once all phases are done:
+
+```bash
+pnpm -C operations check-types
+pnpm -C operations check
+```
+
+If the conformance gate reports a gaps file, apply it:
+
+```bash
+pnpm elevasis-sdk om:scaffold:fill --gaps .elevasis/conformance-gaps.json --dry-run
+```
+
+---
+
+## Quick Reference
+
+| Phase | OM Slot                           | Authoring File                    | Ceremony                |
+| ----- | --------------------------------- | --------------------------------- | ----------------------- |
+| 1     | `systems` map                     | `systems.ts`                      | Scaffold or Level-A     |
+| 2     | `system.ontology.<scope>`         | `systems.ts`                      | Level-A                 |
+| 3     | resources + `resource.systemPath` | `systems.ts`                      | Scaffold or Level-A     |
+| 4     | topology relationships            | `systems.ts` / topology section   | Level-A                 |
+| 5     | `system.governedByKnowledge[]`    | `knowledge/nodes/<path>/<id>.mdx` | Scaffold or Level-A     |
+| 6     | `system.ui` + navigation surfaces | `systems.ts` + `navigation.ts`    | Level-A                 |
+| 7     | `system.apiInterface`             | `systems.ts`                      | Level-A (adopt-only)    |
+| 8     | —                                 | —                                 | `check` + `check-types` |
+
+---
+
+## Cross-Links
+
+- Codify Level-A ceremony: `.claude/skills/om/operations/codify-level-a.md`
+- Scaffold (guided new entries): `.claude/skills/om/operations/scaffold.md`
+- API interface readiness: "API Interface Readiness" section in `.claude/skills/om/SKILL.md`
+- Platform narrative guide + worked examples: `node_modules/@elevasis/sdk/reference/guides/building-systems.md` (if present)

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

@@ -0,0 +1,47 @@
+# /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-08-knowledge-base-page-not-found-fix.md

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

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

@@ -0,0 +1,42 @@
+# 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/sdk/cli-management.mdx

@@ -21,6 +21,26 @@ elevasis-sdk project:task:save <id> --current-state "Updated" --files-modified @
 
 Use `@json:<path>` for generated payloads, nested objects, arrays, or Windows shells. Inline JSON remains supported for small values.
 
+### Passing JSON arguments across shells
+
+Agents launch `elevasis-sdk` from either bash or PowerShell, so JSON quoting guidance must hold for both. A JSON argument crosses two parsers before the CLI sees it:
+
+1. **The outer shell** (bash or PowerShell) -- decides whether embedded `"` survive.
+2. **The pnpm run-script layer** -- `pnpm elevasis-sdk ...` is an npm run-script. On Windows, pnpm runs scripts through `cmd.exe /c`, which re-parses arguments. `pnpm exec elevasis-sdk` and direct bin calls do not add this layer.
+
+Each shell fails at a different layer, so a single inline-quoting fix does not cover both.
+
+- **bash** preserves embedded double quotes, so inline JSON survives the shell itself. The failure is the `pnpm <run-script>` wrapper's `cmd.exe` re-parse: `cmd` treats `( ) & < > | ^ %` as metacharacters, and a value containing them aborts with `<X> was unexpected at this time.` before the CLI runs. Keep inline JSON ASCII and metacharacter-free, or bypass the run-script layer with the direct exec form (`pnpm -C operations exec elevasis-sdk ...`).
+- **Windows PowerShell 5.1** strips embedded double quotes when calling a native exe (`node`, `pnpm`), with or without pnpm. The stop-parsing token `--%` and backslash-escaped quotes both fail. There is no reliable inline-JSON route. PowerShell 7+ fixes this class via `$PSNativeCommandArgumentPassing = 'Standard'`.
+
+**Cross-shell rule:** file-based input is shell-agnostic -- only a path crosses the shell boundary. Prefer `@json:<path>` (or `-f` / `--input-file` for `exec` and `request:submit`) for any non-trivial JSON, and write the file with an editor rather than a shell heredoc.
+
+| Shell          | Inline JSON                             | Why                                           | Use instead                          |
+| -------------- | --------------------------------------- | --------------------------------------------- | ------------------------------------ |
+| bash           | OK if values avoid `( ) & < > | ^ %` | run-script `cmd.exe` re-parses metacharacters | direct exec form, or `@json:<path>`  |
+| PowerShell 5.1 | Never reliable                          | strips embedded `"`; `--%` and `\"` both fail | `@json:<path>`                       |
+| either         | n/a                                     | path arguments avoid all JSON shell escaping  | `@json:<path>` + editor-written file |
+
 ---
 
 ## elevasis-sdk project:\*
@@ -446,21 +466,65 @@ elevasis-sdk agent:get <id>
 
 ## elevasis-sdk session:\*
 
-Inspect and manage agent sessions.
+Create, operate, inspect, and export multi-turn agent sessions. Use `elevasis-sdk exec`
+for one-off workflow or agent execution; use `elevasis-sdk session:*` when the deployed
+agent is `sessionCapable` and needs transcript persistence across turns.
 
 ```bash
+elevasis-sdk session:create <resourceId>
+elevasis-sdk session:turn <id> -f tmp/turn-1.json
+elevasis-sdk session:messages <id>
 elevasis-sdk session:list
 elevasis-sdk session:get <id>
 elevasis-sdk session:end <id>
 ```
 
+- `session:create <resourceId>` -- create a session for a session-capable deployed agent
+- `session:turn <id>` -- execute a turn in an active session; pass input with `--input`
+  or `--input-file`
+- `session:messages <id>` -- export the full transcript by default; use `--page` for a
+  single paginated API read
 - `session:list` -- list sessions for the organization; supports filtering by resource ID, user ID, and limit
-- `session:get <id>` -- get full session detail including messages and events
+- `session:get <id>` -- get session state and metadata
 - `session:end <id>` -- gracefully end an active session
 
-**API routes:** `GET /api/external/sessions`, `/api/external/sessions/:id`, `DELETE /api/external/sessions/:id`
+**API routes:** `POST /api/external/sessions`, `GET /api/external/sessions`,
+`GET /api/external/sessions/:id`, `POST /api/external/sessions/:id/turns`,
+`GET /api/external/sessions/:id/messages`, `POST /api/external/sessions/:id/end`
+
+Hard deletion is intentionally not part of `session:end`; any destructive delete surface
+must be exposed as a separate explicit command.
+
+**`session:create` flags:**
+
+| Flag                  | Description                    |
+| --------------------- | ------------------------------ |
+| `--user-id <id>`    | Optional user ID for session   |
+| `--metadata <json>` | Optional session metadata JSON |
+| `--json`              | Output as JSON                 |
+| `--api-url <url>`   | Override the API base URL      |
+
+**`session:turn` flags:**
+
+| Flag                        | Description                                  |
+| --------------------------- | -------------------------------------------- |
+| `-i, --input <json>`      | Turn input as JSON                           |
+| `-f, --input-file <path>` | Read turn input from a JSON file             |
+| `--json`                    | Output as JSON                               |
+| `--api-url <url>`         | Override the API base URL                    |
+
+**`session:messages` flags:**
+
+| Flag                  | Description                                                 |
+| --------------------- | ----------------------------------------------------------- |
+| `--limit <limit>`   | Messages per API page; default comes from the API           |
+| `--cursor <cursor>` | Message index cursor to start after                         |
+| `--page`              | Fetch one API page for debugging instead of all pages       |
+| `--all`               | Fetch all pages; this is the default transcript export mode |
+| `--json`              | Output as JSON                                              |
+| `--api-url <url>`   | Override the API base URL                                   |
 
-**`session:list` filter flags:**
+**`session:list` flags:**
 
 | Flag                   | Description                          |
 | ---------------------- | ------------------------------------ |
@@ -695,25 +759,25 @@ The same coverage gate runs inside `elevasis-sdk check` when the coverage regist
 
 Current status of all SDK CLI domains. Domains marked `deferred` have no CLI commands yet.
 
-| Domain      | CLI surface                                                               | API surface                                                | Status                       |
-| ----------- | ------------------------------------------------------------------------- | ---------------------------------------------------------- | ---------------------------- |
-| platform    | top-level SDK commands                                                    | mixed platform APIs                                        | implemented                  |
-| project     | `project:*`                                                               | `apps/api/src/projects/`                                   | implemented                  |
-| knowledge   | `knowledge:*`                                                             | file/generated knowledge data                              | implemented                  |
-| creds       | `creds *` nested Commander group                                          | credentials API                                            | implemented                  |
-| ui          | `ui:*`                                                                    | local project file edits                                   | implemented                  |
-| request     | `request:submit`, `request:list`, `request:get`                           | requests API                                               | implemented read/write scope |
-| error       | `error resolve`, `error resolve-execution`                                | execution error APIs                                       | partial                      |
-| acquisition | `acquisition:list:*`, `acquisition:deal:*`                                | `/api/external/acquisition/lists*`, `/api/external/deals*` | implemented read-only scope  |
-| client      | `client:*`                                                                | `/api/external/clients`                                    | implemented read/write scope |
-| agent       | `agent:list`, `agent:get`                                                 | `/api/external/agents*`                                    | implemented read-only scope  |
-| session     | `session:list`, `session:get`, `session:end`                              | `/api/external/sessions*`                                  | implemented management scope |
-| queue       | `queue:list`, `queue:get`, `queue:select`, `queue:expire`, `queue:status` | `/api/external/command-queue*`                             | implemented                  |
-| schedule    | `schedule:list`, `schedule:get`, `schedule:create`, `schedule:update`     | `/api/external/task-scheduler/schedules*`                  | implemented                  |
+| Domain      | CLI surface                                                               | API surface                                                    | Status                        |
+| ----------- | ------------------------------------------------------------------------- | -------------------------------------------------------------- | ----------------------------- |
+| platform    | top-level SDK commands                                                    | mixed platform APIs                                            | implemented                   |
+| project     | `project:*`                                                               | `apps/api/src/projects/`                                       | implemented                   |
+| knowledge   | `knowledge:*`                                                             | file/generated knowledge data                                  | implemented                   |
+| creds       | `creds *` nested Commander group                                          | credentials API                                                | implemented                   |
+| ui          | `ui:*`                                                                    | local project file edits                                       | implemented                   |
+| request     | `request:submit`, `request:list`, `request:get`                           | requests API                                                   | implemented read/write scope  |
+| error       | `error resolve`, `error resolve-execution`                                | execution error APIs                                           | partial                       |
+| acquisition | `acquisition:list:*`, `acquisition:deal:*`                                | `/api/external/acquisition/lists*`, `/api/external/deals*`     | implemented read-only scope   |
+| client      | `client:*`                                                                | `/api/external/clients`                                        | implemented read/write scope  |
+| agent       | `agent:list`, `agent:get`                                                 | `/api/external/agents*`                                        | implemented read-only scope   |
+| session     | `session:create`, `session:turn`, `session:messages`, `session:list`, `session:get`, `session:end` | `/api/external/sessions*`                                      | implemented multi-turn scope  |
+| queue       | `queue:list`, `queue:get`, `queue:select`, `queue:expire`, `queue:status` | `/api/external/command-queue*`                                 | implemented                   |
+| schedule    | `schedule:list`, `schedule:get`, `schedule:create`, `schedule:update`     | `/api/external/task-scheduler/schedules*`                      | implemented                   |
 | skill       | `skill:scaffold`, `skill:check-coverage`                                  | local CLI catalog and `.claude/registries/skill-coverage.json` | implemented developer tooling |
-| content     | none                                                                      | not scoped here                                            | deferred                     |
-| seo         | none                                                                      | not scoped here                                            | deferred                     |
-| monitoring  | none                                                                      | not scoped here                                            | deferred                     |
+| content     | none                                                                      | not scoped here                                                | deferred                      |
+| seo         | none                                                                      | not scoped here                                                | deferred                      |
+| monitoring  | none                                                                      | not scoped here                                                | deferred                      |
 
 ### Promotion Criteria
 

package/reference/ui/exports.mdx

@@ -25,6 +25,7 @@ description: "Auto-generated catalog of all published @elevasis/ui subpath expor
 | `@elevasis/ui/features/delivery` | Features Delivery | Features | Published delivery feature surface for downstream shells. |
 | `@elevasis/ui/features/lead-gen` | Features Lead Gen | Features | Published lead generation feature surface for downstream shells. |
 | `@elevasis/ui/features/operations` | Features Operations | Features | Published operations feature surface for downstream shells. |
+| `@elevasis/ui/features/public-agent-chat` | Features Public Agent Chat | Features | Published public agent chat surface for downstream shells. |
 | `@elevasis/ui/features/monitoring` | Features Monitoring | Features | Published monitoring feature surface for downstream shells. |
 | `@elevasis/ui/features/monitoring/requests` | Features Monitoring Requests | Features | Published submitted-requests list, detail, and triage surface for downstream shells. |
 | `@elevasis/ui/features/seo` | Features SEO | Features | Published SEO feature surface for downstream shells. |