test(middleware): add testify suite for DecompressRequestMiddleware

.agents/skills/i18n-translate/SKILL.md

@@ -3,34 +3,77 @@ name: i18n-translate
 description: >-
   Complete and maintain frontend i18n translations for this project. Covers
   finding missing translation keys, detecting untranslated entries, and adding
-  translations for all supported locales (en, zh, fr, ja, ru, vi). Use when the
-  user asks to add translations, fix i18n, complete missing translations, or
-  when new UI text needs to be internationalized.
+  translations for all supported locales (en, zh, zh-TW, fr, ja, ru, vi). Use for any
+  task involving frontend locale files, missing translation keys, untranslated
+  UI text, `t(...)` keys, `useTranslation()`, static i18n keys, button/label/
+  toast/dialog/placeholder/validation copy, or adding/fixing even a single
+  i18n key. Use when review findings mention missing i18n, when new UI text
+  needs translation, or when the user asks to add translations, fix i18n, or
+  complete missing translations. Always load and follow this skill before
+  translating, adding locale keys, or editing frontend i18n files.
 ---
 
 # Frontend i18n Translation Workflow
 
+## Mandatory Preflight
+
+- Read this entire `SKILL.md` before any frontend i18n work, including one-key fixes.
+- Before editing locale files, confirm the source text comes from a `t(...)` key, `en.json`, existing UI copy, or an explicitly requested new UI string.
+- Use the user conversation only to understand the task target. Do not copy conversation text, review wording, or task descriptions directly into locale values.
+- Before translating each key, re-think the intended UI copy from the code and locale context instead of treating the surrounding chat as the translation source.
+
+### Hard Constraint: Locale Writes Go Through the Script
+
+- You MUST NOT edit `web/src/i18n/locales/*.json` directly with text-editing tools (StrReplace, Write, search-and-replace, manual JSON edits, etc.). This applies even to a single key.
+- ALL locale writes MUST go through the `add-missing-keys.mjs` script, followed by `bun run i18n:sync`. The script is the only sanctioned way to add or change locale values.
+- Why this is mandatory, not optional:
+  - Hand-editing reliably drops one or more of the seven locales (`en`, `zh`, `zh-TW`, `fr`, `ja`, `ru`, `vi`), leaving keys missing in some languages.
+  - Hand-editing breaks the required alphabetical key order and introduces JSON syntax errors (trailing commas, mismatched quotes).
+  - The script writes all seven files atomically with consistent sorting, so the locale set stays in sync by construction.
+- The script does not do the translation for you. You still must reason out each locale's copy and populate the script's `newKeys` object; the script only handles insertion, sorting, and writing. Do not skip the script just because the thinking happens regardless.
+
+## Scope Checklist
+
+Before editing files, treat the task as covered by this skill if it involves:
+
+- `i18n`, translation, locale files, language packs, missing keys, or untranslated text
+- `t('...')`, `useTranslation()`, `static-keys.ts`, or `locales/*.json`
+- UI copy in buttons, labels, toasts, dialogs, placeholders, validation messages, descriptions, or table/empty states
+- A review finding about missing i18n keys
+
+Do not skip this workflow because the fix is "just one key".
+
 ## Overview
 
-- Locale files: `web/default/src/i18n/locales/{en,zh,fr,ja,ru,vi}.json`
+- Locale files: `web/src/i18n/locales/{en,zh,zh-TW,fr,ja,ru,vi}.json`
 - Format: flat JSON under `"translation"` key, keys are English source strings
 - Base locale: `en.json` (most keys), fallback: `zh` (Chinese)
-- Sync script: `bun run i18n:sync` (from `web/default/`)
+- Sync script: `bun run i18n:sync` (from `web/`)
 - All `t()` calls must have corresponding keys in every locale file
 
+## Small Fix Path
+
+For a single known missing key (still script-only, no direct JSON edits):
+
+1. Confirm the exact key at the call site and verify it is absent from all locale files.
+2. Add the key via `add-missing-keys.mjs`, populating its `newKeys` object for every supported locale: `en`, `zh`, `zh-TW`, `fr`, `ja`, `ru`, `vi`. Even one key goes through the script; do not hand-edit the JSON.
+3. The script preserves the flat `"translation"` object and keeps keys alphabetically sorted automatically.
+4. Run a targeted search for the key in code and locale files.
+5. Run `bun run i18n:sync` to normalize file order. This step is mandatory, not optional.
+
 ## Workflow
 
 ### Step 1: Run sync and read report
 
 ```bash
-cd web/default && bun run i18n:sync
+cd web && bun run i18n:sync
 ```
 
-Read `web/default/src/i18n/locales/_reports/_sync-report.json` to see per-locale status (missingCount, extrasCount, untranslatedCount).
+Read `web/src/i18n/locales/_reports/_sync-report.json` to see per-locale status (missingCount, extrasCount, untranslatedCount).
 
 ### Step 2: Find missing keys (used in code but not in locale files)
 
