@elevasis/sdk 1.26.0 → 1.26.2

package/dist/cli.cjs

@@ -37181,15 +37181,55 @@ var ResourceMappingSchema = DisplayMetadataSchema.extend({
 
 // ../core/src/organization-model/domains/branding.ts
 var OrganizationModelBrandingSchema = external_exports.object({
+  /**
+   * @deprecated Prefer `identity.organizationName`; branding retains it for back-compat.
+   * Legacy tenants that have not set `identity.organizationName` fall back to this field.
+   */
   organizationName: LabelSchema,
+  /**
+   * @deprecated Prefer `identity.productName`; branding retains it for back-compat.
+   * Legacy tenants that have not set `identity.productName` fall back to this field.
+   */
   productName: LabelSchema,
+  /**
+   * @deprecated Prefer `identity.shortName`; branding retains it for back-compat.
+   * Legacy tenants that have not set `identity.shortName` fall back to this field.
+   */
   shortName: external_exports.string().trim().min(1).max(40),
+  /**
+   * @deprecated Prefer `identity.description`; branding retains it for back-compat.
+   * Legacy tenants that have not set `identity.description` fall back to this field.
+   */
   description: DescriptionSchema.optional(),
   logos: external_exports.object({
     light: external_exports.string().trim().min(1).max(2048).optional(),
     dark: external_exports.string().trim().min(1).max(2048).optional()
-  }).default({})
-});
+  }).default({}),
+  /**
+   * Brand voice — how the organization communicates. Plain-language description
+   * of tone, register, and personality (e.g. "Direct and human — no jargon").
+   * Max 280 characters.
+   */
+  voice: external_exports.string().trim().max(280).optional(),
+  /**
+   * Brand tagline or positioning statement — the memorable one-liner that
+   * captures the brand's promise or differentiator. Max 200 characters.
+   */
+  tagline: external_exports.string().trim().max(200).optional(),
+  /**
+   * Core brand values — an ordered list of principles the organization stands
+   * for (e.g. ["Transparency", "Craftsmanship", "Velocity"]). Each entry must
+   * be a non-empty trimmed string.
+   */
+  values: external_exports.array(external_exports.string().trim().min(1)).optional(),
+  /**
+   * ID of the active UI theme preset from the UI theme-presets registry.
+   * The UI layer resolves this to colors and typography via `usePresetsContext()`.
+   * Free-form string — validation and fallback state are handled at the UI layer.
+   * Min 1, max 64 characters.
+   */
+  themePresetId: external_exports.string().trim().min(1).max(64).optional()
+}).passthrough();
 var DEFAULT_ORGANIZATION_MODEL_BRANDING = {
   organizationName: "Default Organization",
   productName: "Organization OS",
@@ -37312,8 +37352,33 @@ var IdentityDomainSchema = external_exports.object({
    * background. Populated by /setup; surfaced to agents as organizational context.
    * Optional — many projects have no external client.
    */
-  clientBrief: external_exports.string().trim().default("")
-});
+  clientBrief: external_exports.string().trim().default(""),
+  /**
+   * Display name of the organization as shown to end users.
+   * Recommended placement for display naming — prefer this over the deprecated
+   * `branding.organizationName`. Falls back to `branding.organizationName` for
+   * legacy tenants that have not yet migrated.
+   */
+  organizationName: LabelSchema.optional(),
+  /**
+   * Display name of the primary product or platform.
+   * Recommended placement for display naming — prefer this over the deprecated
+   * `branding.productName`. Falls back to `branding.productName` for legacy tenants.
+   */
+  productName: LabelSchema.optional(),
+  /**
+   * Short abbreviated name used in space-constrained UI surfaces (max 40 chars).
+   * Recommended placement for display naming — prefer this over the deprecated
+   * `branding.shortName`. Falls back to `branding.shortName` for legacy tenants.
+   */
+  shortName: external_exports.string().trim().min(1).max(40).optional(),
+  /**
+   * Plain-language description of the organization for display and discovery.
+   * Recommended placement for display naming — prefer this over the deprecated
+   * `branding.description`. Falls back to `branding.description` for legacy tenants.
+   */
+  description: DescriptionSchema.optional()
+}).passthrough();
 var DEFAULT_ORGANIZATION_MODEL_IDENTITY = {
   mission: "",
   vision: "",
@@ -44059,7 +44124,7 @@ function wrapAction(commandName, fn) {
 // package.json
 var package_default = {
   name: "@elevasis/sdk",
-  version: "1.26.0",
+  version: "1.26.2",
   description: "SDK for building Elevasis organization resources",
   type: "module",
   bin: {

package/dist/index.d.ts

@@ -2884,6 +2884,51 @@ type Database = {
                     }
                 ];
             };
+            deployment_organization_models: {
+                Row: {
+                    created_at: string;
+                    deployment_id: string;
+                    model_hash: string | null;
+                    organization_id: string;
+                    organization_model: Json;
+                    schema_version: string;
+                    updated_at: string;
+                };
+                Insert: {
+                    created_at?: string;
+                    deployment_id: string;
+                    model_hash?: string | null;
+                    organization_id: string;
+                    organization_model: Json;
+                    schema_version?: string;
+                    updated_at?: string;
+                };
+                Update: {
+                    created_at?: string;
+                    deployment_id?: string;
+                    model_hash?: string | null;
+                    organization_id?: string;
+                    organization_model?: Json;
+                    schema_version?: string;
+                    updated_at?: string;
+                };
+                Relationships: [
+                    {
+                        foreignKeyName: "deployment_organization_models_deployment_id_fkey";
+                        columns: ["deployment_id"];
+                        isOneToOne: true;
+                        referencedRelation: "deployments";
+                        referencedColumns: ["id"];
+                    },
+                    {
+                        foreignKeyName: "deployment_organization_models_organization_id_fkey";
+                        columns: ["organization_id"];
+                        isOneToOne: false;
+                        referencedRelation: "organizations";
+                        referencedColumns: ["id"];
+                    }
+                ];
+            };
             deployments: {
                 Row: {
                     created_at: string;
@@ -6897,7 +6942,11 @@ declare const OrganizationModelSchema$1: z.ZodObject<{
             light: z.ZodOptional<z.ZodString>;
             dark: z.ZodOptional<z.ZodString>;
         }, z.core.$strip>>;
-    }, z.core.$strip>>;
+        voice: z.ZodOptional<z.ZodString>;
+        tagline: z.ZodOptional<z.ZodString>;
+        values: z.ZodOptional<z.ZodArray<z.ZodString>>;
+        themePresetId: z.ZodOptional<z.ZodString>;
+    }, z.core.$loose>>;
     navigation: z.ZodDefault<z.ZodObject<{
         sidebar: z.ZodDefault<z.ZodObject<{
             primary: z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodType<SidebarNode, unknown, z.core.$ZodTypeInternals<SidebarNode, unknown>>>>;
@@ -6944,7 +6993,11 @@ declare const OrganizationModelSchema$1: z.ZodObject<{
             }, z.core.$strip>>;
         }, z.core.$strip>>;
         clientBrief: z.ZodDefault<z.ZodString>;
-    }, z.core.$strip>>;
+        organizationName: z.ZodOptional<z.ZodString>;
+        productName: z.ZodOptional<z.ZodString>;
+        shortName: z.ZodOptional<z.ZodString>;
+        description: z.ZodOptional<z.ZodString>;
+    }, z.core.$loose>>;
     customers: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         order: z.ZodNumber;
@@ -7641,7 +7694,7 @@ declare function compileBusinessOntologyValidationIndex(model: OrganizationModel
  * organization model's `sales.lead-gen` stage records). Hosts that own a
  * populated tenant model (e.g. `apps/api` with the Elevasis canonical model)
  * MUST build their own index via `compileBusinessOntologyValidationIndex(model)`
- * and call `createLeadGenStageValidators(index)`. `@repo/core` stays generic —
+ * and call `createLeadGenStageValidators(index)`. The core package stays generic;
  * it must never import a tenant model.
  */
 type LeadGenStageValidators = {

package/dist/node/index.d.ts

@@ -1674,7 +1674,11 @@ declare const OrganizationModelSchema$1: z.ZodObject<{
             light: z.ZodOptional<z.ZodString>;
             dark: z.ZodOptional<z.ZodString>;
         }, z.core.$strip>>;
-    }, z.core.$strip>>;
+        voice: z.ZodOptional<z.ZodString>;
+        tagline: z.ZodOptional<z.ZodString>;
+        values: z.ZodOptional<z.ZodArray<z.ZodString>>;
+        themePresetId: z.ZodOptional<z.ZodString>;
+    }, z.core.$loose>>;
     navigation: z.ZodDefault<z.ZodObject<{
         sidebar: z.ZodDefault<z.ZodObject<{
             primary: z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodType<SidebarNode, unknown, z.core.$ZodTypeInternals<SidebarNode, unknown>>>>;
@@ -1721,7 +1725,11 @@ declare const OrganizationModelSchema$1: z.ZodObject<{
             }, z.core.$strip>>;
         }, z.core.$strip>>;
         clientBrief: z.ZodDefault<z.ZodString>;
-    }, z.core.$strip>>;
+        organizationName: z.ZodOptional<z.ZodString>;
+        productName: z.ZodOptional<z.ZodString>;
+        shortName: z.ZodOptional<z.ZodString>;
+        description: z.ZodOptional<z.ZodString>;
+    }, z.core.$loose>>;
     customers: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         order: z.ZodNumber;

