sync-alphalib-2026-06-02

.ai/rules/general.mdc

@@ -7,7 +7,10 @@ General:
 
 - Do not touch `.env` files!
 - Favor Yarn (4) over npm
-- Never run any dev server yourself. I have one running that auto-reloads on changes.
+- Before starting a dev server, first check whether a suitable one is already running and use that
+  if possible. If none is available and local browser/e2e validation needs one, start the documented
+  dev server, capture its log path/pid, and stop it when you are done unless the user asked to keep
+  it running.
 - Avoid blocking the conversation with terminal commands. For example: A) most of my git commands run through pagers, so pipe their output to `cat` to avoid blocking the
   terminal. B) You can use `tail` for logs, but be smart and use `-n` instead of `-f`, or the conversation will block
 - Use the `gh` tool to interact with GitHub (search/view an Issue, create a PR).

.changeset/fresh-robots-sync.md

@@ -0,0 +1,9 @@
+---
+"@transloadit/node": patch
+"transloadit": patch
+"@transloadit/mcp-server": patch
+"@transloadit/types": patch
+"@transloadit/zod": patch
+---
+
+Refresh generated Transloadit Robot schemas and shared assembly types from alphalib, including `/document/extract`, FFmpeg v8 stack support, and the latest speech transcription provider defaults.

AGENTS.md

@@ -58,7 +58,10 @@ General:
 
 - Do not touch `.env` files!
 - Favor Yarn (4) over npm
-- Never run any dev server yourself. I have one running that auto-reloads on changes.
+- Before starting a dev server, first check whether a suitable one is already running and use that
+  if possible. If none is available and local browser/e2e validation needs one, start the documented
+  dev server, capture its log path/pid, and stop it when you are done unless the user asked to keep
+  it running.
 - Avoid blocking the conversation with terminal commands. For example: A) most of my git commands run through pagers, so pipe their output to `cat` to avoid blocking the
   terminal. B) You can use `tail` for logs, but be smart and use `-n` instead of `-f`, or the conversation will block
 - Use the `gh` tool to interact with GitHub (search/view an Issue, create a PR).

CLAUDE.md

@@ -58,7 +58,10 @@ General:
 
 - Do not touch `.env` files!
 - Favor Yarn (4) over npm
-- Never run any dev server yourself. I have one running that auto-reloads on changes.
+- Before starting a dev server, first check whether a suitable one is already running and use that
+  if possible. If none is available and local browser/e2e validation needs one, start the documented
+  dev server, capture its log path/pid, and stop it when you are done unless the user asked to keep
+  it running.
 - Avoid blocking the conversation with terminal commands. For example: A) most of my git commands run through pagers, so pipe their output to `cat` to avoid blocking the
   terminal. B) You can use `tail` for logs, but be smart and use `-n` instead of `-f`, or the conversation will block
 - Use the `gh` tool to interact with GitHub (search/view an Issue, create a PR).