@salsita-ai/contracts 0.49.0-develop.fc391028c9 → 0.50.0-develop.da56a0c6c3

package/CHANGELOG.md

@@ -2,6 +2,73 @@
 
 All notable changes to the @salsita-ai/contracts package will be documented in this file.
 
+## [0.49.0]
+
+feat: add the `assistant` export path with the assistant's `getBrowserDetails` and `getViewport` tool definitions and user-message metadata schema (CON-2852)
+
+chore: bump `openai` to 7.23.0
+
+feat: the `assistant` export path gains what a deployment registers for the experimental assistant (CON-2854)
+
+`DeploymentAssistant` and `AssistantAiSettings` (types and zod schemas) describe the registration: the GraphQL SDL, the SDK-generated prompt, the optional instructions and the AI settings. `ASSISTANT_AI_PROVIDERS`, `ASSISTANT_MODEL_TIERS` and `ASSISTANT_REASONING_LEVELS` list the allowed values.
+
+change!: remove the experimental `viewportTool` (`getViewport`) from the `assistant` export path
+
+It was a proof of the JSON tool-result path and has no replacement; `browserDetailsTool` stays.
+
+Migration:
+
+- Remove imports and uses of `viewportTool`. There is no replacement.
+
+chore: bump `@tanstack/ai` to 0.64.0
+
+feat: the `assistant` export path gains the `query` and `apply` tools of the experimental assistant (CON-2870)
+
+`queryTool` and `applyTool` are the tool definitions the server registers and the SDK implements in the browser. Both take `{ operations: [{ query, variables?, operationName? }] }`, a list of single-operation GraphQL documents run in order. `AssistantGraphQLToolInput` (type and zod schema) parses that input.
+
+feat: add `CustomerType` (`standard`, `sdk_builder`), its `CustomerTypeSchema`, and a `type` on `Customer`
+
+feat: add the `DeploymentBuild` domain for SDK-builder builds
+
+`DeploymentBuild`, `DeploymentBuildId`, `DeploymentBuildSourceKey`, `DeploymentBuildMode` (`init`, `upload`) and `DeploymentBuildStatus` (`queued` through `live`, `failed`, `cancelled`) describe a build and the statuses a runner reports.
+
+feat: add the `ApiTokenId` domain id for API tokens
+
+feat: add `SdkBuilderSetupState` to the domain module: the setup states of an SDK builder's workspace (`pending`, `ready`, `failed`)
+
+feat: add the optional `sub` claim to `SessionTokenPayload`, and optional `userId` and `userIdSource` fields to the auth handler response (CON-2897)
+
+`sub` is the user a configurator session belongs to, namespaced by the server by its source: `clerk-<id>`, `custom-<id>`, `anonymous-<browser uuid>` or `studio-<id>`. An auth handler returns its user id unprefixed in `userId`; `userIdSource` (`clerk` or `custom`, defaults to `custom`) picks the namespace. Webhooks that return neither keep working. The new `AuthUserIdSource` schema is exported from the `webhook` path.
+
+change!: publish the package publicly as `@salsita-ai/contracts` under a proprietary licence
+
+Published code is minified and ships without source maps; `CHANGELOG.md` ships with the package. `@salsita-ai/platform-contracts` receives no further releases. Projects on the application-spec pipeline do not depend on this package directly: `@salsita-ai/sdk` mirrors every entry point as `@salsita-ai/sdk/contracts/<path>`.
+
+Migration:
+
+- In a customer project, import `@salsita-ai/sdk/contracts/<path>` instead of `@salsita-ai/platform-contracts/<path>` and drop the direct dependency; the entry points (`api`, `clerk`, `domain`, `chat`, `assistant`, `webhook`) are unchanged.
+
+feat: add `DEFAULT_PROJECT_ALIAS` (CON-2948)
+
+`DEFAULT_PROJECT_ALIAS` (`default`) is what an application spec writes as `project` to mean the default project of the signed-in customer. The server refuses it as a project slug.
+
+feat: `Customer` gains `aiAssistantEnabled`, the feature flag that lets a customer use the experimental assistant (CON-2960)
+
+feat: add the feedback domain: `FeedbackId`, `FeedbackType`, `FeedbackSource` and the message and contact length limits (CON-2964)
+
+feat: `DeploymentBuild` records when the runner first reported each running status
+
+`preparingAt`, `buildingAt` and `deployingAt` are set the first time a build reaches that status, and stay empty for a status the runner skipped.
+
+change!: move the server-side behaviour of the domain entities out of contracts into the private `server-domain` package
+
+The `domain` module keeps the types, zod schemas, branded types with their constructors, and the state values clients compare against; `DeploymentBuild.isFinished` and the `SdkBuilderSetupState` values stay. No longer exported are the behaviour objects `Environment`, `Customer`, `Project`, `Deployment`, `ConfigurationSchema`, `Configuration`, `SessionBucket` and `ImageRenderBucket` (their names remain as types), `createDevelopmentKey`, the queueing and status transitions of `DeploymentBuild` (`create`, `canReport`, `applyReport`, `fail`, `isTimedOut`) with `DEPLOYMENT_BUILD_TIMEOUT_MS` and the `DeploymentBuildReport` type, `SdkBuilderSetupState.of`, `DEVELOPMENT_FRONTEND_URL`, and the system environment-variable classification `SYSTEM_ENV_VISIBILITY` with its `DefaultSystemVariables` type.
+
+Migration:
+
+- Nothing to do in a configurator project: none of the removed exports was part of what the SDK, Studio or a demo uses.
+- Server code imports the domain from `server-domain`, which re-exports the contracts `domain` module with the removed behaviour on top.
+
 ## [0.48.0]
 
 change!: remove the process-local `ClerkBackendApiClient.fetchUserCached()` method (CON-2556, CON-2685)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salsita-ai/contracts",
-  "version": "0.49.0-develop.fc391028c9",
+  "version": "0.50.0-develop.da56a0c6c3",
   "description": "Shared API, authentication, domain, chat, and webhook contracts for Phoenix.",
   "keywords": [
     "salsita",
@@ -56,7 +56,7 @@
     "uuid": "14.0.0",
     "valid-url": "1.0.9",
     "zod": "3.25.76",
-    "@salsita-ai/common": "0.49.0-develop.fc391028c9"
+    "@salsita-ai/common": "0.50.0-develop.da56a0c6c3"
   },
   "devDependencies": {
     "@lingui/core": "5.9.5",