Files
youtube-generator/CHANGELOG.md
T
poli0981andClaude Opus 5.5 bc27ce95d5 docs: v1.2.0 — sync docs and templates, changelog; bump to 1.2.0
Docs had drifted since 1.0.0: README missed the 1.1.0 features and
showed an Android step that overwrites the committed Gradle project;
ROADMAP, PACKAGING, ARCHITECTURE and TECH-SPEC still described 1.0.0;
CONTRIBUTING and the PR template listed half the gates; SECURITY named
1.0.x; CLAUDE.md's structure and gate list were out of date.
webapp/TAURI.md (Node 25, no .rpm) is folded into PACKAGING and removed.

Also: purpose-word validation documented in ARCHITECTURE, two stale code
comments (about.ts, vietnamese-banks.ts), .gitignore for the
maintainer's local note files, and the CHANGELOG entry.

Six manifests bumped 1.1.0 -> 1.2.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-12 22:10:58 +07:00

185 KiB
Raw Blame History

Changelog

All notable changes to YTDescGen ship as tagged releases on main.

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. Bilingual in every output language, 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.

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).
  • 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 and build 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), 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 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, 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, 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.
  • 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 and 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) — 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) — 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 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 alongside JA / ES / KO / ZH. Native-speaker corrections are the most welcome contribution to this project; src/i18n/locales/<code>/*.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<T>(null) as RefObject<T | null> rather than RefObject<T> — the old type quietly claimed a ref was non-null before its element mounted. ScrollToTopButton now matches, which keeps its existing null check honest.
  • Tailwind 3 → 4 (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 <html> 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 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 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 and use-languages-ready 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 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/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<SettingsRenderOptions>) 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) — 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) — 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) — 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) — 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) — 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) — 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) — 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/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) — 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/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/#<id>; Instagram expects the group-chat invite https://www.instagram.com/j/<id> or the short https://ig.me/j/<id> (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/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/<id> 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) — 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/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) — 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/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/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) 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) — 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) and Social bulk (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) and the new Playtest invite count warn inline and guard the output. The Input primitive (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/engine/description-builder.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) 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) — the multi-language hook now forwards showTranslationQuality to renderAll, matching useGeneratedOutput. 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) — 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) — the tab pill and the Export/Import buttons drop onto separate rows below sm; the Profile / Preset / Template cards (ProfileCard, PresetCard, TemplateCard) 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 (its Import/Export row shows on Android, where IS_TAURI is true), the video-settings selector grid collapses to one column below sm (VideoSettingsForm), and modals are pinned to calc(100% - 2rem) so they never exceed the viewport (Modal).

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 (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 bundle.android.minSdkVersion, 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) — 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) — 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) — 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) — 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/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 / <input type=file>, 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/main.tsx) — legal-doc / donate / repo / social links did nothing on a real device. On-device debugging showed why: a real tap on <a target="_blank"> 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) — 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) 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 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/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) — 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/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) — a real <input type="checkbox"> styled with theme tokens, distinct from the existing on/off Toggle.
  • 60 new locale strings (10 keys × 6 languages: consentGate.* + about.legalHeading) + _schema.json; validator now expects 937 ui keys per locale (927 → 937).

Fixed

  • Persisted theme is now applied on boot (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 (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.
  • 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, 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 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/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) — /#/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/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 — 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) now renders <ErrorPage kind="runtime" variant="contained" /> 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 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 mounts outside <HashRouter>, 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) — 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 + 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 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) — 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 pins the contract: en available synchronously at import, non-English absent until ensureLanguagesLoaded, real strings served after, idempotent reloads.
  • 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/<code>/ and register the code in SUPPORTED_LANGUAGES (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/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 — validator now expects 907 ui / 542 template keys per locale.

Docs

  • Content-inventory backfill (docs/CONTENT-INVENTORY.md, docs/i18n/vi/CONTENT-INVENTORY.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 — 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) and a new CONTENT_WARNINGS ↔ groups parity guard (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) — 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). 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, 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 and 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/engine/social-post-builder.ts, src/config/social-platforms.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 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). 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/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). 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/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). 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 (new — RAM/GPU validators + validateCompositeField OS-vs-RAM guard), 13 in 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, 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/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 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 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 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 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 (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/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/components/editor/VideoSettingsForm.tsx, 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 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/store/settings-heal.ts, src/store/settings-store.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/config/about.ts). Hardcoded specs drift on every box upgrade. Removed the entire <section> 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/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 showGameCopyright, src/engine/description-builder.ts section 4.5, 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/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 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 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/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/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/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 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). 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 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/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). 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 <main> 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 + 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). 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/config/vietnamese-banks.ts). When the output language is Vietnamese, the "Bank name" field upgrades from a plain text input to a <Select> listing 30 of Vietnam's most-used banks (Big 4 state-owned + top 22 joint-stock commercial banks by retail presence + 4 foreign banks with the strongest Vietnam footprint). Sourced from the State Bank of Vietnam's 2026 register via bankervn.com. Picking "Khác (nhập tay)" reveals an inline text input so unlisted / digital-only / regional banks still work. Persisted shape is unchanged — vnBankName stays a plain string — so saved profiles and exports round-trip cleanly. When the output language is not Vietnamese, the field falls back to the legacy text input.
  • docs/CONTENT-INVENTORY.md + Vietnamese mirror (docs/i18n/vi/CONTENT-INVENTORY.md). Static, hand-maintained manifest of every video type (20), game genre (41), and content warning (96 across 8 groups) the editor surfaces. Linked from the main README.md Documentation table. Transparency aid for anyone evaluating the editor's coverage without reading source.
  • 2 new locale keys × 6 locales: editor.vnBankNameSelectPlaceholder, editor.vnBankNameOther. Localised for VI; left in English for JA/KO/ZH/ES to match the existing convention for VN-donate fields. Schema (src/i18n/locales/_schema.json) updated accordingly.

Fixed

  • UI language reverts to English after app relaunch (src/App.tsx). i18next initialises synchronously with fallbackLng: "en" while Zustand's persist middleware rehydrates appLanguage either synchronously (localStorage) or asynchronously (Tauri settings.json). Neither path bridged the persisted value back to i18n, so the UI rendered English even when the saved setting was Vietnamese / Japanese / etc. App.tsx now reads appLanguage at mount and calls i18n.changeLanguage once, then subscribes to subsequent store changes so the async Tauri rehydrate (and any future external mutation) propagate to i18n automatically.
  • Settings JSON export was a multi-store dump (src/pages/SettingsPage.tsx). The pre-v0.18.0 "Export Settings" button copied the whole on-disk settings.json — which the storage adapter writes as a gross dump of every Zustand store (settings + profiles + presets + templates + history). The new exporter writes only the Settings data through exportTypedToJsonFile("settings", …) — the same envelope-typed flow the Profiles tab already uses. Importer is the matching importParsedFromJsonFile + resolveForType("settings") chain, with an explicit reject for the legacy multi-store dump (friendly toast instead of silent profile-store pollution). extractData was promoted from a private helper in settings-store to a named export for this. The IS_TAURI gate stays — surfacing the buttons on the web build is out of scope for this release.

Removed

  • "Open Folder" button in Settings → top bar (src/pages/SettingsPage.tsx). Niche utility — most users never opened the app-data folder, and Tauri-only meant web builds never saw it. The ensure_dir Tauri command stays in the Rust side for the export/import paths that still rely on it. ~25 LOC removed including the unused FolderOpen icon import.

Under the hood

  • App.tsx mount effect now subscribes to useSettingsStore for appLanguage changes — Header and SettingsPage still call i18n.changeLanguage directly when the user switches, which is now redundant but harmless. Cleanup deferred to a future PR.
  • Persist version unchanged — this release adds no new persisted fields.
  • Bundle: under the 500 KB cap. The bank list is a 33-entry static array, negligible weight; the new envelope flow is a net-negative on SettingsPage size (Tauri dialog + ensure_dir + read_from_file paths replaced with one browser-API call).

Migration notes

  • Pre-v0.18.0 settings export files (multi-store dump) are rejected with a friendly "Legacy export format from v0.17.x or earlier is no longer supported" toast on import. Re-export from v0.18.0+ to get a clean settings-only envelope file.
  • Profiles, presets, templates, history export/import flows on the Profiles tab are unchanged. v0.17.x exports of those types still import unmodified.
  • Saved vnBankName values that don't match any of the 30 preset banks auto-detect as "custom" on first render — the dropdown shows "Khác" and the inline text input is pre-filled with the saved value. No persisted data is lost.

v0.17.1 — 2026-05-15

Per-video Output selector — closes the last deferred piece from the v0.16 ending redesign. Multi-video ending playthroughs (case C) can now flip between per-video previews of title / description / tags without leaving the editor.

Added

  • endingVideoIndex field on EditorData (1-indexed, default 1). Stored on the editor (vs. recomputed per render) so the creator's pick survives navigating away and back. Engine already respected the corresponding GeneratorInput.endingVideoIndex since v0.17.0 — this just persists it.
  • "Preview video" Select dropdown in EndingsEditor case C (src/components/editor/EndingsEditor.tsx). Renders endingVideoCount options labelled "Video N (X–Y)" where X–Y are the matching ending-range bounds. Changing it pipes endingVideoIndex into the engine, which slices endings[] for both title (via buildStructuredEndingLabel) and description (via sliceEndingsForVideo).
  • "Previewing Video X of Y — Endings A–B" banner at the top of the Output page when in case C (src/pages/OutputPage.tsx). Persistent reminder so a creator flipping through videos doesn't forget which slice they're looking at.
  • 3 new locale keys × 6 locales: editor.endings.videoIndexLabel, editor.endings.videoIndexHint, output.previewingVideo. All 718/718 ui keys per locale (up from 715).

Changed

  • use-current-generator-input forwards endingVideoIndex only when endingVideoCount > 1 — single-video mode passes undefined so the slice helpers short-circuit to "render the union", keeping the input cleaner for tests.
  • EndingsEditor.setVideoCount now clamps endingVideoIndex down when the creator shrinks endingVideoCount (e.g. 6 → 2 with index = 4 → snaps to 2), so the preview never targets a non-existent video.
  • Persist version 12 → 13. Additive — endingVideoIndex back-fills to 1 on first rehydrate; pre-v0.17.1 drafts with a stale higher index get clamped to endingVideoCount by migrateEditorState.

Tests

  • 4 new tests in editor-store.endings.test.ts for the v12 → v13 migration (default back-fill, valid value preserved, clamp above max, clamp below 1). Total 426/426 pass.

Under the hood

  • The banner copy is locale-aware and pluralised inline via i18next interpolation ({{index}} / {{total}} / {{from}} / {{to}}).
  • OutputPage selects endingVideoCount, endingVideoIndex, endingVideoRanges as individual store slices so the page only re-renders when those specific fields change — no broader subscription drag.
  • Bundle: index 473.91 KB (+3 KB for Select + banner + migration). Under the 500 KB cap.

v0.17.0 — 2026-05-14

Combined release: logging overhaul + the deferred ending title piece from v0.16.0. The Output title now reflects the structured endings the creator filled in (case-A/B/C aware), and the Logs tab persists entries across app restarts with session-grouped navigation and JSON/TXT export.

Added

  • Structured ending titles (src/engine/title-builder.ts). When videoType === "ending" AND endings[] is filled, the title's video-type segment swaps from the static "Ending" to a context-aware label, picked by a four-tier resolver:
    1. Single entry → formatEndingEntry() (e.g. "Ending 3: Best End", "Ending 3", or "Best End" depending on which fields are filled).
    2. Multi-entry, every entry named → comma-joined names ("True End, Bad End, Hidden").
    3. Multi-entry, every entry numbered + contiguous run → title.endingLabel.range ("Endings 1–3" / "Kết thúc 1–3").
    4. Mixed / non-contiguous → title.endingLabel.count ("3 Endings"). Falls back to the legacy locale label when no usable entries — pre-v0.16 single-ending creators see byte-identical output. Slicing respects endingVideoIndex + endingVideoRanges so a per-video title renders only that video's slice (foundation for the v0.17.1 per-video Output selector).
  • Persistent log storage (src/utils/log-storage.ts). Logs now survive app restarts:
    • Tauri: append-only JSONL file {appData}/logs/ytdescgen-YYYYMMDD.jsonl. Daily rotation; cleanup deletes whole files older than logRetentionDays so retention sweeps are O(files) not O(entries). Three new Tauri commands feed this: append_to_file, list_dir, delete_file.
    • Web: localStorage key ytdescgen-logs, FIFO-capped at 5000 entries.
    • Best-effort: persistence failures never throw, so a disk hiccup can't recurse into a log loop.
  • Session-grouped LogPage (src/pages/LogPage.tsx). Each entry now carries a sessionId (one per app boot). The page renders one collapsible block per session — current session expanded, prior sessions collapsed — with a per-session "Clear this session" affordance. Header shows entry count + error/warning counts + time range per session.
  • Log export buttons:
    • JSON — envelope-wrapped via the v0.15 exportTypedToJsonFile (currently keyed _type: "history"; promote to a dedicated log type later when re-import becomes a use case).
    • TXT — [ISO time] [LEVEL] [source] message — details one line per entry, chronological. Pastes cleanly into bug reports.
  • logRetentionDays setting (src/store/settings-store.ts, src/store/settings-heal.ts). Default 7 days; clamped to [1, 90] by healSettings. New section in Settings → Logs with inline hint. Persist-store version bumped 9 → 10.
  • Boot-time log hydration (src/App.tsx). hydrateLogStore(retentionDays) runs in the root useEffect, loads recent persisted entries before the UI mounts, then schedules pruneOldLogs so the AppData folder stays trim.
  • Locale keys (10 new × 6 locales): title.endingLabel.{range,count} (2 templates keys), settings.{logSettings,logRetentionDays,logRetentionHint} + logs.{clearPersistedConfirm,clearSession,exportJson,exportTxt,sessionCurrent,sessionLabel,entriesShort} (10 ui keys). All 715 ui + 370 templates keys per locale.

Changed

  • log-store schema — LogEntry gained a sessionId field; in-memory cap raised from 500 → 2000 with persistence in play so a current session can fully populate the accordion without pagination. New actions: clearAllPersisted (in-memory + disk), clearSession(id).
  • LogPage "Clear All" now clears in-memory state AND deletes persisted JSONL files / localStorage. Two-step confirm via clearPersistedConfirm toast.
  • File envelope — SCHEMA_VERSIONS.settings bumped 9 → 10 to match the persist version. v0.15+ settings exports still import unchanged via the healSettings defensive merge.

Tests

  • 11 new title-builder tests covering all four ending-label tiers + Vietnamese localisation + slice + fallback. 422/422 pass overall.
  • 3 new settings-heal tests for the logRetentionDays default and [1, 90] clamp.

Under the hood

  • Tauri command surface gained 3 entries (append_to_file, list_dir, delete_file). All stdlib — no new crates.
  • pruneOldLogs runs after loadRecentLogs at boot, so an entry on the retention edge is read into memory before being deleted from disk (last-chance access).
  • Bundle: index 470.51 KB (+7 KB for title-builder ending logic), LogPage chunk 8.37 KB (+3 KB for session accordion + export buttons). Still under the 500 KB cap.

Migration notes

  • Settings persist version 9 → 10. Additive — logRetentionDays back-fills to 7 on first rehydrate, no user action required.
  • First-run on Tauri: app creates %APPDATA%\com.skullmute.ytdescgen\logs\ on the first log entry. The new append_to_file command auto-creates the parent dir via std::fs::create_dir_all.
  • Web users: persisted entries live in localStorage["ytdescgen-logs"]; nothing to migrate.
  • Pre-v0.16 ending creators: title behaviour unchanged unless they fill the new structured fields. Filling triggers the new resolver immediately.

v0.16.0 — 2026-05-14

Structured ending editor + multi-video split. The Playthrough Notes section's free-form "Endings shown" Input is replaced with a structured row table that knows about ending numbers, names, multi-video splits, and timeline cross-validation.

Added

  • EndingsEditor component (src/components/editor/EndingsEditor.tsx) — three logical cases driven by ending count + video count:
    • Case A (1 ending) — Number + Name pair with live preview. At least one of the two must be filled; otherwise an inline warning explains the bullet will be dropped.
    • Case B (≥2 endings, 1 video) — full table row per ending. A gate inspects the Timestamps textarea — if it doesn't contain at least endings.length lines tagged with the ending keyword, a warning banner surfaces ("Timeline needs N markers; only M found").
    • Case C (≥2 endings, ≥2 videos) — endings table + per-video range table. Default ranges are contiguous and balanced via the new computeContiguousRanges helper (extras spill into the last video for the climactic-final convention); the creator can override per-row. Overlap / gap / out-of-bounds errors surface inline.
  • Structured endings: EndingEntry[] schema in EditorData (v0.16.0). Each entry pairs an optional number (1–100) with an optional name. Empty entries are dropped silently. Companions: endingVideoCount, endingVideoRanges: EndingVideoRange[], endingVideoIndex? (engine-only — picks which video's slice to render).
  • Engine endings-format.ts — pure helpers formatEndingEntry, sliceEndingsForVideo, clampRange. Used by both the description builder and the editor's live preview so creators see exactly what will render.
  • Ending ordinal capture in timeline-parser.ts — the ending keyword pattern now captures an optional trailing number, so timeline lines like 1:23:45 Ending 3: Best End parse into { keyword: "ending", number: 3, rest: ": Best End" }. Unblocks the case-B timeline gate.
  • Locale keys (19 new × 6 locales) under editor.endings.* covering count / video-count labels, per-row labels, the preview line, warnings (singleEmpty, timelineShort, rangeInvalid, rangeGap, rangeOverlap, rangeShort), and helper hints. Schema bumped from 686 to 705 ui keys.
  • Tests — 42 new tests (367 → 409): endings-format.test.ts (15), editor-store.endings.test.ts (16), description-builder.test.ts (5 added inline), timeline-parser.test.ts (6 added inline).

Changed

  • PlaythroughNotesForm — the old single <Input label="Endings shown"> is replaced by <EndingsEditor />. 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) wrapping every <Route> 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) — 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:
  • Store-level import validators in profile-store.ts, preset-store.ts, 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<T> → 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<EditorData> | null | undefined so TS forces null-handling at call sites. Existing callers still work — Partial<T> 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). 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) 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 <html> 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/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 <SidebarNavList collapsed onItemClick?> so the same nav can render inside the desktop sidebar and the new mobile Drawer. Outer <aside> now hidden md:flex.
  • AppShell.tsx — wires mobileNavOpen state + renders <Drawer side="left"> containing <SidebarNavList /> for mobile. Header gets onOpenMobileNav prop.
  • Header.tsx — adds Menu hamburger (md:hidden), pt-[max(0.75rem,env(safe-area-inset-top))] for iOS notch, donate icon-only below md, language dropdown width min-w-[200px] max-w-[calc(100vw-2rem)] so it never overflows at 360px width.
  • Button.tsx / Input.tsx / Textarea.tsx / ValidatedInput.tsx — bump heights to min-h-touch (44 px) for md / lg; sm to min-h-[36px] (iOS minimum). Inputs / textareas use text-base sm:text-sm to prevent iOS Safari focus zoom (Safari zooms when font-size < 16 px).
  • EditorPage.tsx — responsive padding gap-6 p-6 lg:flex-row → gap-4 p-3 sm:p-4 md:gap-6 md:p-6 lg:flex-row. Sticky preview wrapper changed to lg:sticky lg:top-6 so mobile portrait doesn't lock the preview.
  • OutputPreview.tsx — description scroll-box max-h-[400px] → max-h-[60vh] sm:max-h-[400px].
  • CopyAllBar.tsx — pb-[max(0.75rem,env(safe-area-inset-bottom))] for iOS home indicator; button class compaction below sm.
  • README.md — full rewrite (~200 lines). Badges (Apache-2.0 / Node ≥ 22 / latest release / last commit), Use Cases (esp. horror gameplay), Privacy section, full doc table, AI disclosure, channel/socials block.
  • CLAUDE.md — license MIT → Apache-2.0; project-structure tree updated (PRD.md removed, DEVELOPMENT.md added with VI mirror sibling).
  • src/config/about.ts — license MIT → Apache-2.0. pcSpecDocUrl / devEnvDocUrl field names preserved for About-page layout compat but now point to docs/DEVELOPMENT.md (EN) and docs/i18n/vi/DEVELOPMENT.md (VI) respectively.
  • webapp/TAURI.md — cross-links updated to docs/DEVELOPMENT.md.

Removed

  • docs/PRD.md — Product Requirements Document V1.0 (2026-04-07). Shipped through v0.13.1; no longer load-bearing for public readers.
  • docs/pc_spec.md + docs/dev_env.md — merged into docs/DEVELOPMENT.md.
  • docs/i18n/vi/pc_spec.md + docs/i18n/vi/dev_env.md — merged into docs/i18n/vi/DEVELOPMENT.md.

Under the hood

  • _schema.json updated with the 23 new keys (1 new group label + 22 new option keys + 22 new long-description keys). All 6 locales × 2 files now at 686/686 ui + 368/368 templates.
  • No engine logic changes. description-builder.ts:415-431 already loops content warnings by user selection order — the new IDs are pure-data additions.
  • 350/350 tests still pass — no engine math changed.
  • Bundle: 443.55 KB raw / 136.55 KB gzip (under the 500 KB cap; ~+30 KB vs v0.13.1 from the docs imports being inlined).
  • Repository URL canonicalized — all README / CLAUDE / DEVELOPMENT references that pointed to github.com/poli0981/yt-desc-gen now correctly resolve github.com/poli0981/youtube-generator. src/config/about.ts still uses the canonical name; no behavior change.
  • Tauri app-data identifier (com.skullmute.ytdescgen) documented correctly in PRIVACY.md.

Migration notes

  • License change is not a code migration — your build environment doesn't need any action. If you redistribute the source, the new LICENSE + NOTICE apply per Apache 2.0 §§ 4(a)–4(d). Pre-v0.14 forks may continue under their snapshot's license; this is a forward change.
  • No store schema bump. Editor / settings / profile / preset / template store versions unchanged. Persisted drafts containing the legacy contentWarnings array round-trip unchanged — the array just renders against the expanded ID set.
  • Mobile users get the new layout automatically on next visit; nothing to opt in to.

v0.13.1 — 2026-05-11

Same-day hotfix for v0.13.0. Three small but load-bearing pieces:

Added

  • GitHub-side housekeeping — .github/FUNDING.yml (mirrors Donate.txt), .github/ISSUE_TEMPLATE/{config,bug_report,feature_request}.yml, docs/pc_spec.md + docs/dev_env.md (+ VI mirrors), webapp/TAURI.md. Auto-link-discussion job added to announce-release.yml (gh release edit --discussion-category "Announcements") so every future release auto-creates a linked Discussion thread.
  • AboutPage restructure — split into Repository / Donate / Connect / Dev Environment / Third-Party sections. Ko-fi / Patreon moved out of ABOUT.socials into a new @config/donate (PRIMARY_DONATE_URL constant feeds the Header donate button). Socials expanded with Bluesky, Mastodon, Steam, Telegram (bot + user), email, game-server Discord.
  • Header donate button — persistent pink Ko-fi link to the left of the language switcher.
  • Sidebar external link — Report Bug item added to the tabs array via a new external?: boolean field on TabItem; branches render between <NavLink> and plain <a target="_blank">.
  • Basic SEO — expanded <head> (description, OG, Twitter card, JSON-LD WebApplication, 6 locale alternates) + new useDocumentTitle(title) hook applied to all 9 page components + public/{robots.txt,sitemap.xml,manifest.webmanifest,favicon.svg} (favicon is a placeholder SVG).
  • Heavy-horror content-warning group (7 IDs: eye_horror, body_horror, face_horror, cosmic_horror, extreme_gore, decay_rot, mutilation) translated to all 6 locales in both short-label and long-description forms.

Changed

  • Workflow workflow_run filters narrowed — notify-ci-failure.yml / notify-deploy.yml / notify-release-pipeline.yml switched from workflows: ["*"] to specific producer names. Eliminates Skipped-row spam in the Actions tab.
  • @tauri-apps/api 2.10.1 → 2.11.0 to match Rust tauri 2.11.1 (Dependabot bumped Rust side; tauri-action requires the npm and Rust minors to match).

Fixed

  • Tauri-action releaseDraft: true is search-by-version, not search-by-tag. The initial v0.13.1 tag push silently uploaded 0.13.0-labelled binaries to the existing v0.13.0 release object because src-tauri/{tauri.conf.json, Cargo.toml, Cargo.lock} stayed at 0.13.0. Recovered with PR #58 (Tauri-side manifests to 0.13.1), then PR #59 (@tauri-apps/api bump), then force-moving the signed v0.13.1 tag twice via git tag -fs + git push origin v0.13.1 --force, finally gh workflow run release-desktop.yml -f tag=v0.13.0 to rebuild and restore v0.13.0's binaries.

Migration notes

  • Version-bump ritual is now SIX files, not five: package.json, package-lock.json, src-tauri/Cargo.toml, src-tauri/Cargo.lock (the yt-desc-gen entry only), src-tauri/tauri.conf.json, and — when Rust tauri minor moves — @tauri-apps/api in package.json (its minor must equal Rust tauri crate minor).

v0.13.0 — 2026-05-08

A scope-broadening release: two UI/Gacha bugs squashed, Gacha-quest editor extended with three structured fields (Anniversary year dropdown, Showcase character name, free-form gachaVersion), copy buttons hard-stop when text exceeds YouTube's title/description/tags limits, the Tauri desktop window is now locked at 1100×750 (no resize, no maximize), 27 new content warnings — including a brand-new "Playstyle disclosures" group — fill the phobia / mental-health / sensitive / playstyle gaps, and the My Rig editor's free-text GPU and RAM inputs are replaced with structured cascading dropdowns (Brand → Series → Model for GPU, Size + DDR generation for RAM) covering ~200+ GPU models across 14 series and 4 brands. Two QoL touches round it out: per-quest-type smart placeholders ("Day 12" for Daily Commission, "Floor 12" for Endgame, "Part 1" for Main Story) and inline validation badges that nudge the creator when a rig field is half-filled.

Added

  • Anniversary year dropdown (1–20) (src/components/editor/ExtraFieldsInput.tsx) — replaces the v0.12 chapterName text input for the anniversary quest type. Title and description templates render "{{anniversaryYear}}{{ordinalSuffix}} Anniversary" (e.g. "2nd Anniversary", "11th Anniversary") with a locale-aware ordinalSuffix() helper that returns st/nd/rd/th for English and an empty string for non-English locales (so "周年記念" / "주년" / "周年纪念" don't pick up an English suffix).
  • Showcase character name — when gachaQuestType === "showcase", the editor swaps Chapter/Quest/Part for a single characterName input. The description renders the user's exact requested phrasing: "This video showcases the skills, appearance, and details of {{characterName}} in {{gameName}}{{versionLabel}} on {{channelName}}." Title becomes "{{gameName}} — Character Showcase: {{characterName}}".
  • Gacha gachaVersion field (src/store/editor-store.ts) — free-form game version label like "1.2", "2.4", scoped to the Gacha Quest video type. Distinct from versionInfo (driver/general game version, rendered in the 🖥 VIDEO SETTINGS block for any video type). Surfaces in Gacha-specific intros via a new description.intro.versionInline template helper that renders only when non-empty (so the parenthetical "(version 1.2)" disappears entirely when the field is blank — no "(version )" artifact).
  • Cascading GPU dropdown (src/config/gpu-catalog.ts, src/config/rig-fields.ts) — three-level Brand → Series → Model picker covering NVIDIA (GTX 700/900/10/16, RTX 20/30/40/50), AMD (HD 7000, R7/R9 200/300, RX 400/500/Vega/5000/6000/7000/9000), Intel Arc (A and B series), and Apple Silicon (M1–M4 with Pro/Max/Ultra variants). A Custom brand swap-in keeps free-text entry available for niche cards. Stored as pipe-delimited "<brand>|<series>|<model>" so the rig store stays a flat Record<string, string> — no schema migration vs. v0.12. formatRigValue("gpu", …) outputs "NVIDIA RTX 4090" (drops the redundant series label).
  • Composite RAM input — two cascading dropdowns (Size + DDR) replace the free-text RAM field. Sizes: 4/6/8/12/16/32/64/96/128/256 GB plus a Custom… numeric input for unusual sticks. DDR generations: DDR1–DDR7. Output renders as "32 GB DDR5" / "48 GB DDR5" (custom). Same flat-string storage approach as GPU ("<size>|<ddr>", with "custom:48|DDR5" for custom numeric).
  • 27 new content warnings + Playstyle disclosures group (src/engine/types.ts, src/config/content-warning-groups.ts) — Phobias gain cynophobia / nyctophobia / pyrophobia / pediophobia / hemophobia (5). Mental health gains bipolar_themes / ocd_themes / panic_attacks / dissociation (4). Sensitive gains hate_speech / historical_atrocity / slavery_themes / terrorism_themes / bullying_themes (5). A brand-new Playstyle disclosures group (8 items) covers blind_playthrough / no_spoilers_chat / casual_difficulty / hardcore_difficulty / permadeath_run / speedrun_attempt / completionist_run / learning_mechanics — disclosure-style warnings that aren't really "content" but viewers benefit from knowing (e.g. "Blind playthrough — first time" sets expectations for repeated dying).
  • Smart placeholders per Quest Type (src/config/gacha-quest-types.ts) — GACHA_QUEST_PLACEHOLDERS map drives the Chapter / Quest / Part inputs to show context-specific hints based on the selected quest type: "Day 12" for Daily Commission, "Floor 12" for Endgame, "Part 1" and "Chapter 5 Act 2" for Main Story, etc. Placeholders only — no value clearing or auto-fill, so user input is preserved when switching types.
  • Inline rig validation badges (src/utils/rig-validation.ts) — validateGpuValue / validateRamValue flag half-filled selections (brand picked but no model, RAM size set but DDR missing, custom numeric empty) and the rig editor renders a small ⚠️ warning under the affected field. Soft warning only — the description still renders, but the badge nudges the creator to complete the field.
  • Copy-over-limit guard (src/hooks/use-clipboard.ts) — useClipboard().copy(text, { limit, fieldLabel }) now refuses to write to the clipboard when text.length > limit. Surfaces a toast like "Title is too long: 117/100 chars. Trim before copying." Each output button (Title / Description / Tags) passes its respective YT_LIMITS.* cap; the Copy All bar pre-validates Title and Description and shows a combined error if either is over. Over-limit copy buttons render with a text-danger style and a ⚠️ icon so the lock state is visible before the user clicks.

Changed

  • Editor store v10 → v11 (src/store/editor-store.ts) — additive only: characterName: "", anniversaryYear: null, gachaVersion: "" back-fills. Out-of-range or non-integer anniversaryYear values coerce to null so a hand-edited persistent blob with anniversaryYear: 99 doesn't render "99th Anniversary" in titles. Existing fields round-trip unchanged.
  • Tauri window locked (src-tauri/tauri.conf.json) — resizable: false, maximizable: false, and minWidth = maxWidth = 1100 / minHeight = maxHeight = 750 ensure the desktop binary opens at the design resolution and stays there. Eliminates layout drift from users dragging the window to ultra-wide ratios where the editor → preview split breaks.
  • AppShell layout reflow (src/components/layout/AppShell.tsx) — root min-h-screen swapped for h-screen overflow-hidden so the outer container can't grow beyond viewport height. The <main> scroll container now actually constrains content, fixing the v0.12 bug where long descriptions caused the entire page (sidebar + header included) to scroll instead of just the main pane.
  • Showcase template renders character, not quest — gachaQuestType.showcase title and description.intro.gacha_quest_showcase now consume characterName instead of questName. Pre-v0.13 drafts that picked showcase and filled questName will see characterName empty after upgrade — re-enter the character into the new field.
  • Anniversary template renders year + ordinal — gachaQuestType.anniversary and description.intro.gacha_quest_anniversary consume anniversaryYear (number) instead of chapterName (free text). The English title is now "<game> — 2nd Anniversary - Day N" driven by the new ordinal helper; locale variants render in their native conventions ("2周年記念", "2주년 기념", "Aniversario 2", etc.).
  • formatRigValue() extended — switches on field.type to handle the two new cascading / composite types. Pre-v0.13 free-text GPU and RAM values (no pipes) pass through unchanged so existing profiles render the same string they did before; the editor displays them under the Custom brand for further editing.

Under the hood

  • Schema-driven locale validation still passes with 629 ui keys + 339 templates keys across all 6 locales (en/es/ja/ko/vi/zh) — every new key is mirrored in the schema and translated where applicable. Validation errors are caught at the build / pre-merge step via npm run validate:locales.
  • tests/engine/rig-fields.test.ts grew from 7 → 18 cases — new coverage for cascading_dropdown (brand+model formatting, custom-brand verbatim, brand-only fallback, legacy free-text passthrough) and composite_dropdown (size+DDR, custom numeric, partial values, legacy passthrough).
  • tests/store/editor-store.migrate.test.ts grew from 9 → 13 cases — new v10 → v11 migration tests assert the Gacha field back-fills, the 1–20 anniversary-year range guard, and the round-trip preservation of valid persisted values.
  • tests/engine/title-builder.test.ts updated — the Anniversary test now passes anniversaryYear: 7 instead of chapterName: "7th" to match the new template shape.
  • Test count: 350/350 (was 335/335).

Migration notes

  • v10 → v11 is automatic and additive; the migration runs once on first launch of v0.13. Existing drafts are preserved.
  • Showcase users: the questName you previously typed for showcase videos won't be carried into characterName. Open the editor, pick Showcase, and re-enter the character — the field name change is intentional (Showcase = character, not quest).
  • Anniversary users: the free-text chapterName you used to type "2nd" / "Year 2" / etc. is no longer used by the Anniversary template. Pick the year from the new dropdown instead.
  • Free-text GPU / RAM users: existing profiles render identically. The editor will show your old free-text under the Custom brand / RAM legacy fallback; switch to the structured dropdowns when convenient.

v0.12.1 — 2026-05-06

Hotfix for v0.12.0. Ticking a Tech Notes checkbox (or filling any of the new Playthrough Notes structured fields — Endings shown, Language patch, Game version) updated the editor state but never reached the description preview, because the editor → engine mapping in useCurrentGeneratorInput wasn't kept in sync when the new fields were added. The unit-test suite caught nothing because every v0.12 description-builder test passed GeneratorInput directly to the engine, bypassing the hook.

Fixed

  • Editor → engine pipeline carries every v0.12 field (src/hooks/use-current-generator-input.ts) — endingsShown, languagePatch, languagePatchCustom, gameVersion, gameVersionCustom, and techNotes are now forwarded into GeneratorInput. Symptom of the bug was that the description preview (and Output / Batch tabs) didn't change when the user ticked tech-note items or filled language-patch / game-version, even though the editor checkboxes / selects reflected the change correctly.
  • Save-as-template captures every v0.12 field (src/components/templates/TemplateSaveForm.tsx) — the snapshot builder explicitly enumerates each editor field and was missing the same six fields. A v0.12.0 user saving a template lost their Tech Notes / Playthrough Notes selections; loading the template later didn't restore them.

Changed

  • Hook field-mapping extracted into a pure helper — buildGeneratorInputFromEditor(state, languageOverride?) is now exported alongside the React hook. Pure function so it's directly unit-testable; the hook just wraps it in useMemo. Same change pattern used for migrateEditorState in v0.12.0 — pull the load-bearing logic out of React-coupled wrappers so tests can hit it without a render harness.
  • Hook useMemo deps simplified — the previous list enumerated every field individually (50+ entries); a missing field would silently freeze that field's value in the memoised output. Replaced with a single [state, languageOverride] since useEditorStore() returns a fresh state reference on every store update — equivalent invalidation, fewer footguns.
  • TemplateSnapshot carries the v0.12 fields as optional (src/store/template-store.ts) — endingsShown, languagePatch, languagePatchCustom, gameVersion, gameVersionCustom, techNotes joined the snapshot type. Optional for back-compat with templates saved before this hotfix; the editor's loadProfile spread keeps existing values when the patch lacks them.
  • EditorData is now export interface in src/store/editor-store.ts so the shared snapshot helper can reference it.
  • package-lock.json synced to the v0.12 / v0.12.1 version line — was carrying a stale v0.11.0 root version since the v0.12.0 PR forgot it (the v0.9.0 lockfile-bump-miss memory note reminded us, but only after the v0.12.0 ship).

Under the hood

  • New tests/hooks/generator-input-mapping.test.ts (6 cases) — direct assertions that each v0.12 field reaches GeneratorInput (endingsShown, languagePatch + custom, gameVersion + custom, techNotes selection-order), plus a parity guard that walks every key of an EditorData instance and fails if any non-allowlisted field is dropped from the resulting GeneratorInput. The allowlist is exactly two keys (thumbnailText, pinnedComment — both feed the pinned-comment builder via a separate code path); anything else added in the future will trip the assertion immediately.
  • Test count: 335/335 (was 329/329). Bundle: 345.50 KB raw / 115.52 KB gzipped (essentially flat versus v0.12.0 — only swapped a deps array for a single ref).

Migration notes

  • No state migration needed. loadProfile / loadPreset continue to spread snapshots over current state, and the new fields are all optional on TemplateSnapshot. A v0.12.0 user with templates saved during the bug window will see those templates load with empty Tech Notes / Playthrough Notes — re-save the template after upgrading to capture the fields properly.

v0.12.0 — 2026-05-06

A bug fix and a description overhaul. The Tauri desktop build picks up tauri-plugin-single-instance so launching the app twice no longer stacks tray icons / orphan processes — second launches refocus the existing window. The description's Playthrough block consolidates the v0.7 standalone "🎯 Playthrough" line and the standalone "🎮 DIFFICULTY" block into a unified ▸ 🎮 PLAYTHROUGH NOTES section with three new structured fields (endingsShown, languagePatch, gameVersion), and a new ▸ 🛠 TECH NOTES bilingual checklist (24 items across 5 groups) sits alongside Content Warnings for production / playstyle disclaimers.

Added

  • Single-instance enforcement (desktop) — src-tauri/Cargo.toml adds tauri-plugin-single-instance = "2", registered first in the Builder chain in src-tauri/src/lib.rs with a get_webview_window("main") → show + unminimize + focus callback. Closing-to-tray then double-clicking the launcher / start-menu shortcut surfaces the existing window instead of spawning a fresh process with its own tray icon.
  • Unified ▸ 🎮 PLAYTHROUGH NOTES description block — replaces the v0.7 standalone "🎯 Playthrough:" line and the v0.7 standalone "🎮 DIFFICULTY" block with one bulleted section that renders five fields: Run type (reads from existing playthroughStatus), Difficulty (reads from existing difficulty + difficultyCustomLabel), Endings shown (NEW free text), Language patch (NEW enum + custom slot), Game version (NEW enum + custom slot). Empty bullets are skipped; the whole block is skipped when every field is empty. Bilingual EN · LOCAL rendering for both label and value when tEn is provided and output language ≠ English. Section sits in slot 1.5 (right after the intro), matching the position of the pre-v0.12 standalone playthrough line.
  • ▸ 🛠 TECH NOTES checklist — a 24-item, 5-group bilingual multi-select for production / playstyle disclaimers: audio (5: copyright muting, volume reduction, music replacement, cutscene-only mute, original-audio kept), video quality (3: low resolution, low graphics, FPS drops with FPS counter pointer), recording issues (4: bug-from-game, crash kept, loading cut, OBS artifacts), playstyle (8: not no-hit, not clean walkthrough, casual no-commentary, many deaths, slow exploration, puzzle-stuck, grinding cut, not speedrun), production (4: exploration-focused, edited-for-pacing, support-developers, online-connectivity-issues). Same render pattern as v0.11 Content Warnings — header / two-line intro / EN · LOCAL bullets with U+00B7 MIDDLE DOT separator. Section sits right after Content Warnings; both transparency blocks group together.
  • languagePatch enum with options none / official_en / official_other / fan_translation / mtl / custom and a paired free-form languagePatchCustom slot — covers the most common patch states (canonical EN release, official non-EN locale, fan TL, machine TL) plus an escape hatch for niche cases. none is the skip-bullet sentinel; official_other and custom both surface the free-form input under the Select.
  • gameVersion enum with options full_release / demo / early_access / beta / prologue / pre_release / custom and a paired gameVersionCustom slot — full_release is the implicit default (no bullet rendered) so creators recording the released game don't have to fill anything; "Steam Next Fest demo" / "Kickstarter backer build" / similar niche cases go through custom.
  • Free-text endingsShown field — captures values like "1 of 3", "True ending only", "All routes 100%", "Normal + True". Free text on purpose — the natural value space is too varied for an enum, and a custom escape hatch would catch 80% of selections anyway.

Changed

  • Editor store v9 → v10 — additive only: endingsShown: "", languagePatch: "none", languagePatchCustom: "", gameVersion: "full_release", gameVersionCustom: "", techNotes: [] back-fills. Existing playthroughStatus / difficulty / difficultyCustomLabel values round-trip unchanged — only the description-builder render path moves them into the unified block. Invalid persisted enum values coerce to their skip-sentinel default; unknown techNotes ids are filtered out (defensive against hand-edited blobs). The migrate function is now extracted into a named migrateEditorState export so the v9→v10 path can be unit-tested without going through localStorage.
  • ContentDetailsForm.tsx is removed and replaced with the v0.12 PlaythroughNotesForm.tsx — the new component owns all five PN fields (Run type, Difficulty + custom, Endings shown, Language patch + custom, Game version + custom) in one block, with the custom-slot inputs only appearing when their parent enum carries one. The Editor page mounts PlaythroughNotesForm then ContentWarningChecklist then TechNotesChecklist inside the Content Details accordion.
  • description-builder.ts — the v0.7 standalone playthrough conditional (if (input.playthroughStatus !== "none") sections.push(...)) and the standalone difficulty conditional (if (input.difficulty !== "none") sections.push(...)) are gone; replaced with one call to a new buildPlaythroughNotesSection(input, t, tEn) helper at slot 1.5. A new buildTechNotesSection(input, t, tEn) helper at slot 7.5 mirrors the v0.11 content-warnings render pattern.

Removed

  • description.sections.playthrough / description.sections.difficulty template keys — section heading is now bullet-formatted inside the ▸ 🎮 PLAYTHROUGH NOTES block via description.playthroughNotes.labels.*. The per-status / per-level value labels (description.playthrough.{blind,replay,…}, description.difficulty.{easy,normal,…}) are kept — the new block reads them for the "Run type" and "Difficulty" bullet values.
  • ContentDetailsForm.tsx — superseded by PlaythroughNotesForm.tsx.

Under the hood

  • New src/config/tech-note-groups.ts carries the 5-group UI structure (audio / video_quality / recording_issues / playstyle / production). Engine doesn't read groups — output follows selection order — but the editor uses them to render collapsible sections.
  • New src/config/playthrough-options.ts exports LANGUAGE_PATCH_UI_OPTIONS / GAME_VERSION_UI_OPTIONS (Select-friendly {id, labelKey} shapes) plus languagePatchHasCustomSlot / gameVersionHasCustomSlot predicates so the editor knows when to show the paired custom-text input.
  • src/engine/types.ts adds LANGUAGE_PATCH_OPTIONS / LanguagePatch, GAME_VERSION_OPTIONS / GameVersion, TECH_NOTES / TechNote const-and-type pairs, plus six new optional fields on GeneratorInput.
  • All 6 locales (en / vi / ja / es / ko / zh) updated with description.playthroughNotes.{header,intro,labels,languagePatchOptions,gameVersionOptions} + description.techNotes.{header,intro,items} (24 items) + matching editor short labels (editor.playthroughNotes.*, editor.techNoteOptions.*, editor.techNoteGroups.*). validate:locales clean at 585 ui + 316 templates per locale.
  • Engine tests grow by 14 cases: PN block bullet formatting (en single-language, all five filled), PN block omission when every field is empty, regression that the old standalone 🎯 Playthrough: and 🎮 DIFFICULTY lines no longer render, custom-difficulty label passthrough, custom-difficulty blank-label skip, PN bilingual VI mode, PN with languagePatch: official_other + custom slot, PN with gameVersion: custom + custom slot, TN selection-order preservation, TN bilingual VI / JA modes, TN single-language fallback when tEn omitted, TN block omission when list is empty. Plus a new tests/store/editor-store.migrate.test.ts with 9 cases covering the v9→v10 migration: default back-fills, preservation of existing playthrough / difficulty / contentWarnings, invalid enum coercion, unknown tech-note id filtering, idempotency on a v10 blob, and null / undefined handling. Full suite: 329 / 329 green.
  • Bundle: main chunk 345.85 KB raw / 115.78 KB gzipped (under the 500 KB constraint).

Migration notes

  • No manual action required. First launch after upgrade migrates state in place: pre-v0.12 drafts gain the new PN + TN field defaults; existing playthroughStatus / difficulty keep their values, the description just renders them under the unified PN header now.
  • The Tauri single-instance fix only takes effect after a fresh install of the v0.12 build; existing v0.11 desktop installs need to be uninstalled / replaced. Web builds are unaffected.

v0.11.0 — 2026-05-06

Three independent features: vendor-aware graphics dropdowns (DLAA + XeSS Ultra Quality joined the ladder, multipliers cap per vendor), a third-party advertising block driven by a per-profile copy field, and a major content-warning overhaul — the v0.7 trio (spoilerWarning / matureWarning toggles + 3-item checklist) becomes a unified bilingual checklist of 44 items across 5 categories with EN · output-language rendering and asterisk-masked Vietnamese terms for YouTube ToS safety.

Added

  • Vendor-aware upscaling & frame-gen options — when the creator picks an FG vendor, the upscale-quality and frame-gen-multiplier dropdowns filter to that vendor's actual ladder. NVIDIA exposes DLAA + Quality / Balanced / Performance / Ultra Performance and goes up to x4 multi-frame-gen; AMD keeps FSR Native AA + 4 quality bins and caps at x3 (FSR 3.1); Intel adds XeSS Ultra Quality (its own tier) and ships only x2 (XeFG). Description-builder uses vendor-keyed full labels — NVIDIA DLAA, AMD FSR Quality, Intel XeSS Ultra Quality, AMD Fluid Motion Frames x3 — instead of the old "brand prefix in code" pattern, so dlaa reads NVIDIA DLAA not NVIDIA DLSS DLAA. Pre-v0.11 drafts / presets / templates with stale combos (e.g. NVIDIA + native_aa) coerce to none on rehydrate via coerceUpscaleQuality + coerceFrameGenMultiplier in src/engine/graphics-vendor.ts.
  • Third-party advertising block — new showThirdPartyAds toggle in Settings → Description renders a 🤝 SPONSORS & PARTNERS block in the description, sourced from a new thirdPartyAdText Textarea on the channel Profile (multi-line preserved verbatim). Block is gated on toggle ON AND profile field non-empty; toggling on without text is a no-op and surfaces an inline hint pointing the user to Profiles → Edit. Per-profile (not per-video) — partner copy is channel-stable.
  • Bilingual content-warning checklist — replaces WarningToggles with ContentWarningChecklist: a searchable, collapsible-grouped checkbox grid covering 44 items across Spoilers / Photosensitive / Phobias / Mental health / Mature & Sensitive. Description format becomes ▸ ⚠️ CONTENT WARNINGS / CẢNH BÁO NỘI DUNG header (bilingual when output language ≠ English), a two-line intro, then bullets • {EN} · {local} separated by U+00B7 MIDDLE DOT — matches the visual format in the v0.11 spec exactly. Selection order is preserved in the rendered output. Vietnamese translations apply asterisk masking on YouTube-ToS-prone terms (t* tử, x*m h*i t*nh d*c, g*ết người, b*o h*nh, ng*y h*i); other locales use clinical wording (Sexual assault references, Self-harm / suicide themes, Violence against minors).

Changed

  • Editor store v8 → v9 (three concerns rolled into one bump): thirdPartyAdText: "" default, legacy spoilerWarning: true → push "spoiler_story" into contentWarnings (same for matureWarning → "mature_18plus"), and vendor-incompatible upscale-quality / multiplier combos coerce to "none". normalizeEditorPatch runs the same coercion + boolean-merge logic on every loadProfile / loadPreset / loadTemplate call so legacy snapshots round-trip cleanly.
  • Settings store v8 → v9 (additive — showThirdPartyAds: false default; healed via initialSettings spread).
  • Profile store unversioned → v1 (additive — thirdPartyAdText: "" back-fill for pre-v0.11 profiles).
  • Template store unversioned → v1 (vendor-quality coercion on persisted snapshots).
  • UPSCALE_QUALITIES enum gains "dlaa" and "ultra_quality". The flat enum stays — vendor filtering happens at the UI / engine layer via getValidUpscaleQualities(vendor) so storage shape doesn't fork per vendor.
  • ContentDetailsForm drops its content-warning ChipGroup (the new ContentWarningChecklist mounted in the Editor's Content Details accordion is the new home). Playthrough + difficulty stay where they were.
  • description-builder drops the v0.7 "skip brand on second mention" optimization — both halves of upscale + framegen now carry the brand. Worth the mild verbosity for AMD / Intel: AMD's frame-gen brand is Fluid Motion Frames (not Frame Generation), Intel's is XeFG; the old code emitted Frame Generation regardless. The 3 separate warning blocks (spoilerWarning header, contentWarnings bullet list, matureWarning header) collapse into one unified bilingual block, placed at the same description position.

Removed

  • WarningToggles.tsx — superseded by ContentWarningChecklist.tsx. Editor-state fields spoilerWarning / matureWarning stay (marked @deprecated) so v8-shaped persisted drafts round-trip through the migration without data loss; they're no longer exposed in the UI and no longer drive description rendering.
  • description.sections.spoilerWarning / matureWarning / contentWarnings template keys — section heading lives at description.contentWarnings.header now. The old per-warning description.contentWarnings.{flashing_lights,loud_noises,jump_scares} keys moved under description.contentWarnings.items.* alongside 41 new entries.

Under the hood

  • New src/engine/graphics-vendor.ts exports getValidUpscaleQualities / getValidFrameGenMultipliers / coerceUpscaleQuality / coerceFrameGenMultiplier — pure functions reused by the editor-store migration, the template-store migration, normalizeEditorPatch, the VideoSettingsForm Select option lists, and the handleVendorChange reset path so changing vendors mid-edit doesn't leave the Selects stuck on a stale value.
  • New src/config/content-warning-groups.ts carries the 5-group UI structure (spoilers / photosensitive / phobias / mental_health / sensitive). Engine never reads the groups — output ordering follows user selection — but the editor uses them to render collapsible sections with per-group counts so 44 items stay scannable.
  • BuildDescriptionOptions extends with tEn?: TranslationFn — the engine stays framework-agnostic; the caller (use-generated-output) builds it via i18next.getFixedT("en", "templates") and passes it in alongside the locale-fixed t. Falls back to t when omitted, so existing callers / unit tests keep working.
  • All 6 locales (en / vi / ja / es / ko / zh) updated with vendor-keyed description.graphics.upscale.{vendor}.{q} + description.graphics.frameGen.{vendor}.{m} maps, vendor-keyed editor short labels (editor.upscaleQuality.{vendor}.* / editor.frameGenMultiplier.{vendor}.*), 5 group headings, 44 bilingual warning items, 44 short editor labels, plus settings.showThirdPartyAds / settings.thirdPartyAdsHint and profiles.thirdPartyAdText{,Placeholder,Help}. validate:locales clean at 529 ui + 274 templates per locale.
  • Engine tests grow by 9 cases: vendor-aware DLAA / XeSS Ultra Quality / AMD label rendering, content-warning bilingual EN · VI block, EN-only single-language output, single-language fallback when tEn is omitted, censoring snapshot for VI, third-party-ads gating (toggle on + text non-empty, toggle off + text non-empty, toggle on + text empty), multi-line preservation, and selection-order preservation. Two legacy-deprecation tests replace the old spoilerWarning / matureWarning standalone-block tests. Full suite: 310 / 310 green.
  • Bundle: main chunk 313 KB (under the 500 KB constraint).

Migration notes

  • No manual action required. First launch after upgrade migrates state in place: pre-v0.11 drafts with spoilerWarning: true / matureWarning: true get the equivalent items checked in contentWarnings; vendor-incompatible upscale combos coerce to none; profile / settings stores back-fill their new defaults.
  • Channel partners / affiliates: the toggle in Settings → Description does nothing until you fill Third-party ad copy in your profile (Profiles → Edit). The inline hint in Settings calls this out when the toggle is on but the text is empty.

v0.10.0 — 2026-05-05

Three independent features shipped in #44: a publisher-name tag for the Store Links editor, a hotfix for the live web build that had been serving a blank page since the v0.5 scaffold, and a vertical collapsible sidebar with a new About page.

Added

  • Pub/Dev Name → tag (#44) — when the Publisher / Developer site URL is filled in, a free-text "Pub/Dev Name" input appears underneath. Whatever the user types becomes a bare YouTube tag (e.g. Ubisoft, FromSoftware) via the existing dedup + 30-char trim pipeline. Independent from sponsorName / sponsorPlatform, which still drive the description's "🎁 Thanks to …" line — different semantic, different output.
  • Vertical collapsible sidebar (#44) — replaces the horizontal top tab bar. Hamburger toggle (PanelLeftClose / PanelLeftOpen from lucide), w-56 ↔ w-14 width transition, persisted across reloads via the settings store. Ctrl+B shortcut wired (VS Code convention) and surfaced in the keyboard help cheatsheet.
  • About page (#44) — new /about route with app metadata (version pulled live from package.json), repo / issues / author / license links, configurable social links (YouTube / X / Discord / Ko-fi / Patreon — empty entries hide their row), and a third-party credits list with versions read live from package.json deps. shadcn/ui evaluated and skipped — would have forced a 10+ component retrofit and a token-system swap (--background / --foreground / --primary) for one feature.

Fixed

  • GitHub Pages white page (#44) — the deployed site at https://poli0981.github.io/youtube-generator/ was blank because Vite's base was hardcoded to /yt-desc-gen/ (an old project name carried over from the v0.5 scaffold). Every asset 404'd. Aligning the base with the actual repo name unblocks the live web build. public/.nojekyll added defensively.

Changed

  • Editor store v7 → v8 (additive — pubDevName: "" default).
  • Settings store v7 → v8 (additive — sidebarCollapsed: false default; healed automatically through initialSettings spread).
  • AppShell layout changed from flex flex-col (Header / TabBar / main) to a left-sidebar / right-pane (Sidebar / Header / main). Header stays at the top of the right pane.

Under the hood

  • tag-generator.ts gains a pubDevName step before the dedup pass; reuses tagFriendlyGameName(name, 30) for the per-tag char limit. 4 new tag-generator tests cover emission, empty / whitespace skip, dedup against sponsorName, and over-long truncation.
  • TabBar.tsx renamed to Sidebar.tsx (git mv to preserve blame).
  • New src/config/about.ts (single source of truth for app metadata + socials) and src/config/third-party.ts (credits with versions auto-derived from package.json).
  • All 6 locales (en / vi / ja / es / ko / zh) updated with editor.pubDevName + editor.pubDevNamePlaceholder (F1), plus tabs.about, sidebar.{expand,collapse}, the full about.* namespace including about.socials.*, and shortcuts.toggleSidebar (F3). validate:locales clean at 448 / 448 keys.
  • Full suite: 301 tests green; main bundle 277 KB.

Migration notes

  • No manual action required. First launch after upgrade heals any missing keys in place.
  • Pre-v0.10 drafts get pubDevName: "" and sidebarCollapsed: false by default — the fields only become visible once the user fills the publisher URL or toggles the sidebar.

v0.9.0 — 2026-05-03

Two-phase release. Phase 1 covered the gacha video type and four new URL extractors with a typed-name-mismatch banner; phase 2 wrapped the version with a QoL trio and a four-platform CI release matrix. PRs that landed: #37 (phase 1 B2), #40 (phase 1 B1, re-ship of #38), #41 (phase 2).

Added

  • Gacha-quest video type (#40) — new VideoType: "gacha_quest" with a 17-value gachaQuestType enum grouped by use case (Story / Events / Tutorial-Trial / Endgame-Multiplayer / Showcase) plus free-form chapterName and questName extras. partNumber is reused, with the suffix wording driven by quest type — main_story → "- Part N", anniversary + daily_commission → "- Day N", endgame → "- Floor N", every other quest type drops the suffix. Per-quest-type title format and intro template, single shared pinned-comment greeting.
  • 4 new URL extractors (#37) — Epic Games Store (locale-prefixed /p/<slug>, strips trailing 6+-char hex hash), Nintendo US (/us/store/products/<slug>, strips -switch / -switch-2 platform suffix), Nintendo EU (/<locale>/Games/<segment>/<slug>-<id>.html, strips trailing numeric id), and Humble Bundle. PlayStation / Xbox / Amazon Luna stay unsupported because their canonical URLs use opaque product IDs.
  • Name-mismatch warning banner (#37) — StoreLinkEditor shows a reactive banner above the platform grid when any filled link extracts to a name whose tokens aren't a subset of the typed Game Name. New isLinkNameMismatch(gameName, url) helper applies a subset-tolerant token comparison; apostrophes are stripped (not spaced) so Marvel's matches Marvels in Steam slugs. Per-pair dismissal (gameName|url fingerprint); banner re-shows automatically when either side changes.
  • Keyboard-shortcuts cheatsheet (#41) — bare ? key now opens the existing modal (Ctrl+/ still works); the ? handler skips firing when the keydown target is an input / textarea / select / contentEditable element. The modal grows a search input that filters by translated label OR by the literal key combo string.
  • Genre selector search + bulk-toggle (#41) — case-insensitive substring filter above the chip group, plus three bulk-select buttons ("All RPGs" / "All Shooters" / "All Horror") that replace the current selection with the first MAX_GENRES (3) ids of the matching GENRE_GROUPS entry. Filter clears on bulk-toggle.

Changed

  • Editor store v6 → v7 (additive — gacha extras gachaQuestType / chapterName / questName).
  • TemplateSnapshot — extends with the gacha extras as optional so legacy templates load cleanly.

CI / Release

  • release-desktop.yml (#41) grows from a Windows-only build to a four-entry matrix: windows-latest, macos-13 (Intel), macos-14 (ARM), ubuntu-latest. fail-fast: false so one platform breaking doesn't cancel the others. Linux runner installs libwebkit2gtk-4.1-dev + companions for Tauri's webview + AppImage tooling. tauri-action@v0 collects all artifacts onto a single draft GitHub Release named YTDescGen v__VERSION__. No code signing; release notes come from the tag message.

Under the hood

  • New src/config/gacha-quest-types.ts houses the 17-value enum, display-order grouping, and the per-quest-type partNumber suffix style map (GACHA_PART_SUFFIX_STYLES).
  • New src/config/genres.ts:GENRE_GROUPS typed Record<GenreGroupId, readonly GenreId[]> drives the bulk-toggle buttons.
  • All 6 locales updated: 428 ui + 203 template keys each (up from 391 + 164 in v0.8). en + vi fully translated; ja / es / ko / zh seeded with English placeholders for the new strings.
  • Full suite: 297 tests green; main bundle 270 KB.

Migration notes

  • No manual action required. First launch after upgrade heals any missing keys in place.
  • Pre-v0.9 drafts get gachaQuestType: "main_story" and empty chapterName / questName defaults. The fields only matter when videoType === "gacha_quest".

v0.8.1 — 2026-05-02

Patch release fixing a v0.8 regression in the genre-playlist suggestion feature.

Fixed

  • Genre-playlist URL validator (#36) accepted only https://www.youtube.com/playlist?list=… with the literal www. subdomain and rejected any extra query parameters. Real share URLs from YouTube emit https://youtube.com/… (no www.) or …&si=… tracking params, both of which silently failed validation and the ValidatedInput component then wiped the entry from the settings store. Now accepts: optional www., list=… at any position in the query string with sibling params before/after, and a trailing fragment. watch?v=… and youtu.be/… short URLs still rejected (path must be /playlist).

Under the hood

  • 4 new validation tests cover the relaxed regex (no-www, mixed query order, trailing fragment, &si= tracking suffix). Full suite: 253 tests green.

v0.8.0 — 2026-05-02

Three-PR release covering graphics rebuild, livestream support, pinned-comment polish, and Vietnamese-specific donate fields. PRs that landed: #32 (phase 1), #33 (phase 2), #34 (polish), #35 (version bump).

Added

  • Graphics Settings v2 — preset is now an enum (Low → Extreme + Custom) instead of free-form text, default Medium. New multi-select Ray Tracing modes (Ray Tracing / Full Ray Tracing / Path Tracing / Ray Reconstruction), Frame Generation vendor + multiplier (NVIDIA / AMD / Intel × x2 / x3 / x4 / x6), Upscaling Quality (DLSS / FSR / XeSS quality presets), Art Style dropdown, free-form Driver / Game Version field, and a Skip-graphics toggle for 2D / pixel-art / web games (auto-suggested when a visual_novel / fmv / rhythm genre is added). Description renders a labelled multi-line block: Video: 1080p - 60 FPS / In-game Setting: Cinematic - NVIDIA Frame Generation x2 with Ray Tracing / Art Style: … / Version: ….
  • Livestream — new VideoType with liveUrl + scheduledTime extras. Title gets 🔴 LIVE segment, description gets 🔴 LIVE on {{time}} / Watch / replay: {{link}} block (locale-aware datetime via Intl.DateTimeFormat), tag pool gets livestream / live gameplay / ${gameName} live / ${gameName} stream, pinned-comment template gets a livestream-specific greeting.
  • Pinned-comment genre playlists — Settings → Genre Playlists section configures one YouTube playlist URL per genre. When the new pinnedCommentIncludeGenrePlaylist toggle is on, the template auto-suggests 📺 More <genre> gameplay on the channel: <link> for the video's primary genre.
  • Vietnamese donate — five new editor fields (bank name, account number, account holder, MoMo, ZaloPay) in a new VietnameseDonateEditor component. Description block 🏦 CHUYỂN KHOẢN / VÍ ĐIỆN TỬ (Việt Nam) only renders when output language is vi; bank line drops the parens when holder is empty; e-wallet lines render independently.
  • Mod List textarea — new modList field exposed alongside modName for the mods videoType. Description gets a 🧩 MOD LIST block right after MY RIG.
  • Publisher / Developer site — 10th store-link platform with a permissive HTTPS pattern for indie / niche releases.
  • URL paste auto-extract — pasting a Steam / itch.io / GOG URL into a store-link input auto-fills an empty Game Name with a 5s Undo toast. Other storefronts skipped because their URL slugs aren't stable.
  • YouTube playlist URL validator — validatePlaylistUrl for the editor's playlist-link field and the new Genre Playlists settings. (Note: a regression in the strict regex shipped here; corrected in v0.8.1.)

Fixed

  • Long-game-name tag bug (#32) — composite tags built from a long game name (Tony Hawk's Pro Skater 1+2 Remastered: Definitive Edition) used to silently disappear because they exceeded YouTube's 30-char per-tag limit. New tagFriendlyGameName helper strips trademark marks + edition qualifiers, then composes ≤21-char form for composite tags + bare ≤30-char form. The game name now always lands in the tag list.

Changed

  • Editor store: v4 → v5 (graphics enum + livestream + new fields, legacy graphicsPreset text mapped via legacyGraphicsPresetToEnum); v5 → v6 (additive — VN donate fields + modList).
  • Settings store: v6 → v7 (additive — genrePlaylists map + the new pinned-comment toggle).
  • TemplateSnapshot — extended to capture the v0.7 phase 2 fields that had been missing (playthroughStatus, difficulty, difficultyCustomLabel, contentWarnings) plus all v0.8 fields. Saving a template now preserves full editor state.
  • Video Settings description block — was a single pipe-separated line 1080p | 60 FPS | Cinematic Setting - …, now multi-line with explicit labels matching the rig + timestamps shape.

Under the hood

  • New src/config/graphics-settings.ts houses every graphics-related enum + the GENRES_WITHOUT_GRAPHICS_SETTINGS allowlist for the auto-suggest hint.
  • New src/utils/url-extractors.ts implements Steam / itch.io / GOG slug extraction with a shared titleCase helper.
  • Brand-name table (VENDOR_GFX_BRANDS) is engine-internal and English-only across locales (DLSS / FSR / XeSS preserved verbatim for SEO).
  • All 6 locales updated: 391 ui + 164 template keys each. Vietnamese fully translated; ja / es / ko / zh seeded with English defaults for the new strings.
  • Full suite: 249 tests green; main bundle 239 KB.

Migration notes

  • No manual action required. First launch after upgrade heals any missing keys in place.
  • Pre-v0.8 free-form graphicsPreset text values map automatically: known labels ("Ultra", "Very High", …) become enum values; anything else lands in the new Custom slot ("Epic" → graphicsPreset: "custom" + graphicsPresetCustom: "Epic").
  • Existing Profile and TemplateSnapshot shapes are TS-extended to the v0.8 enum types; legacy on-disk values round-trip via normalizeEditorPatch on loadProfile / loadPreset.

v0.7.0 — 2026-04-24

Two-phase release. Phase 1 landed as #30; this entry is cumulative across both phases.

Added

  • Title format settings (phase 1): configure where the quality badge sits (prefix / middle / suffix), which separator joins the segments (— / - / : / |), and the badge case (2K / 2k). Defaults reproduce v0.6 output byte-for-byte. Setting the trio to prefix + hyphen + lower produces e.g. [2k] - Elden Ring - phần 1 - Gameplay No Commentary.
  • Settings page reorganized (phase 1) from 5 → 7 sections: Appearance, Language & Defaults, Editor, Title, Description, Tags, History.
  • Content Details (phase 2): three new editor fields for framing a run.
    • Playthrough status — Blind / Replay / New Game+ / Post-game. Renders a 🎯 Playthrough: … line right after the intro.
    • Difficulty — Easy / Normal / Hard / Nightmare / Custom. Custom reveals a free-form label so game-specific names like "Lethal" or "NG+7" survive a locale switch unchanged.
    • Content warnings — multi-select chips for Flashing lights / Loud noises / Jump scares. Renders a ⚠️ CONTENT WARNINGS bulleted block between spoiler and mature warnings.
  • Pinned-comment template system (phase 2): opt-in Settings toggle generates a ready-to-paste pinned comment per video. Per-video-type greetings (boss / ending / speedrun / …) sit atop four shared CTA lines (thanks / playlist / engage / ask-next-game). Shown as a third section on the Output page alongside the user's freeform pinned comment; Batch generates one per part per language with its own copy button.

Changed

  • Settings store: v4 → v6. Heal migration back-fills titleFormat (v4→v5) and the two pinned-comment toggles (v5→v6) with sensible defaults — upgrading from v0.6 requires no manual action.
  • Editor store: v3 → v4. Heal migration back-fills playthroughStatus, difficulty, difficultyCustomLabel, and contentWarnings — existing drafts round-trip cleanly.
  • Shared useCurrentGeneratorInput hook: the editor → GeneratorInput shape used to be copy-pasted across four call sites (two hooks + Batch + OutputExtras). Extracted into one hook; future input-field additions now touch one file instead of four.
  • buildTitle options bag: third arg accepts either the legacy boolean (showQualityBadge) OR a full options object. Legacy callers (including title-variants.ts) don't need to change.

Fixed

  • useMultilangOutput was silently missing showSponsorCredit and the sponsor fields on its built GeneratorInput, so multi-language output hid the sponsor credit line even when the setting was on. Fixed while threading the new titleFormat options through.

Under the hood

  • engine/types.ts gained TitleFormatConfig, PlaythroughStatus, DifficultyLevel, ContentWarning + the const-tuple ID registries that back them. Engine stays pure; store/settings-heal.ts re-exports.
  • New pure module engine/pinned-comment-builder.ts (10 unit tests).
  • Description builder gained 9 new cases; title builder has 10 new options-bag cases; settings-heal has 5 new migration cases. Full suite: 175 tests green.
  • All 6 locales (en, vi, ja, es, ko, zh) now in sync at 314 UI + 125 template keys each.

Migration notes

  • No manual action required. First launch after upgrade heals any missing keys in place.
  • If you've been hand-editing settings.json or ytdescgen-editor-draft.json, the new optional fields will be back-filled to sensible defaults (playthrough/difficulty default to "none" → section is skipped; content warnings default to []; pinned-comment template defaults to off).