mastra 1.27.3-alpha.0 → 1.27.3-alpha.2

package/dist/docs/SKILL.md

@@ -3,7 +3,7 @@ name: mastra
 description: Documentation for mastra. Use when working with mastra APIs, configuration, or implementation.
 metadata:
   package: "mastra"
-  version: "1.27.3-alpha.0"
+  version: "1.27.3-alpha.2"
 ---
 
 ## When to use
@@ -16,13 +16,13 @@ Read the individual reference documents for detailed explanations and code examp
 
 ### Docs
 
-- [API Reference: Mastra platform](references/docs-mastra-platform-api.md) - API Reference for the Mastra platform REST API.
+- [API Reference: Mastra platform](references/docs-mastra-platform-api.md) - Use the Mastra platform REST API to manage members, tokens, Studio and Server deployments, gateways, observability feedback, and project-scoped resources.
 
 ### Reference
 
-- [Reference: CLI commands](references/reference-cli-mastra.md) - Documentation for the Mastra CLI to develop, build, and start your project.
-- [Migrate from Mastra Cloud](references/reference-migrations-mastra-cloud.md) - Learn how to migrate from Mastra Cloud to the Mastra platform
-- [CLI](references/reference-migrations-upgrade-to-v1-cli.md) - Learn how to migrate CLI changes when upgrading to v1.
+- [Reference: CLI commands](references/reference-cli-mastra.md) - You can use the Command-Line Interface (CLI) provided by Mastra to develop, build, and start your Mastra project.
+- [Migrate from Mastra Cloud](references/reference-migrations-mastra-cloud.md) - The Mastra platform replaces Mastra Cloud with separate Studio and Server products, CLI-driven deploys, and a new observability system.
+- [CLI](references/reference-migrations-upgrade-to-v1-cli.md) - The CLI has been simplified by removing deployment commands, configuration flags, and starter files. A new migration command has been added to help with database schema upgrades.
 
 
 Read [assets/SOURCE_MAP.json](assets/SOURCE_MAP.json) for source code references.

package/dist/docs/assets/SOURCE_MAP.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.27.3-alpha.0",
+  "version": "1.27.3-alpha.2",
   "package": "mastra",
   "exports": {},
   "modules": {}

package/dist/docs/references/reference-cli-mastra.md

@@ -353,7 +353,7 @@ The command runs `mastra build` and zips the output before uploading it to the s
 
 Organization, project, and environment are resolved in order from: environment variable (`MASTRA_ORG_ID`, `MASTRA_PROJECT_ID`), CLI flag (`--org`, `--project`, `--env`), `.mastra-project.json` config file, current org from credentials, and lastly interactive prompt. On first deploy, the CLI saves the resolved org and project IDs to `.mastra-project.json` so subsequent deploys skip the prompts.
 
-If the project doesn't exist yet, the CLI creates it from the `package.json` `name` field after confirmation. If the target environment doesn't exist, the CLI creates it (defaulting to `type: staging` for anything other than `production`) after confirmation. Combined with `--yes`, this creates and deploys everything in one non-interactive command:
+After confirmation, the CLI creates a missing project from the `package.json` `name` field and creates a missing target environment, defaulting to `type: staging` for anything other than `production`. Combined with `--yes`, this creates and deploys everything in one non-interactive command:
 
 ```bash
 mastra deploy --env staging --yes
@@ -717,7 +717,7 @@ Shows diagnosis results and suggested fixes for a failed Studio deploy.
 mastra studio deploy suggestions [deploy-id]
 ```
 
-If you omit `deploy-id`, the command uses the latest deploy for the linked project. If a diagnosis doesn't exist yet, the command starts one and polls until results are ready. Suggestions appear only when the diagnosis finds a problem.
+When you omit `deploy-id`, the command uses the latest deploy for the linked project and starts a diagnosis if needed, polling until the results are ready. Suggestions appear only when the diagnosis finds a problem.
 
 ### `mastra studio projects`
 
@@ -725,7 +725,7 @@ Lists all projects in the current organization.
 
 ### `mastra studio projects create`
 
-Creates a new project through an interactive prompt. This command doesn't accept a `--name` flag; for non-interactive project creation, use [`mastra studio deploy --project <name> --yes`](#mastra-studio-deploy) instead, which creates the project and deploys to it in one step.
+Creates a new project through an interactive prompt, but doesn't accept a `--name` flag. For non-interactive project creation, use [`mastra studio deploy --project <name> --yes`](#mastra-studio-deploy) instead. That command creates the project and deploys to it in one step.
 
 ## `mastra server deploy`
 
