@elevasis/sdk 1.36.5 → 1.37.0

package/dist/test-utils/index.js

@@ -7561,17 +7561,13 @@ var AcqListMetadataSchema = z.object({
 }).catchall(z.unknown());
 var ProspectingBuildTemplateIdSchema = z.string().trim().min(1).max(100);
 var ListStageCountsSchema = z.object({
-  // Attempted counts by canonical lead-gen stage. The detailed status
-  // distribution lives on ListProgress; telemetry keeps the overview payload small.
-  stageCounts: z.object({
-    populated: z.number().int(),
-    extracted: z.number().int(),
-    qualified: z.number().int(),
-    discovered: z.number().int(),
-    verified: z.number().int(),
-    personalized: z.number().int(),
-    uploaded: z.number().int()
-  }),
+  // Attempted counts keyed by the tenant's declared lead-gen stage catalog IDs.
+  // The catalog is tenant-owned and OM-derived at compute time; the schema
+  // validates the transport shape (string keys → integer values) rather than
+  // a fixed key set, so tenants with custom stages receive complete telemetry.
+  // Canonical Elevasis stages (populated, extracted, qualified, discovered,
+  // verified, personalized, uploaded) are included when declared in the catalog.
+  stageCounts: z.record(z.string().min(1), z.number().int()),
   deliverability: z.object({
     valid: z.number().int(),
     risky: z.number().int(),
@@ -8775,17 +8771,48 @@ var SYSTEM_INTERFACE_PROFILES = [
 var SYSTEM_INTERFACE_READINESS_PROFILES = SYSTEM_INTERFACE_PROFILES.map(
   (profile) => profile.readinessProfile
 );
-var SystemInterfaceReadinessProfileSchema = z.enum(SYSTEM_INTERFACE_READINESS_PROFILES);
+var SystemInterfaceReadinessProfileSchema = z.string().trim().min(1);
 var SystemInterfaceResourceScopeSchema = z.array(ModelIdSchema).default([]);
+var SystemApiInterfaceReadinessContractSchema = z.object({
+  /** Ontology IDs of object types the interface depends on. */
+  requiredObjects: z.array(z.string().trim().min(1)).default([]),
+  /** Ontology IDs of catalog types the interface requires (must be non-empty). */
+  requiredCatalogs: z.array(z.string().trim().min(1)).default([]),
+  /** Optional ontology kind filters (reserved for future profile extensions). */
+  requiredKinds: z.array(z.string().trim().min(1)).optional()
+}).strict();
 var SystemApiInterfaceSchema = z.object({
   lifecycle: SystemInterfaceLifecycleSchema.default("active"),
+  /**
+   * Open-string profile id. Built-in platform presets are looked up through
+   * the profile registry; custom ids are validated structurally via
+   * `readinessContract`. Optional — `profileForInterface` provides a default.
+   */
   readinessProfile: SystemInterfaceReadinessProfileSchema.optional(),
   /**
    * Resource ids that participate in this API interface. This scopes readiness
    * derivation without duplicating authored required/provided contract refs.
    */
-  resourceIds: SystemInterfaceResourceScopeSchema.optional()
+  resourceIds: SystemInterfaceResourceScopeSchema.optional(),
+  /**
+   * Tenant-authorable readiness declaration. Required for custom
+   * (non-built-in) profile ids so structural validation can proceed. Built-in
+   * profiles ignore this field (requirements are derived from platform code).
+   */
+  readinessContract: SystemApiInterfaceReadinessContractSchema.optional()
 }).strict();
+var _profileRegistry = new Map(
+  SYSTEM_INTERFACE_READINESS_PROFILES.map((profileId) => [
+    profileId,
+    { profileId, kind: "built-in" }
+  ])
+);
+function profileForInterface(systemPath, interfaceKey, readinessProfile) {
+  return readinessProfile ?? `${systemPath}.${interfaceKey}`;
+}
+function isBuiltInReadinessProfile(profileId) {
+  return _profileRegistry.get(profileId)?.kind === "built-in";
+}
 z.object({
   systemPath: SystemPathSchema,
   interfaceKey: SystemInterfaceKeySchema
@@ -9032,14 +9059,11 @@ function addReadinessIssue(issues, family, code, message, details = {}) {
 function formatInterfaceIdentity(systemPath, interfaceKey) {
   return `${systemPath}/${interfaceKey}`;
 }
-function profileForInterface(systemPath, interfaceKey, readinessProfile) {
-  return readinessProfile ?? `${systemPath}.${interfaceKey}`;
-}
 function readinessMarkerPath(context) {
   return context.interfaceKey === "api" ? `systems.${context.systemPath}.apiInterface` : `systems.${context.systemPath}.derivedCrmHandoffReadiness`;
 }
 function formatSupportedReadinessProfiles() {
-  return SYSTEM_INTERFACE_READINESS_PROFILES.map((profile) => `"${profile}"`).join(", ");
+  return SYSTEM_INTERFACE_PROFILES.map((p3) => `"${p3.readinessProfile}"`).join(", ");
 }
 function getActiveScopedResources(model, resourceIds, issues, context) {
   const resources = [];
@@ -9231,9 +9255,6 @@ function getLeadGenCrmHandoffResourceIds(model) {
 function getSystemInterfaceReadinessMarker(model, request) {
   const system = getSystem(model, request.systemPath);
   if (system === void 0) return void 0;
-  if (request.interfaceKey === LEAD_GEN_API_INTERFACE.interfaceKey) {
-    return system.apiInterface;
-  }
   if (request.systemPath === LEAD_GEN_CRM_HANDOFF_INTERFACE.systemPath && request.interfaceKey === LEAD_GEN_CRM_HANDOFF_INTERFACE.interfaceKey) {
     return {
       lifecycle: "active",
@@ -9241,6 +9262,9 @@ function getSystemInterfaceReadinessMarker(model, request) {
       resourceIds: getLeadGenCrmHandoffResourceIds(model)
     };
   }
+  if (request.interfaceKey === "api" && system.apiInterface !== void 0) {
+    return system.apiInterface;
+  }
   return void 0;
 }
 function mergeLeadGenDerivedCatalogs(model) {
@@ -9285,6 +9309,18 @@ function tryCompileBusinessOntology(model, readinessProfile, issues) {
     return void 0;
   }
 }
+function requireContractReadiness(issues, index2, resources, contract, context) {
+  const reads = resourceBindingIds(resources, "reads");
+  const catalogs = resourceBindingIds(resources, "usesCatalogs");
+  for (const objectId of contract.requiredObjects) {
+    requireObjectReadiness(issues, index2, objectId, context);
+    requireScopedBinding(issues, reads, "reads", objectId, context);
+  }
+  for (const catalogId of contract.requiredCatalogs) {
+    requireCatalogReadiness(issues, index2, catalogId, context);
+    requireScopedBinding(issues, catalogs, "usesCatalogs", catalogId, context);
+  }
+}
 function computeInterfaceReadiness(model, request) {
   const issues = [];
   const system = getSystem(model, request.systemPath);
@@ -9332,20 +9368,22 @@ function computeInterfaceReadiness(model, request) {
       { path: `${readinessMarkerPath(request)}.lifecycle` }
     );
   }
-  const supportedProfile = readinessProfile !== void 0 && SYSTEM_INTERFACE_PROFILES.some((profile) => profile.readinessProfile === readinessProfile);
-  if (!supportedProfile) {
+  const checkedReadinessProfile = readinessProfile ?? profileForInterface(request.systemPath, request.interfaceKey);
+  const isBuiltIn = isBuiltInReadinessProfile(checkedReadinessProfile);
+  const readinessContract = systemInterface.readinessContract;
+  if (!isBuiltIn && readinessContract === void 0) {
     addReadinessIssue(
       issues,
       "SYSTEM_INTERFACE_INVALID",
-      "unknown-readiness-profile",
-      `System Interface "${formatInterfaceIdentity(request.systemPath, request.interfaceKey)}" references unknown readiness profile "${readinessProfile}". Supported profiles: ${formatSupportedReadinessProfiles()}. Custom Systems should not declare apiInterface; route custom behavior through workflows/operations plus ontology, resources, and topology.`,
-      { path: `${readinessMarkerPath(request)}.readinessProfile`, ref: readinessProfile }
+      "missing-readiness-contract",
+      `System Interface "${formatInterfaceIdentity(request.systemPath, request.interfaceKey)}" uses custom readiness profile "${checkedReadinessProfile}" but declares no readinessContract. Built-in profiles: ${formatSupportedReadinessProfiles()}.`,
+      { path: `${readinessMarkerPath(request)}.readinessContract`, ref: checkedReadinessProfile }
     );
     return {
       ready: false,
       systemPath: request.systemPath,
       interfaceKey: request.interfaceKey,
-      readinessProfile,
+      readinessProfile: checkedReadinessProfile,
       scopedResourceIds,
       issues
     };
@@ -9359,10 +9397,6 @@ function computeInterfaceReadiness(model, request) {
       { path: `${readinessMarkerPath(request)}.resourceIds` }
     );
   }
-  const checkedReadinessProfile = readinessProfile;
-  if (checkedReadinessProfile === void 0) {
-    throw new Error("Supported readiness profile unexpectedly resolved to undefined");
-  }
   const resources = getActiveScopedResources(model, scopedResourceIds, issues, request);
   const index2 = tryCompileBusinessOntology(model, checkedReadinessProfile, issues);
   if (index2 !== void 0) {
@@ -9374,13 +9408,15 @@ function computeInterfaceReadiness(model, request) {
       requireLeadGenInterfaceReadiness(issues, index2, resources, request);
       requireCrmInterfaceReadiness(issues, index2, resources, { ...request, allowForeignOwner: true });
       requireHandoffBridgeReadiness(issues, model, request);
+    } else if (readinessContract !== void 0) {
+      requireContractReadiness(issues, index2, resources, readinessContract, request);
     }
   }
   return {
     ready: issues.length === 0,
     systemPath: request.systemPath,
     interfaceKey: request.interfaceKey,
-    readinessProfile,
+    readinessProfile: checkedReadinessProfile,
     scopedResourceIds,
     issues
   };

package/dist/worker/index.js

@@ -5537,17 +5537,13 @@ var AcqListMetadataSchema = z.object({
 }).catchall(z.unknown());
 var ProspectingBuildTemplateIdSchema = z.string().trim().min(1).max(100);
 var ListStageCountsSchema = z.object({
-  // Attempted counts by canonical lead-gen stage. The detailed status
-  // distribution lives on ListProgress; telemetry keeps the overview payload small.
-  stageCounts: z.object({
-    populated: z.number().int(),
-    extracted: z.number().int(),
-    qualified: z.number().int(),
-    discovered: z.number().int(),
-    verified: z.number().int(),
-    personalized: z.number().int(),
-    uploaded: z.number().int()
-  }),
+  // Attempted counts keyed by the tenant's declared lead-gen stage catalog IDs.
+  // The catalog is tenant-owned and OM-derived at compute time; the schema
+  // validates the transport shape (string keys → integer values) rather than
+  // a fixed key set, so tenants with custom stages receive complete telemetry.
+  // Canonical Elevasis stages (populated, extracted, qualified, discovered,
+  // verified, personalized, uploaded) are included when declared in the catalog.
+  stageCounts: z.record(z.string().min(1), z.number().int()),
   deliverability: z.object({
     valid: z.number().int(),
     risky: z.number().int(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.36.5",
+  "version": "1.37.0",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -58,9 +58,9 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.51.0",
-    "@repo/typescript-config": "0.0.0",
-    "@repo/eslint-config": "0.0.0"
+    "@repo/core": "0.53.0",
+    "@repo/eslint-config": "0.0.0",
+    "@repo/typescript-config": "0.0.0"
   },
   "scripts": {
     "lint": "eslint src --max-warnings 0",

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.