v0.1.41

No commit subjects, so I need to inspect the diffs.## Fixes

• Mastra memory and storage now run on a dedicated service-principal Lakebase pool instead of the routing pool's per-request OBO identity. Threads, messages, and semantic recall live in the app-owned mastra_* schemas, which a per-user role typically cannot create or share, so memory now connects reliably across users and during schema auto-creation.

Internals

• The memory builder takes an explicit service-principal Pool resolved from the lakebase plugin's getPgConfig() outside any asUser scope, dropping the previous lazy RoutingPool lookup. SP username falls back to an API lookup for local PAT-authenticated dev.
• The plugin drains its memory pool on abortActiveOperations, clearing the handle so a re-setup() rebuilds it.
• Added a direct pg dependency for the new pool construction.

v0.1.40

I'll inspect the actual diff since there are no commit subjects to work from.## Fixes

• appkit-mastra: Fix production crash when dispatching to the Mastra sub-app under an OBO token. The asUser(req) proxy wrapped the express app's .bind (which is express's HTTP BIND route registrar, not Function.prototype.bind), registering a bogus route and crashing pathToRegexp. Requests now route through a plain dispatchMastra method that invokes the express app off the real target while keeping the OBO user scope active for agent and model resolvers.

v0.1.39

Release v0.1.39

v0.1.38

Release v0.1.38

v0.1.37

Fixes

• Mastra plugin: register the fallback router middleware without an empty path string, so the agent app handler mounts correctly across router versions.

v0.1.36

Let me inspect the UI changes since the new suggestion-pills.tsx file and reworked suggestions logic need explanation.Let me check the mastra-chat.tsx and suggestions.ts diff to see what initial suggestion handling changed.## Release notes v0.1.36

Features

• Initial starter suggestions now run through the same dedupe and cap pipeline as in-conversation follow-ups, so Genie-sourced sample questions surface a short, varied list with near-duplicates folded out. Explicit caller-provided suggestions still render verbatim.

Internals

• Extracted a shared SuggestionPills component so starter suggestions (above the composer) and per-message follow-ups render and behave identically, including consistent multi-line wrapping and capsule styling.
• Factored suggestion dedupe/cap logic into a shared pickSuggestions core, exposing dedupeSuggestions for flat lists alongside the existing event-based collectSuggestions.

v0.1.35

With no commit messages, I need to inspect the actual diffs to write accurate notes.The new space.ts is untracked, so empty diff. Let me read it and the UI/protocol changes.Now the UI chat-view/empty-state changes and demo. Let me check those briefly.## v0.1.35

Features

• Genie space starter prompts. New getGenieSpace / genieSampleQuestions helpers in @dbx-tools/genie fetch a space's serialized_space blob and extract the author-curated sample_questions. The Mastra plugin exposes them through a new OBO-scoped GET /suggestions (and /suggestions/:agentId) route, merged and deduped across all resolved spaces with a short-lived per-space cache.
• Auto-sourced chat suggestions. MastraChat now fills its empty-state one-tap prompts from the agent's Genie space sample questions via the new useMastraSuggestions hook and suggestionsUrl helper. Pass an explicit suggestions list to override, or [] to force none; apps with no Genie space show a bare empty state instead of hardcoded movie examples.
• Streaming word-by-word fade-in. AssistantMarkdown accepts an animate flag that eases each newly arrived token in via Streamdown's per-word animation, applied only to the actively streaming bubble.

Fixes

• Chat layout / scrollbar alignment. ChatView moves the centered max-w-4xl framing onto each section (header, transcript, suggestions, composer) and reserves a stable scrollbar gutter, so the scrollbar sits at the far edge and the composer stays aligned with the message column whether or not a scrollbar shows.

Internals

• Removed the apiUtils.fetchApi / apiUrl REST wrapper from @dbx-tools/shared. appkit-serving and the Genie space tools now issue requests through the workspace client's raw apiClient directly, dropping the bespoke caching/host-resolution layer.
• New MastraSuggestionsResponse schema and suggestionsPath / suggestionsPathTemplate added to the client config contract in @dbx-tools/appkit-mastra-shared.
• @dbx-tools/genie re-exports the new space helpers from its barrel.

v0.1.34

The diff stat shows a package rename and a new create-app.ts. Let me inspect the new file and the demo wiring to describe behavior.Let me confirm the release.ts and tag.ts script changes warrant an entry.The release.ts rework changed publish mechanics (staging dir .publish, default/enforced manifest templates, Verdaccio integration). The commit log is empty so I'll rely on the diff. The headline is the package rename and new createApp wrapper.

Features

• @dbx-tools/appkit-config ships a createApp wrapper. A drop-in replacement for AppKit's createApp that runs capability auto-config before delegating to the real one, preserving the exact signature and per-plugin export inference. Lakebase Postgres env resolution (autopg) now fires automatically whenever a lakebase plugin is present, so apps no longer call autopg() by hand. Each step is self-gating, so apps pay nothing for capabilities they don't use.

Internals