@@ -747,7 +747,7 @@ Shows diagnosis results and suggested fixes for a failed Server deploy.
 mastra server deploy suggestions [deploy-id]
 ```
 
-If you omit `deploy-id`, the command uses the latest deploy for the linked project. If a diagnosis doesn't exist yet, the command starts one and polls until results are ready. Suggestions appear only when the diagnosis finds a problem.
+When you omit `deploy-id`, the command uses the latest deploy for the linked project and starts a diagnosis if needed, polling until the results are ready. Suggestions appear only when the diagnosis finds a problem.
 
 ## `mastra server pause`
 

package/dist/docs/references/reference-migrations-mastra-cloud.md

@@ -60,7 +60,7 @@ The Mastra platform replaces Mastra Cloud with separate Studio and Server produc
 
 ## Replace Mastra Cloud Store with a hosted database
 
-Mastra Cloud provided a managed libSQL database, backed by [Turso](https://turso.tech). The Mastra platform doesn't host a database for you, so you need to point your storage at an externally hosted instance.
+Unlike Mastra Cloud, which provided a managed libSQL database backed by [Turso](https://turso.tech), the Mastra platform doesn't host a database for you. Point your storage at an externally hosted instance.
 
 If you were already using a hosted database ("bring your own"), keep the existing database configuration. Ensure the connection string is set as an environment variable in the dashboard rather than hardcoded.
 
@@ -80,7 +80,7 @@ Once the download completes, convert the dump into a SQLite database file:
 sqlite3 mydb.db < ~/Downloads/mastra-cloud-dump.sql
 ```
 
-You now have a portable `mydb.db` file you can inspect locally, back up, or use as the source for the new database in the steps that follow.
+You now have a portable `mydb.db` file that you can inspect locally or back up before using it as the source for the new database in the following steps.
 
 #### Option B: Export via the Turso CLI
 
@@ -88,16 +88,16 @@ If you prefer to work from the command line, or need to script the export, you c
 
 1. Retrieve your Cloud Store credentials from the dashboard.
 
