@elevasis/sdk 1.36.4 → 1.37.0

package/reference/claude-config/skills/project/SKILL.md

@@ -256,6 +256,28 @@ Organization scoping is handled server-side via `ELEVASIS_PLATFORM_KEY`. No org
 
 ---
 
+## Output Flags
+
+All `project:*` commands support three output modes via flags:
+
+| Flag        | Behavior                   | Use when                                            |
+| ----------- | -------------------------- | --------------------------------------------------- |
+| _(no flag)_ | Raw JSON (legacy default)  | Existing scripts that parse default stdout          |
+| `--json`    | Clean JSON via `printJson` | Agent automation — the preferred machine-parse flag |
+| `--pretty`  | Human-readable text        | Interactive / debugging output                      |
+
+**Canonical machine-parse recipe:**
+
+```bash
+pnpm -s elevasis-sdk project:task:list --project <uuid> --json
+```
+
+The `-s` / `--silent` flag suppresses the pnpm lifecycle preamble (`> project@... elevasis-sdk ...`) so stdout is pure JSON with no wrapper noise. Use `--json` and `-s` together for all agent automation.
+
+**Defensive parse fallback** (if any wrapper noise remains): slice from the first `{` or `[` to the last `}` or `]` before calling `JSON.parse`.
+
+---
+
 ## Database Schema
 
 ### Tables

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

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

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

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

@@ -0,0 +1,34 @@
+# 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/rules/vibe.md

@@ -270,3 +270,4 @@ Layers 2 (Public API), 3 (UI Shell Runtime), 5 (Toolkit), and 6 (Graph) require
 - Vibe is not a skill. It lives in this rule file + CLAUDE.md + the PreToolUse hook -- not in `.claude/skills/`.
 - Vibe does not own the codify ceremony. `/om` owns draft, confirm, write, and typecheck for both Level A and Level B codify pipelines (decision #21 -- Codify ceremony delegated to `/om`). Vibe detects intent and hands off.
 - Vibe is not active in the monorepo. If working inside the monorepo (not an `external/` project), this ambient routing does not apply.
+- Vibe does not flip **public agent exposure**. Making a deployed agent reachable on the public internet (the `agent_access_grants` row behind `/public/agents/:slug`, managed via `grant:create` / `grant:update` / `grant:disable` or the Resource-page public/private toggle) is a **security boundary deliberately kept out of ambient routing** — a non-technical user describing their business must never be able to expose an agent by accident. This is a deliberate non-route, not an unhandled gap: do NOT classify "make my agent public" / "put the interview online" as Toggle (which is System on/off) and do NOT auto-execute. Surface the `grant:*` CLI or the Resource-page toggle in plain language and require explicit confirmation.