package/dist/test-utils/index.d.ts

@@ -2717,6 +2717,51 @@ type Database = {
                     }
                 ];
             };
+            deployment_organization_models: {
+                Row: {
+                    created_at: string;
+                    deployment_id: string;
+                    model_hash: string | null;
+                    organization_id: string;
+                    organization_model: Json;
+                    schema_version: string;
+                    updated_at: string;
+                };
+                Insert: {
+                    created_at?: string;
+                    deployment_id: string;
+                    model_hash?: string | null;
+                    organization_id: string;
+                    organization_model: Json;
+                    schema_version?: string;
+                    updated_at?: string;
+                };
+                Update: {
+                    created_at?: string;
+                    deployment_id?: string;
+                    model_hash?: string | null;
+                    organization_id?: string;
+                    organization_model?: Json;
+                    schema_version?: string;
+                    updated_at?: string;
+                };
+                Relationships: [
+                    {
+                        foreignKeyName: "deployment_organization_models_deployment_id_fkey";
+                        columns: ["deployment_id"];
+                        isOneToOne: true;
+                        referencedRelation: "deployments";
+                        referencedColumns: ["id"];
+                    },
+                    {
+                        foreignKeyName: "deployment_organization_models_organization_id_fkey";
+                        columns: ["organization_id"];
+                        isOneToOne: false;
+                        referencedRelation: "organizations";
+                        referencedColumns: ["id"];
+                    }
+                ];
+            };
             deployments: {
                 Row: {
                     created_at: string;
@@ -6095,7 +6140,11 @@ declare const OrganizationModelSchema: z.ZodObject<{
             light: z.ZodOptional<z.ZodString>;
             dark: z.ZodOptional<z.ZodString>;
         }, z.core.$strip>>;
-    }, z.core.$strip>>;
+        voice: z.ZodOptional<z.ZodString>;
+        tagline: z.ZodOptional<z.ZodString>;
+        values: z.ZodOptional<z.ZodArray<z.ZodString>>;
+        themePresetId: z.ZodOptional<z.ZodString>;
+    }, z.core.$loose>>;
     navigation: z.ZodDefault<z.ZodObject<{
         sidebar: z.ZodDefault<z.ZodObject<{
             primary: z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodType<SidebarNode, unknown, z.core.$ZodTypeInternals<SidebarNode, unknown>>>>;
@@ -6142,7 +6191,11 @@ declare const OrganizationModelSchema: z.ZodObject<{
             }, z.core.$strip>>;
         }, z.core.$strip>>;
         clientBrief: z.ZodDefault<z.ZodString>;
-    }, z.core.$strip>>;
+        organizationName: z.ZodOptional<z.ZodString>;
+        productName: z.ZodOptional<z.ZodString>;
+        shortName: z.ZodOptional<z.ZodString>;
+        description: z.ZodOptional<z.ZodString>;
+    }, z.core.$loose>>;
     customers: z.ZodDefault<z.ZodDefault<z.ZodRecord<z.ZodString, z.ZodObject<{
         id: z.ZodString;
         order: z.ZodNumber;
@@ -10494,8 +10547,8 @@ type TypedAdapter<TMap extends ToolMethodMap$1> = {
  * Message protocol:
  *   Parent -> Worker:  { type: 'manifest' }
  *   Worker -> Parent:  { type: 'manifest', workflows: [...], agents: [...],
- *                         triggers?: [...], integrations?: [...], humanCheckpoints?: [...],
- *                         relationships?: {...} }
+ *                         organizationModel?: {...}, triggers?: [...], integrations?: [...],
+ *                         humanCheckpoints?: [...], relationships?: {...} }
  *
  *   Parent -> Worker:  { type: 'execute', resourceId, executionId, input, organizationId?, organizationName?,
  *                         sessionId?, sessionTurnNumber?, parentExecutionId?, executionDepth }

package/dist/test-utils/index.js

@@ -9284,6 +9284,7 @@ function startWorker(org) {
     if (msg.type === "manifest") {
       parentPort.postMessage({
         type: "manifest",
+        organizationModel: org.organizationModel,
         workflows: (org.workflows ?? []).map((w2) => ({
           resourceId: w2.config.resourceId,
           name: w2.config.name,
@@ -21298,7 +21299,7 @@ function recordAsyncAnnotation(test5, promise) {
   return promise;
 }
 
-// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_655b5a9ef789d2c00bade142a29242c2/node_modules/vitest/dist/chunks/utils.XdZDrNZV.js
+// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_d1cccf33043c821cd797d4ac11d33b3e/node_modules/vitest/dist/chunks/utils.XdZDrNZV.js
 var NAME_WORKER_STATE = "__vitest_worker__";
 function getWorkerState() {
   const workerState = globalThis[NAME_WORKER_STATE];
@@ -21346,7 +21347,7 @@ async function waitForImportsToResolve() {
   await waitForImportsToResolve();
 }
 
-// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_655b5a9ef789d2c00bade142a29242c2/node_modules/vitest/dist/chunks/_commonjsHelpers.BFTU3MAI.js
+// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_d1cccf33043c821cd797d4ac11d33b3e/node_modules/vitest/dist/chunks/_commonjsHelpers.BFTU3MAI.js
 var commonjsGlobal = typeof globalThis !== "undefined" ? globalThis : typeof window !== "undefined" ? window : typeof global !== "undefined" ? global : typeof self !== "undefined" ? self : {};
 function getDefaultExportFromCjs3(x2) {
   return x2 && x2.__esModule && Object.prototype.hasOwnProperty.call(x2, "default") ? x2["default"] : x2;
@@ -23379,7 +23380,7 @@ var SnapshotClient = class {
   }
 };
 
-// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_655b5a9ef789d2c00bade142a29242c2/node_modules/vitest/dist/chunks/date.Bq6ZW5rf.js
+// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_d1cccf33043c821cd797d4ac11d33b3e/node_modules/vitest/dist/chunks/date.Bq6ZW5rf.js
 var RealDate = Date;
 var now2 = null;
 var MockDate = class _MockDate extends RealDate {
@@ -23427,7 +23428,7 @@ function resetDate() {
   globalThis.Date = RealDate;
 }
 
-// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_655b5a9ef789d2c00bade142a29242c2/node_modules/vitest/dist/chunks/vi.bdSIJ99Y.js
+// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_d1cccf33043c821cd797d4ac11d33b3e/node_modules/vitest/dist/chunks/vi.bdSIJ99Y.js
 var unsupported = [
   "matchSnapshot",
   "toMatchSnapshot",
@@ -26108,7 +26109,7 @@ function getImporter(name) {
   return stack?.file || "";
 }
 
-// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_655b5a9ef789d2c00bade142a29242c2/node_modules/vitest/dist/index.js
+// ../../node_modules/.pnpm/vitest@3.2.4_@edge-runtime+_d1cccf33043c821cd797d4ac11d33b3e/node_modules/vitest/dist/index.js
 __toESM(require_dist());
 
 // src/test-utils/mock-adapters.ts

package/dist/types/worker/index.d.ts

@@ -7,8 +7,8 @@
  * Message protocol:
  *   Parent -> Worker:  { type: 'manifest' }
  *   Worker -> Parent:  { type: 'manifest', workflows: [...], agents: [...],
- *                         triggers?: [...], integrations?: [...], humanCheckpoints?: [...],
- *                         relationships?: {...} }
+ *                         organizationModel?: {...}, triggers?: [...], integrations?: [...],
+ *                         humanCheckpoints?: [...], relationships?: {...} }
  *
  *   Parent -> Worker:  { type: 'execute', resourceId, executionId, input, organizationId?, organizationName?,
  *                         sessionId?, sessionTurnNumber?, parentExecutionId?, executionDepth }

package/dist/worker/index.js

@@ -6801,6 +6801,7 @@ function startWorker(org) {
     if (msg.type === "manifest") {
       parentPort.postMessage({
         type: "manifest",
+        organizationModel: org.organizationModel,
         workflows: (org.workflows ?? []).map((w) => ({
           resourceId: w.config.resourceId,
           name: w.config.name,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elevasis/sdk",
-  "version": "1.26.0",
+  "version": "1.26.2",
   "description": "SDK for building Elevasis organization resources",
   "type": "module",
   "bin": {
@@ -58,7 +58,7 @@
     "tsup": "^8.0.0",
     "typescript": "5.9.2",
     "zod": "^4.1.0",
-    "@repo/core": "0.31.0",
+    "@repo/core": "0.33.0",
     "@repo/eslint-config": "0.0.0",
     "@repo/typescript-config": "0.0.0"
   },

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

@@ -23,7 +23,7 @@ Before collecting any information or running any steps, determine which state th
 
 **State A — Virgin (placeholders present):** One or more of the above placeholder strings is found. Run the full bootstrap flow (Steps 1–7 below), then hand off to `/om`.
 
-**State B — Already bootstrapped, org-model at defaults:** No placeholders found, but `core/config/organization-model.ts` contains only the default branding override (just `branding.organizationName`, `branding.productName`, `branding.shortName` — no identity, customers, offerings, roles, goals, or techStack overrides). Print:
+**State B — Already bootstrapped, org-model at defaults:** No placeholders found, but `core/config/organization-model.ts` contains only the default display naming override (just `identity.organizationName`, `identity.productName`, `identity.shortName`, with legacy `branding.*` fallback values — no customers, offerings, roles, goals, or techStack overrides). Print:
 
 ```
 This project is already set up. The organization model has not been configured yet.
@@ -32,7 +32,7 @@ Running /om to set up your organization profile...
 
 Then execute `/om` (the full layered flow) and stop.
 
-**State C — Fully configured:** No placeholders found AND `core/config/organization-model.ts` has at least one non-branding domain populated (identity, customers, offerings, roles, goals, or techStack present). Print:
+**State C — Fully configured:** No placeholders found AND `core/config/organization-model.ts` has at least one non-default business domain populated (customers, offerings, roles, goals, techStack, or identity fields beyond display naming/client brief). Print:
 
 ```
 This project is already configured. To update your organization profile, run /om.

package/reference/claude-config/sync-notes/2026-05-23-branding-names-to-identity.md

@@ -0,0 +1,49 @@
+# Branding Names to Identity
+
+## Why this note exists
+
+The Organization Model now treats `identity.organizationName`, `identity.productName`,
+and `identity.shortName` as the preferred source for display naming. The older
+`branding.*` name fields remain valid for backward compatibility, but new template code
+reads identity first and falls back to branding only for legacy projects.
+
+Branding also now supports first-class expression fields such as `voice`, `tagline`,
+`values`, and `themePresetId`, while still accepting tenant-specific passthrough fields.
+
+## Applies to
+
+Template-derived projects that customize Organization Model branding or read
+`organizationModel.branding.organizationName`, `productName`, or `shortName` directly in
+UI or setup code.
+
+## Required actions
+
+1. Keep existing `branding.organizationName`, `branding.productName`, and
+   `branding.shortName` values in place for compatibility.
+2. Add matching values under `identity.organizationName`, `identity.productName`, and
+   `identity.shortName`.
+3. Update project UI code to read `identity.* ?? branding.*` for display naming.
+4. Move brand expression into the broadened `branding` fields: `voice`, `tagline`,
+   `values`, `themePresetId`, and project-owned passthrough fields as needed.
+
+## Verification
+
+Run the normal template-derived project gates after syncing:
+
+```powershell
+pnpm -C core test
+pnpm -C ui check-types
+pnpm -C ui build
+pnpm -C operations check-types
+pnpm -C operations check
+```
+
+Also open the app shell and Knowledge Base identity/branding views. Confirm display names
+render from identity and branding expression fields render under Branding.
+
+## Not handled by /git-sync
+
+`/git-sync` cannot choose real brand voice, tagline, values, logo assets, or custom
+passthrough fields for an individual tenant. It also cannot remove legacy
+`branding.*` name fields from project-specific code until maintainers confirm every
+consumer has migrated to the identity-first fallback.

package/reference/claude-config/sync-notes/2026-05-23-lead-gen-manage-access.md

@@ -0,0 +1,31 @@
+# Lead Gen Manage Access Package Baseline
+
+## Why this note exists
+
+This train adds `sales.lead-gen.manage` as the OM-aligned runtime permission for operating Lead Gen list-builder mutations. The implementation ships through `@elevasis/core` and `@elevasis/ui`; template projects need the package baseline update so derived apps receive the new access key and shared Lead Gen UI guards.
+
+## Applies to
+
+- Template UI package baseline: `external/_template/ui/package.json`
+- Template core package baseline: `external/_template/core/package.json`
+- Template operations package baseline: `external/_template/operations/package.json`
+- Derived projects that expose the shared Lead Gen list-builder UI
+
+## Required actions
+
+1. Publish the prepared `@elevasis/core` release containing `sales.lead-gen.manage` and `AccessKeys.leadGenManage`.
+2. Publish the prepared `@elevasis/ui` release containing the shared Lead Gen mutation affordance guards.
+3. Run the prepared external sync manifest so derived projects receive the updated package baselines.
+4. For client launches, verify Operator users receive `sales.lead-gen.manage` through platform role grants before list-builder smoke.
+
+## Verification
+
+- `pnpm -C packages/core build:publish`
+- `pnpm -C packages/ui build:publish`
+- `pnpm -C external/_template/ui check-types`
+- `pnpm -C external/_template/ui build`
+- `pnpm sync:verify` after the manifest-scoped external sync stage
+
+## Not handled by /git-sync
+
+Database permission rows and system role grants are environment state, not template files. Apply the SQL migration or equivalent environment change separately before inviting Operator users.

package/reference/claude-config/sync-notes/2026-05-23-om-deployment-drift-detection.md

@@ -0,0 +1,42 @@
+# OM Deployment Drift Detection
+
+## Why this note exists
+
+The platform API now persists deployed Organization Model snapshots and validates tenant
+lead-gen and CRM catalogs against the requesting tenant's active deployed model. The
+template does not need source changes for this server-side fix, but template-derived
+projects should accept the `@elevasis/core` package baseline when this release train
+publishes it so generated database and shared type surfaces stay aligned.
+
+## Applies to
+
+Template-derived projects that use SDK deployments, lead-gen list creation, CRM stages,
+or CRM actions through the hosted Elevasis API.
+
+## Required actions
+
+1. Pull the package baseline update produced by this ship train.
+2. Redeploy or verify tenant operations resources if the project has recently changed its
+   Organization Model catalogs.
+3. After the API deployment stage completes, smoke lead-gen list creation with a
+   project-owned build template ID.
+
+## Verification
+
+Run the normal template-derived project gates after syncing:
+
+```powershell
+pnpm -C core test
+pnpm -C operations check-types
+pnpm -C operations check
+pnpm -C ui check-types
+pnpm -C ui build
+```
+
+For projects using lead-gen, also verify list creation against the hosted API with a
+tenant-owned build template ID.
+
+## Not handled by /git-sync
+
+`/git-sync` cannot apply the production database change or deploy the hosted API. It also
+does not create project-specific Organization Model catalogs or workflow resources.

package/reference/claude-config/sync-notes/2026-05-23-ui-sdk-package-fixes.md

@@ -0,0 +1,37 @@
+# UI + SDK package fixes (lastVisitedOrg, worker-manifest organizationModel)
+
+## Why this note exists
+
+`@elevasis/ui` and `@elevasis/sdk` were republished with two backward-compatible fixes:
+
+- `@elevasis/ui`: `OrganizationProvider` now persists org preference as `lastVisitedOrg` (matching the `/api/users/me` schema), removing the noisy 400 on organization switching.
+- `@elevasis/sdk`: the worker manifest now includes `organizationModel`, so platform deployment persistence receives your tenant Organization Model snapshot.
+
+The SDK change requires a deploy, not just an install, to take effect on your active platform deployment.
+
+## Applies to
+
+All template-derived projects that consume `@elevasis/ui` and `@elevasis/sdk` and run an `operations/` resources bundle on the Elevasis platform.
+
+## Required actions
+
+1. Pull and install so the new baselines land:
+   - `@elevasis/ui` baseline bump in `ui/package.json`
+   - `@elevasis/sdk` baseline bump in `operations/package.json`
+2. `pnpm -C ui install && pnpm -C operations install` (or a project-root install) to update lockfiles.
+3. Redeploy your operations bundle so the worker manifest publishes your Organization Model to the active deployment:
+   - dev: `pnpm -C operations deploy`
+   - prod: `pnpm -C operations deploy:prod`
+4. Redeploy the UI (your host, e.g. Vercel) so the `lastVisitedOrg` fix ships to the browser.
+
+No source merges are required; both changes are internal to the published packages.
+
+## Verification
+
+- `pnpm -C ui check-types && pnpm -C ui build`
+- `pnpm -C operations check && pnpm -C operations check-types`
+- After deploy, confirm the active deployment persists an Organization Model snapshot (Lead Gen / list surfaces resolve the tenant model rather than erroring), and that organization switching no longer emits a 400 against `/api/users/me`.
+
+## Not handled by /git-sync
+
+`/git-sync` pulls the new baselines and surfaces this note, but it does NOT install dependencies, deploy your operations bundle, or redeploy your UI. Run the install + deploy steps above yourself; the worker-manifest fix only takes effect on your active deployment after an operations redeploy.

package/reference/cli-management.mdx

@@ -149,9 +149,9 @@ For exact required flags and accepted enum values, see the command source under
 
 ## elevasis-sdk note:\*
 
-`elevasis-sdk note:*` is the agent-facing surface for pushing and reading personal user notes. Workflows and agents use it to surface information -- such as "deal X stalled" or "review run completed" -- directly into a user's Notes panel in the Command Center, without sending an email or notification.
+`elevasis-sdk note:*` is the agent-facing surface for pushing and reading user notes. Workflows and agents use it to surface information -- such as "deal X stalled" or "review run completed" -- directly into a user's Notes panel in the Command Center, without sending an email or notification.
 
-Notes are personal to the target user and scoped to the calling organization. The external API surface exposes `GET + POST` only; `note:update` and `note:delete` are not yet available via SDK CLI. Users edit and delete notes through the right-panel view in the Command Center.
+Agent-written notes are private to the target user and scoped to the calling organization. The authenticated Notes panel can also create and edit org-shared notes (`visibility: 'org'`), which are visible to active members of the same organization and show creator attribution. The external SDK CLI surface exposes `GET + POST` only; `note:update` and `note:delete` are not yet available via SDK CLI. Users edit, delete, and change visibility through the right-panel view.
 
 ### note:create
 
@@ -187,6 +187,7 @@ elevasis-sdk note:create --content <text>
 - Posts to `POST /api/external/user-notes`
 - When `--user` is omitted the note is created for the identity bound to the API key (the caller)
 - When `--user` is provided the platform resolves the email to a Supabase user UUID and verifies the resolved user is an active member of the calling organization before writing
+- External agent-created notes are always private; org-shared visibility is a signed-in UI capability, not a broadcast CLI mode
 - The `--source` flag is recorded as the `source` column in `user_notes`; agent runtimes should pass their resource ID here so users can see which workflow created the note
 - Priority `normal` produces no badge in the UI; `high` renders orange, `urgent` renders red, `low` renders dimmed gray
 
@@ -279,9 +280,9 @@ elevasis-sdk note:list --user ops@acme.com --priority high --pinned --pretty
 
 ### Command Boundary
 
-- `note:create` and `note:list` operate on the **personal notes** surface -- not project notes. For project-scoped notes use `project:note:*`.
+- `note:create` and `note:list` operate on the **user notes** surface -- not project notes. For project-scoped notes use `project:note:*`.
 - `note:update` and `note:delete` are not yet available via SDK CLI. Edit and delete notes using the Notes panel in the Command Center.
-- The Notes panel view (`NotesPanelView`) is registered in the right-panel registry alongside Overview, Recent Executions, and Notifications.
+- The shared Notes panel view (`NotesPanelView`) is exported from `@elevasis/ui/features/notes` and registered in the right-panel registry alongside Overview, Recent Executions, and Notifications.
 
 **Implementation:** `packages/sdk/src/cli/commands/notes.ts` -- delegates to `POST /api/external/user-notes` and `GET /api/external/user-notes`
 
@@ -289,7 +290,8 @@ elevasis-sdk note:list --user ops@acme.com --priority high --pinned --pretty
 
 The following invariants govern the Notes feature and are relevant when building agents or workflows that write notes:
 
-- **Scope:** Notes are user-scoped and organization-scoped by default. A user can optionally make a note global, but the default scope is the current org.
+- **Scope:** Notes are user-scoped and organization-scoped by default. A signed-in user can mark a note as org-shared; agent-created notes stay private to the target user.
+- **Org-shared visibility:** `visibility: 'org'` lets active org members see and edit the note. Only the creator can change the visibility value.
 - **Sort order:** Pinned first, then by priority (`urgent` > `high` > `normal` > `low`), then by most recently updated.
 - **Broadcast:** Out of scope. Agents create notes for one resolved user at a time. Broadcast is a notifications concern, not a notes concern.
 - **Retention:** Notes persist until the user explicitly deletes them. There is no TTL and no dismissed state.
@@ -426,7 +428,7 @@ elevasis-sdk session:end <id>
 
 ## elevasis-sdk queue:\*
 
-Manage HITL command queue tasks. See the [Command Queue CLI Guide](/technical/development/agent-driven-development/command-cli-guide) for the full command reference.
+Manage HITL command queue tasks. See the [Command Queue CLI Guide](/technical/development/agent-driven-development/cli-operations) for the full command reference.
 
 **Quick reference:**
 
@@ -444,7 +446,7 @@ elevasis-sdk queue:status --pretty
 
 ## elevasis-sdk schedule:\*
 
-Manage recurring, relative, and absolute task schedules. See the [Schedule CLI Guide](/technical/development/agent-driven-development/schedule-cli-guide) for the full command reference including schedule config JSON shapes.
+Manage recurring, relative, and absolute task schedules. See the [Schedule CLI Guide](/technical/development/agent-driven-development/cli-operations) for the full command reference including schedule config JSON shapes.
 
 **Quick reference:**
 
@@ -466,7 +468,7 @@ elevasis-sdk schedule:cancel <id> --pretty
 
 Knowledge map inspection. The `om:*` (Organization Model) commands expose knowledge graph traversal via the CLI.
 
-For the full command reference, flag details, and graph architecture, see the [knowledge:\* CLI documentation](/technical/features/knowledge/knowledge-cli).
+For the full command reference, flag details, and graph architecture, see the [knowledge:\* CLI documentation](/technical/features/knowledge/cli-and-skill).
 
 **Quick reference:**