-   Open your project in the [Mastra dashboard](https://projects.mastra.ai) and navigate to **Runtime → Settings → Env Variables**. For Cloud Store–backed projects, two variables are injected alongside your own:
+   Open your project in the [Mastra dashboard](https://projects.mastra.ai) and navigate to **Runtime → Settings → Env Variables**. For projects backed by Cloud Store, two variables are injected alongside your own:
 
    - `MASTRA_STORAGE_URL`: A libSQL connection string (e.g. `libsql://<db-name>-<org>.turso.io`).
    - `MASTRA_STORAGE_AUTH_TOKEN`: A read-capable auth token scoped to that database.
 
-   Each row supports the standard environment variable actions — show/hide via the eye toggle, Edit, Delete, and Copy Value. Use **Copy Value** to grab both values for the dump command below.
+   Each row supports the standard environment variable actions: show or hide via the eye toggle, Edit, Delete, and Copy Value. Use **Copy Value** to grab both values for the dump command below.
 
    > **Note:** These variables only appear for projects that were provisioned with Cloud Store. If you brought your own database to Mastra Cloud, you already have these credentials and can skip ahead to [Point your Mastra app at the new database](#point-your-mastra-app-at-the-new-database).
 
-   > **Note:** If the variables are missing, the values do not decrypt, or the Turso CLI rejects the token, email <support@mastra.ai> from the address associated with your Mastra Cloud account and ask for the libSQL URL and auth token for the project you want to export. Include the project name/ID. Support can also run the dump on your behalf if CLI access is blocked on your network.
+   > **Note:** If the variables are missing, the values don't decrypt, or the Turso CLI rejects the token, email <support@mastra.ai> from the address associated with your Mastra Cloud account and ask for the libSQL URL and auth token for the project you want to export. Include the project name/ID. Support can also run the dump on your behalf if CLI access is blocked on your network.
 
 2. Install the Turso CLI.
 
@@ -113,7 +113,7 @@ If you prefer to work from the command line, or need to script the export, you c
 
 3. Export the database to a SQL dump.
 
-   Set the credentials provided by support (or use the dashboard values if you already copied them earlier) as environment variables, then dump the database to a local file. If you copied the URL from the dashboard, swap the `libsql://` scheme for `https://` — the Turso CLI expects the HTTPS form when passing the URL with an auth token.
+   Set the credentials provided by support (or use the dashboard values if you already copied them earlier) as environment variables, then dump the database to a local file. If you copied the URL from the dashboard, swap the `libsql://` scheme for `https://` because the Turso CLI expects the HTTPS form when passing the URL with an auth token.
 
    ```bash
    export MASTRA_STORAGE_URL="https://<db-name>-<org>.turso.io"
@@ -122,7 +122,7 @@ If you prefer to work from the command line, or need to script the export, you c
    turso db shell "$MASTRA_STORAGE_URL?authToken=$MASTRA_STORAGE_AUTH_TOKEN" ".dump" > mastra-cloud-dump.sql
    ```
 
-   > **Warning:** Embedding the auth token in the connection string is less secure than Turso's recommended pattern — the full URL (with token) can end up in shell history, process listings, and terminal logs. Turso officially recommends running `turso auth login` and then dumping by database name only: `turso db shell <database-name> ".dump" > mastra-cloud-dump.sql`. That flow requires the database to live in a Turso account you own, which is not the case for Cloud Store, so the env-var example above is provided as an alternative for this one-time export. If you prefer to avoid token interpolation entirely, ask support to run the dump on your behalf and send you the resulting SQL file.
+   > **Warning:** Embedding the auth token in the connection string is less secure than Turso's recommended pattern because the full URL, including the token, can appear in command history and in process or terminal output. Turso recommends running `turso auth login` and dumping by database name only: `turso db shell <database-name> ".dump" > mastra-cloud-dump.sql`. That flow requires the database to belong to a Turso account you own, which isn't true for Cloud Store, so the environment-variable example above provides an alternative for this one-time export. To avoid token interpolation entirely, ask support to run the dump and send you the resulting SQL file.
 
    The resulting `mastra-cloud-dump.sql` contains the full schema and data: thread and message history, workflow snapshots, traces, and eval scores. Store it somewhere safe before continuing.
 
@@ -136,7 +136,7 @@ The dump is a standard SQL file and can be loaded into any libSQL-compatible dat
    turso auth login
    ```
 
-   If you do not have a Turso account, the CLI will prompt you to create one. See [Turso pricing](https://turso.tech/pricing) for plan details.
+   If you don't have a Turso account, the CLI will prompt you to create one. See [Turso pricing](https://turso.tech/pricing) for plan details.
 
 2. Create a new database and load the dump in one step.
 
@@ -144,7 +144,7 @@ The dump is a standard SQL file and can be loaded into any libSQL-compatible dat
    turso db create mastra-migrated --from-dump ./mastra-cloud-dump.sql
    ```
 
-   `--from-dump` restores a local SQLite/libSQL dump at create time, which is faster and safer than piping statements through `turso db shell` after the fact. Pick a region close to where your Mastra Server runs to minimize latency — list available regions with `turso db locations` and pass `--group <group-name>` if you manage multiple groups.
+   `--from-dump` restores a local SQLite/libSQL dump at create time, which is faster and safer than piping statements through `turso db shell` after the fact. Pick a region close to where your Mastra Server runs to minimize latency. List available regions with `turso db locations` and pass `--group <group-name>` if you manage multiple groups.
 
    For multi-gigabyte dumps, add `--wait` so the CLI blocks until the database is fully available.
 

package/dist/factory/assets/{engine-javascript-C3-9bBUN.js → engine-javascript--ixMstp8.js}

@@ -1 +1 @@
-import{J as t}from"./index-DbguJ_5R.js";import{c as p,d as i}from"./index-DbguJ_5R.js";function n(){const e={cache:new Map,regexConstructor:()=>{throw new Error("JavaScriptRawEngine: only support precompiled grammar")}};return{createScanner(r){return new t(r,e)},createString(r){return{content:r}}}}export{t as JavaScriptScanner,n as createJavaScriptRawEngine,p as createJavaScriptRegexEngine,i as defaultJavaScriptRegexConstructor};
+import{J as t}from"./index-Z8BEHJ8i.js";import{c as p,d as i}from"./index-Z8BEHJ8i.js";function n(){const e={cache:new Map,regexConstructor:()=>{throw new Error("JavaScriptRawEngine: only support precompiled grammar")}};return{createScanner(r){return new t(r,e)},createString(r){return{content:r}}}}export{t as JavaScriptScanner,n as createJavaScriptRawEngine,p as createJavaScriptRegexEngine,i as defaultJavaScriptRegexConstructor};