-Create and run `web/default/scripts/find-missing-keys.mjs`:
+Create and run `web/scripts/find-missing-keys.mjs`:
 
 ```javascript
 import fs from 'node:fs/promises'
@@ -93,7 +136,7 @@ if (missingKeys.size === 0) {
 
 ### Step 3: Find untranslated entries (value equals English)
 
-Create and run `web/default/scripts/find-untranslated.mjs`:
+Create and run `web/scripts/find-untranslated.mjs`:
 
 ```javascript
 import fs from 'node:fs/promises'
@@ -124,7 +167,7 @@ const brandNames = new Set([
   'WeChat','Xinference','Xunfei','AI Proxy','One API',
 ])
 
-const locales = ['fr', 'ja', 'ru', 'zh', 'vi']
+const locales = ['fr', 'ja', 'ru', 'zh', 'zh-TW', 'vi']
 
 for (const locale of locales) {
   const locFile = JSON.parse(await fs.readFile(path.join(LOCALES_DIR, `${locale}.json`), 'utf8'))
@@ -153,7 +196,7 @@ for (const locale of locales) {
 
 ### Step 4: Add translations
 
-Create `web/default/scripts/add-missing-keys.mjs` with this structure:
+This script is the ONLY sanctioned way to write locale values. You MUST NOT bypass it by hand-filling the JSON files. Create `web/scripts/add-missing-keys.mjs` with this exact structure:
 
 ```javascript
 import fs from 'node:fs/promises'
@@ -168,6 +211,7 @@ function stableStringify(obj) {
 const newKeys = {
   en: { /* "key": "English value" */ },
   zh: { /* "key": "中文翻译" */ },
+  'zh-TW': { /* "key": "繁體中文翻譯" */ },
   fr: { /* "key": "Traduction française" */ },
   ja: { /* "key": "日本語翻訳" */ },
   ru: { /* "key": "Русский перевод" */ },
@@ -214,7 +258,7 @@ Populate the `newKeys` object with actual translations for each locale.
 ### Step 5: Verify and clean up
 
 ```bash
-cd web/default
+cd web
 node scripts/add-missing-keys.mjs   # apply translations
 node scripts/find-missing-keys.mjs  # verify: should say "All t() keys found"
 bun run i18n:sync                   # normalize file order
@@ -224,10 +268,25 @@ Delete temporary scripts after completion.
 
 ## Translation Guidelines
 
+### Source Text Rules
+
+- Reconsider every key's UI meaning before translating: component location, user action, placeholder variables, button/label/toast/dialog/validation context, and whether the copy is a noun, command, status, or full sentence.
+- Prefer the English key or `en` value as the source text. Use the call site only to clarify meaning, tone, and constraints.
+- Do not copy chat messages, review comments, issue descriptions, or task wording as translation text.
+- If the source text is unclear, inspect the code and locale files first. Ask the user for exact source copy only when the intended UI text remains ambiguous.
+
+### Length and Layout Awareness
+
+- Consider whether translated text may overflow the UI before choosing final wording, especially for buttons, table headers, menu items, labels, toasts, dialog titles, tabs, badges, and empty states.
+- For languages that often expand relative to English, especially French, Russian, and Vietnamese, prefer natural but compact wording.
+- Do not sacrifice meaning just to shorten text. When the call site has limited space, choose the shortest clear translation that preserves the UI intent.
+- For interpolated variables, counts, model names, provider names, quotas, and dates, consider the longest realistic rendered text, not only the translation string itself.
+
 | Language | Code | Notes |
 |----------|------|-------|
 | English | en | Base locale, key = value |
 | Chinese | zh | Fallback locale, must be complete |
+| Traditional Chinese | zh-TW | Use natural Traditional Chinese wording |
 | French | fr | Many English cognates are valid (e.g., "Configuration") |
 | Japanese | ja | Use katakana for technical loanwords |
 | Russian | ru | Use formal register |
@@ -246,9 +305,10 @@ Delete temporary scripts after completion.
 
 ## Key Rules
 
-1. All scripts run from `web/default/` directory
+1. All scripts run from `web/` directory
 2. Use `node scripts/xxx.mjs` (ESM format with top-level await)
 3. Sort keys alphabetically when writing locale files
 4. Always run `bun run i18n:sync` as the final step
 5. Delete temporary scripts after completion
 6. The `{{variable}}` placeholders in keys must be preserved in all translations
+7. NEVER edit `locales/*.json` directly. Any non-script write to a locale file (StrReplace, Write, manual JSON edit) is non-compliant, including single-key fixes.

.agents/skills/shadcn-ui/SKILL.md

@@ -3,7 +3,7 @@ name: shadcn-ui
 description: >-
   Give the assistant project-aware shadcn/ui context: components.json,
   composition patterns, CLI, registries, theming, and MCP. Use when working on
-  web/default UI, shadcn components, or presets. Overview aligns with
+  web UI, shadcn components, or presets. Overview aligns with
   https://ui.shadcn.com/docs/skills.md; full upstream skill text is vendored
   under vendor/shadcn/.
 ---
@@ -37,7 +37,7 @@ npx skills add shadcn/ui
 That installs the skill where the `skills` CLI is available. **This repository** keeps the same intent under `.agents/skills/shadcn-ui/` (overview here + **vendored** upstream docs in [`vendor/shadcn/`](./vendor/shadcn/)) and runs the shadcn CLI from the frontend app root:
 
 ```bash
-cd web/default && bunx shadcn@latest info --json
+cd web && bunx shadcn@latest info --json
 ```
 
 Learn more about skills at [skills.sh](https://skills.sh).
@@ -48,7 +48,7 @@ Learn more about skills at [skills.sh](https://skills.sh).
 
 ### Project context
 
-Run **`shadcn info --json`** (here: `cd web/default && bunx shadcn@latest info --json`) for framework, Tailwind version, aliases, base (`radix` | `base`), icon library, installed components, and resolved paths.
+Run **`shadcn info --json`** (here: `cd web && bunx shadcn@latest info --json`) for framework, Tailwind version, aliases, base (`radix` | `base`), icon library, installed components, and resolved paths.
 
 ### CLI commands
 
@@ -70,10 +70,10 @@ Vendored: [`vendor/shadcn/mcp.md`](./vendor/shadcn/mcp.md). Live docs: [MCP Serv
 
 ## How it works
 
-1. **Project detection** — Applies when `components.json` exists (here: `web/default/components.json`).
+1. **Project detection** — Applies when `components.json` exists (here: `web/components.json`).
 2. **Context injection** — Use `shadcn info --json` as ground truth for imports and APIs.
-3. **Pattern enforcement** — Follow rules in [`vendor/shadcn/SKILL.md`](./vendor/shadcn/SKILL.md) and [`vendor/shadcn/rules/`](./vendor/shadcn/rules/).
-4. **Component discovery** — `shadcn docs`, `shadcn search`, MCP, or registries — see vendored SKILL + MCP doc.
+3. **Pattern enforcement** — Use [`vendor/shadcn/rules/`](./vendor/shadcn/rules/) for concrete markup checks; the complete official workflow reference is listed below for deeper CLI, registry, and preset questions.
+4. **Component discovery** — `shadcn docs`, `shadcn search`, MCP, or registries — see the official workflow reference and MCP doc when deeper context is needed.
 
 ---
 
@@ -88,11 +88,11 @@ Vendored: [`vendor/shadcn/mcp.md`](./vendor/shadcn/mcp.md). Live docs: [MCP Serv
 
 ## Vendored upstream bundle (deep rules)
 
-Snapshot from [shadcn-ui/ui `skills/shadcn`](https://github.com/shadcn-ui/ui/tree/main/skills/shadcn); revision note in [`vendor/shadcn/UPSTREAM.txt`](./vendor/shadcn/UPSTREAM.txt).
+Snapshot from [shadcn-ui/ui `skills/shadcn`](https://github.com/shadcn-ui/ui/tree/main/skills/shadcn); revision note in [`vendor/shadcn/UPSTREAM.txt`](./vendor/shadcn/UPSTREAM.txt). The upstream workflow is stored as a reference file, with its original skill frontmatter removed, so the vendored copy is not discovered as a second local skill.
 
 | Doc | Path |
 | --- | --- |
-| Full official skill body | [`vendor/shadcn/SKILL.md`](./vendor/shadcn/SKILL.md) |
+| Official shadcn/ui workflow reference | [`vendor/shadcn/official-shadcn-ui-workflow.md`](./vendor/shadcn/official-shadcn-ui-workflow.md) |
 | CLI reference | [`vendor/shadcn/cli.md`](./vendor/shadcn/cli.md) |
 | Theming / customization | [`vendor/shadcn/customization.md`](./vendor/shadcn/customization.md) |
 | MCP | [`vendor/shadcn/mcp.md`](./vendor/shadcn/mcp.md) |
@@ -102,4 +102,4 @@ Snapshot from [shadcn-ui/ui `skills/shadcn`](https://github.com/shadcn-ui/ui/tre
 | Styling | [`vendor/shadcn/rules/styling.md`](./vendor/shadcn/rules/styling.md) |
 | Base vs Radix | [`vendor/shadcn/rules/base-vs-radix.md`](./vendor/shadcn/rules/base-vs-radix.md) |
 
-**Workflow:** Prefer this **root** `SKILL.md` for repo paths (`web/default`, Bun). Read **`vendor/shadcn/SKILL.md`** for the complete upstream workflow, patterns, and CLI quick reference. Use **`vendor/shadcn/rules/*.md`** when validating concrete markup.
+**Workflow:** Prefer this **root** `SKILL.md` for repo paths (`web`, Bun). Read **`vendor/shadcn/official-shadcn-ui-workflow.md`** only when you need the complete official component, registry, or preset workflow. Use **`vendor/shadcn/rules/*.md`** when validating concrete markup.