# Changelog All notable changes to YTDescGen ship as tagged releases on `main`. ## v1.6.0 — 2026-11-17 The last feature release: **DLSS 5 Neural Rendering** and more frame-generation modes in Video settings, a **Custom** LUT that prints just "LUT applied", and **JetBrains Qodana** next to SonarCloud. From this version on YTDescGen is in **maintenance mode**: it stays maintained, but takes no new features. Web, desktop and Android all ship as 1.6.0. ### Added - **DLSS 5 Neural Rendering** — a switch in **Video settings** for NVIDIA (RTX 50 series), printed after the DLSS mode: `In-game Setting: Ultra - NVIDIA DLSS Quality + NVIDIA DLSS 5 Neural Rendering + NVIDIA Dynamic Multi Frame Generation`. Picking another vendor turns it off. - **More frame generation** — NVIDIA's **x6** and **Dynamic** Multi Frame Generation (DLSS 4.5), and **Custom…** for every vendor: type what you used (_NVIDIA Smooth Motion_, _Lossless Scaling x3_) and the description prints it as typed. - **Custom LUT** — "Custom" is the LUT field's first suggestion (typing it works too, in any case). **My Rig** then reads just _LUT applied_ — _Có áp dụng LUT_ in Vietnamese, and so on in every output language — without naming your own LUT. - **Option request** and **Translation or wording fix** issue forms. ### Changed - **Maintenance mode.** YTDescGen is feature-complete. Dependency and security updates, major language / runtime / framework upgrades, bug, UI/UX, accessibility and translation fixes, options added to or removed from its lists when people really need them, and Cloudflare or website fixes still land; new features don't. See README → Project status and CONTRIBUTING → Maintenance mode; the README carries a status badge. - The **Feature request** form is gone — ideas go to Discussions → Ideas. A workflow closes feature issues and `feat:` pull requests from outside contributors with an explanation in English and Vietnamese (option requests, accessibility and translation pull requests stay open), and anything the maintainer labels `out-of-scope`. - Bug and accessibility reports carry the `needs-triage` label; the `triage` label they named never existed. ### Under the hood - **Qodana** (JetBrains, Ultimate licence): Qodana for JS in native mode and Qodana for Rust (Early Access, Docker) run on every push and pull request, each with a quality gate of zero problems, reported to Qodana Cloud. Dependabot and fork pull requests, which get no token, skip it; the token never shares a step with `npm ci`. The first run's findings (74 in TypeScript, 12 in Rust) were fixed — React 19.3's deprecated `FormEvent` in the three save forms (now `SubmitEvent`), `[^\s]` written as `\S` in the 18 store and playtest URL patterns, the theme start-up script's globals, two copies of the sorted-JSON helper made one (`stableJson`), Vitest reusing Vite's alias map, `show_main_window` for the desktop's three copies of the same block — or excluded in `qodana.yaml` with the reason written next to each. - **Editor store v22** back-fills `frameGenCustom` and `dlssNeuralRendering`; backups and templates from older versions restore unchanged. - **Dependencies**, the newest releases at least a week old: react-i18next 17.1.13, lucide-react 1.70, zustand 5.1.0, simple-icons 16.37, vite 8.3.7 (rolldown 1.2.18), @vitejs/plugin-react 6.3.0, tailwindcss 4.3.5, typescript-eslint 8.72.2, knip 6.44.2, marked 18.2.0, wrangler 4.159.0. Workflows: sonarqube-scan-action 8.4.1, action-semantic-pull-request 6.1.2, setup-java 6.2.0. Rust: async-executor 1.14.0 → 1.14.1 (1.14.0 was yanked). THIRD_PARTY_NOTICES regenerated. - **Node.js 26.13.1**, the 2026-11-11 security release (16 CVEs, 7 rated high, in HTTP/2 and TLS servers): `.node-version` names the 26 line, so CI picks it up; the app runs no Node server, so nothing else changes. - Held back, still inside the 7-day cooldown: eslint 10.15 / typescript-eslint 8.73 — they move to minimatch 11, which closes the medium, development-only alert #50 — and Tauri 2.12.6. - **Docs**: README, CONTRIBUTING, SECURITY, MAINTAINERS, ROADMAP, FEATURES (upscaler and frame generation, LUT Custom), TECH-SPEC (Qodana, store v22, the rig block), DEVELOPMENT (+ Vietnamese), CONTENT-INVENTORY (+ Vietnamese), CLAUDE.md, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **1158 tests** (was 1131), build, cf:check and `cargo fmt` / `clippy` / `test` / `deny` all pass; Qodana reports no problems in either project and SonarCloud none on new code; initial load 279.6 of 280 KB gzip. Verified live: `wrangler dev` on 4.159.0 serves the gate page, `/legal/accessibility` and `robots.txt` and refuses a verify without a token; in the dev server a draft survives a reload on zustand 5.1, a v21 draft migrates to v22, NVIDIA offers x6 / Dynamic / Custom… and the DLSS 5 switch (the Output page prints the line above), switching to AMD turns DLSS 5 off and keeps a Custom frame generation, and a Custom LUT prints "LUT applied" in English and "Có áp dụng LUT" in Vietnamese. - Six manifests bumped 1.5.2 → 1.6.0. ## v1.5.2 — 2026-11-10 A maintenance release: the desktop and Android apps move to **Tauri 2.12.5**, with the fixes its window, webview and single-instance layers collected since 2.12.4, and this week's dependency updates are folded in. What the app generates does not change. Web, desktop and Android all ship as 1.5.2. ### Fixed - **Windows: starting the app a second time.** A second copy started while the first was still starting up could miss the first one's window and stay open instead of handing over and exiting (tauri-plugin-single-instance 2.5.5). A hidden window — the app sitting in the tray — no longer flashes when it leaves the maximized state (tao 0.37.2). - **macOS: dragging onto the window.** No abort when a drag enters or is dropped on the window, and no panic while the dragged file paths are collected (tao 0.37.2, wry 0.57.1). - **Android:** the webview runs Tauri's start-up scripts once per page instead of twice (wry 0.57.1). - **Windows installer:** the NSIS installer blocks a downgrade over a newer MSI installation in silent, passive and update modes too (Tauri 2.12.5). ### Under the hood - **Tauri 2.12.4 → 2.12.5**: tauri-build, tauri-macros and tauri-codegen 2.7.4, tauri-runtime-wry 2.12.3, wry 0.57.1, tao 0.37.2, tauri-plugin-dialog 2.8.4 (rfd 0.17), tauri-plugin-single-instance 2.5.5. - **Dependencies**, the newest releases at least a week old (the same cooldown Dependabot uses): i18next 26.6.0, react-i18next 17.1.11, i18next-resources-to-backend 1.2.4, lucide-react 1.66, react-router-dom 7.18.5, simple-icons 16.36, vite 8.3.5 (rolldown 1.2.16), @vitejs/plugin-react 6.2.1, tailwindcss 4.3.4, postcss 8.5.32, autoprefixer 10.6.2, marked 18.1.3, eslint 10.14, typescript-eslint 8.72.1, knip 6.44.1, @types/node 26.6.6, wrangler 4.156.2. Workflows: sonarqube-scan-action 8.4.0, zizmor-action 0.8.1. THIRD_PARTY_NOTICES regenerated. - **i18next stays on 26.6.x** (`~26.6.0` and a Dependabot ignore for 26.7.x). 26.7, the last 26.x minor, adds the debug-mode warnings that prepare the move to v27: about 1.9 KB gzip in the i18n chunk, which would take the initial load from 279.0 to 280.9 KB — over the 280 KB budget — for code the app never runs. Both go with the i18next 27 migration. - **The `undici` override from v1.3.1 is gone**: miniflare 5.20261102.0-beta (under wrangler, development only) depends on undici 7.30.1 itself, so alert #49 stays fixed without it. - **Docs**: TECH-SPEC's `package.json` listing follows the real file again (its dependency versions were several releases old) and notes the i18next hold; ROADMAP, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **1131 tests**, build, cf:check and `cargo fmt` / `clippy` / `test` / `deny` all pass; initial load 279.0 of 280 KB gzip. Verified live: `wrangler dev` on 4.156.2 serves the gate page, `/legal/accessibility` and `robots.txt`, and refuses a verify without a token; the desktop app (`tauri dev` with a separate test identifier) answers its commands, writes, lists, reads and deletes a backup, and opens and cancels the native Save and Open dialogs on the new dialog plugin. - Six manifests bumped 1.5.1 → 1.5.2. ## v1.5.1 — 2026-11-09 An **accessibility** release. YTDescGen already worked with the keyboard alone and with Narrator; this release adds an accessibility statement and fixes what an audit against WCAG 2.2 AA turned up — colour contrast, the language of generated text, page changes a screen reader didn't hear, a single-key shortcut that couldn't be turned off, and zoom in the desktop app. Web, desktop and Android all ship as 1.5.1. ### Added - **[ACCESSIBILITY.md](ACCESSIBILITY.md)** — what works with a keyboard, screen readers, zoom, reduced motion and touch, how it is checked, the supported environments, known limitations, how to report a barrier (severity levels, a reply within 7 days, Critical fixes in the next patch) and a checklist for contributors. Also in Vietnamese, in the app's **Legal Center**, at `ytgenerator.stream/legal/accessibility`, and linked from the website's check page in all eight languages. - **Accessibility barrier** issue form on GitHub (assistive technology, severity, platform), an _Accessibility_ option in feature requests, and an accessibility checklist in the pull request template. - **Settings › Editor › Single-key shortcuts** — on by default; turning it off stops the bare `?` from opening the shortcut list (for speech input and stray key presses), and Ctrl/⌘ + / still opens it. Travels with backups. - **Zoom in the desktop app** — Ctrl/⌘ + = and Ctrl/⌘ + − (and Ctrl + mouse wheel on Windows). - **The page's name is read out** after you open another page; the focus stays on the link you used. - **Alt + T** (go to the notifications) in the shortcut list. ### Changed - **Colours reach WCAG AA (4.5:1) for text** in both themes: secondary "muted" text (hints, placeholders, counters) is lighter in the dark theme and darker in the light theme; the dark theme's accent is a little lighter; filled buttons with white text use a deeper purple and red; the light theme's success, warning, danger and donate colours are darker. A test now checks every colour token against every background. - Generated titles, descriptions, tags, captions and playlist text are marked with the **language they were written in**, so a screen reader reads Japanese output with a Japanese voice while the interface is in English or Vietnamese — on Output, the On YouTube and Quick previews, History, Batch, Social and Playlist. - The Legal Center's intro mentions accessibility. ### Fixed - The notifications area and its close button were announced in English ("Notifications alt+T", "Close toast") whatever the interface language. - The Endings table's number and name fields and the per-video From / To fields had no accessible name, and the From / To column headers were always English; the bank name typed under _Other_ had only a placeholder. - In Windows High Contrast, text fields showed no focus outline. - The genre chips' remove button was 20 px (now 24 px); dialog close and banner dismiss buttons grow on touch screens. - `SECURITY.md` still listed 1.3.x as the supported version. ### Under the hood - New tokens `accent-solid`, `accent-solid-hover`, `danger-solid`, `danger-solid-hover`; `tests/styles/contrast.test.ts` reads both palettes from `globals.css` (text tokens on surface-0 to 2, muted also on surface-3, accent on its own tint, white on the solid fills, 3:1 for marks on `accent`). It found the light theme's donate colour at 4.26:1 on the first run. - `RouteAnnouncer` listens for `ytdescgen:page-title`, which `useDocumentTitle` fires in a microtask after the commit's effects, so pages rendered in the same commit and lazy pages are both heard and a language switch stays silent. - `singleKeyShortcuts` is an additive setting, healed (anything but a boolean → `true`) without a store version bump, like `hideScrollbars`. - Text controls use Tailwind's `outline-hidden` instead of `outline-none`. `zoomHotkeysEnabled` on the main window, plus `core:webview:allow-set-webview-zoom` for Tauri's macOS / Linux zoom polyfill. - Legal Center doc `accessibility` (`consent: false`, English + Vietnamese); `GateStrings.accessibility` in the Worker; the `accessibility` label on GitHub. New keys in all eight locales and `_schema.json`. - **Docs**: ACCESSIBILITY.md (+ Vietnamese), README, CONTRIBUTING, DEVELOPMENT (+ Vietnamese), FEATURES (accessibility section, shortcuts, settings), ARCHITECTURE, TECH-SPEC, PACKAGING, ROADMAP, CLAUDE.md, SECURITY, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **1131 tests** (was 1093), build, cf:check and `cargo fmt` / `clippy` / `test` all pass; initial load 279.0 of 280 KB gzip. Verified in the dev server: Settings → Output announces "Settings", then "Output", without moving the focus, and switching to Vietnamese doesn't announce; the notifications region reads "Thông báo (Alt+T)" in Vietnamese; Japanese output under a Vietnamese interface carries `lang="ja"`; with the switch off `?` does nothing and leaves the list while Ctrl + / still opens it; `/legal/accessibility` in both languages with every in-page link resolving. In the desktop app (`tauri dev`, WebView2): Ctrl + = zooms to 110 %, Ctrl + − back to 100 %. - Six manifests bumped 1.5.0 → 1.5.1. ## v1.5.0 — 2026-11-08 A feature release for videos **upscaled in the editor**: recorded at 1440p, exported at 4K — the title says `[4K Upscaled]`, the description says what was upscaled to what and warns that fine detail may look different from the original image. Web, desktop and Android all ship as 1.5.0. ### Added - **Upscaled from** (Video settings), next to Resolution — the resolution the footage was recorded at, when the video editor upscaled it to the video's resolution. Only lower resolutions are offered (none at 720p); lowering the resolution to or below the source sets it back to _Not upscaled_. Like resolution and FPS, it is saved with the channel profile. With it set: - **Title** — the quality badge reads `[4K Upscaled]`, `[2K Upscaled]` (1440p), `[4K Upscaled 120FPS]`, the word in the output language (`Upscale` in Vietnamese, Portuguese and Indonesian, `アップスケール`, `업스케일`, `超分`, `Reescalado`). Badge position, case and _Show quality badge_ work as before; 1080p 60fps still has no badge, upscaled or not. - **🖥 VIDEO SETTINGS** — a line right under the resolution, the editor taken from My Rig (left out when My Rig has none): ``` Video: 4K - 60 FPS Upscale: 1440p → 4K (DaVinci Resolve Studio 21.2) ``` It stays when _This game has no in-game graphics settings_ is on, like the video-style line. - **▸ 🛠 TECH NOTES** — a note of its own, after the ones you picked and bilingual like them: _Upscaled to a higher resolution in editing — fine detail is reconstructed, so text, textures and edges may look slightly different from the original image._ It isn't in the checklist, so it can't be forgotten, and it goes away with the upscale. The DLSS / FSR / XeSS note is unchanged. - The collapsed Video settings section reads `1440p → 4K · 60 FPS`. ### Under the hood - `src/engine/upscale.ts`: `validUpscaleSource` is the one rule the title, the description and the form share — anything other than a known resolution below the video's is ignored. `VIDEO_RESOLUTIONS`, `UPSCALED_FROM_OPTIONS` and `isUpscaledFrom` live in `src/config/graphics-settings.ts`. - `AUTO_TECH_NOTES` (`editor_upscaled`) holds the engine's own notes: never stored in `techNotes`, their bullets share `description.techNotes.items`; the tech-note parity test checks the checklist and the bullets separately. - Editor store v20 → v21: `upscaledFrom` back-fills to `""` and an unknown value becomes `""`; an applied profile or template and a restored backup read one the same way. `Profile.upscaledFrom` is optional, so the profile store stays at v3. New keys in all eight locales and `_schema.json`. - **Docs**: FEATURES (upscaled video, the badge setting, the profile row), CONTENT-INVENTORY (+ Vietnamese: the automatic note), ARCHITECTURE and TECH-SPEC (`upscale.ts`, the field, store v21, test count), ROADMAP, CLAUDE.md, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **1093 tests** (was 1065), build all pass; initial load 277.8 of 280 KB gzip. Verified in the dev server: Elden Ring at 4K upscaled from 1440p with DaVinci Resolve Studio 21.2 in My Rig gives `Elden Ring — [4K Upscaled] — Gameplay No Commentary`, the Upscale line under `Video: 4K - 60 FPS` and the note; Vietnamese output gives `[4K Upscale]` and the `EN · VI` note; 1080p sets the field back to _Not upscaled_, 720p disables it; hidden graphics settings keep the Upscale line; the four selects sit in one column at 375 px, 2 × 2 at 1024 px and in a row at 1440 px. - Six manifests bumped 1.4.0 → 1.5.0. ## v1.4.0 — 2026-11-06 A feature release for the description and the tags: a **LUT** field in My Rig, printed on its own line under the video editor, and the **boss's name as a tag** in boss videos — plus this week's dependency updates. Web, desktop and Android all ship as 1.4.0. ### Added - **LUT** (My Rig) — the LUT you grade with, on its own line right under the video editor, in the description and the social captions: ``` Video Editor: DaVinci Resolve Studio 21.2 LUT: Arri Alexa LogC to Rec709 ``` Typing offers 14 LUTs that come with DaVinci Resolve, named the way its LUT menu shows them (Arri Alexa LogC to Rec709, the Rec709 Kodak 2383 and Fujifilm 3513DI film looks, HDR 1000 nits to Gamma 2.4, …); any other name is printed as typed. A pasted file name or path — Explorer's _Copy as path_ included — is cut down to the LUT's name: `"C:\…\Arri\Arri Alexa LogC to Rec709.dat"` → `Arri Alexa LogC to Rec709`. Like the rest of the rig, it is saved with the channel profile. Left empty, there is no line. - **The boss's name as a tag** — Boss Fight and Boss No Hit videos get the Boss Name field as a tag of its own, right after the game's name, so fitting the tags to 500 characters never drops it. Marks that add nothing to a search are left out: "Gael, Slave Knight" → `Gael Slave Knight`, "Mr. X" → `Mr X`, "S.T.A.L.K.E.R." → `STALKER`, "「マレニア」" → `マレニア`; apostrophes and hyphens inside a word stay ("Mergo's Wet Nurse", "T-103"), and so does a dot between digits ("Phase 2.0"). Over 30 characters (YouTube's per-tag limit here), the name before its title is used: "Loretta, Knight of the Haligtree" → `Loretta`. A boss name left in the draft after switching to another video type is not tagged. ### Fixed - A **CPU name pasted from Windows** ("Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz") is tidied in the output too, not only once you leave the field — Ctrl/⌘+Shift+C or Ctrl/⌘+S pressed with the cursor still in it copied or saved the raw name. The new LUT field works the same way. ### Under the hood - **Dependencies**, the newest releases at least a week old (Dependabot's cooldown): i18next 26.5.11, react-i18next 17.1.9, lucide-react 1.64, zustand 5.0.16, knip 6.44, wrangler 4.152 (miniflare 5.20261019.2-beta), @tauri-apps/cli 2.12.4. Dependabot's five npm PRs (#223–#227) were folded into one change: each failed CI alone because it left THIRD_PARTY_NOTICES stale (regenerated), and they would have conflicted with each other. GitHub Actions: Swatinem/rust-cache 2.9.3, zizmor-action 0.8.0. The undici override stays — miniflare still pins undici 7.29.1. - Dependabot alert #50 (minimatch, development tools only, through eslint and typescript-eslint) stays open for now: its fix is minimatch 11, a new matching engine outside eslint's `^10` range, and the issue needs attacker-controlled glob patterns, which lint never reads. - `RigField` gains `clean` (CPU, LUT) and `wide`; `formatRigValue` runs a field's cleaner; a test now holds the `rig.*` and `description.rigLabels.*` keys of all eight locales to `RIG_FIELDS`. `bossNameTag` in `tag-generator.ts` uses linear regexes and no lookbehind (the macOS 11–13 desktop webview is older WebKit, which rejects one); its word fit is shared with `tagFriendlyGameName`. - **Docs**: FEATURES (11 rig fields, the LUT, the boss name tag), ARCHITECTURE (tag priority), TECH-SPEC (rig block, tag order, test count), ROADMAP, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **1065 tests** (was 1017), build, cf:check all pass; initial load 277.2 of 280 KB gzip. Verified in the dev server: the LUT field sits under Video Editor across both columns with its suggestions, a quoted Explorer path becomes the LUT's name when the field loses focus, and Quick Preview prints `LUT: Arri Alexa LogC to Rec709` right after `Video Editor: DaVinci Resolve Studio 21.2`; Boss Fight with "Gael, Slave Knight" puts `Gael Slave Knight` second in the tags, Full Gameplay drops it. `wrangler dev` on 4.152 serves the gate page. - Six manifests bumped 1.3.2 → 1.4.0. - **The macOS app is built on the `macos-15` runner.** GitHub retired the macOS 14 image on 2026-11-02, so the tag's first desktop run lost its macOS job ("The configuration 'macos-14-arm64-us-default' is not supported"); the Windows and Linux builds were unaffected. The macOS `.app.tar.gz` comes from a manual re-run of the desktop workflow for `v1.4.0`, which builds the tag's code. ## v1.3.2 — 2026-10-27 A hosting release: the website now **rate-limits** each visitor's address, so a script hammering ytgenerator.stream gets a cheap `429 Too Many Requests` instead of the gate, the app or a Turnstile check. Nothing a person does in normal use comes near the limits. The desktop and Android apps are unchanged apart from the version number. Web, desktop and Android all ship as 1.3.2. ### Added - **Rate limiting for the website**, in two layers: - **In the Worker** (Workers Rate Limiting bindings in `wrangler.jsonc`, checked before anything else): 120 requests a minute per address for everything the Worker serves — the gate page, the app shell, the legal pages, the gate's own endpoints — and 10 a minute for the gate's verification call, each of which costs a call to Cloudflare Turnstile. An IPv6 address counts by its /64, the block one connection usually holds. Over the limit: `429` with `Retry-After: 60`; the gate page shows its usual "try again" message. - **At the zone**: a WAF rate limiting rule (60 requests per 10 seconds per address, build output and verified search-engine bots left out) stops a fast burst at Cloudflare's edge, before the Worker runs. It is set in the Cloudflare dashboard; [HOSTING.md](docs/HOSTING.md#waf-rate-limiting-rule-one-time) has the steps. - Like the Turnstile gate, the Worker's limiter fails open: if it is missing or fails, the site stays reachable and the Worker logs it. ### Under the hood - `worker/rate-limit.ts` (client key, the check, the `429`), wired in first in `worker/router.ts`; a test keeps the `ratelimits` bindings and their period in step with the code. - **Docs**: HOSTING (both layers, the WAF rule step by step, changing a limit, burst checks against production), TECH-SPEC, ARCHITECTURE, CLAUDE.md, ROADMAP, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **1017 tests** (was 984), build, cf:check all pass; initial load 276.3 of 280 KB gzip. Verified live with `wrangler dev` (10 verification calls then `429`, 120 requests a minute then `429`, back to normal a minute later) and on ytgenerator.stream after the deploy: page loads at four a second, under the WAF rule, got 121 × `200` then the Worker's `429` with `Retry-After: 60`; verification calls got 11 × `403` (foreign origin) then `429`; a fast burst was stopped by the WAF rule (Cloudflare's `429`, error 1015) within about a second. - Six manifests bumped 1.3.1 → 1.3.2. ## v1.3.1 — 2026-10-26 A maintenance release: the desktop and Android apps move to **Tauri 2.12.4**, the desktop's Save and Open dialogs stop holding up the app's background work, and this week's dependency updates close the one open security alert. What the app generates does not change. Web, desktop and Android all ship as 1.3.1. ### Fixed - **Desktop: saving and opening files.** The native Save / Open dialogs (exporting and importing text files, backups to a file) and their file read or write now run on Tauri's blocking pool. Before, each one held one of the async runtime's worker threads for as long as the dialog stayed open. Same dialogs, same results. - **Tauri 2.12.0 → 2.12.4**, with upstream fixes that reach the app: no panic in the IPC and asset handlers on a request with an empty path; on Android, a plugin call that answers after its caller gave up no longer aborts the app; `Channel` messages keep arriving after a handler throws; a `once` event listener no longer panics when two events arrive together. Plugins: dialog 2.8.3, opener 2.7.2, single-instance 2.5.4, fs 2.7.1. - **Security (development tools only — nothing here ships in the app):** undici 7.30.1 — alert #49 (denial of service through too many content encodings), used by `wrangler dev` through miniflare. miniflare pins undici exactly, so Dependabot's security update could not land; an npm `overrides` entry lifts it, and `.github/dependabot.yml` says when to remove it. ### Under the hood - **SonarCloud runs in CI** instead of Automatic Analysis: the `sonarcloud` job reads the coverage report from `check`, counts tests as tests, and analyses the Rust code for the first time — which is how the dialog issue above was found. Quality gate green, 0 open issues. - **Dependencies**, the newest releases at least a week old (the same cooldown Dependabot uses): react 19.3.1, i18next 26.5.3, react-i18next 17.1.0, lucide-react 1.59, simple-icons 16.35, eslint 10.13, typescript-eslint 8.72, knip 6.42.1, postcss 8.5.31, @types/node 26.6.5, wrangler 4.151.2; tauri 2.12.4, tauri-build 2.7.3. THIRD_PARTY_NOTICES regenerated. - **Docs**: CLAUDE.md and PACKAGING (blocking work in an `async` Tauri command goes through `spawn_blocking`), DEVELOPMENT + Vietnamese, TECH-SPEC and CONTRIBUTING (the SonarCloud job and its coverage scope), ROADMAP, version references. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **984 tests**, build, cf:check and `cargo fmt` / `clippy` / `test` (15 tests) all pass; initial load 276.3 of 280 KB gzip. Verified live: `wrangler dev` serves the gate page on the new undici; the desktop app (`tauri dev` with a separate test identifier) answers its commands, writes, reads and deletes a backup, and opens and cancels the native Save dialog. - Six manifests bumped 1.3.0 → 1.3.1. ## v1.3.0 — 2026-10-22 A toolchain release: **TypeScript 7**, **Node 26**, two rounds of dependency updates that close five security alerts, and every open **SonarCloud** issue fixed. What the app generates does not change. Web, desktop and Android all ship as 1.3.0. ### Changed - **Android keeps your data out of cloud backups.** The app now sets `android:allowBackup="false"`, so Android's backup to Google Drive no longer copies your profiles, presets, templates, history and settings — they stay on the phone, as the Privacy Policy says. To move to a new phone, use **Settings › Backup & restore**: back up to a file, then restore it there. - **Supported WebViews.** The desktop and Android apps are built for the same engines as the website — Chromium 111, Safari 16.4, Firefox 114 (Vite's `baseline-widely-available`) — instead of being lowered to ES2020. In practice: WebView2 on Windows (it updates itself), macOS 11 or later with current Safari updates, WebKitGTK 2.40+ on Linux, and on Android 11+ a System WebView kept current through Google Play. An older WebView already showed the app unstyled. The macOS app now states its minimum, macOS 11 (it is Apple silicon only). - **Security policy**: 1.3.x is the supported version. - **Docs**: DEVELOPMENT + Vietnamese (Node 26, TypeScript 7 and the IDE setting), TECH-SPEC (package.json, tsconfig, the toolchain notes), PACKAGING (supported WebViews, Android backups), HOSTING, ARCHITECTURE, ROADMAP, README, FEATURES, I18N, CONTENT-INVENTORY, DISCLAIMER + Vietnamese, CLAUDE.md, the bug-report template. ### Fixed - **Security (development tools only — nothing here ships in the app):** - vite 8.3.4 — `launch-editor` alerts #41, #42, #43 (command execution and Windows path checks in the dev server's open-in-editor). - vitest 4.1.12 brings `@vitest/mocker` 4.1.12 — alerts #44, #45 (manual-mock code injection, Windows redirect traversal). Dependabot's own security update could not land: vitest 4.1.11 pins the old mocker. - The error boundary now really falls back to the browser console when the in-app logger can't load — a `try/catch` around the asynchronous import never caught that. - **SonarCloud: 44 open issues → 0** (the 45th, a Gradle lockfile for the Tauri-generated Android project, is accepted). Sixteen regular expressions could backtrack quadratically on long runs of spaces, colons or slashes (CPU names, timestamps, edition suffixes, endings, the Google Play link, license expressions, the Worker's cookie and paths); each is rewritten to run in linear time with the same results. Also: sorts with an explicit comparator, `Number.parseInt`, a profile migration that returns a new object, the shortcut dialog's search box focused through the dialog instead of `autoFocus`, and IDs that never fall back to `Math.random`. ### Under the hood - **TypeScript 7.0** (the native compiler) type-checks the code — about six times faster. TypeScript 7.0 has no JavaScript API yet, so typescript-eslint keeps using TypeScript 6.0 through an npm alias (`typescript` → `@typescript/typescript6`, Microsoft's documented setup), and CI fails if `tsc` is ever anything but 7.x. Target **ES2025** (ES2026 comes with TypeScript 7.1); the app's `lib` stays at ES2022 — the browsers' floor, since Vite never polyfills — while tests, scripts, the Worker and the build plugins get ES2025. `baseUrl` is gone, and `erasableSyntaxOnly` / `verbatimModuleSyntax` are on. - **Node 26** everywhere (`.node-version`, `engines`, Workers Builds). Vitest runs its workers with `--no-experimental-webstorage`: Node 25+ defines a `localStorage` that is `undefined`, which made 39 store tests crash. - **React 19 refs**: Button, IconButton, Input, Select and Textarea take `ref` as an ordinary prop — no more `forwardRef`, which React plans to deprecate. - **CI**: every workflow installs with `npm ci --ignore-scripts`; CI runs `npm run cf:check` instead of `npx wrangler`. - **Dependencies**: eslint 10.12, typescript-eslint 8.71.2, knip 6.41, prettier 3.9.10, vite 8.3.4, @vitejs/plugin-react 6.1.2, vitest 4.1.12, marked 18.1.1, postcss 8.5.30, i18next 26.4.5, lucide-react 1.57, radix-ui 1.8.1, @tauri-apps/api 2.12.4 / plugin-opener 2.7.2 / cli 2.12.3; actions setup-node 7.1, setup-java 6.1, upload-artifact 7.0.2, scorecard 2.5, zizmor 0.7.1. THIRD_PARTY_NOTICES names the real package behind an npm alias. - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **984 tests**, build and `cargo fmt` / `clippy` / `test` all pass; initial load 276.1 of 280 KB gzip. Verified live in the browser: tooltips, the History export popover (focus returns to its button), dialogs and the command palette after the ref change, and the shortcut dialog's focus. - Six manifests bumped 1.2.0 → 1.3.0. ## v1.2.0 — 2026-10-12 Say when a game is **made with AI**: a new group of content warnings for AI-generated game content, three more disclosures, and the docs, notices and wiki brought back in line with the app. Web, desktop and Android all ship as 1.2.0. ### Added - **AI-generated content** — a new content-warning group, the thirteenth, for games that are made or run with generative AI (a story _about_ AI is still "AI / artificial intelligence themes"): - AI-generated content (general) · AI art / visuals · AI / synthetic voices · AI music / sound · AI-written text / dialogue - **Generated live by AI while playing** — the game makes content as you play, so a viewer's own run may differ - **AI use disclosed by the developer** — the store page says so (Steam shows an "AI Generated Content Disclosure"), so viewers know you aren't guessing The split follows Steam's AI disclosure: content made with AI during development and shipped, and content an AI generates while the game runs. Machine translation stays a playthrough note (**Language patch → Machine translation**). YouTube doesn't ask for gameplay footage to be labelled as altered or synthetic — these lines are for viewers. In all eight output languages, next to the English line like every warning. - **Simulated gambling** (Mature / Sensitive) and **In-game purchases** (Internet / Digital life, next to loot boxes) — the two ESRB / PEGI descriptors that had no warning. - **Tech note: Upscaling / frame-gen artifacts** (Video quality) — "Possible upscaling / frame-generation artifacts (DLSS, FSR, XeSS)". Which upscaler and frame generation were on is already the 🖥 Video settings line; the note only warns about what they do to the footage. 257 content warnings in 13 groups, 25 tech notes — all listed in [docs/CONTENT-INVENTORY.md](docs/CONTENT-INVENTORY.md). ### Changed - **Third-party notices** said the app uses the operating system's fonts; it bundles **Inter** and **JetBrains Mono** (OFL-1.1), and now says so. The Rust table lists every direct crate — `serde` was missing — and a crate with no known license stops the generator ([scripts/lib/third-party.ts](scripts/lib/third-party.ts)). - **REUSE**: the Gradle wrapper under `src-tauri/gen/android/` is credited to Gradle's authors, not to the project. - **Privacy Policy** (Effective 2026-10-12) lists the one `sessionStorage` flag, `ytdescgen-chunk-reload`, next to the `localStorage` keys. Not a material change: nobody is asked to accept the terms again. - **Security policy**: 1.2.x is the supported version. - **Docs**: README (contact emails by purpose, themes and scrollbars, installer sizes, the Android build step), ROADMAP (1.1.0 and 1.2.0; finished items checked off), PACKAGING (the installers' copyright, the yearly `update:copyright`, v1.1.0 sizes, `tauri info`), ARCHITECTURE and TECH-SPEC (purpose-word validation, versions, test count), FEATURES, I18N, CONTENT-INVENTORY + Vietnamese (now with the tech notes), CONTRIBUTING and the PR template (the full gate list), the issue templates, DISCLAIMER + Vietnamese, CLAUDE.md. `webapp/TAURI.md` (Node 25, no `.rpm`) is folded into PACKAGING and removed. - **Wiki**: Home (1.2.0, what's new in 1.1 and 1.2), Field Reference (warnings and tech notes, the copyright / DMCA line and purpose words, Hide scrollbars), FAQ ("How do I say a game uses AI-generated content?"), Release Process (copyright years, the wiki step, the rust-toolchain pin). ### Under the hood - No store version bump: the warning and tech-note lists only grow. The backup whitelist checks ids against them, so a 1.2.0 backup restores on 1.1.0 without the new ids. - **A test fails when a content warning or tech note has no editor label or description line** in `_schema.json` — and so, through `validate:locales`, in any locale. Until now a missing key showed the raw key in the editor and silently dropped the line from the description. Tech notes also get the group-parity test content warnings already had. - New strings in all eight locales (1,264 UI + 584 template keys each). - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:tauri, check:licenses, check:copyright, **984 tests**, build and `cargo fmt` / `clippy` / `test` all pass; initial load 275.2 of 280 KB gzip. Verified live in the browser: the new group and its search, pick order in the description, the bilingual English · Vietnamese lines and the tech note. - `.gitignore` covers the maintainer's local `note.txt`, `warning.txt` and `__pycache__/`. - Six manifests bumped 1.1.0 → 1.2.0. ## v1.1.0 — 2026-10-03 A small release: a **copyright email** and **purpose words** for the split contact block, an option to **hide scrollbars**, and copyright years that keep themselves current. Web, desktop and Android all ship as 1.1.0. ### Added - **Copyright / DMCA email.** With Settings › _Split contact email by purpose_ on, the contact block gains a fourth line, `©️ Copyright / DMCA: …`, in all eight output languages. It is saved with the channel profile. - **Purpose words before the @.** In split mode every purpose address has to say what it is for: the part before `@` must contain one of the field's words ([src/config/contact-emails.ts](src/config/contact-emails.ts)), in any case and anywhere, so Gmail's `name+dmca@gmail.com` works. - Advertising / sponsorship: sponsor, ads, advert, business, biz, partner, collab, brand, marketing, promo - Game keys & playtest: key, game, gaming, press, media, review, playtest, beta, curator - Copyright / DMCA: dmca, takedown, copyright, legal, rights, claim A missing word is an error like a malformed address: the value is not saved, and Strict Mode blocks. The help text under each field lists its words. The general Contact address has no rule. - **Hide scrollbars** (Settings › Appearance). No scrollbar anywhere in the app — the mouse wheel, touchpad, touch and keyboard still scroll. Off by default; it travels with backups, like the theme. ### Changed - **Addresses saved before this release** in the advertising or game-keys field are left exactly as they are. If one has no purpose word, Strict Mode points at it — edit it, or use the `name+sponsor@gmail.com` form. - The Spanish example addresses now carry a purpose word (`sponsors@`, `games@`). - **The desktop installers carry a copyright string**, `Copyright 2026 poli0981 (SkullMute)`. The Windows `.exe` / NSIS copyright field, the macOS `Info.plist` and the Linux packages had none. ### Under the hood - **Copyright years, checked.** 2026 is right everywhere — the first commit is from 2026-04-07, so there was no 2025 to correct. [src/config/brand.ts](src/config/brand.ts) now owns the start year and `copyrightYears()`. **`npm run check:copyright`** (in CI) holds NOTICE, REUSE.toml and the installers' copyright string to the year of HEAD's commit — "2026", then "2026-2027" from the first commit of 2027 — and **`npm run update:copyright`** rewrites them. The `/legal` pages' footer prints the same range. - **CI**: `dtolnay/rust-toolchain` is pinned to a commit on its master branch. Its `stable` branch is regenerated upstream, which orphaned the old pin and turned `workflow-lint` (zizmor: impostor-commit) red on every pull request. - Editor store v19 → v20 (`copyrightEmail`, additive), so a backup's draft made by 1.1.0 needs 1.1.0 to restore; everything else in it still restores on 1.0.0. `hideScrollbars` joins the settings without a version bump. - New strings in all eight locales (1,253 UI + 574 template keys each). - typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, check:licenses, check:copyright, **968 tests** and build all pass; verified live in the browser — the purpose-word errors and Strict Mode, the copyright line in the description, and the scrollbar toggle (on, off, after a reload). - Six manifests bumped 1.0.0 → 1.1.0. ## v1.0.0 — 2026-09-30 **YTDescGen moves to [ytgenerator.stream](https://ytgenerator.stream)**, gets a new interface, and the data it writes is right: hardware names, YouTube's own tag count, chapters, history. Backups you can preview and undo, a quick start for the next video, and a hardened desktop app. Web, desktop and Android all ship as 1.0.0. ### Moving house - **The web app lives at [ytgenerator.stream](https://ytgenerator.stream)**, served by a Cloudflare Worker that Cloudflare builds and deploys from `main` (`wrangler.jsonc` is the only Cloudflare file). GitHub Pages is retired: until **2026-11-29** the old address shows a moving notice that **downloads the data your browser saved there as a backup file** — restore it on the new site in Settings › Backup & restore. See [Moving from GitHub Pages](https://github.com/poli0981/youtube-generator/wiki/Moving-from-GitHub-Pages). - **A Cloudflare Turnstile check** (usually invisible) runs once a day before the web app loads. The token is verified server-side; a signed, `HttpOnly` `__Host-` cookie remembers the pass for 24 hours. Agreeing to the terms on that page counts, so web visitors see one screen, not two. - **Legal pages in the site**: Terms, Privacy, Disclaimer (+ Vietnamese), Security, License, Notice, Code of Conduct and third-party notices are rendered at build time — public and crawlable at `/legal/*`, and offline in the app's Legal Center. The Privacy Policy was rewritten for Cloudflare hosting, Turnstile and Web Analytics, so everyone accepts the terms once more (**terms version 2**). - **Cloudflare Web Analytics** (cookieless) in the web build only; the desktop and Android apps have no analytics. - Security headers on everything (CSP per page type, COOP/CORP, frame and referrer policies), `/.well-known/security.txt`, HSTS preload at the edge, clean URLs on the web (old `/#/…` links still work). - **New contacts** by purpose: contact@, security@, privacy@, legal@, dmca@, copyright@, code@ and sponsor@ poli0981.dev, plus [poli0981.dev](https://poli0981.dev/) and [poli0981.dev/links](https://poli0981.dev/links/). The dead Discord invite is gone. - **Brand**: one logo drives the favicon, PWA icons, link-preview card and every desktop/Android icon — the apps used to ship a plain purple square. ### New interface - **Design system** on Radix primitives, Motion and sonner: consistent dark and light themes, self-hosted Inter/JetBrains Mono (with Vietnamese), compact controls (larger on touch screens), animated icons that respect _reduce motion_, real focus handling in dialogs, labelled controls. - **App shell**: collapsible sidebar, a top bar with the output and interface languages, a **bottom bar on phones**, and a **⌘/Ctrl + K command palette** (navigate, copy, apply profile/preset/template, theme, languages, help). - **Editor**: a **sticky live preview** beside the form (a sheet on phones), sections in the order a video is filled in, a searchable genre picker, collapsed sections that show a summary. - **Output**: a **YouTube preview** — the title where search results cut it and the description above "…more". - Every page restyled; hard-coded English translated; flag emoji (which Windows shows as letters) replaced by language names. - Desktop window resizable (1280×820 by default). ### Data that is right - **Hardware names**: _NVIDIA GeForce RTX 5080_ (was "NVIDIA RTX 5080"), _AMD Radeon RX 9070 XT_, _Apple M4 Pro_, laptop GPUs named as such. One **searchable GPU picker** replaces Brand › Series › Model; cards that never shipped are gone; laptop, integrated, handheld and Apple M5 chips added. RAM gains 24/48/192 GB, LPDDR and speeds ("32 GB DDR5-6000"); OS lists SteamOS, Bazzite, CachyOS and current Fedora/macOS; pasted Windows CPU names are tidied. Old saved values are migrated. The rig block is labelled in the output language, in a fixed order. - **Tags counted the way YouTube counts them** (quotes around multi-word tags, commas between them): 15 of 51 real tag sets were over 500 while showing as under. Trimming keeps trying shorter tags; platform names read "Steam", "itch.io". - **Chapters**: "Final Fantasy VII" no longer turns into "Ending Fantasy VII"; `[0:00]` and frame-accurate times are read; a live check shows whether YouTube will show chapters (0:00 first, at least 3, ≥ 10 s apart) and **Tidy up** rewrites pasted lists. - **History** keeps one entry per video (every Output visit used to add one). - **Copy** is blocked only for the field that is over its limit; Ctrl/⌘+Shift+C follows the same rules as the Output page. - Warnings for `<` and `>` (YouTube rejects them); validation accepts real variants (Steam `/sub/` and `s.team`, regional Nintendo sites, `m.`/`www.` links, playlist links from phones) and rejects email domains without a TLD. - **An empty channel name** no longer leaves "…of Hades on ." — the phrase is dropped in all eight languages. ### Backup & restore - **Settings › Backup & restore**: back up everything (or chosen parts) to one file, restore from a file or by dropping it. Files from every earlier version are read — v0.15–v0.38 exports, pre-v0.15 arrays, the old desktop data file — and run through the same migrations the app uses, then a strict whitelist. - **Preview before anything changes**: new / already here / different, per item; **Merge** (keep the newer one, or both) or **Replace**; one step, with **Undo**. Settings never carry your consent or panel state. - **Automatic backups on desktop**: the newest ten, written after your library changes (and before every restore); restore them from Settings. - History exports as **CSV** or JSON; exports carry the date in their names. - Templates save **every** editor field; presets save store link types and all per-game fields; profiles save donate and community links. Edit forms can update from the current editor and save on Enter. ### Faster data entry - **Quick start** at the top of the editor: pick the **channel profile** and the **game preset** (remembered); replacing filled-in fields asks first; "Update profile/preset" appears when the editor drifts from them. - **Next part** and **New video, same game** clear what belonged to the last video; applying a preset for another game does too. **Start over** keeps your channel; a new draft starts in your **Default Output Language** (it always started in English). - **Paste a store link anywhere** — it lands in the right store field, sets the platform and names the game ("Final Fantasy VII Remake", "Baldur's Gate 3"). Game-name suggestions from presets and history. - **Title shapes**: the alternatives dialog can apply one; new **Title order** setting (game first / video first). - **Copy All can include the tags**; **Batch** chooses Part or Demo part and continues from your part number; **Ctrl/⌘+S** saves the output to History. ### Catalogs - Stores: EA app, Ubisoft, Battle.net, Google Play, App Store, Meta Quest. - Social links: YouTube, Threads, Kick, Reddit, Bilibili; "X (Twitter)" with the X mark. - Cross-posting: **YouTube Shorts, X** (counted the way X counts), **Threads, Bluesky**. - Vietnamese banks: MBV, VCBNeo, Vikki Bank (formerly OceanBank, CBBank, DongA Bank — saved old names get a one-click switch), Cake by VPBank, Timo. ### Desktop - **The webview can no longer name a path.** The five commands that read, wrote, listed and deleted any path it sent are replaced by name-only commands under the app's data folder and by Save/Open dialogs run from Rust (text formats only, size-capped). The fs and shell plugins are removed. - **The settings "mirror" file never worked**: it was written next to the data folder and never read back. It is gone; on first start the old file becomes a restorable backup (never applied on its own) and stray log files are moved into place. - One tray icon, with the app icon. ### Under the hood - CI: dependency review, actionlint + zizmor, OpenSSF Scorecard, REUSE, Conventional-Commit titles, rustfmt/clippy/cargo test/cargo-deny, coverage thresholds, a measured bundle budget (initial load ≤ 280 KB gzip), licence allow-list and generated third-party notices, `wrangler deploy --dry-run`; every action pinned by SHA; release builds verify first. - Dependencies current (React 19.3, Vite 8.3, Tauri 2.12); `npm audit` clean; Tauri 2.12 dropped the `rand` advisory; cargo-deny caught and fixed two `quick-xml` advisories. - New strings in all eight locales (Japanese, Spanish, Korean, Chinese, Portuguese and Indonesian are AI-translated — see the Disclaimer). - 930+ tests (was 698). ## v0.38.0 — 2026-08-17 Two new languages: **Portuguese (Brazil)** and **Indonesian**. Brazil is a top-three market for gameplay viewing and Indonesia the largest in Southeast Asia; both use Latin script, so neither needed font or layout work. ### Added - **`pt-BR` and `id` locales** — 1,562 strings each. Both are complete: titles, every description block, all 248 content warnings, tech notes, playthrough notes, pinned comments, playlist copy, and the whole interface from the editor through Settings, Batch, Social and Logs. - **Per-language tag pools** ([src/engine/tag-generator.ts](src/engine/tag-generator.ts)) — `CORE_TAGS_BY_LANG` and `MULTILINGUAL_TAGS` gained entries for both, so a Brazilian video gets `gameplay sem comentários` and `detonado` rather than falling back to English tags. - **Region-aware browser detection** ([src/store/settings-heal.ts](src/store/settings-heal.ts)) — `detectBrowserLanguage` now matches the full BCP-47 tag before the bare language, or `pt-BR` would be reduced to `pt` and never found. Any other Portuguese variant also resolves to `pt-BR` rather than falling through to English. ### Fixed - **`docs/I18N.md` was wrong about what registering a locale takes.** It said `SUPPORTED_LANGUAGES` was "the only registration step". It is one of four, and they fail differently: the `SupportedLanguage` union and the two tag-pool records are compile errors, but `detectBrowserLanguage`'s own hardcoded copy of the list fails **silently** — the language works and simply never auto-selects for a visitor whose browser is set to it. `SUPPORTED_LANGUAGES` is also not type-bound to the union, and every consumer casts, so a mismatch between the first two compiles cleanly. Corrected, and `SUPPORTED_LANGUAGES` now carries a `satisfies` clause that binds it to the union. - **`__dirname` in the Vite and Vitest configs** replaced with `import.meta.dirname`. Vite 8's native config loader — planned to become the default — doesn't provide the CJS global, and warned on every run. ### Under the hood - **New guard: [tests/i18n/locale-registration.test.ts](tests/i18n/locale-registration.test.ts)** checks the picker list against the locale directories on disk *in both directions*, plus namespace files, flags, native names and tag pools. It exists specifically to close the two registration gaps that fail silently. - 115 UI keys were not hand-translated at all — their English text is byte-identical to a string already translated in `templates.json` (graphics presets, ray-tracing modes, difficulty names, content-warning labels), so they are copied across. Translating those twice risks a checkbox and the rendered description disagreeing about what the same option is called. - Left as English on purpose, matching what the Spanish locale already does: vendor product names (NVIDIA DLSS, AMD FSR, Intel XeSS, Fluid Motion Frames), platform brands (Ko-fi, Patreon, Discord, Steam, TikTok), hardware acronyms (CPU, GPU, RAM), genre terms that are loanwords in both languages (RPG, FPS, MMO, Indie, Metroidvania, Roguelike, Battle Royale), and example URLs / emails in placeholders. **pt-BR 1,344 / 1,562 and id 1,308 / 1,562 strings differ from English**; the remainder are those pass-throughs, not gaps. - Both are **AI-translated and not native-reviewed** — recorded in [DISCLAIMER.md](DISCLAIMER.md) alongside JA / ES / KO / ZH. Native-speaker corrections are the most welcome contribution to this project; `src/i18n/locales//*.json` can be edited straight from GitHub's web UI. - Validator now **1,562 keys × 8 locales**. typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, **698 tests** and build all pass; verified live in the browser — both languages appear in every picker, generate correctly translated titles and descriptions, and translate the interface itself. - Six manifests bumped 0.37.0 → 0.38.0. (v0.36.0 was skipped: the dependency release shipped first and had already taken 0.37.0.) ## v0.37.0 — 2026-08-17 A **dependency modernization** release. No user-facing feature changes; the app should behave identically. Every major the project had been sitting on is now current, and the two new lint rules that came with them found four real performance bugs. ### Changed - **React 18 → 19**, `@types/react` 19, `@vitejs/plugin-react` 6. One source change: React 19 types `useRef(null)` as `RefObject` rather than `RefObject` — the old type quietly claimed a ref was non-null before its element mounted. [ScrollToTopButton](src/components/layout/ScrollToTopButton.tsx) now matches, which keeps its existing null check honest. - **Tailwind 3 → 4** ([src/styles/globals.css](src/styles/globals.css)) — configuration moves from `tailwind.config.ts` (deleted) into CSS. The design tokens live in an `@theme` block that maps Tailwind's names onto the existing `:root` / `.light` variables, so the runtime theme toggle keeps working exactly as before. `darkMode: "class"` becomes `@custom-variant dark`, because the app toggles a class on `` rather than following the OS. PostCSS now loads `@tailwindcss/postcss`. Verified in the browser in both themes. - **ESLint 9 → 10** + `eslint-plugin-react-hooks` 5 → 7, which enables the React Compiler diagnostics. - **Zustand 4 → 5**, **i18next 23 → 26**, **react-i18next 15 → 17**, `@testing-library/*`, `typescript-eslint` 8.67, plus the Vite / Vitest / tsx / knip / Tauri-plugin patch line. ### Fixed The new `react-hooks/set-state-in-effect` rule flagged seven call sites. Four were real extra render passes and are fixed: - **[use-online-status](src/hooks/use-online-status.ts)** rewritten to `useSyncExternalStore`. It was re-reading `navigator.onLine` inside an effect to close the gap between the first render and the listeners attaching — subscribing properly removes the gap rather than patching it, and costs one render fewer on every mount. - **[ShortcutHelpModal](src/components/ui/ShortcutHelpModal.tsx)** derives its filter from `open` instead of resetting state in an effect, so a modal that spends most of its life closed no longer schedules work on unrelated parent updates. - **[DraftIndicator](src/components/editor/DraftIndicator.tsx)** and **[use-languages-ready](src/hooks/use-languages-ready.ts)** now guard their setters. Three remain as **warnings**, deliberately: they genuinely sync state *from* an external source (i18next bundle readiness, a text mirror of a numeric store field, and a `useMemo` the compiler can't preserve). Each needs a restructure rather than a guard, so they are recorded in [eslint.config.js](eslint.config.js) rather than silenced or used as a reason to hold back the upgrade. ### Not upgraded - **`lucide-react` stays at 0.577.0.** 1.x removes every brand icon (Instagram, Facebook, GitHub, YouTube, X) — upstream dropped them for trademark reasons. Taking 1.x would mean either a generic globe next to a Facebook link, or re-adding the marks ourselves and inheriting the exposure lucide just shed. Neither is worth it: 0.577 already delivered the win, cutting the main bundle **175 kB → 137 kB**. ### Under the hood - `knip` now ignores `tailwindcss`, whose only reference after the migration is `@import "tailwindcss"` in CSS — which knip doesn't follow. - Full gate green: typecheck, typecheck:all, lint, format:check, validate:locales, knip, check:version, **692 tests**, build. Verified live in the browser: both themes render, icons intact, editor and batch functional. - Six manifests bumped 0.35.0 → 0.37.0. (0.36.0 is reserved for the two new locales.) ## v0.35.0 — 2026-08-17 A **guardrails** release. Four things the app quietly let you do wrong — publish a Batch description missing its contact block, copy output YouTube would reject, paste a novel into a field, and export a file without being asked where to put it — now can't happen. ### Fixed - **Split contact emails now render in Batch** ([src/hooks/use-render-options.ts](src/hooks/use-render-options.ts), [src/pages/BatchPage.tsx](src/pages/BatchPage.tsx)) — with **Settings → Split contact email** on, the Batch tab showed only the legacy single `📧 Business inquiries:` line while the Output tab correctly showed the grouped `📧 BUSINESS / CONTACT` block. The engine was never at fault: `renderAll` had three call sites each hand-copying the same twelve settings fields, and BatchPage's copy was missing `splitContactEmail` and `showThirdPartyAds`. An absent flag defaults to `false`, so the wrong branch ran silently. The mapping now lives in one hook, guarded from both sides — a missing key is a compile error (`Required`) *and* a named test failure. **The SPONSORS & PARTNERS block was being dropped in Batch for the same reason and now renders too, so Batch descriptions get longer if you had either toggle on.** - **Exports ask where to save** ([src/utils/file-ops.ts](src/utils/file-ops.ts)) — every JSON export (Settings, Profiles, Presets, Templates, Social, Log) bypassed the one writer that branched per platform and dumped straight into `Downloads`, even on desktop where a native Save As dialog was available the whole time. One writer now serves all seven: native **Save As** on Tauri desktop, the **file picker** on Chromium browsers, and the download fallback on Android / Firefox / Safari. Cancelling is silent — dismissing a dialog is a decision, not a failure. Settings Import/Export is also no longer desktop-only. - **`ValidatedInput` no longer destroys good input** ([src/components/ui/ValidatedInput.tsx](src/components/ui/ValidatedInput.tsx)) — on an invalid value it called `onChange("")`, wiping the stored value while the box still showed your text. Backspacing one character out of a complete URL silently emptied the field, and autosave persisted the empty. It now simply doesn't commit, keeping the last valid value. Separately, the box never re-synced when the value changed underneath it, so applying a profile or preset left stale text on screen disagreeing with the store. ### Added - **Over-limit output can't be copied** ([src/engine/limits.ts](src/engine/limits.ts)) — if any one of title / description / tags is over its YouTube limit, none of them can be copied, on **Output and Batch**. The engine has returned `warnings` since v0.5 and nothing ever read it; three ad-hoc checks had grown up instead, and the one in `CopyAllBar` skipped every check whenever more than one output language was selected. Batch also gained the description and tag counters it never had. Scoped sensibly: one over-limit part blocks itself and Copy All Batch, not the other 99. - **Strict Mode** ([src/utils/editor-issues.ts](src/utils/editor-issues.ts)) — a **Settings → Guardrails** toggle, off by default. When on, Generate / Copy / Export are blocked while any field has a hard error, with a banner naming each one. Errors only: a working link that merely doesn't match a platform's usual prefix stays a warning, because blocking it would strand anyone on a vanity domain. Derived from state rather than from mounted inputs, so it works from any page and also catches bad data that arrived by import. The log export stays ungated — a debugging export shouldn't be held hostage by an unrelated bad URL. - **Field length caps** ([src/config/field-limits.ts](src/config/field-limits.ts)) — `maxLength` appeared nowhere in the codebase before this release. Caps are grouped by what a field holds (URL 200, email 320, short name 100, label 300, long text 2000, timestamps 5000) and wired at 53 call sites. Imports are clamped too, since `maxLength` only constrains typing. - **Emails hard-stop at three per field** ([src/utils/validation.ts](src/utils/validation.ts)) — typing a fourth is refused outright instead of wiping the field. Enforced on the *increase*, so a field that already holds four (from an older profile) stays editable down to three, and a half-typed `a@b.com,c@` is never punished. - **Collapsible Settings sections** ([src/pages/settings/GenrePlaylistsSection.tsx](src/pages/settings/GenrePlaylistsSection.tsx)) — **Genre Playlists** renders one input per genre (42 of them) and was the tallest block on the page. It now ships collapsed with a filled-count badge. The other eight sections became accordions too, defaulting open. ### Under the hood - Settings persist **v11 → v12** (`strictMode`, `settingsAccordionState`), with `SCHEMA_VERSIONS.settings` bumped in lockstep. Both are *coerced*, not merely back-filled — a hand-edited `"strictMode": "yes"` is truthy in JS, and switching a seatbelt on by accident is the opposite of an opt-in. `SCHEMA_VERSIONS.profile` corrected 1 → 2, left behind when profile-store bumped in v0.34.0. - `SettingsPage` split 544 → 347 lines, extracting the import/export IO and the Genre Playlists section. - 16 i18n keys per locale across all six locales (validator **999 ui / 563 templates**). typecheck, lint, locale validation, dead-code, formatting, version-sync and **692 tests** (621 + 71) pass; verified live in the browser — Batch renders all three contact lines, a bad Steam URL disables Batch generation and names the field, a fourth email is refused with the three intact, and Genre Playlists opens to 42 inputs behind a `0/42` badge. - Six manifests bumped 0.34.0 → 0.35.0. ## v0.34.0 — 2026-07-20 A **feature** release that lets creators publish a different email per purpose instead of a single catch-all address — so viewers, sponsors, and studios each reach the right inbox. ### Added - **Split contact email by purpose** ([src/pages/SettingsPage.tsx](src/pages/SettingsPage.tsx), [src/components/editor/ContactEmailEditor.tsx](src/components/editor/ContactEmailEditor.tsx)) — a new **Settings → Description** toggle (off by default). Off keeps today's single `📧 Business inquiries:` line, unchanged. On splits the editor's Contact Email field into three: **Contact** (general), **Advertising / sponsorship**, and **Game keys & playtest** — each accepting up to 3 comma-separated addresses via the existing email validator. - **Grouped contact block** ([src/engine/description-builder.ts](src/engine/description-builder.ts)) — when the toggle is on, the description renders a localized `📧 BUSINESS / CONTACT` block with one labeled line per non-empty field (`📧 Contact:`, `🤝 Advertising:`, `🎮 Game keys & playtest:`). Empty fields are skipped and the whole block drops when all three are empty — same skip logic as the Community block. The existing `contactEmail` is reused as the Contact line, so no saved data moves. ### Under the hood - Two editor fields (`adEmail`, `gameKeyEmail`) thread through defaults, the store (persist **v17 → v18**), `GeneratorInput`, the editor → engine mapping, template snapshots, and Profiles (persist **v1 → v2**) — guarded by the existing parity test. The `splitContactEmail` toggle mirrors `showThirdPartyAds` end-to-end: the settings store (persist **v10 → v11**, `SCHEMA_VERSIONS.settings` in lockstep), both output hooks, and the render options. Both migrations are additive `""` / `false` back-fills, so existing drafts, profiles, and settings upgrade untouched. - Twelve i18n keys per locale added (8 ui + 4 templates) across all six locales (validator **983 ui / 563 templates**). typecheck, lint, locale validation, and **621 tests** (613 + 8: split render on/off/partial/empty, v18 migration back-fill/coerce/preserve) pass; verified live. - Five manifests bumped 0.33.0 → 0.34.0. ## v0.33.0 — 2026-07-13 A **feature** release that turns the description's Community block into the channel's full "join the chat" hub: two new invite links (**Signal**, **Instagram group chat**) and **Facebook Group** moved in from the generic Social list. ### Added - **Signal + Instagram community invites** ([src/components/editor/CommunityEditor.tsx](src/components/editor/CommunityEditor.tsx), [src/utils/validation.ts](src/utils/validation.ts)) — two new inputs in the **Community** section that feed the `💬 COMMUNITY` description block for **every** output language (like Messenger). Signal expects `https://signal.group/#`; Instagram expects the group-chat invite `https://www.instagram.com/j/` or the short `https://ig.me/j/` (distinct from the Instagram **profile** link, which stays in Social). Both hard-reject anything off-format via `ValidatedInput`, so a broken invite never reaches the description. - **Facebook Group moved into Community** ([src/config/social-fields.ts](src/config/social-fields.ts), [src/engine/description-builder.ts](src/engine/description-builder.ts)) — the old generic `fb_group` Social entry is now a dedicated `facebookGroupLink` community field with its own strict `https://facebook.com/groups/` validator (tolerating `www.` / `m.` / `web.` and a trailing slash). It renders in the Community block for all languages. The block order is Messenger → Signal → Instagram → Facebook Group → Zalo (Vietnamese-only). ### Under the hood - Three editor fields (`signalGroupLink`, `instagramGroupLink`, `facebookGroupLink`) thread through defaults, the store (persist **v16 → v17**), `GeneratorInput`, the editor → engine mapping, and template snapshots — guarded by the existing parity test. The v17 migration **lifts** a legacy `social.fb_group` value into `facebookGroupLink` and drops the dead key; `normalizeEditorPatch` does the same when a pre-move profile / preset / template is applied. Consequence: like the other community links, Facebook Group is no longer stored inside Profiles. - Nine i18n keys per locale added, one (`social.fb_group`) removed, across all six locales (validator **975 ui / 559 templates**). typecheck, lint, locale validation, and **613 tests** (583 + 30: three new validators, v17 migration incl. the fb_group lift, community render/order/all-language cases, mapping parity) pass; verified live — Vietnamese output shows all five lines in order with a localized heading, English output drops the Zalo line while keeping the rest, and a malformed Signal link surfaces an inline hard-reject error. - Five manifests bumped 0.32.1 → 0.33.0. ## v0.32.1 — 2026-07-12 A **hotfix** to v0.32.0. The Messenger Community field accepted the wrong link shape: `https://m.me/[id]` is a personal-page link, while a community/channel invite is `https://m.me/ch/[id]` (e.g. `https://m.me/ch/Abb1hmBhU_97UMCF/`). Creators following the in-app example published a link that did not open the community. ### Fixed - **Messenger community link format** ([src/utils/validation.ts](src/utils/validation.ts)) — `MESSENGER_URL_REGEX` now requires the `/ch/` segment (trailing slash optional) and hard-rejects the old bare form, so a wrong link can no longer reach the description. The shown example (`MESSENGER_URL_EXPECTED`) and the placeholder in all six locales moved to `https://m.me/ch/yourid`; stale doc comments were refreshed alongside. ### Under the hood - Engine and store are untouched — the link is printed verbatim and the field's type and persist shape are unchanged, so no migration was needed. Validation, engine, and migration tests updated, with new trailing-slash-accept and bare-form-reject cases. - Five manifests bumped 0.32.0 → 0.32.1. ## v0.32.0 — 2026-07-08 A **feature** release adding the first two "join the chat" community links, in a single `💬 COMMUNITY` description block — the block that v0.33.0 later grew to five entries. ### Added - **Messenger community + Zalo group** ([src/components/editor/CommunityEditor.tsx](src/components/editor/CommunityEditor.tsx), [src/utils/validation.ts](src/utils/validation.ts)) — a new **Community** section feeding a localized `💬 COMMUNITY` block. Messenger renders for **every** output language. Zalo is a Vietnam-audience app, so its input only appears — and its line only renders — when the output language is Vietnamese, mirroring the existing VN donate block; a value entered while in Vietnamese survives a language switch. Both links are hard-validated (`validateMessengerUrl` / `validateZaloGroupUrl`) so a malformed URL never reaches the output. ### Under the hood - Two editor fields (`messengerCommunityLink`, `zaloGroupLink`) thread through defaults, the store (persist **v15 → v16**, an additive back-fill), `GeneratorInput`, the editor → engine mapping, and template snapshots — guarded by the existing parity test. - i18n across all six locales (validator **967 ui / 559 templates**). typecheck, lint, locale validation, and **581 tests** (560 + 21: two new validators, the v16 migration, and community render/language-gating cases) pass. - Five manifests bumped 0.31.0 → 0.32.0. ## v0.31.0 — 2026-06-28 A **feature** release for the Playlist Generator: the pinned comment a series needs on its latest video, and an honest answer to "why did this playlist stop?" ### Added - **Status-adaptive playlist pinned comment** ([src/engine/playlist-builder.ts](src/engine/playlist-builder.ts)) — a new `buildPlaylistComment` engine function produces a pinned comment for the series' latest video whose wording follows the playlist status (completed / dropped / incomplete / in progress), rather than one generic template for all four. - **Dropped reasons** ([src/config/dropped-reasons.ts](src/config/dropped-reasons.ts), [src/pages/PlaylistPage.tsx](src/pages/PlaylistPage.tsx)) — when a series is marked **dropped**, a multi-select of six predefined reasons (`😴 boring`, `🐌 performance`, `🐛 bugs`, `🗑️ delisted`, `📉 low views`, `⏳ time`) plus a free-text "other reason" field. Selected reasons render in **both** the playlist description and the pinned comment. Reason labels are localized in both namespaces — `ui` for the selection chips, `templates` for the rendered output — the same split content warnings use. ### Under the hood - Playlist state stays local to the page; nothing was added to the editor store, so there is no migration in this release. - i18n across all six locales (validator **959 ui / 558 templates**). `playlist-builder` gained its first test file — **197 lines** covering comment generation per status and dropped-reason rendering. - Five manifests bumped 0.30.0 → 0.31.0. ## v0.30.0 — 2026-06-27 A **feature** release adding two things creators kept doing by hand: advertising a game's **playtest / early-access signup**, and getting **stopped before a bad number** breaks a batch. ### Added - **Playtest section** ([src/components/editor/PlaytestEditor.tsx](src/components/editor/PlaytestEditor.tsx), [src/config/playtest-platforms.ts](src/config/playtest-platforms.ts)) — a new entry in the **Store & Social** group: a signup link, a platform dropdown (Steam Playtest, Epic, itch.io, Discord / Community, Other), and an invite count. The invite input maxes out at the selected platform's cap (≤ 100); switching to a lower-cap platform clamps an over-budget count down. It renders into the description **only when a link is entered** — no toggle, no video-type gating — exactly like Store Links. The description block ([src/engine/description-builder.ts](src/engine/description-builder.ts)) is a localized `🧪 PLAYTEST / EARLY ACCESS` heading, the platform-labelled link, and an optional `🎟️ N invites available` line (emitted only for a positive whole number, so a stray decimal / negative can never produce a broken line). - **Invalid-number guarding** ([src/utils/validation.ts](src/utils/validation.ts)) — two pure validators (`validateIntegerInRange`, `validateBatchRange`) now reject negative, decimal, out-of-range, and `end < start` / over-100-span inputs. The **Batch** ([src/pages/BatchPage.tsx](src/pages/BatchPage.tsx)) and **Social bulk** ([src/pages/SocialPage.tsx](src/pages/SocialPage.tsx)) part-range inputs **disable the Generate button** and show a warning when the range is invalid; **Playlist** "Total videos" ([src/pages/PlaylistPage.tsx](src/pages/PlaylistPage.tsx)) and the new Playtest invite count warn inline and guard the output. The `Input` primitive ([src/components/ui/Input.tsx](src/components/ui/Input.tsx)) gained optional `errorText` / `helpText` props (backward-compatible). ### Under the hood - Three editor fields (`playtestLink`, `playtestPlatform`, `playtestInvites`) thread through the store (persist **v14 → v15** migration: unknown platform → default, invite count clamped to an integer in `[0, 100]`), `GeneratorInput`, and the editor → engine mapping — guarded by the existing parity test. - 60 new i18n strings across all six locales (validator **948 ui / 544 templates**). typecheck, lint, locale validation, and **544 tests** (517 + 27: playtest block, validators, v15 migration, mapping parity) pass; verified live — the block renders and localizes (EN / JA), the itch.io cap clamps invites 80 → 50, decimals warn, and Batch generation blocks on `end < start` and over-100 ranges. - Five manifests bumped 0.29.3 → 0.30.0. ## v0.29.3 — 2026-06-20 A follow-up **hotfix** to v0.29.2. Forwarding the always-English `tEn` translator to multi-language Output (so the AI-translation disclaimer could render `EN · LOCAL`) also turned the **content-warnings, tech-notes, and playthrough-notes** blocks bilingual in every multi-language tab — because `tEn` was the single shared signal for bilingual rendering. Each multi-language tab is already a dedicated single language, so those "video" blocks should be that language only; only the translation disclaimer is meant to stay bilingual. ### Fixed - **Multi-language tabs render content blocks single-language again** ([src/hooks/use-multilang-output.ts](src/hooks/use-multilang-output.ts), [src/engine/description-builder.ts](src/engine/description-builder.ts), [src/engine/template-renderer.ts](src/engine/template-renderer.ts)) — a new `bilingualContentBlocks` render option (default `true`) gates the three video blocks. The multi-language hook passes `false`, so content warnings / tech notes / playthrough notes show the target language only, while the `▸ 🌐 ABOUT THIS TRANSLATION` disclaimer keeps the raw `tEn` and stays bilingual `EN · LOCAL`. Single-language output is unchanged (default `true` preserves the v0.11/v0.12 bilingual blocks). ### Under the hood - The Social / cross-post path ([src/engine/social-post-builder.ts](src/engine/social-post-builder.ts)) is intentionally left as-is — it is driven by separate hooks, never wired through the multi-language Output tabs, and its bilingual content warnings are long-standing v0.24.0 behavior. The asymmetry is deliberate. - Additive, default-preserving change: the engine option defaults to the old behavior, so every existing caller and test is unaffected. typecheck, lint, locale validation (937/542), and all **517 tests** (513 + 4 new `bilingualContentBlocks` gate tests) pass; verified live — multi-language JA tab shows JA-only content blocks with a bilingual disclaimer, the EN tab omits the disclaimer, and single-language JA still renders content warnings bilingually. - Five manifests bumped 0.29.2 → 0.29.3. ## v0.29.2 — 2026-06-20 A one-line **hotfix**. The opt-in *"Show translation-quality notice"* setting (the AI-translation disclaimer, v0.24.0) had no effect when the Output page was showing **two or more languages at once** — the multi-language output hook had drifted out of sync with the single-language one and never forwarded the setting to the engine. ### Fixed - **AI-translation disclaimer now appears in multi-language Output** ([src/hooks/use-multilang-output.ts](src/hooks/use-multilang-output.ts)) — the multi-language hook now forwards `showTranslationQuality` to `renderAll`, matching [useGeneratedOutput](src/hooks/use-generated-output.ts). The same patch also restores `showThirdPartyAds` (an identical latent gap — its disclaimer was dropped in multi-language mode too) and the always-English `tEn` translator, so the bilingual blocks render `EN · LOCAL` instead of target-language-only. Selecting 2+ languages and viewing a non-English/Vietnamese tab now shows the `▸ 🌐 ABOUT THIS TRANSLATION` block. Single-language output and the Batch page were already correct. ### Under the hood - One-file fix; no engine, store, config, or i18n changes (the `translationQuality` template keys already exist in all six locales). typecheck, lint, locale validation (937/542), all **513 tests**, and the production build pass; verified live — the JA tab renders the block bilingually while the EN/VI tabs correctly omit it. - This hook has drifted out of sync before (a prior `showSponsorCredit` miss), so the recurrence is a known class of bug. - Five manifests bumped 0.29.1 → 0.29.2. ## v0.29.1 — 2026-06-17 A UI/UX hotfix for **mobile viewport overflow**. On Android and narrow web mobile (~360–400px) the **Batch** and **Profile** screens overran the viewport horizontally — rows laid out side-by-side on desktop never collapsed to a stack on small screens. This release makes those rows responsive and sweeps a few adjacent overflow spots. Layout-only: no logic, store, or i18n changes, and desktop layout is byte-for-byte unchanged (every change is gated behind the `sm` breakpoint). ### Fixed - **Batch page fits mobile** ([src/pages/BatchPage.tsx](src/pages/BatchPage.tsx)) — the part-range row (Start / End / Generate) stacks vertically below `sm` with a full-width Generate button, and the result-card copy-button rows wrap instead of overflowing. - **Profile page fits mobile** ([src/pages/ProfilesPage.tsx](src/pages/ProfilesPage.tsx)) — the tab pill and the Export/Import buttons drop onto separate rows below `sm`; the Profile / Preset / Template cards ([ProfileCard](src/components/profiles/ProfileCard.tsx), [PresetCard](src/components/presets/PresetCard.tsx), [TemplateCard](src/components/templates/TemplateCard.tsx)) move their action buttons below the content and let long names wrap (`min-w-0`) instead of shoving the buttons off-screen. - **Adjacent mobile overflow swept** — responsive padding + a wrapping header on [Settings](src/pages/SettingsPage.tsx) (its Import/Export row shows on Android, where `IS_TAURI` is true), the video-settings selector grid collapses to one column below `sm` ([VideoSettingsForm](src/components/editor/VideoSettingsForm.tsx)), and modals are pinned to `calc(100% - 2rem)` so they never exceed the viewport ([Modal](src/components/ui/Modal.tsx)). ### Under the hood - Layout-only className changes across 8 components. typecheck, lint, locale validation (937/542), all **513 tests**, and the production build pass; verified live at 375 px and 1280 px with zero horizontal overflow on Batch, Profiles, Settings, and Editor. - Five manifests bumped 0.29.0 → 0.29.1 (`package-lock.json`, which had drifted at 0.28.0, is resynced to 0.29.1). ## v0.29.0 — 2026-06-15 Adds an **Android build** — an installable, sideloadable signed `.apk` built from the same Tauri 2 codebase as the desktop apps. No app rewrite: Tauri 2 ships Android support, the crate was already `cdylib`/`staticlib` with a `#[cfg_attr(mobile, …)]` entry point, and the Android launcher icons were already in the repo. The work was making the Rust shell compile for mobile, routing file export through the WebView on Android, and wiring a signed-APK CI job that publishes the APK alongside the desktop binaries. ### Added - **Android APK target** — `cargo tauri android init` + `cargo tauri android build --apk` produce a signed, sideloadable APK. The generated Gradle project lives at [src-tauri/gen/android](src-tauri/gen/android) (committed so signing/manifest edits persist); secrets (`keystore.properties`, `*.jks`) and build artifacts are gitignored. - **Requires Android 11+ (minSdk 30)** ([src-tauri/tauri.conf.json](src-tauri/tauri.conf.json) `bundle.android.minSdkVersion`, [build.gradle.kts](src-tauri/gen/android/app/build.gradle.kts)) — raised from Tauri's default 24 (Android 7) to API 30. Android 11+ covers the large majority of active devices and keeps a modern, auto-updating System WebView plus Google Play system/Play-services security updates — even though Google's OS-level security bulletins for Android 11–13 have now ended (12 in 2025, 13 in early 2026). `targetSdk` stays at 36 (Android 16). - **APK signing config** ([src-tauri/gen/android/app/build.gradle.kts](src-tauri/gen/android/app/build.gradle.kts)) — a `release` `signingConfigs` block reads `keystore.properties`, guarded by `if (exists())` so keystore-less debug / contributor builds still work (they produce an unsigned release build instead of failing). - **Android release CI** ([.github/workflows/release-android.yml](.github/workflows/release-android.yml)) — on a `v*` tag (or `workflow_dispatch`), an `ubuntu-latest` job sets up JDK 17 + Android SDK/NDK + the four Rust android targets, decodes the keystore from repo secrets, builds the signed APK, and uploads it to the same draft release as the desktop binaries. Needs four secrets: `ANDROID_KEYSTORE_BASE64`, `ANDROID_STORE_PASSWORD`, `ANDROID_KEY_PASSWORD`, `ANDROID_KEY_ALIAS`. ### Changed - **Rust shell is now mobile-aware** ([src-tauri/src/lib.rs](src-tauri/src/lib.rs)) — the tray icon, single-instance plugin, hide-to-tray and exit-prevention logic are gated behind `#[cfg(desktop)]`; the four cross-platform plugins (dialog / fs / opener / shell) and all six file commands register on every platform. Desktop behaviour is byte-for-byte unchanged (`cargo check` clean). - **`tauri-plugin-single-instance` is desktop-only** ([src-tauri/Cargo.toml](src-tauri/Cargo.toml)) — moved under `[target.'cfg(not(any(target_os = "android", target_os = "ios")))'.dependencies]` so it is never compiled into the Android library. - **File export is mobile-aware** ([src/utils/platform.ts](src/utils/platform.ts), [src/utils/file-ops.ts](src/utils/file-ops.ts)) — a new `IS_MOBILE` flag routes `saveFile()` (log export) through the in-WebView blob download on Android (lands in Downloads), since the native save dialog + `std::fs` path write is unreliable under Android scoped storage. Settings / profile / preset JSON export + import already use blob download / ``, which work as-is in the Android WebView. ### Fixed These two surfaced during on-device testing of the Android build: - **External links now open on Android** ([src/utils/open-external.ts](src/utils/open-external.ts), [src/main.tsx](src/main.tsx)) — legal-doc / donate / repo / social links did nothing on a real device. On-device debugging showed why: a real tap on `` makes the Android WebView fire its native `onCreateWindow`, which Tauri tries to satisfy via the shell plugin's `open` — there is no such binary on Android, so it throws an uncaught *"Scoped shell IO error"* and nothing opens (JS `preventDefault` does **not** stop that native path). Fix (Tauri-only; the web build keeps native `target="_blank"`): strip `target="_blank"` from external anchors (a `MutationObserver` covers React re-renders) so `onCreateWindow` never fires, and intercept the click in the **capture** phase, routing the URL through the `opener` plugin (`openUrl` → system browser). `opener:default` already grants `allow-open-url`, so no capability change was needed. Verified end-to-end on an Android 13 emulator (tap → Chrome opens, no shell error). - **No more black screen on older Android WebViews** ([src/utils/uuid.ts](src/utils/uuid.ts)) — `generateId()` called `crypto.randomUUID()`, which only exists in Chromium/WebView **92+**. It runs at module load (the log store's `CURRENT_SESSION_ID`), so on a stale WebView (e.g. the Chromium 91 some emulator images ship) it threw during boot and black-screened the whole app. It now falls back to a manual RFC 4122 v4 built on `crypto.getRandomValues`. As defence-in-depth, Tauri builds also set `build.target: "es2020"` ([vite.config.ts](vite.config.ts)) so the bundle's *syntax* stays within reach of older WebViews (the web build keeps Vite's modern default). ### Under the hood - **+4 tests (509 → 513)** — [tests/utils/uuid.test.ts](tests/utils/uuid.test.ts) locks down the `generateId()` v4 shape and both fallback paths (no `randomUUID`, no `crypto` at all) so the WebView-91 black screen can't regress. The rest is build/infra plus small guards. Storage (`appDataDir()` via the six file commands) and localStorage persistence both work unchanged on Android (the app's private data dir is writable with `std::fs`). - Five manifests bumped 0.28.0 → 0.29.0. ## v0.28.0 — 2026-06-13 Adds a first-run **legal consent gate**. Before the app is usable, the user reviews the Terms of Use, Privacy Policy, Disclaimer, and License (all already published at the repo root) and ticks a single "I agree" box. Acceptance is recorded and only re-prompts when the terms version changes — so it is a one-time step in normal use, and naturally re-appears in a fresh / incognito browser. On Windows desktop, the installer additionally shows a license page. ### Added - **Legal consent gate** ([src/components/ConsentGate.tsx](src/components/ConsentGate.tsx), [src/config/legal.ts](src/config/legal.ts)) — a full-screen, non-dismissible screen rendered in place of the router until consent is recorded. Lists the four legal docs as links (open in the browser) + one combined agree checkbox; Continue is disabled until checked. Version-based re-prompt via `CURRENT_TERMS_VERSION` + `needsConsent()`; acceptance persists in the existing settings record (`legalConsentVersion` + timestamp) — **no cookie, no new storage key**. - **About → Legal section** ([src/pages/AboutPage.tsx](src/pages/AboutPage.tsx)) — the License/Terms/Privacy/Disclaimer docs are now linked in-app (previously only the License was), reusing the shared `LEGAL_DOCS` list. - **Windows installer license page** ([src-tauri/tauri.conf.json](src-tauri/tauri.conf.json), [src-tauri/installer-license.txt](src-tauri/installer-license.txt)) — `bundle.licenseFile` shows an "accept the terms" page in the MSI/NSIS installers. (macOS `.app`/Linux packages have no interactive license step — they rely on the in-app gate.) - **Accessible `Checkbox` primitive** ([src/components/ui/Checkbox.tsx](src/components/ui/Checkbox.tsx)) — a real `` styled with theme tokens, distinct from the existing on/off `Toggle`. - **60 new locale strings** (10 keys × 6 languages: `consentGate.*` + `about.legalHeading`) + [`_schema.json`](src/i18n/locales/_schema.json); validator now expects 937 ui keys per locale (927 → 937). ### Fixed - **Persisted theme is now applied on boot** ([src/main.tsx](src/main.tsx)) — `index.html` hardcodes `class="dark"`, and previously only the Header toggle wrote the theme class, so a light-theme user saw a brief dark flash on every cold start (and the new gate, which renders before the app shell, would have shown in the wrong theme). The persisted theme is now applied synchronously before first paint. ### Under the hood - **+9 tests (500 → 509)** — [tests/config/legal.test.ts](tests/config/legal.test.ts) (the `needsConsent` version logic + `LEGAL_DOCS` shape; a `NaN`/Infinity version re-shows the gate) and two `legalConsentVersion` back-fill / coercion cases in [tests/store/settings-heal.test.ts](tests/store/settings-heal.test.ts). - Consent state is **additive** — `legalConsentVersion` / `legalConsentAt` join `SettingsData`, `initialSettings`, `extractData`, and `healSettings` (which coerces a malformed value to `0` so a corrupt file re-shows the gate, never skips it). **No persist version bump** (stays at 10). - The gate is a boot-time blocker but stays inside the root `ErrorBoundary`, behind a single boolean — a render error degrades to the designed error page, not a black screen. - Web bundle: the gate + Checkbox + legal config + English strings add ~4 kB min to the main chunk (local Rollup measure); the shipped size comes from CI's vite 8 / Rolldown build. - Five manifests bumped 0.27.1 → 0.28.0. ## v0.27.1 — 2026-06-13 Security/dependency release. Resolves the 4 high-severity `esbuild` advisories deferred from v0.27.0 by upgrading `vite` 7 → 8. The advisories ([GHSA-gv7w-rqvm-qjhr](https://github.com/advisories/GHSA-gv7w-rqvm-qjhr), [GHSA-g7r4-m6w7-qqqr](https://github.com/advisories/GHSA-g7r4-m6w7-qqqr)) affect `esbuild` `0.17.0 – 0.28.0`; the fix lives in `esbuild` 0.28.1, which only `vite` 8 pulls (`vite` 7.3.3 pins `esbuild ^0.27.0` and cannot reach it). They only ever affected the local dev server, never the shipped static bundle. No feature or behaviour changes — `npm audit` now reports **0 vulnerabilities**. ### Security / dependencies - **`vite` `^7.3.3` → `^8.0.16`** — the only release line whose `esbuild` constraint reaches the patched 0.28.1. - **`@vitejs/plugin-react` `^4.3.0` → `^5.2.0`** — the vite-8-compatible major. Stays on the 5.x line (peer `vite: ^4 || ^5 || ^6 || ^7 || ^8`); 6.x is the Rolldown/react-compiler variant and would pull extra peers, so it was avoided. - **`tsx` `^4.16.0` → `^4.22.4`** — 4.22+ is the first `tsx` on patched `esbuild ~0.28.0` (resolves to 0.28.1). Used only by `validate:locales` / `generate:locale`. - `vitest` 4.1.8 already supports `vite` 8 (peer `^6 || ^7 || ^8`) — unchanged. - The tree now hoists a single `esbuild@0.28.1`; `npm audit` → 0 high. ### Changed - **`manualChunks` object form → function form** ([vite.config.ts](vite.config.ts)) — **vite 8 bundles with Rolldown** (replacing Rollup), which only accepts the function form of `manualChunks` (the object form was a Rollup-only API). The same three vendor chunks (`react`, `router`, `i18n`) are reproduced via anchored `[\\/]node_modules[\\/]…` regexes so `react-router*` and `react-i18next` don't get swept into the `react` chunk. This is the only source change the upgrade required. ### Under the hood - Full gate chain green on vite 8: `typecheck`, `lint`, `knip`, `validate:locales` (927/542), `test:run` (**500/500**), `build`. `npm run dev` (port 5173, matching the Tauri `devUrl`) and `npm run preview` (4173) both serve. The Tauri-context frontend build (`TAURI_ENV_PLATFORM` set) still switches `base` to `/` correctly; `tauri.conf.json` `devUrl`/`frontendDist` are unchanged and compatible. - Web bundle (Rolldown): entry chunk 165.3 kB / 46.3 kB gzip, `react` 133.4 kB, `i18n` 57.9 kB, `router` 23.4 kB — all well under the 500 kB budget. Chunk sizes are not directly comparable to the v0.27.0 Rollup numbers (different bundler, different chunking heuristics). - Five manifests bumped 0.27.0 → 0.27.1. ## v0.27.0 — 2026-06-13 Adds a designed, internationalized **error-page system**. A mistyped hash route used to render a blank screen; now any unknown route shows a full-screen 404, and a non-blocking banner signals lost connectivity (the app is fully offline-capable, so it never blocks input). The render-crash boundary adopts the same visual language, and `403 / 419 / 500` pages are route-reachable and ready for future triggers (a Tauri command failure, a future sync backend). ### Added - **Error-page system** ([src/components/errors/ErrorPage.tsx](src/components/errors/ErrorPage.tsx), [src/config/error-pages.ts](src/config/error-pages.ts)) — one reusable, router-agnostic component covering six kinds (`notFound`, `forbidden`, `expired`, `serverError`, `offline`, `runtime`) driven by a pure kind→meta config (HTTP code, lucide icon, severity colour, i18n key prefix). Renders a `fullscreen` variant for standalone routes and a `contained` variant for the crash boundary. - **Standalone error routes + live 404** ([src/App.tsx](src/App.tsx)) — `/#/403`, `/#/419`, `/#/500`, `/#/offline`, plus a catch-all `*` → 404, all rendered **outside** the `AppShell` group so they fill the screen with no Sidebar/Header. The catch-all closes a long-standing gap where unknown hash routes rendered nothing. - **Offline detection** ([src/hooks/use-online-status.ts](src/hooks/use-online-status.ts), [src/components/errors/OfflineBanner.tsx](src/components/errors/OfflineBanner.tsx)) — a `navigator.onLine` hook (SSR/Tauri-safe) drives a dismissible, non-blocking bottom banner; dismissal hides only the current offline episode, and a toast confirms when the connection returns. The app keeps working offline throughout. - **120 new locale strings** (20 keys × 6 languages) + [`_schema.json`](src/i18n/locales/_schema.json) — per-kind titles/descriptions, shared action labels, and offline-banner copy across en/vi/ja/es/ko/zh. Validator now expects 927 ui keys per locale (907 → 927). ### Changed - **ErrorBoundary fallback** ([src/components/ErrorBoundary.tsx](src/components/ErrorBoundary.tsx)) now renders `` instead of a bespoke hardcoded-English card — render crashes share the error-page look and are localized. The boundary still logs the crashing subtree's `label` for bug reports; only the visible copy went generic. ### Under the hood - **+6 tests (494 → 500)** — [tests/config/error-pages.test.ts](tests/config/error-pages.test.ts) guards the pure config: exactly six kinds, correct HTTP codes, unique key prefixes, the resolver / severity-token mappings, and that every kind's `title` + `description` exists in `en/ui.json` (so the config can't point at a missing key — complements `validate:locales`, which only proves cross-locale key parity). - `ErrorPage` is **router-agnostic by design** — the root boundary in [src/main.tsx](src/main.tsx) mounts *outside* ``, so it navigates via `#/` anchors + `history.back()` rather than `useNavigate()`, which would throw in that crash path. - Web bundle: main chunk 264.0 → 270.8 kB minified (82.0 → 84.2 kB gzip) — the eagerly-bundled ErrorPage + config + icons (must render synchronously in the crash path) and the English error strings account for the delta; still well under Rollup's 500 kB threshold. - Five manifests bumped 0.26.0 → 0.27.0. ### Security / dependencies - `npm audit` reports 4 high-severity advisories in **dev-only** `esbuild` (transitive via `vite` / `tsx` / `@vitejs/plugin-react`); the only remedy is a `vite` 7 → 8 major upgrade. They affect the local dev server, not the shipped static bundle. Deferred to a dedicated dependency-upgrade release rather than bundling a breaking change into a feature release. ## v0.26.0 — 2026-06-11 Performance release: locale bundles are now lazy-loaded per language, so visitors only download the languages they actually use. **Main chunk drops 594.0 → 264.0 kB minified (204.3 → 82.0 kB gzip)** — back under Rollup's 500 kB warning threshold (outstanding since ~v0.23) and the project's bundle budget. No feature changes. ### Changed - **Lazy-loaded locale bundles** ([src/i18n/index.ts](src/i18n/index.ts)) — the 10 non-English locale JSONs (5 languages × `ui`/`templates`) left the main chunk and are fetched on first use as Vite async chunks (~27–40 kB min / ~12–17 kB gzip each) via [`i18next-resources-to-backend`](https://github.com/i18next/i18next-resources-to-backend) + a statically-analysable dynamic `import()`. English stays eagerly bundled (`partialBundledLanguages`): it is the `fallbackLng` and the engine's bilingual `tEn` translator, both of which must work synchronously. - **Generation is gated on bundle readiness** — `getFixedT` for an unloaded language silently serves English fallback strings, which would have let the Output page auto-save a *wrong-language history entry*. A new [`useLanguagesReady`](src/hooks/use-languages-ready.ts) hook holds every reactive generator (output preview, multi-language tabs, social captions, playlist, pinned-comment template, title variants) on a placeholder until the bundle is in memory, and the Batch / Social bulk handlers `await ensureLanguagesLoaded(selectedLangs)` before their multi-language loops. - **Cold-start preload** ([src/main.tsx](src/main.tsx)) — the persisted UI + output languages are fetched before first paint (capped at 2 s), so a non-English user never sees an English flash; `react: { useSuspense: false }` keeps lazily-ready namespaces from suspending the app shell, which has no Suspense boundary. - **Failure degrades, never hangs** — a locale chunk that cannot be fetched (offline, stale deploy HTML) is retried once by importing the chunk directly into the resource store (i18next marks a failed language permanently and both `loadLanguages` and `reloadResources` skip it forever after), then logged to the in-app Log page, and the UI falls back to English. ### Under the hood - **+4 tests (490 → 494)** — [tests/i18n/lazy-locales.test.ts](tests/i18n/lazy-locales.test.ts) pins the contract: `en` available synchronously at import, non-English absent until `ensureLanguagesLoaded`, real strings served after, idempotent reloads. - [src/utils/platform.ts](src/utils/platform.ts) — `IS_TAURI` now guards `typeof window`, keeping the i18n module importable in vitest's node environment. - Adding a language no longer touches `src/i18n/index.ts` imports — drop `ui.json`/`templates.json` into `locales//` and register the code in `SUPPORTED_LANGUAGES` ([docs/I18N.md](docs/I18N.md) checklist simplified). - Five manifests bumped 0.25.0 → 0.26.0. ## v0.25.0 — 2026-06-10 Adds 41 content warnings, including two new groups — **Dialogue / Language** and **Internet / Digital life** — plus color phobias, suggestive-imagery disclosures, body-image phenomena, and an educational-purpose disclosure. Also backfills the content-inventory docs to the real warning baseline. ### Added - **2 new content-warning groups + 41 new warnings (207 → 248 across 12 groups)** ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)): - **Dialogue / Language (10)** — what characters *say*, ESRB-descriptor style: `profanity_frequent`, `sexual_innuendo`, `inflammatory_speech`, `verbal_abuse`, `threatening_language`, `slurs_derogatory`, `crude_humor`, `mature_humor`, `dark_humor`, `drug_references`. - **Internet / Digital life (18)** — 21st-century online phenomena: `cyberbullying`, `doxxing`, `trolling_griefing`, `cancel_culture`, `social_media_addiction`, `doomscrolling`, `fomo`, `fake_news`, `online_scams`, `catfishing`, `deepfake_themes`, `cyberstalking`, `internet_challenges`, `influencer_culture`, `online_radicalization`, `loot_boxes`, `ai_themes`, `data_privacy`. - **Phobias +5 color phobias (51 → 56)** — `chromophobia` plus per-color `erythrophobia` (all-red rooms), `xanthophobia`, `leukophobia` (stark-white spaces), `melanophobia`. - **Social phenomena +2 (20 → 22)** — `body_shaming`, `beauty_standards`. - **Mature / Sensitive +5 suggestive-imagery (61 → 66)** — visuals unsuitable for minors short of explicit content, placed beside `mature_18plus`: `revealing_outfits`, `partial_nudity`, `sexualized_characters`, `fanservice`, `suggestive_poses`. - **Gameplay disclosure +1 (4 → 5)** — `educational_purpose_only` for games made for education / PSA / propaganda purposes. - The engine renders all of these automatically (selection-order bullets, bilingual `EN · LOCAL`); cross-post captions inherit them via the shared bullet helper. Vietnamese flag-prone labels follow the v0.21.0 asterisk/euphemism precedent (`t*nh d*c`, `Kh*a th*n`). 504 new locale strings (84 keys × 6 locales) + [`_schema.json`](src/i18n/locales/_schema.json) — validator now expects 907 ui / 542 template keys per locale. ### Docs - **Content-inventory backfill** ([docs/CONTENT-INVENTORY.md](docs/CONTENT-INVENTORY.md), [docs/i18n/vi/CONTENT-INVENTORY.md](docs/i18n/vi/CONTENT-INVENTORY.md), [README.md](README.md)) — the docs still claimed "187 across 9 groups": the v0.22.0 Audio / Sensory group and the v0.23.0 VFX items were never added (the v0.23.0 entry's "187 → 195" total repeated that stale baseline; the actual progression was 199 → 207). Backfilled to the true 207 baseline, then updated to the new 248 / 12-group totals. - [docs/FEATURES.md](docs/FEATURES.md) — replaced the stale v0.7-era "Spoiler Warning / 18+ Warning" description-structure lines with the unified Content Warnings block (v0.11+). ### Under the hood - **+8 tests (482 → 490)** — render/bilingual/VI-masking cases for the new warnings ([tests/engine/description-builder.test.ts](tests/engine/description-builder.test.ts)) and a new `CONTENT_WARNINGS` ↔ groups parity guard ([tests/config/content-warning-groups.test.ts](tests/config/content-warning-groups.test.ts)) that fails if an id is added to the engine list but forgotten from every UI group. - Five manifests bumped 0.24.2 → 0.25.0. First *published* tag carrying the v0.24.2 Linux AppImage hardening (`APPIMAGE_EXTRACT_AND_RUN=1`, `NO_STRIP=true`) — the v0.24.2 tag itself was never released due to the upstream CDN incident. - Web bundle: main chunk 568.5 → 594.0 kB minified (191.5 → 204.3 kB gzip) — the 504 statically-imported locale strings account for the whole delta; Rollup's >500 kB chunk warning predates this release. ## v0.24.2 — 2026-06-08 CI-only patch to recover the Linux desktop binaries. **No application code changes** — identical app to v0.24.1. ### CI - **Hardened the Linux AppImage build** ([.github/workflows/release-desktop.yml](.github/workflows/release-desktop.yml)) — set `APPIMAGE_EXTRACT_AND_RUN=1` and `NO_STRIP=true` on the `tauri-action` step. `linuxdeploy` (itself an AppImage) needs FUSE to mount, which GitHub-hosted runners don't reliably provide → intermittent `failed to run linuxdeploy`. Extract-and-run sidesteps FUSE; `NO_STRIP` skips a strip pass that also flakes. No-op on Windows / macOS. - **Rebuilt to ship the Linux binaries** (`.deb` / `.AppImage` / `.rpm`) that v0.24.1 missed when the AppImage tooling download hit a sustained upstream GitHub-CDN `http status: 504` during bundling. v0.24.1 published with Windows + macOS binaries; this tag re-runs the full matrix once the transient outage cleared. ## v0.24.1 — 2026-06-08 Maintenance patch: clears all `npm audit` advisories, drops unused Rust dependencies, and documents the v0.24.0 cross-post caption generator. ### Security / dependencies - **react-router / react-router-dom 6.30.3 → 6.30.4** — patches the moderate open-redirect advisory ([GHSA-2j2x-hqr9-3h42](https://github.com/advisories/GHSA-2j2x-hqr9-3h42)). Non-breaking; a HashRouter SPA on static hosting was low-exposure, but patched for hygiene. - **vitest 3.2.4 → 4.1.8** — clears the critical Vitest-UI-server advisory ([GHSA-5xrq-8626-4rwp](https://github.com/advisories/GHSA-5xrq-8626-4rwp), dev-only — never in a shipped artifact). All 482 tests pass unchanged on the new major; no test or config code needed adjusting. `npm audit` now reports **0 vulnerabilities**. ### Removed - **Unused `serde` / `serde_json` from `src-tauri/Cargo.toml`** — neither was referenced anywhere in `src-tauri/src/` (Tauri scaffolding leftovers; the `#[tauri::command]` functions only use `String` / `Result`). `cargo check` confirms the crate still compiles without them; `Cargo.lock`'s `yt-desc-gen` entry no longer lists them. ### Docs - Documented the **cross-post caption generator** (Social tab — TikTok / Instagram Reels / Facebook Reels) in [README.md](README.md) and [docs/FEATURES.md](docs/FEATURES.md). ### Under the hood - Five manifests bumped 0.24.0 → 0.24.1 (`package.json`, `package-lock.json` root + self-reference, `src-tauri/Cargo.toml`, `src-tauri/Cargo.lock` self-entry, `src-tauri/tauri.conf.json`). Gates green: typecheck, lint, validate:locales, knip, build, 482 tests, `npm audit` clean. ## v0.24.0 — 2026-06-08 Adds a **cross-post caption generator** that re-packages the YouTube source into TikTok / Instagram Reels / Facebook Reels captions, a navigation **theme toggle**, an opt-in **translation-quality notice**, and a **Telegram** social link — plus a fix for a stray validation warning on the OS Rig field. ### Added - **Cross-Post Captions** — a new **Social** tab ([src/pages/SocialPage.tsx](src/pages/SocialPage.tsx), [src/engine/social-post-builder.ts](src/engine/social-post-builder.ts), [src/config/social-platforms.ts](src/config/social-platforms.ts), [src/hooks/use-social-posts.ts](src/hooks/use-social-posts.ts)). Re-packages the same editor source that drives the YouTube description into short-form captions for **TikTok (4000)**, **Instagram Reels (2200)**, and **Facebook Reels (2200)**. Each caption pulls Title (badge suppressed), 💻 MY RIG, ⚠️ Content Warnings, 🎁 Thanks, © Copyright, and hashtags (game + primary genre + a curated per-platform popular-hashtag set, deduped case-insensitively). Per-platform char counter + over-limit warning; when a caption overflows, optional blocks are dropped in priority order (warnings → copyright → thanks → rig) — Title + hashtags are never dropped, and there's no mid-string truncation. **Single** mode (platform tabs) and **Bulk** mode (part range × selected languages, reusing the Batch loop) with Copy-All. **JSON import/export** of the generated captions via a new `social` envelope type ([src/utils/file-schema.ts](src/utils/file-schema.ts) `ExportType` / `SCHEMA_VERSIONS` / `isExportType`); import is display-only since captions are derived artifacts. New `tabs.social` + `socialPost.*` locale block across all 6 locales (no new `templates.json` keys — captions reuse existing description/title strings). - **Dark/Light theme toggle in the header** ([src/components/layout/Header.tsx](src/components/layout/Header.tsx)). A Sun/Moon icon button next to the language picker, reusing the existing `settings.setTheme` action so it stays in sync with the Settings toggle both ways. New `header.toggleTheme` key across 6 locales. No store/persist change — the theme field + setter already existed. - **Translation-quality notice** ([src/engine/description-builder.ts](src/engine/description-builder.ts), [src/pages/SettingsPage.tsx](src/pages/SettingsPage.tsx)). New opt-in `showTranslationQuality` setting. When on, descriptions generated in a language **outside the trusted set (English / Vietnamese, which are human-reviewed)** get a bilingual `▸ 🌐 ABOUT THIS TRANSLATION` block: an intro naming the trusted languages + caveat bullets (accuracy not 100%, phrasing may be literal/stiff, may not match local style, corrections welcome). English/Vietnamese descriptions skip it. New `description.translationQuality.{header,intro,items.*}` template keys + `settings.showTranslationQuality{,Hint}` UI keys across 6 locales. Additive setting — `healSettings` back-fills the default, so no persist bump. - **Telegram social link** ([src/config/social-fields.ts](src/config/social-fields.ts)). New `telegram` field (`https://t.me/` prefix, ✈️ icon) in the Social category. `social` is a generic record, so no profile migration. New `social.telegram` label across 6 locales. ### Fixed - **"Pick a DDR generation" no longer appears on the OS Rig field** ([src/components/editor/RigEditor.tsx](src/components/editor/RigEditor.tsx), [src/utils/rig-validation.ts](src/utils/rig-validation.ts)). `renderComposite` hard-coded the RAM validator for **every** composite dropdown, so selecting an OS — also a composite — ran the RAM check (`"windows||"` parses as size=`"windows"`, ddr=`""`, tripping `ramMissingDdr`). Validator selection moved into a pure `validateCompositeField(fieldId, raw)` helper that only validates RAM; the OS composite (and any future one) shows no spurious badge. ### Under the hood - **Shared `buildBilingualBulletSection` helper** ([src/engine/description-builder.ts](src/engine/description-builder.ts)). The inline Content-Warnings render block and the standalone Tech-Notes function were collapsed into one exported pure helper (header + intro + `• EN · LOCAL` bullets, U+00B7 separator) — reused by Content Warnings, Tech Notes, the new Translation-Quality notice, and the social-post builder. Description output is byte-for-byte unchanged, guarded by the existing description tests. - **28 new tests** (454 → 482): 12 in [tests/utils/rig-validation.test.ts](tests/utils/rig-validation.test.ts) (new — RAM/GPU validators + `validateCompositeField` OS-vs-RAM guard), 13 in [tests/engine/social-post-builder.test.ts](tests/engine/social-post-builder.test.ts) (new — hashtag derivation/dedupe/sanitization, rig, bilingual warnings, copyright/sponsor gating, overflow drop-order), 3 translation-quality cases in [tests/engine/description-builder.test.ts](tests/engine/description-builder.test.ts), plus the `settings-heal` complete-payload guard updated for the new field. - Five manifests bumped 0.23.0 → 0.24.0 (`package.json`, `package-lock.json` root + self-reference, `src-tauri/Cargo.toml`, `src-tauri/Cargo.lock` self-entry, `src-tauri/tauri.conf.json`). - Pre-release gates run green: lint, typecheck, validate:locales (12/12 files complete; 864 ui + 501 template keys per locale), 482 tests, knip, build. ## v0.23.0 — 2026-05-27 Extends audience-protection coverage with eight VFX-intensity warnings and unlocks the new OS Rig field (introduced in v0.22.0) for macOS and Linux creators via a cascading dropdown that adapts its slot semantics to the chosen OS family. ### Added - **8 new VFX content warnings in the `photosensitive` group** ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)). New IDs: `lens_flare_intense`, `bloom_excessive`, `particle_effects_dense`, `screen_overlay_flashing`, `color_saturation_extreme`, `motion_blur_heavy`, `depth_of_field_aggressive`, `post_processing_intense`. Closes the gap between blanket `flashing_lights` / `strobe_effects` and the AAA / horror games that ship intense visual-effects passes (bloom, particles, lens flares, post-processing) without ever triggering a strobe-style flash. Total content warnings 187 → 195 across 10 groups (no new group; `photosensitive` 5 → 13). Purely additive — engine renders each warning automatically; existing profiles round-trip unchanged. Fully translated across all 6 locales (`ui.json` short labels + `templates.json` description phrases) with `_schema.json` updated. - **macOS support in the OS Rig field** ([src/config/rig-fields.ts](src/config/rig-fields.ts) `MACOS_VERSION_OPTIONS`). 7 macOS major versions: `10` (Mojave era), `11 Big Sur`, `12 Monterey`, `13 Ventura`, `14 Sonoma`, `15 Sequoia`, `26 Tahoe`. The intentional 15 → 26 jump matches Apple's 2025 year-aligned marketing-number reset. Stored values carry the human label (e.g. `"macos|15 Sequoia|"`) so the description output reads as a single recognisable string. macOS has no Edition tier, so the third dropdown is hidden when macOS is selected. - **Linux support in the OS Rig field** ([src/config/rig-fields.ts](src/config/rig-fields.ts) `LINUX_DISTRO_OPTIONS`, `LINUX_VERSION_BY_DISTRO`). 7 distros gameplay creators actually use via Proton: Ubuntu (`20.04 / 22.04 / 24.04 / 26.04 LTS`), Fedora (`40 / 41 / 42`), Debian (`12 Bookworm / 13 Trixie`), Arch (`rolling`), Manjaro (`latest`), Pop!_OS (`22.04 / 24.04 LTS`), Linux Mint (`21 / 22`). When Linux is selected the second slot re-labels to "Distro" and the third slot re-labels to "Version" with a per-distro option list — so Ubuntu's versions don't bleed into Fedora's dropdown. - **Cascading composite dropdown** ([src/config/rig-fields.ts](src/config/rig-fields.ts) `CompositePart`, `resolveCompositeOptions`, `resolveCompositeLabelKey`). `CompositePart.options` widened from `RigFieldOption[]` to a union with `(previousParts) => RigFieldOption[]` so a part can resolve its option list from previously-selected siblings. New optional `labelKeyResolver` lets a single part swap its i18n key (Version / Distro), and `hiddenWhen` removes a part from both the editor form and the description output. RAM (the existing 2-part static composite) is unaffected — the union accepts arrays unchanged. - **`editor.os_distro` locale key** across all 6 locales (`Distro` / `Distro` / `ディストリ` / `Distro` / `배포판` / `发行版`) — the new Linux-only second-slot label. ### Changed - **Editor form resets downstream parts on parent change** ([src/components/editor/RigEditor.tsx](src/components/editor/RigEditor.tsx) `renderComposite`). When a user switches OS name from Windows to macOS, any previously-selected version / edition values are cleared so the form can't end up in an invalid state (e.g. `macOS 11 Pro`). The new `setPart` clears all indices `>` the changed one, so the cascading dropdown is always self-consistent. ### Under the hood - Composite dropdown `formatRigValue` walks parts with a `previousValues` accumulator now, calls `hiddenWhen` first to skip hidden parts entirely (so they don't leak empty tokens into the joined output), then resolves the option list with the accumulator. Stored shapes are unchanged — v0.22.0's `"windows|11|pro"` round-trips byte-for-byte. - 9 new tests in [tests/engine/rig-fields.test.ts](tests/engine/rig-fields.test.ts) (24 → 33): 7 OS cascading cases (macOS Sequoia / Tahoe, Linux Ubuntu / Arch / Fedora / Debian, hidden macOS edition fallback, Windows backward-compat guard), 1 empty-name fallback (degenerate input), 1 RAM regression check that confirms the static-array path still works after the union widening. - Five manifests bumped 0.22.0 → 0.23.0 (`package.json`, `package-lock.json` root + self-reference, `src-tauri/Cargo.toml`, `src-tauri/tauri.conf.json`). - Pre-release gates run green: lint, typecheck, validate:locales (12/12 files complete; 844 ui + 495 template keys per locale), 454 tests, build. ## v0.22.0 — 2026-05-27 Adds a dedicated **Audio / Sensory** content-warning group, introduces an opt-in video-style era credit that combines with the rig's Video Editor field, surfaces a structured **Operating System** dropdown in My Rig, and drops two stale Settings/About items (Default Genre, Dev Environment). ### Added - **12 new audio content warnings in a new `audio` group** ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)). Splits audio-sensitive triggers out of the `photosensitive` group where they never quite fit. New IDs: `ear_piercing`, `jumpscare_audio`, `sudden_volume_changes`, `distorted_audio`, `screeching_metallic`, `persistent_high_pitch`, `audio_glitches`, `heavy_bass_rumble`, `screaming_audio`, `glass_breaking_audio`, `microphone_pops`, `white_noise_static`. `loud_noises` migrated out of `photosensitive` into this group. Total content warnings 175 → 187 across 9 → 10 groups. Purely additive; engine renders each warning automatically. Fully translated across all 6 locales (`ui.json` short labels + `templates.json` description phrases) with `_schema.json` updated. - **Video-style era toggle** ([src/config/video-styles.ts](src/config/video-styles.ts), [src/components/editor/VideoSettingsForm.tsx](src/components/editor/VideoSettingsForm.tsx), [src/engine/description-builder.ts](src/engine/description-builder.ts)). New per-video opt-in field `videoStyleEra` on `EditorData` — empty string sentinel for "off", 12 valid eras: `1980s`/`1990s`/`2000s`/`2010s`/`2020s` + `modern`/`cinematic`/`retro`/`vhs`/`film_noir`/`anime_mv`/`documentary`. When set, the description renderer emits a single line at the end of the Video Settings section combining the era with the rig's video editor: `"Edited in 1990s VHS style using DaVinci Resolve 19.1"`. Falls back to an editor-less template (`"Edited in 1990s VHS style"`) when `rig.video_editor` is empty. **Renders even when `skipGraphicsSettings` is on** — 2D / pixel-art creators still edit their footage, so the style credit survives as a standalone one-line section under the same header. New file exports `VIDEO_STYLE_ERAS` literal union + `isVideoStyleEra` type guard. Field shape mirrors the existing `artStyle` / `playthroughStatus` / `difficulty` per-video sentinels — no parallel boolean toggle. - **Operating System field in My Rig** ([src/config/rig-fields.ts](src/config/rig-fields.ts) `OS_COMPOSITE`). New `composite_dropdown` entry at the top of `RIG_FIELDS` modelled on the existing RAM pattern. Three parts: name → version → edition. Stored as `"windows|11|pro"` → renders `"Windows 11 Pro"` via `formatRigValue`. Windows 10 / 11 + Home / Pro / Enterprise / Education / IoT Enterprise. Pre-v0.22 profiles with no `rig.os` key pass through the existing empty-value filter chain in `description-builder.ts` — no migration needed. New schema keys `editor.os_name`, `editor.os_version`, `editor.os_edition` + `rig.os` across 6 locales. ### Removed - **Default Genre setting** ([src/pages/SettingsPage.tsx](src/pages/SettingsPage.tsx), [src/store/settings-heal.ts](src/store/settings-heal.ts), [src/store/settings-store.ts](src/store/settings-store.ts), [src/config/defaults.ts](src/config/defaults.ts)). The `ChipGroup` never wired through to the editor — orphan field. Removed UI, `SettingsData.defaultGenres`, `setDefaultGenres` action, `initialSettings.defaultGenres`, `SettingsDefaults.defaultGenres`, `DEFAULTS.settings.defaultGenres`, `extractData` entry, and the v1→v2 migration block in `healSettings` (replaced by a single `delete incoming.defaultGenres` + `delete incoming.defaultGenre` so persisted blobs don't leak the dead field). Two migration tests removed from `settings-heal.test.ts`. `settings.defaultGenre` key removed from 6 `ui.json` + `_schema.json`. - **Dev Environment section from About** ([src/pages/AboutPage.tsx](src/pages/AboutPage.tsx), [src/config/about.ts](src/config/about.ts)). Hardcoded specs drift on every box upgrade. Removed the entire `
` block (~33 lines of JSX + `devEnvRows` constant), `Cpu`/`Monitor` icon imports, `ABOUT.pcSpecDocUrl` and `ABOUT.devEnvDocUrl`, and all `about.devEnvHeading` / `devEnvHelp` / `devEnv.{os,cpu,gpu,ram,ide,toolchains,fullSpecLink,fullDevEnvLink}` keys from 6 `ui.json` + `_schema.json` (10 keys per locale). ### Changed - **`loud_noises` migrated from `photosensitive` to `audio`.** Sudden-volume / high-frequency triggers affect a different audience than strobe / motion-sickness triggers, so the group split is cleaner. Stored ID unchanged — existing profiles using `loud_noises` round-trip without any per-warning migration. ### Under the hood - **Editor-store persist version 13 → 14.** Adds `videoStyleEra` field with defensive coercion: unknown / hand-edited / future-downgrade values are coerced back to `""` via the `isVideoStyleEra` type guard so the form `Select` never lands on a missing option. Additive — pre-v0.22 drafts round-trip through the migration with `videoStyleEra` defaulting to off. - **`healSettings` strips both legacy keys.** Whether the persisted blob carries the v1 shape (`defaultGenre: string`) or the v2 shape (`defaultGenres: GenreId[]`), the heal step now deletes both before the final `{ ...initialSettings, ...incoming }` spread — guarantees the field never resurfaces. - **B3 "Localize My Rig labels" was a phantom task.** Initial planning assumed the `rig.{cpu,gpu,ram,storage,monitor,capture,motherboard,controller,video_editor}` locale keys didn't exist anywhere; verification showed all 6 locales already had them with proper translations. Only the new `rig.os` key was actually missing — folded into the OS-field work. - Five manifests bumped 0.21.0 → 0.22.0 (`package.json`, `package-lock.json` root + self-reference, `src-tauri/Cargo.toml`, `src-tauri/tauri.conf.json`). - Pre-release gates run green: lint, typecheck, validate:locales (12/12 files complete; 835 ui + 487 template keys per locale), 445 tests (was 416 — +5 video-style line render cases in `description-builder.test.ts`, +6 OS composite cases in `rig-fields.test.ts`, –2 deleted default-genre migration tests, plus pre-existing growth), build. ## v0.21.0 — 2026-05-27 Reduces YouTube auto-flag risk on Vietnamese descriptions, adds twelve method-specific death/violence warnings, rewords the channel copyright line to disambiguate video content from game IP, and adds an opt-in toggle for crediting the game's studio/publisher in the description. ### Added - **12 new content warnings** ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)). Extends the **Sensitive** group with method-specific death/violence depictions that YouTube's auto-moderation flags harder than the umbrella `blood_gore` / `war_violence` labels: `hanging_depiction`, `drowning_depiction`, `burning_alive`, `asphyxiation_depiction`, `restraint_torture`, `public_execution`, `decapitation`, `impalement`, `mass_casualty_event`, `vehicular_violence`, `overdose_depiction`, `defenestration`. Total content warnings 175 → 187 across the existing 9 groups. Purely additive — engine renders each warning automatically; existing profiles round-trip unchanged. Fully translated across all 6 locales (`ui.json` short labels + `templates.json` description phrases) with `_schema.json` updated. VI labels follow the v0.21.0 censoring policy (see below). - **Game-copyright toggle** ([src/store/settings-heal.ts](src/store/settings-heal.ts) `showGameCopyright`, [src/engine/description-builder.ts](src/engine/description-builder.ts) section 4.5, [src/pages/SettingsPage.tsx](src/pages/SettingsPage.tsx)). New Settings → Description toggle (default **off**) that, when enabled with a non-empty `pubDevName`, emits a `© {publisher}. All rights reserved.` line right after the Store Links block. Decoupled from the publisher store-URL — the credit renders based on the studio name alone. Used by creators covering games whose dev/publisher contractually requires attribution in the description. New i18n key `description.sections.gameCopyright` across all 6 locales; new UI keys `settings.showGameCopyright` + `settings.showGameCopyrightHint`. Persists in `GamePreset` so a series spanning many episodes hydrates the studio name + toggle together on preset apply. - **`pubDevName` promoted to first-class field** ([src/components/editor/GameInfoForm.tsx](src/components/editor/GameInfoForm.tsx), [src/store/preset-store.ts](src/store/preset-store.ts) `GamePreset.pubDevName?`). Previously a side-label that only appeared under a non-empty Publisher store URL; now an always-visible "Studio / Publisher" input in Game Info that also drives the game-copyright section. Removed from [StoreLinkEditor.tsx](src/components/editor/StoreLinkEditor.tsx) lines 140–172. Optional in `GamePreset` so older presets hydrate without breaking. ### Changed - **Channel copyright line reworded across 6 locales** ([src/i18n/locales/*/templates.json](src/i18n/locales/) `description.sections.copyright`). Old: `© {year} {channelName}. All rights reserved.` (one short line, ambiguous about whether the channel claims the game's IP). New: a 2–3 sentence disclaimer making explicit that the copyright applies only to the video recording, and that the game, characters, music, and related IP belong to their respective owners. Same `{{year}}` / `{{channelName}}` placeholders — no engine change. JA/KO/ZH now ship a proper localised translation instead of falling back to English. - **VI censoring sweep — consistency + euphemism policy** ([src/i18n/locales/vi/ui.json](src/i18n/locales/vi/ui.json), [src/i18n/locales/vi/templates.json](src/i18n/locales/vi/templates.json)). The Vietnamese warning labels previously used asterisk censoring on some terms (`t* tử`, `b*o h*nh`, `g*ết người`) but left others uncensored (`Bạo lực liên quan chiến tranh`, `Bạo lực từ cảnh sát`) and had a malformed `b* ng*y h*i` for `child_harm`. Sweep unifies them under a 2-tier policy: asterisk for graphic verbs with no natural euphemism (`tự` → `t*`, `giết` → `g*ết`, `treo cổ` → `treo c*`, `bạo hành` → `b*o h*nh`), euphemism for words with a natural softer register (`bạo lực` → `tác động vật lý`, `nổ súng` → `khai hỏa`, `xử bắn` → `hành quyết`). Fixes `child_harm` to use the unambiguous euphemism `chịu tác động`. Proper nouns (game titles, character names) untouched. Goal is to reduce YouTube auto-flag risk on Vietnamese descriptions — purely a static i18n edit, no runtime utility. ### Under the hood - Persist version unchanged — `showGameCopyright` is additive (`healSettings` back-fills via `{ ...initialSettings, ...incoming }`) and `pubDevName` / `showGameCopyright` on `GamePreset` are optional. No migration step needed. - Description-builder section ordering: Store Links → **Game Copyright (new)** → Video Settings → … → Channel Copyright. The two `©` lines (channel + game) are intentional when both toggles are on; the Settings help text is explicit so creators don't mistake it for a bug. - Three test fixtures updated for the new wording / censoring / settings shape ([tests/engine/description-builder.test.ts](tests/engine/description-builder.test.ts), [tests/store/settings-heal.test.ts](tests/store/settings-heal.test.ts)). 435 tests still green. - Five manifests bumped 0.20.0 → 0.21.0 (`package.json`, `src-tauri/Cargo.toml`, `src-tauri/Cargo.lock` `yt-desc-gen` entry, `src-tauri/tauri.conf.json`). - Pre-release gates run green: lint, typecheck, validate:locales (12/12 files complete, 814 ui + 461 template keys), 435 tests, build. ## v0.20.0 — 2026-05-23 Fifty new content-warning IDs across three thematic axes — political / religion / war, social-psychological phenomena (autism, hikikomori, parasocial, etc.), and weather-related phobias — plus a tag-engine fix for game names containing comma / semicolon / pipe characters. ### Added - **50 new content warnings** ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)). The **Phobias** group gains 10 weather-related fears — `homichlophobia` (fog), `lilapsophobia` (tornadoes / hurricanes), `ombrophobia` (heavy rain), `nephophobia` (clouds), `ancraophobia` (strong wind), `cryophobia` (extreme cold, distinct from `chionophobia`/snow), `heliophobia` (sunlight), `cymophobia` (large waves), `limnophobia` (lakes), `potamophobia` (rivers); 41 → 51. The **Sensitive** group gains 20 political / religious / war themes — `political_extremism`, `religious_extremism`, `genocide`, `holy_war`, `holocaust_themes`, `civil_war`, `mass_shooting`, `colonialism`, `propaganda`, `dystopian_state`, `conspiracy_theories`, `censorship_themes`, `ethnic_conflict`, `refugee_crisis`, `revolution_themes`, `assassination`, `coup_themes`, `inquisition`, `forced_labor`, `ultranationalism`; 29 → 49. A new **Social phenomena** group (inserted between *Mental health* and *Sensitive*) carries 20 psychological-social IDs that don't fit clinical mental-health framing — `autism_themes`, `adhd_themes`, `hikikomori`, `neet_themes`, `social_anxiety_themes`, `social_isolation`, `schizophrenia_themes`, `burnout_themes`, `survivor_guilt`, `abandonment_themes`, `parasocial_themes`, `gaslighting_themes`, `stockholm_syndrome`, `behavioral_addiction`, `existential_crisis`, `impostor_syndrome`, `midlife_crisis`, `quarter_life_crisis`, `workplace_harassment`, `masculinity_pressure`. Total content warnings 125 → 175 across 9 groups (was 8). Purely additive — engine renders each warning automatically; existing profiles / templates round-trip unchanged. Fully translated across all 6 locales (`ui.json` short labels + `templates.json` description phrases) with `_schema.json` updated. - **1 new locale key × 6 locales**: `editor.contentWarningGroups.social_phenomena` (the new group's heading). Initial-collapse default set in [ContentWarningChecklist.tsx](src/components/editor/ContentWarningChecklist.tsx) so the 20-item group stays scannable until expanded. ### Fixed - **Tag generator splitting at commas / semicolons / pipes in game names** ([src/engine/tag-generator.ts](src/engine/tag-generator.ts)). YouTube treats `,` as a tag delimiter, so a game title like `Hello, World` previously produced composite tags such as `Hello, World gameplay` that YouTube split into two broken tags (`Hello` + `World gameplay`). New `sanitizeForTag` helper strips `,` `;` `|` from the game name before it enters bare / composite tags and is also called inside `tagFriendlyGameName` (idempotent). Title / description / hashtag paths still read `input.gameName` verbatim — the original punctuation is preserved for human-facing copy, only the tag list is cleaned. Nine new test cases in [tests/engine/tag-generator.test.ts](tests/engine/tag-generator.test.ts) cover the comma / semicolon / pipe paths plus idempotence. ### Under the hood - **Documentation count sweep.** `README.md` content-warning total bumped 125 → 175 and group count 8 → 9; `docs/CONTENT-INVENTORY.md` heading updated, three group sections regenerated (Phobias 41 → 51, Sensitive 29 → 49, new Social phenomena 20), Vietnamese mirror at `docs/i18n/vi/CONTENT-INVENTORY.md` kept in lock-step. - Persist version unchanged — this release adds no new persisted fields. Existing `contentWarnings: ContentWarning[]` profiles widen the allowed enum but reject nothing. - Five manifests bumped 0.19.0 → 0.20.0 (`package.json`, `package-lock.json` root + self-reference, `src-tauri/Cargo.toml`, `src-tauri/Cargo.lock` `yt-desc-gen` entry, `src-tauri/tauri.conf.json`). - Pre-release gates run green: lint, typecheck, validate:locales (12/12 files complete), 435 tests, knip, build, `npm audit` (zero vulnerabilities). ## v0.19.0 — 2026-05-20 Twenty-eight new content-warning IDs (twenty-five clinical phobias plus three discrimination themes) + a scroll-to-top button + a moderate-severity security patch + a dead-code sweep backed by new `knip` tooling + a documentation accuracy pass. ### Added - **28 new content warnings** ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)). The **Phobias** group gains 25 clinically-recognised fears relevant to gameplay / horror content — automatonophobia (animatronics), megalophobia (giant objects), submechanophobia (submerged man-made objects), necrophobia, spectrophobia, demonophobia, selachophobia (sharks), mysophobia, emetophobia, scopophobia, monophobia, musophobia, chiroptophobia, ornithophobia, ichthyophobia, herpetophobia, katsaridaphobia, apiphobia, astraphobia, agoraphobia, enochlophobia, chionophobia, nosocomephobia, aichmophobia, pnigophobia — 16 → 41. The **Sensitive** group gains 3 bigotry-content warnings — `homophobia`, `transphobia`, `xenophobia` — placed next to `discrimination` / `hate_speech`. These are prejudices, not involuntary fear responses, so they are deliberately kept out of the Phobias group. Total content warnings 97 → 125. Purely additive — the engine auto-renders each warning, no persist migration. Fully translated across all 6 locales (`ui.json` short labels + `templates.json` description phrases) with `_schema.json` updated. - **Scroll-to-top button** ([src/components/layout/ScrollToTopButton.tsx](src/components/layout/ScrollToTopButton.tsx)). A floating up-arrow fixed to the bottom-right of the viewport that fades in once the page is scrolled past 300 px and smooth-scrolls back on click. The scroll target is the `
` element — the app's real scroll container, not `window` — which `AppShell` now passes down as a ref. Honors `prefers-reduced-motion`, uses a 44 px touch target with a focus ring, sits at `z-40` so toasts render above it, and re-checks visibility on route change. New `common.scrollToTop` locale key across all 6 locales. - **`knip` dead-code tooling** ([knip.json](knip.json) + `npm run knip`). Authoritative cross-file detection of unused files, exports, and dependencies — coverage TypeScript strict mode (in-file only) cannot provide. Configured so `scripts/` and `tests/` are recognised entry points. ### Fixed - **`brace-expansion` moderate-severity DoS** ([advisory GHSA-jxxr-4gwj-5jf2](https://github.com/advisories/GHSA-jxxr-4gwj-5jf2)). `npm audit fix` bumped the transitive dependency (reached through `@typescript-eslint`) 5.0.5 → 5.0.6. A dev/lint-time dependency only — no effect on shipped web or desktop binaries. `npm audit` now reports zero vulnerabilities. ### Removed - **Dead-code sweep** (knip-driven). Deleted the unused `use-debounce.ts` hook plus ~13 unreferenced exports across config / engine / store / utils (`findGpuSeries`, `formatSingleEndingForTitle`, `PlaylistOutput`, `loadFile`, `exportToJsonFile`, `importFromJsonFile`, `EnglishTranslationFn`, `PlatformId`, `SocialFieldId`, `SocialCategory`, `VietnameseBank`, `RigFieldId`, `SupportedLanguageId`). A further ~12 symbols were tightened from `export` to module-private and the settings layer's redundant type re-exports were trimmed. No behaviour change — all 426 tests still pass. ### Under the hood - **Documentation accuracy pass.** `TECH-SPEC.md` package version (`0.1.0` → `0.19.0`) and CI Node version (`20` → `22`); `ROADMAP.md` corrected a never-built `TabBar` component reference to `Sidebar`; `FEATURES.md` video-type / genre / language counts refreshed, with the stale duplicate tables replaced by links to `CONTENT-INVENTORY.md` (the maintained source of truth); `CONTENT-INVENTORY.md` and its Vietnamese mirror updated for the new warning counts; `README.md` content-warning count corrected (91 → 125). - Persist version unchanged — this release adds no new persisted fields. - Five dependencies knip flagged as unused are intentionally kept and listed under `knip.json` `ignoreDependencies`: the three Tauri plugin packages cannot be safely verified without a desktop build, and `@testing-library/*` is documented test infrastructure. ## v0.18.0 — 2026-05-15 Vietnamese-bank dropdown for the donate form + two persistence-layer bug fixes (UI language reverting to English after relaunch, Settings export bundling unrelated stores) + one cleanup (Open Folder button removed) + a new content-inventory documentation page (EN + VI). ### Added - **Vietnamese bank dropdown** in `VietnameseDonateEditor` ([src/components/editor/VietnameseDonateEditor.tsx](src/components/editor/VietnameseDonateEditor.tsx), [src/config/vietnamese-banks.ts](src/config/vietnamese-banks.ts)). When the output language is Vietnamese, the "Bank name" field upgrades from a plain text input to a `` is replaced by ``. The legacy `endingsShown` freeform is kept on the editor type for migration round-trip but no longer surfaces in the UI. - **`description-builder` endings bullet** — reads from structured `endings[]` first, falls back to legacy `endingsShown` only when the array is empty (covers migrated drafts that still carry both). Multi-row entries render as comma-joined: `Ending 1: True End, Ending 3: Bad End, Hidden`. When `endingVideoIndex` is supplied, only that video's slice renders. - **`timeline-parser` keyword templates** — every locale's `timeline.keywords.ending` is now `"Ending {{n}}"` instead of `"Ending"`. The renderer collapses trailing whitespace so a bare `Boss` (no ordinal) still renders cleanly as `Boss` instead of `Boss `. - **`TemplateSnapshot`** in `template-store.ts` — gained `endings?`, `endingVideoCount?`, `endingVideoRanges?` (all optional for back-compat with pre-v0.16 templates). ### Migration - **`migrateEditorState` v11 → v12** — `liftLegacyEndingString` parses the freeform `endingsShown` into a single-row structured entry: - `"Ending 3: Best End"` → `{ number: 3, name: "Best End" }` - `"Ending 3"` → `{ number: 3, name: "" }` - `"True ending only"` → `{ number: null, name: "True ending only" }` - `""` → `[]` (no entry) Localised "Kết thúc N", "エンディングN", etc. are also recognised. After lifting, `endingVideoCount` defaults to 1, `endingVideoRanges` to a single span; the existing `endingsShown` string is left in place but unused. ### Under the hood - `EndingEntry` and `EndingVideoRange` types live in `src/engine/types.ts`. The 1-indexed inclusive `from/to` convention matches the user-facing "Video 1, Video 2…" labels. - The Output preview for case C currently renders the *union* of all endings (same as case B) — per-video output rendering is wired into the engine via `endingVideoIndex` but the UI selector for it lands in a follow-up patch. Documented inline in `EndingsEditor` as `multiVideoOutputNote`. - Bundle: index 463.08 KB (+62 KB for EndingsEditor + endings-format + table-row UI). Still under the 500 KB cap. - 409/409 tests pass. Lint + typecheck + locale-validate all clean. ## v0.15.0 — 2026-05-14 Import / export overhaul + stability hardening. Closes the "black screen on bad file" class of bugs and gives every JSON export an auto-detect header so users can no longer confuse profile / preset / template files with each other. ### Added - **`ErrorBoundary` ([src/components/ErrorBoundary.tsx](src/components/ErrorBoundary.tsx))** wrapping every `` plus a top-level boundary in `main.tsx`. Catches render-time errors that previously black-screened the app, surfaces a fallback UI with `Try again` (remount the subtree) + `Reload page` actions, and copies the error into the Logs tab via the in-app `logger`. Per-route boundaries mean a crash on the Profiles tab doesn't take down the Editor — the user can navigate elsewhere and recover. - **File envelope format ([src/utils/file-schema.ts](src/utils/file-schema.ts))** — every `.json` export written from this version onwards is wrapped in `{ _app: "ytdescgen", _type, _schemaVersion, _exportedAt, data }`. The `_type` discriminator (`"profile" | "preset" | "template" | "settings" | "history"`) lets imports detect "you opened a Template file in the Profiles importer" and offer to switch tabs instead of silently failing. - **`detectShape` / `resolveForType`** — shape inspector handles envelope files (authoritative `_type`), legacy bare arrays (best-effort guess from `snapshot` / `channelName` + `social` + `rig` / `gameName` + `storeLinks` / `createdAt` + title), and the multi-store settings dump (recognised by the `ytdescgen-settings` key). 17 new unit tests in `tests/utils/file-schema.test.ts` cover the round-trip + every detection branch. - **`importTypedFromJsonFile(expectedType)`** — high-level reader that resolves to a tagged-union `ImportResult`: either `{ ok: true; data; sourceVersion? }` or `{ ok: false; failure }` with one of five kinds (`cancelled`, `read-failed`, `empty`, `parse-error`, `wrong-shape`, `newer-schema`). Replaces the throw/catch-and-show-generic-toast pattern. - **Auto tab-switch on wrong-type import** — when the user clicks Import on the Profiles tab but the file is detected as a Templates export, the toast says "This file looks like a Templates export. Switching tabs…" and `setTab("templates")` runs immediately. One click instead of three. - **Import-result summary** in toasts — `Imported 5 of 7 profiles (some skipped).` when the store-level validator drops malformed rows. Previously a partial success surfaced as a plain "Imported!" even when half the file got rejected. ### Fixed - **Black-screen crash** on loading a corrupt profile or template ("Cannot convert undefined or null to object"). Root cause was three unguarded spreads/`Object.values` chained together: - [src/components/profiles/TemplateCard.tsx:21](src/components/profiles/TemplateCard.tsx) `loadProfile(template.snapshot)` with `snapshot: null` → - [src/store/editor-store.ts:149](src/store/editor-store.ts) `normalizeEditorPatch` spread of `null` patch → - [src/components/profiles/ProfileCard.tsx:34](src/components/profiles/ProfileCard.tsx) `Object.values(profile.social)` with `social: null`. All three now null-guard. `normalizeEditorPatch` returns `{}` for a falsy patch; `loadProfile`-chain spreads degrade to a no-op; `Object.values(profile.social ?? {})` returns 0 instead of throwing. The new ErrorBoundary catches anything that still slips through. - **Store-level import validators** in [profile-store.ts](src/store/profile-store.ts), [preset-store.ts](src/store/preset-store.ts), [template-store.ts](src/store/template-store.ts) now filter incoming arrays for rows with a string `id` of non-zero length; templates additionally require a non-null `snapshot` object. Bad rows are silently dropped (count surfaces in the import toast). ### Changed - **`exportToJsonFile` → `exportTypedToJsonFile`** at every ProfilesPage call site. The legacy bare-value exporter is retained for back-compat but unused. - **`importFromJsonFile` → `importTypedFromJsonFile`** at every ProfilesPage handler. Legacy bare reader retained for the same reason — callers outside Profiles can migrate later. - **`detectShape` is forward-compatible**: an envelope from a future version (whose `_schemaVersion` exceeds `SCHEMA_VERSIONS[expected]`) returns `newer-schema` instead of importing silently. Tells the user to upgrade the app. ### Under the hood - Two layers of validation by design: `detectShape` confirms the file *kind*; per-store `importX` rejects malformed *rows*. A future tab-specific quirk in one validator can't corrupt other stores' data. - `normalizeEditorPatch` signature widened to `Partial | null | undefined` so TS forces null-handling at call sites. Existing callers still work — `Partial` is assignable to the new union. - Vite reports one dynamic-import-also-statically-imported warning for `logger.ts`. Intentional: the boundary uses a dynamic import so logger init failures during the *primary* render error don't escalate into a secondary boundary crash. Bundle is not split. - Bundle: index 401.06 KB (+2.49 KB), ProfilesPage chunk 18.44 KB (+4.38 KB for envelope + failure-toast rendering). Total still well under the 500 KB cap. - 367/367 tests pass (350 + 17 new for file-schema). ### Migration notes - **No store schema bump**. v0.14.x persisted state loads unchanged in v0.15.0; new envelope only affects on-disk JSON export files. - **Legacy export files still import** via the shape-detector path. Re-export to get the envelope header + tab-switch hints. - **Envelope schema versions**: profile=1, preset=2, template=1, settings=9, history=2. Bump per-type when introducing a non-additive change to that store's shape. ## v0.14.1 — 2026-05-14 Same-day patch on v0.14.0. Two desktop-only items closing user-reported issues on Windows + a small Settings convenience. ### Fixed - **Windows "cannot find ... `AppData\Roaming\com.skullmute.ytdescgen`"** when clicking *Settings → Open Folder* on a fresh install ([`src/pages/SettingsPage.tsx:25-35`](src/pages/SettingsPage.tsx)). Root cause: `appDataDir()` only resolves the path string — the directory itself is created lazily on the first `save_to_file` write, so first-run users hit the OS shell before any setting had been persisted. New Rust command `ensure_dir(path)` ([`src-tauri/src/lib.rs:18-27`](src-tauri/src/lib.rs)) wraps `std::fs::create_dir_all` and is invoked before both `openPath(dir)` and `read_from_file` in `exportSettingsToFile`, so the shell + read paths can never encounter a non-existent folder. ### Added - **Settings → Import button** (Tauri-only, next to *Export*). Reads a `.json` settings file via the existing `loadFile()` Tauri dialog, accepts either the full multi-store dump produced by *Export* (object keyed by `ytdescgen-settings`) or a bare `SettingsData` payload, runs it through `healSettings()` to back-fill any missing keys, then dispatches via `useSettingsStore.setState`. Theme class on `` is re-applied directly because `setState` bypasses the `setTheme` action. Five distinct failure modes get their own toast: dialog-cancel (silent), `read_from_file` error, empty file, JSON parse error, non-object root. Each failure logs to the in-app logger with the source `"settings"` so it surfaces in the Logs tab without leaving the UI. ### Under the hood - New Tauri command `ensure_dir` registered in `invoke_handler!` macro alongside `save_to_file` and `read_from_file`. Pure stdlib — no new crates. - `exportSettingsToFile` also pre-creates the data folder so *Export* works on a fresh install without first triggering any other write. - Settings store gained no schema fields; the import path reuses the existing `healSettings` (v9) for back-fill so no `version` bump on the persist store. - 350/350 tests still pass; lint + typecheck clean. - Bundle: SettingsPage chunk grew ~0.18 KB raw for the new icon import + import handler; main bundle and overall gzip totals unchanged. ### Migration notes - No store schema bump. Existing v0.14.0 installs upgrade in place. - Web (GitHub Pages) build is unchanged — both fixes are Tauri-only by virtue of the `IS_TAURI` gate on the Settings toolbar. ## v0.14.0 — 2026-05-14 Three independent strands land together: 1. **License flip MIT → Apache-2.0.** The repo previously claimed MIT in README/CLAUDE.md but had no `LICENSE` file. Adds canonical Apache License 2.0 text, a `NOTICE` asserting copyright + AI-assisted-development disclosure, and the `license` field in `package.json` + `src-tauri/Cargo.toml`. Per the production-docs spec. 2. **Content warnings 69 → 91** across a new 8th group `gameplay_disclosure`. Adds horror-channel staples plus transparency disclosures for non-vanilla play. See "Added" below for the full ID list. 3. **Mobile-responsive web** without PWA or Tauri-mobile. The GitHub Pages build is now usable on phones (drawer nav below `md`, touch-sized form controls, iOS-safe focus behavior, safe-area-inset padding for notch/home indicator). Plus a documentation sweep: full `README.md` rewrite, new root policy files for public release (`SECURITY`, `CONTRIBUTING`, `CODE_OF_CONDUCT`, `PRIVACY`, `DISCLAIMER`, `TERMS`, `THIRD_PARTY_NOTICES`, `MAINTAINERS`), `docs/DEVELOPMENT.md` merging the deleted `pc_spec.md` + `dev_env.md`, Vietnamese mirrors for DEVELOPMENT and DISCLAIMER, and a `.github/PULL_REQUEST_TEMPLATE.md`. ### Added - **`LICENSE`** (root) — canonical Apache License 2.0 text. **`NOTICE`** asserting `Copyright 2026 poli0981` + Claude Code 4.7 Opus (1M context) co-authorship disclosure. `license` field added to `package.json` and `src-tauri/Cargo.toml`. - **22 new content-warning IDs** across 8 groups ([src/engine/types.ts](src/engine/types.ts), [src/config/content-warning-groups.ts](src/config/content-warning-groups.ts)): - Phobias (+3): `coulrophobia` (clowns), `ablutophobia` (drowning), `taphophobia` (live burial). - Photosensitive (+2): `strobe_effects`, `screen_shake_intense`. - Mental Health (+3): `paranoia_themes`, `intrusive_thoughts`, `medical_horror`. - Sensitive (+3): `human_experimentation`, `cannibalism`, `nuclear_themes`. - Horror-Specific (+5): `liminal_spaces`, `analog_horror`, `unreality_themes`, `pursuit_chase`, `entity_horror`. - Playstyle (+2): `first_time_playing`, `returning_player`. - **NEW group Gameplay Disclosure (+4)**: `mods_used`, `cheats_enabled`, `glitch_exploits`, `assisted_run`. - **`src/components/ui/Drawer.tsx`** — slide-in mobile-nav drawer. Reuses overlay + Esc patterns from `Modal.tsx`; body-scroll lock + safe-area-inset padding; tap-outside-to-close. - **`tailwind.config.ts`** — `theme.extend.spacing.touch = "44px"` (iOS HIG minimum), exposed via `min-h-touch` / `h-touch` utilities. - **Mobile keyboard hints** — `inputMode` / `autoComplete` / `enterKeyHint` on game-name, channel-name, contact-email, and playlist-URL fields so iOS shows the right keyboard. - **Root policy file set** for public release: `SECURITY.md` (private-disclosure flow), `CONTRIBUTING.md` (PR process, validate:locales gate, auto-ignore rules), `CODE_OF_CONDUCT.md` (Contributor Covenant v2.1 link), `PRIVACY.md` (offline-first, localStorage keys listed, GDPR/CCPA), `DISCLAIMER.md` (AI-assistance + translation-quality disclosure), `TERMS.md` (Apache-2.0 + GitHub ToS + GDPR/CCPA/PIPL/LGPD/VN Cybersecurity), `THIRD_PARTY_NOTICES.md` (full dep table + AI disclosure paragraph), `MAINTAINERS.md`. Plus `.github/PULL_REQUEST_TEMPLATE.md`. - **`docs/DEVELOPMENT.md`** (EN) + **`docs/i18n/vi/DEVELOPMENT.md`** (VI) — merge of the deleted `pc_spec.md` + `dev_env.md`. Covers toolchain (Node ≥ 22, Rust stable, Tauri 2), JetBrains 2026.x + VS Code setup, build commands, per-OS Tauri prerequisites, troubleshooting. - **`docs/i18n/vi/DISCLAIMER.md`** — VI mirror of `DISCLAIMER.md`. ### Changed - **`Sidebar.tsx`** — extracts `` so the same nav can render inside the desktop sidebar **and** the new mobile Drawer. Outer `