sync-alphalib-2026-07-10

.ai/rules/coding-style.mdc

@@ -43,6 +43,8 @@ Coding style:
   serializer intentionally emits POSIX-style text.
 - Comments should explain why code exists or why an exception is needed, not narrate what the next
   line already says.
+- Use JSDoc block comments for exported constants, functions, classes, and types when documenting
+  their purpose or contract. Use regular line comments for local quirks, reasoning, or exceptions.
 - Do not put TODOs, internal implementation notes, or future-work placeholders in user-facing text
   or schema descriptions. Put those in code comments, issues, or docs for maintainers instead.
 - Put API keys and secrets in `.env` files, not hardcoded in components

.ai/rules/playwright.mdc

@@ -4,8 +4,13 @@ globs: _src/tests/**/*.pwtest.ts,playwright.config.ts
 alwaysApply: false
 ---
 - Prefer user-centric locators: `getByRole`/`getByText` with accessible names; avoid `page.locator('body')`, `innerText()`, or raw CSS unless there is no accessible alternative.
+- Treat `data-*` attributes as implementation details in browser tests unless they are the only
+  stable contract available. If UI needs testing via state such as notifications, prefer adding or
+  using an accessible role/name/state contract over asserting hidden implementation attributes.
 - Make positive assertions on expected UI/text instead of looping over regexes to assert absence.
 - Keep tests simple: no control-flow loops or extra variables for straightforward assertions.
+- For localized route work, cover page chrome as well as body content: navbar/mobile nav, search
+  labels, subnav, post metadata/bylines, dynamic cards, `html lang`, canonical, and hreflang.
 - Navigate with relative URLs (`page.goto('/path')`) by setting `baseURL` in `playwright.config.ts`; avoid stringing environment URLs in tests.
 - Stub or mock external/third‑party requests (Intercom, Sentry, etc.) and any auth/login endpoints to keep tests deterministic; return minimal valid JSON when the app expects data.
 - Each unexpected error should surface and fail the test.

.changeset/alphalib-july-sync.md

@@ -0,0 +1,10 @@
+---
+'@transloadit/mcp-server': patch
+'@transloadit/node': patch
+'@transloadit/types': patch
+'@transloadit/zod': patch
+'transloadit': patch
+---
+
+Update Robot schemas and Assembly status types with the latest supported parameters, formats,
+validation, and status fields.

AGENTS.md

@@ -40,6 +40,8 @@ Coding style:
   serializer intentionally emits POSIX-style text.
 - Comments should explain why code exists or why an exception is needed, not narrate what the next
   line already says.
+- Use JSDoc block comments for exported constants, functions, classes, and types when documenting
+  their purpose or contract. Use regular line comments for local quirks, reasoning, or exceptions.
 - Do not put TODOs, internal implementation notes, or future-work placeholders in user-facing text
   or schema descriptions. Put those in code comments, issues, or docs for maintainers instead.
 - Put API keys and secrets in `.env` files, not hardcoded in components
@@ -73,8 +75,13 @@ General:
 ## playwright
 
 - Prefer user-centric locators: `getByRole`/`getByText` with accessible names; avoid `page.locator('body')`, `innerText()`, or raw CSS unless there is no accessible alternative.
+- Treat `data-*` attributes as implementation details in browser tests unless they are the only
+  stable contract available. If UI needs testing via state such as notifications, prefer adding or
+  using an accessible role/name/state contract over asserting hidden implementation attributes.
 - Make positive assertions on expected UI/text instead of looping over regexes to assert absence.
 - Keep tests simple: no control-flow loops or extra variables for straightforward assertions.
+- For localized route work, cover page chrome as well as body content: navbar/mobile nav, search
+  labels, subnav, post metadata/bylines, dynamic cards, `html lang`, canonical, and hreflang.
 - Navigate with relative URLs (`page.goto('/path')`) by setting `baseURL` in `playwright.config.ts`; avoid stringing environment URLs in tests.
 - Stub or mock external/third‑party requests (Intercom, Sentry, etc.) and any auth/login endpoints to keep tests deterministic; return minimal valid JSON when the app expects data.
 - Each unexpected error should surface and fail the test.

CLAUDE.md

@@ -40,6 +40,8 @@ Coding style:
   serializer intentionally emits POSIX-style text.
 - Comments should explain why code exists or why an exception is needed, not narrate what the next
   line already says.
+- Use JSDoc block comments for exported constants, functions, classes, and types when documenting
+  their purpose or contract. Use regular line comments for local quirks, reasoning, or exceptions.
 - Do not put TODOs, internal implementation notes, or future-work placeholders in user-facing text
   or schema descriptions. Put those in code comments, issues, or docs for maintainers instead.
 - Put API keys and secrets in `.env` files, not hardcoded in components
@@ -73,8 +75,13 @@ General:
 ## playwright
 
 - Prefer user-centric locators: `getByRole`/`getByText` with accessible names; avoid `page.locator('body')`, `innerText()`, or raw CSS unless there is no accessible alternative.
+- Treat `data-*` attributes as implementation details in browser tests unless they are the only
+  stable contract available. If UI needs testing via state such as notifications, prefer adding or
+  using an accessible role/name/state contract over asserting hidden implementation attributes.
 - Make positive assertions on expected UI/text instead of looping over regexes to assert absence.
 - Keep tests simple: no control-flow loops or extra variables for straightforward assertions.
+- For localized route work, cover page chrome as well as body content: navbar/mobile nav, search
+  labels, subnav, post metadata/bylines, dynamic cards, `html lang`, canonical, and hreflang.
 - Navigate with relative URLs (`page.goto('/path')`) by setting `baseURL` in `playwright.config.ts`; avoid stringing environment URLs in tests.
 - Stub or mock external/third‑party requests (Intercom, Sentry, etc.) and any auth/login endpoints to keep tests deterministic; return minimal valid JSON when the app expects data.
 - Each unexpected error should surface and fail the test.