feat: add release baseline and workspace scene

.changeset/README.md

@@ -0,0 +1,51 @@
+# Changesets In This Repo
+
+This directory is the release-intent ledger for Cadence UI.
+
+The repo is still an internal/private monorepo, so Changesets is used conservatively:
+
+- track version intent for releasable workspace packages
+- keep release notes attached to code changes
+- avoid auto-committing release files
+- avoid tagging private packages during early internal iteration
+
+## What should get a changeset
+
+Create a changeset when a change affects:
+
+- `@ai-ui/ui`
+- `@ai-ui/tokens`
+
+Do not create a changeset for docs-only work in `@ai-ui/docs` unless that work ships alongside
+a package change that already needs one. The docs app is ignored in the config on purpose.
+
+## What kind of summary to write
+
+Keep the summary short and consumer-facing:
+
+- describe what changed
+- mention the component, token, or contract surface
+- avoid implementation detail unless it changes behavior
+
+Good:
+
+```md
+Add the Sheet component for contextual side panels and bottom trays.
+```
+
+Less useful:
+
+```md
+Refactor dialog wrapper internals and update story coverage.
+```
+
+## Current release posture
+
+The root repo is private and package publishing is not fully wired yet. Until the main release
+flow is enabled, treat Changesets as the source of truth for:
+
+- which package versions should move
+- which changes deserve release notes
+- which internal dependency bumps should be coordinated
+
+See `docs/releasing.md` for the expected workflow around creating and consuming changesets.

.changeset/config.json

@@ -0,0 +1,17 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": false,
+  "commit": false,
+  "access": "restricted",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "fixed": [],
+  "linked": [],
+  "ignore": [
+    "@ai-ui/docs"
+  ],
+  "privatePackages": {
+    "version": true,
+    "tag": false
+  }
+}