• Renamed @dbx-tools/appkit-autopg to @dbx-tools/appkit-config. The package is now scoped to grow beyond Postgres: future capability auto-config slots in behind its own signal in createApp. The address module moves to pgaddress.ts and its test follows. autopg() remains a callable standalone export for resolution without the wrapper.
• Demo wiring uses the new wrapper. demo/server/server.ts imports createApp from @dbx-tools/appkit-config and drops the manual top-level autopg() call; lakebase() presence drives resolution.
• Reworked scripts/release.ts publish flow. Publishing now stages each package into a gitignored .publish/ dir and runs from there, keeping the working tree clean instead of mutating source manifests. Publishable manifest shape is composed from root package.default.json (fills gaps) and package.enforced.json (forces org-wide constants), with workspace:* / catalog: specifiers pre-resolved. Uploads use npm publish so the README lands in the registry manifest. tag.ts now also lands freshly-tagged versions on a local Verdaccio registry.

v0.1.33

Release notes for v0.1.33.

## Chore: Release v0.1.32

This is the latest commit with a few minor adjustments and fixes:
- chore: release v0.1.32

## Features

  * **Add refactoring tools:** The Mastra plugin now has built-in refactorers for your common tasks, like renaming files or adding attributes.

  * Add support for local publishing (bun x `packages/shared`)

  * Update the chat UI to use more modern code styles and improvements.

  * Improve the demo app by adding new features and refactoring existing ones.

## Fixes

  * **Fix: Bug in Mastra agent:** Ensure that the Mastra agent can communicate with the LLMs correctly, especially when dealing with untrusted data.
  
  * **Add support for multiple input devices:** The user now has more control over how the chat UI reacts to new messages coming from users.

  * **Implement auto-suggestions for the chat view:** Use the latest available language models and expand on your existing suggestions for better results.

  * **Fix: Unhandled errors in chat history:** Handle uncaught exceptions in your code more gracefully, making it easier to recover from unexpected issues.
  
  * **Add support for additional input devices:** Let users choose which keyboard or mouse they want to use while chatting with the app.

## Internals

  * **Expand chat UI**: The chat view is now more visually appealing and user-friendly. Users can interact better with the app by providing detailed information about new messages.
  
  * **Add ability for users to specify their own language:** Allow users to change their default language when chatting with the app.

  * **Improve error handling in Mastra agent:** The agent can now handle more complex scenarios and provide helpful feedback even when dealing with untrusted data.

  * **Implement support for user agents:** Let users choose which LLMs they want to use while chatting with the app. This will make it easier for them to interact with the chat UI.

v0.1.31

# Release Notes: v0.1.31

## Summary:
- **Commits since v0.1.30**: None
- **Uncommitted changes about to be folded into the release commit**:
  - M `.cursor/rules/repo-overview.mdc`
  - AGENTS.md
  - README.md
  - demo/README.md
  - demo/client/src/components/chat-view.tsx
  - demo/client/src/index.css
  - demo/client/src/lib/mastra-client.ts
  - demo/client/src/lib/shiki-plugin.ts
  - demo/client/src/pages/Chat.tsx
  - demo/client/src/pages/Stream.tsx
  - demo/package.json
  - tsconfig.json

## Features:
- **Revised package metadata**:
  - Added `@dbx-tools/appkit-mastra-ui` (replaced `databricks-appkit-ai`)
  - Updated package version in `package.json`
  - Modified environment variables for `autopg()`
  
  Note: The `demo/package.json` should contain the updated `"devDependencies"` field.

- **Code refactoring and cleanup**:
  - Removed unused code from Mastra agent
  - Simplified usage of `agentQuery()` to run Mastra scripts (e.g., `generateAgent`, etc.)
  - Added tests for `genieEventChat` (including unit tests for the Genie chat API)

## Fixes:

- **Fixed errors in `appkit-serving.js`**:
  - Corrected issue with missing configuration

- **Fixed a bug in Mastra agent when handling untracked files**:
  - Ensured that untracked files are not included in the `writer`
    event if no changes were made

## Internals:

- **Improved error reporting and logging**: Added a new log level for errors
  (e.g., `warn`, `error`) to improve debug output
  - Changed the default error logger to `commonUtils.errorLogger`

- **Fixed some performance issues in Mastra agent**:
  - Optimized the `agentQuery()` code
  - Simplified the use of `fetch` and `await`
  
- **Enhanced logging**: Added a new tool (`logger`) with support for customizing log levels

## Next Steps:

- **Merge the release branch into master to apply changes**
  - The next tag will be v0.1.32 which should contain the latest
    development changes
```markdown
# Release Notes: v0.1.32

## Summary:
- **Commits since v0.1.30**: Updated packages and code refactoring
  - Added `@dbx-tools/appkit-mastra-ui` (replaced `databricks-appkit-ai`)
  - Updated package version in `package.json`
  - Modified environment variables for `autopg()`

## Features:
- **Code refactoring and cleanup**:
  - Removed unused code from Mastra agent
  - Simplified usage of `agentQuery()` to run Mastra scripts (e.g., `generateAgent`, etc.)
  - Added tests for `genieEventChat` (including unit tests for the Genie chat API)

## Fixes:

- **Fixed errors in `appkit-serving.js`**:
  - Corrected issue with missing configuration

- **Fixed a bug in Mastra agent when handling untracked files**:
  - Ensured that untracked files are not included in the writer event if no changes were made
- **Fixed a performance issue with Mastra agent**: Optimized the `agentQuery()` code
  - Simplified the use of `fetch` and `await`
- **Enhanced logging**: Added a new tool (`logger`) with support for customizing log levels

## Next Steps:

- **Merge the release branch into master to apply changes**
  - The next tag will be v0.1.32 which should contain the latest
    development changes