@vellumai/assistant 0.10.9-dev.202607162126.2d253b7 → 0.10.9-staging.2

package/ARCHITECTURE.md

@@ -1944,7 +1944,7 @@ Connected channels are resolved at signal emission time: vellum is always includ
 
 **Audit trail (SQLite):** `notification_events` → `notification_decisions` (with `conversationActions` in validation results) → `notification_deliveries` (with `conversation_id`, `message_id`, `conversation_strategy`, `conversation_action`, `conversation_target_id`, `conversation_fallback_used`)
 
-**Configuration:** `llm.callSites.notificationDecision` (decision engine) and `llm.callSites.preferenceExtraction` (preference extractor) in `config.json`. Both fall back to their shipped call-site defaults when unset.
+**Configuration:** `llm.callSites.notificationDecision` (decision engine) and `llm.callSites.preferenceExtraction` (preference extractor) in `config.json`. Both fall back to `llm.default` when unset.
 
 ---
 

package/Dockerfile

@@ -129,14 +129,6 @@ COPY packages/twilio-client /app/packages/twilio-client
 
 COPY assistant /app/assistant
 
-# Materialize the git-ignored offline plugin manifest from its canonical source.
-# `assistant/src/cli/lib/plugin-catalog-local.ts` statically imports this JSON
-# (loaded even when platform features are enabled), so it must exist in the image
-# — the build installs with --ignore-scripts, so the postinstall sync that
-# regenerates it in dev never runs here. Mirrors how CI materializes the
-# feature-flag registry before building.
-COPY plugins/marketplace.json /app/assistant/src/cli/lib/bundled-marketplace.json
-
 # Install assistant CLI launcher backed by the bundled assistant package
 RUN printf '#!/usr/bin/env sh\nexec bun run /app/assistant/src/index.ts "$@"\n' > /usr/local/bin/assistant && \
     chmod +x /usr/local/bin/assistant

package/docs/activation-funnel-telemetry.md

@@ -36,11 +36,7 @@ Flow, end to end:
    `assistant/src/onboarding/onboarding-events-store.ts`:
    - emission is **deterministic, tied to a `ui_show` surface** — there is no
      model-facing tool. The model tags the surface it is already rendering for a
-     rail move with an optional `activation_moment` parameter on `ui_show` (the
-     param is present in ui_show's schema only for activation-rail
-     conversations — `injectActivationMomentParam` in
-     `tools/ui-surface/channel-variants.ts`, applied at tool resolution when
-     `isActivationSession` is true); the
+     rail move with an optional `activation_moment` parameter on `ui_show`; the
      daemon captures that tag on the surface's server-side state and records the
      milestone (gated on `isActivationSession`). **Timing is per-moment**
      (`ACTIVATION_MOMENT_EMIT_AT` in `activation-funnel.ts`): most moments record
@@ -57,9 +53,8 @@ Flow, end to end:
    - emission is best-effort (wrapped in try/catch) and never blocks or alters
      the surface-action flow;
    - `recordActivationEvent` respects the platform `share_analytics` consent gate
-     via `getRawShareAnalytics()`: only a confirmed opt-out (`false`) drops the
-     event; an `"unknown"` state (cold cache, no platform session) records and
-     lets the flush/ingest gates enforce consent before anything ships.
+     via `getCachedShareAnalytics()` (returns `null` / no row when the platform
+     user has not consented; default-off when there is no platform session).
 2. **Reporter flushes** every ~5 min: `usage-telemetry-reporter.ts`
    (`REPORT_INTERVAL_MS = 5 * 60 * 1000`, with a one-time
    `INITIAL_FLUSH_DELAY_MS = 30_000` after startup) POSTs queued onboarding
@@ -185,11 +180,10 @@ the conversation in `activation_sessions` on first build of the system prompt.
 Two distinct concerns: whether record-time rows reach SQLite (consent gate), and
 whether those rows reach BigQuery (flush gate, dev-disabled).
 
-1. `recordActivationEvent` no-ops only on a confirmed `share_analytics` opt-out
-   (it reads `getRawShareAnalytics()`); an `"unknown"` state records, but the
-   flush defers until consent resolves. So for rows to actually SHIP, the dev
-   session must be signed in to
-   the platform with `share_analytics` consent enabled, or no rows reach
+1. `recordActivationEvent` no-ops when the platform `share_analytics` consent is
+   off (it reads `getCachedShareAnalytics()`), and the consent is **default-off
+   when there is no platform session**. So the dev session must be signed in to
+   the platform with `share_analytics` consent enabled, or no rows are written to
    SQLite. The consent cache is refreshed by `startConsentRefresh()` in
    `assistant/src/daemon/lifecycle.ts`, which runs **regardless of dev mode** — so
    a dev session signed in with `share_analytics` consent enabled writes

package/node_modules/@vellumai/ces-client/node_modules/@vellumai/service-contracts/package.json

@@ -15,7 +15,6 @@
     "./handles": "./src/handles.ts",
     "./rpc": "./src/rpc.ts",
     "./attachment-naming": "./src/attachment-naming.ts",
-    "./redacted-credential": "./src/redacted-credential.ts",
     "./error": "./src/error.ts"
   },
   "scripts": {

package/node_modules/@vellumai/gateway-client/node_modules/@vellumai/service-contracts/package.json

@@ -15,7 +15,6 @@
     "./handles": "./src/handles.ts",
     "./rpc": "./src/rpc.ts",
     "./attachment-naming": "./src/attachment-naming.ts",
-    "./redacted-credential": "./src/redacted-credential.ts",
     "./error": "./src/error.ts"
   },
   "scripts": {

package/node_modules/@vellumai/service-contracts/package.json

@@ -15,7 +15,6 @@
     "./handles": "./src/handles.ts",
     "./rpc": "./src/rpc.ts",
     "./attachment-naming": "./src/attachment-naming.ts",
-    "./redacted-credential": "./src/redacted-credential.ts",
     "./error": "./src/error.ts"
   },
   "scripts": {