Video settings:
- NVIDIA frame generation gains x6 (the multiplier was already in the list
but offered by no vendor) and Dynamic Multi Frame Generation (DLSS 4.5).
- "Custom…" for every vendor reveals a text field (`frameGenCustom`); the
description prints what was typed, like a custom graphics preset, and
nothing for an empty box.
- A "DLSS 5 Neural Rendering" switch (`dlssNeuralRendering`), shown for
NVIDIA only and printed after the DLSS mode:
"Ultra - NVIDIA DLSS Quality + NVIDIA DLSS 5 Neural Rendering + NVIDIA
Dynamic Multi Frame Generation". Another vendor turns it off
(`coerceDlssNeuralRendering`: the vendor switch, applied profiles and
templates, backup import).
- Editor store v21 -> v22 back-fills both fields.
- composeGraphicsPart's vendor half moves into small helpers.
My Rig: "Custom" is the LUT field's first suggestion (typing it works too,
any case). The rig block then prints just "LUT applied" in the output
language ("Có áp dụng LUT") instead of "LUT: Custom" — a field's
`customNoteKey`. No migration: the rig is a string map.
i18n: the new editor and description keys in all 8 locales and
_schema.json; brand names stay English. tests/engine/graphics-vendor.test.ts
also holds every vendor's options to their labels in the schema.
Docs: FEATURES (upscaler / frame-gen table, LUT Custom), TECH-SPEC (input
fields, store v22, rig block), CLAUDE.md (how to add an option).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first Qodana run found 74 problems in TypeScript / JavaScript and 12 in
Rust. Fixed:
- React 19.3 deprecates `FormEvent`: the three save forms take the
`SubmitEvent` their `onSubmit` hands them.
- The URL patterns read `\S` instead of `[^\s]` (18 patterns in platforms.ts
and playtest-platforms.ts, same characters).
- public/theme-init.js declares its browser globals and drops an unused
catch binding.
- The two private `stable()` JSON helpers (restore.ts, library-apply.ts)
become one `stableJson()` in src/utils/stable-json.ts, with a test.
- vitest.config.ts reuses vite.config.ts's alias map instead of a copy.
- Accordion destructures `icon` as `Icon` instead of copying it, a JSDoc
link points at nothing any more, and i18next's `init()` promise is
`void`ed on purpose.
- Rust: the three "show the main window" blocks become `show_main_window`.
Excluded in qodana.yaml, each with its reason: the Discord webhook secret
reference (HardcodedPasswords), escaped `]` / `}` in regexes, the
`@i18n/index` imports tsconfig needs, the three react-hooks warnings
eslint.config.js documents, the legacy `@deprecated` draft fields in the
files that migrate them; in src-tauri/qodana.yaml the module paths
`generate_handler!` needs.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ACCESSIBILITY.md (+ docs/i18n/vi): goal (WCAG 2.2 AA, not a conformance
claim), what works with a keyboard, screen readers, zoom, motion and touch,
how it is checked, supported environments, known limitations, how to
report a barrier (severity, response), and a checklist for contributors.
- In the Legal Center (consent: false, English + Vietnamese) and as
/legal/accessibility on the website; the Turnstile page's footer links it
in all eight languages.
- .github: Accessibility barrier issue form (label `accessibility`), an
Accessibility option in the feature request scope, an accessibility
checklist in the PR template.
- README, CONTRIBUTING, DEVELOPMENT (+vi), FEATURES and CLAUDE.md point to
it; SECURITY.md's supported versions move from 1.3.x to 1.5.x.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Colour tokens reach WCAG AA: lighter muted text and accent in the dark
theme, darker muted/success/warning/danger/donate in the light theme, and
new accent-solid / danger-solid fills for buttons with white text.
tests/styles/contrast.test.ts checks every text token on every surface.
- Generated text carries its language (lang) on Output, the YouTube and
quick previews, History, Batch, Social and Playlist, so screen readers read
Japanese output with a Japanese voice.
- RouteAnnouncer reads the new page's name after a navigation; focus stays.
- Toast region and close button are translated; Alt+T is in the shortcut list.
- Endings table inputs and the custom bank name get accessible names; the
From/To headers are translated.
- Settings > Editor > Single-key shortcuts turns the bare ? off (WCAG 2.1.4).
- Text inputs use outline-hidden so the focus outline shows in Windows High
Contrast; the genre remove button is 24px, small close/dismiss buttons
grow on touch screens.
- Desktop: zoomHotkeysEnabled (Ctrl/Cmd + = / -), with the
set-webview-zoom permission for the macOS/Linux polyfill.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Video settings gain "Upscaled from" next to Resolution: footage recorded
at 1440p and exported at 4K in the video editor is now declared as such.
- Title: the quality badge reads "[4K Upscaled]" ("[2K Upscaled]",
"[4K Upscaled 120FPS]"), with the word in the output language; badge
position, case and the "Show quality badge" setting apply as before.
1080p 60fps keeps no badge, upscaled or not.
- Description, VIDEO SETTINGS: "Upscale: 1440p → 4K (DaVinci Resolve
Studio 21.2)" right under the Video line, the editor taken from My Rig.
It stays when the graphics settings are hidden.
- Description, TECH NOTES: an automatic bilingual note that upscaling
reconstructs fine detail, so text, textures and edges may look slightly
different from the original image. It is not in the checklist and
goes away with the upscale.
- The Select lists only resolutions below the video's; lowering the
resolution to or below the source ends the upscale. The collapsed
section reads "1440p → 4K · 60 FPS". Saved with the channel profile.
- Editor store v20 → v21 (back-fills "" and drops unknown values);
backups and applied items read an unknown value as not upscaled.
`validUpscaleSource` in src/engine/upscale.ts is the one rule the
title, description and form share. AUTO_TECH_NOTES holds the engine's
own notes; their bullets share description.techNotes.items.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Boss Fight and Boss No Hit videos get the boss's name as a tag of its
own, right after the game's name, so fitting the list to 500 characters
never drops it.
bossNameTag cleans the Boss Name field the way a search term reads:
- NFC first; everything but letters (any script), marks, digits,
whitespace and in-word ' ' - becomes a space: , : ; ! ? quotes,
brackets, &, the CJK brackets and dots, (TM), emoji.
- A dot stays between digits ("Phase 2.0"), goes between initials
("S.T.A.L.K.E.R." -> "STALKER") and is a space anywhere else
("Mr.X" -> "Mr X"). Done per word in code: a lookbehind would be a
syntax error in the macOS 11-13 webview and stop the chunk loading.
- Over 30 characters, the name before its title ("Loretta, Knight of
the Haligtree" -> "Loretta"), else the leading words that fit; the
word fit is now a helper shared with tagFriendlyGameName (same result
there).
Only the video types whose extraFields include bossName add it, so a
boss name left in the draft after switching to Full Gameplay is not
tagged. Docs: FEATURES, ARCHITECTURE 2.3, TECH-SPEC.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new My Rig field for the LUT graded in the video editor. The
description and the social captions print it on its own line right
under the editor ("LUT: Arri Alexa LogC to Rec709"); left empty, there
is no line.
- Typing offers the LUTs that come with DaVinci Resolve, named the way
its LUT menu shows them (from Resolve 21's own LUT folder); any other
name is printed as typed.
- cleanLutName tidies a pasted file name or path: Explorer's "Copy as
path" or a macOS path keeps only the file name, and a .cube / .dat /
.3dl / .csp / .ilut / .olut / .look extension goes. Dots inside a
name ("SLog3SGamut3.CineToLC-709") stay.
- RigField gets `clean` (CPU and LUT) and `wide`. The cleaner runs when
the field loses focus and again in formatRigValue, so Ctrl/Cmd+Shift+C
or Ctrl/Cmd+S pressed with the cursor still in the field prints the
tidy name too; the LUT field spans both columns, under the editor row.
- `rig.lut` and `description.rigLabels.lut` ("LUT") in all eight
locales and _schema.json; a test now holds both label sets to
RIG_FIELDS.
No store migration: the rig is a flat string map in the channel
profile.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two Workers Rate Limiting bindings in wrangler.jsonc, checked first in
the router so a flood costs no siteverify call, HMAC check or asset
fetch:
- RATE_LIMIT: 120 requests a minute for everything the Worker handles
(gate page, app shell, legal pages, /__gate/*, any method).
- VERIFY_RATE_LIMIT: 10 a minute for POST /__gate/verify on top.
Clients are keyed by IPv4 address or IPv6 /64. Over the limit: 429 with
Retry-After: 60 (plain text, or JSON for the verify call). Like the
gate, it fails open when a binding is missing or limit() throws, and
logs that once per isolate. A test keeps wrangler.jsonc's bindings and
period in step with the code.
HOSTING documents both layers and the zone's WAF rate limiting rule
(Free plan: one rule, per IP, 10 s) as the first one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Regexes with super-linear backtracking (S8786 x16) are rewritten to stay
linear on long runs; each new pattern gives the same results as the old one
on 150k-450k fuzzed inputs (except where noted) and finishes adversarial
50k-character inputs in under 3 ms:
- tag-generator QUALIFIER_SUFFIX_RE starts just before a `:`/space run
(`(^|[^:\s])…` + "$1"), never inside one
- timeline-parser matches `line.trimEnd()` with a greedy label, and renders
with trimEnd(); cleanCpuName collapses whitespace before the patterns
- editor-store endings, Google Play urlPattern (lookahead for `id=`),
channel-phrase punctuation, SPDX OR/AND split, legal-docs slug and link
stripping (link text/URL may not contain `[`), base64url padding, and a
loop for trailing slashes in the worker router
Others:
- S2871: sorts take the shared code-unit comparator (same order as before;
THIRD_PARTY_NOTICES is unchanged)
- S4822: ErrorBoundary catches the logger import with .catch(), which a
try/catch never could
- S3516: migrateProfilesState returns a new object
- S7773: Number.parseInt (x10)
- S9379: Modal takes an initialFocusRef (Radix onOpenAutoFocus), so the
shortcut search box gets focus without an autoFocus attribute
- S2245: generateId drops the Math.random fallback; getRandomValues exists
everywhere the app runs, and a non-random ID is worse than an error
- S4036: NOSONAR on the dev script's `git` call (PATH lookup by design)
- S6505/S8543: every workflow installs with `npm ci --ignore-scripts`, and CI
runs `npm run cf:check` instead of `npx wrangler …`
- S6358: Android sets allowBackup="false" — app data is no longer copied to
Google Drive backups; Backup & Restore moves it to a new phone
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
TypeScript 7.0 is the native compiler and ships no JavaScript API, which
typescript-eslint still needs. Install both, as Microsoft documents it:
- "@typescript/native": "npm:typescript@^7.0.2" gives `tsc` = 7.0
- "typescript": "npm:@typescript/typescript6@^6.0.2" gives the 6.0 API
that typescript-eslint loads (its peer range stops below 6.1), and `tsc6`
CI fails if `tsc` ever resolves to TypeScript 6 (@typescript/old, pulled in
by the 6.0 package, ships a `tsc` too).
tsconfig.json (src):
- target ES2025: the newest year TypeScript 7.0, esbuild and Vite all know
- lib ES2022 + DOM: the browser floor (Vite's baseline-widely-available,
Chrome 111 / Safari 16.4 / Firefox 114), because nothing polyfills
- baseUrl removed (gone in 7.0; paths were already relative), DOM.Iterable
dropped (merged into DOM), `types: []` spelled out, erasableSyntaxOnly and
verbatimModuleSyntax on (both clean)
tsconfig.check.json: lib ES2025 for tests, scripts, worker and build plugins.
Platform floor: the Tauri build no longer lowers to es2020; it shares the
web build's baseline (the stylesheet already needed Chromium 99+ /
Safari 15.4+). macOS minimumSystemVersion is 11.0 (the build is arm64).
Also: eslint.config.js uses ESLint's defineConfig (tseslint.config is
deprecated); THIRD_PARTY_NOTICES names the real package behind an npm
alias, sorted with a shared code-unit comparator (src/utils/sort.ts);
Dependabot groups typescript + @typescript/*; a test's typed-array
annotation follows TypeScript 7's lib.dom.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- THIRD_PARTY_NOTICES said the app uses the operating system's fonts; it
bundles Inter and JetBrains Mono (OFL-1.1). The Rust table claimed to
list the direct dependencies of src-tauri but only took names starting
with "tauri", so serde was missing. The generator now reads Cargo.toml's
dependency tables and fails on a crate whose license it doesn't know.
- REUSE.toml credited the Gradle wrapper to the project; it is Gradle's
("the original author or authors", Apache-2.0).
- The Privacy Policy lists the session-only ytdescgen-chunk-reload flag
next to the localStorage keys. Not a material change, so the terms
version stays 2; the Effective date moves.
- DISCLAIMER (+ vi) pointed at a THIRD_PARTY_NOTICES section by an old
heading.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A new content-warning group, AI-generated content (7): general, art /
visuals, voices, music / sound, text / dialogue, generated live while
playing, and disclosed by the developer. It follows Steam's AI
disclosure (made with AI during development vs generated live while the
game runs); machine translation stays the Language patch field.
Also simulated gambling and in-game purchases (ESRB / PEGI descriptors
with no warning so far), and a tech note for upscaling / frame-generation
artifacts (which upscaler was on is already the Video settings line).
A test now fails when a content warning or tech note has no editor label
or description bullet in _schema.json, and so in any locale; tech notes
get the group-parity test content warnings already had.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Every notice already says 2026, which is right: the first commit is from
2026-04-07, so there is no 2025 to fix and no 2025-2026 range to claim.
What was missing is anything keeping the years current.
- src/config/brand.ts: COPYRIGHT_START_YEAR and copyrightYears(), "2026"
now and "2026-2027" from the first commit made in 2027
- npm run check:copyright (CI, next to check:licenses) holds NOTICE,
REUSE.toml and the installers' copyright string to HEAD's commit year,
not the clock, so old commits stay green; npm run update:copyright
rewrites them
- tauri.conf.json gains bundle.copyright, so the .exe/NSIS, macOS and
Linux packages stop shipping an empty copyright field
- the /legal pages' footer prints the same range at build time
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings › Appearance › Hide scrollbars removes every scrollbar in the
app; the mouse wheel, touchpad, touch and keyboard still scroll.
- hideScrollbars setting (default off), coerced to a boolean by
healSettings; portable like the theme, no store version bump (the heal
back-fills it, and older builds can still read newer backups)
- applied as <html class="hide-scrollbars">: theme-init.js before first
paint, main.tsx at boot, an App store subscription afterwards (the
toggle, a restored backup and its undo)
- unlayered CSS beats .scrollbar-thin: scrollbar-width: none on every
element for Chromium and Firefox, ::-webkit-scrollbar for the WebKit
webviews on macOS and Linux
- labels in 8 locales
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
poli0981.github.io/youtube-generator still serves v0.38 to old bookmarks,
and the data people saved there can't follow to ytgenerator.stream on its
own (browser storage belongs to a site). A single static page replaces it:
- reads the ytdescgen-* stores this browser saved on the old address and
downloads them as a backup file in the new format (Settings › Restore
reads it: migrations, the preview and Undo apply as for any backup);
- points to ytgenerator.stream, in English or Vietnamese;
- noindex, canonical to the new site, and a 404 copy for old deep links.
pages-migration.yml deploys it by hand (workflow_dispatch, pinned
actions, job-scoped permissions). The page, the workflow and the
github-pages environment go on 2026-11-29.
A regression test feeds the page's exact output through the restore.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Editor:
- Quick start at the top: pick the channel profile and the game preset
(remembered per device); replacing fields that hold something else asks
first, everything offers Undo; "Update profile / preset" appears when the
editor drifts from the one in use.
- Next part (number + 1) and New video (same game) clear what belonged to
the last video: boss, timestamps, endings, pinned comment, sponsor…
Applying a preset for another game or a template does the same first.
- Start over replaces Clear Draft and keeps the channel (profile fields);
a new draft starts in the Default Output Language (it was always "en").
- A store link pasted anywhere — the page, the Game name field, another
store's field — lands in the right store field, sets the platform for a
game's first link and names the game from it (Roman numerals and
well-known possessives restored: "Final Fantasy VII", "Baldur's Gate 3").
Steam links keep their name slug and drop tracking parameters.
- Game-name suggestions from presets and history.
Catalogs:
- Stores: EA app, Ubisoft, Battle.net, Google Play, App Store, Meta Quest.
- Social: YouTube, Threads, Kick, Reddit, Bilibili; "X (Twitter)" with the
X mark; threads.net and youtu.be links accepted.
- Cross-posting: YouTube Shorts, X (counted the way X counts — CJK,
Vietnamese letters with diacritics and emoji count twice), Threads (one
topic tag), Bluesky; hashtag caps per platform.
- Banks: MBV, VCBNeo, Vikki Bank (renamed OceanBank, CBBank, DongA Bank —
saved old names get a one-click switch), Cake by VPBank, Timo.
Output:
- An empty channel name no longer leaves "…of Hades on ." — the channel
phrase is dropped per language (8 locales, every template tested).
- Title alternatives are real title shapes with the user's separator and
badge case; "Use this shape" sets them (new Title order setting:
game first / video first); over-long ones can't be copied.
- Copy All can include the tags (setting); Batch picks Part or Demo part
and continues from the editor's part number; Ctrl/Cmd+S saves the
output to History.
- Social editor headings and hints translated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Storage (desktop):
- The webview can no longer name a path. Five commands that read, wrote,
listed and deleted any path the frontend sent are replaced by name-only
commands (backups, logs) that resolve under the app data folder, and by
export/import commands that open the native dialog from Rust, so the only
file touched is the one the user picked (json/jsonl/txt/csv/md, 20 MB).
The fs and shell plugins are removed (Rust, npm, capabilities).
- The settings "mirror" file is gone: it was written next to the data
folder (a missing path separator) and never read back. On first start
the file becomes a restorable backup — never applied on its own — and
the stray log folder is merged into the right one.
- Automatic backups on desktop: after library changes (quiet 30 s, at most
every 10 min, skipped when unchanged or empty), newest ten kept, plus one
before every restore. Settings lists them with Restore.
- One tray icon, built in code with the app icon (the config entry that
could add a second, iconless one is removed).
Backup & restore (every platform):
- Format 2 files carry each section's store version; imports run the
stores' own migrations (now exported functions), then a whitelist
sanitizer: known fields and values only, editor limits, safe unique ids.
- Reads every earlier export: v0.15-v0.38 envelopes (log exports were
labelled "history"), pre-v0.15 bare arrays, the old desktop data file.
- Restore dialog: new / already here / different per item, merge (keep the
newer one, or both) or replace, section and item selection, one step,
Undo. Newer-version sections are shown, not restored.
- Settings: Back up (choose sections) / Restore / drop a file. Consent and
panel state are never exported or overwritten.
- History export as CSV (spreadsheet-safe) or JSON; logs export as "logs";
dated file names; no more 250 ms timer guessing that a picker was
cancelled.
Library:
- Templates save every editor field; presets save store link types and the
other per-game fields; profiles save donate, community links and the
custom graphics preset. Edit forms can update from the current editor,
start fresh each time they open, and save on Enter. Toasts translated.
Dev: Vite no longer watches src-tauri (cargo's locked .dll crashed
`tauri dev` on Windows).
Verified in `tauri dev` on Windows under a test identifier: legacy file
recovered, old logs merged, auto backup, restore from the legacy backup
with a backup before it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hardware
- GPU catalog rewritten with stable ids and official names: descriptions
read "NVIDIA GeForce RTX 5080", "AMD Radeon RX 9070 XT", "Apple M4 Pro"
instead of "NVIDIA RTX 5080" / "AMD RX 9070 XT" / "Apple Silicon M4 Pro".
Cards that never shipped (RX 9080, RX 9090 XT, Arc B380) are gone;
RTX 50/40/30 laptop GPUs, RX 9070 GRE, VRAM variants, Radeon/Intel
integrated graphics, handheld APUs and Apple M5 (Pro/Max/Ultra) added.
One searchable picker ("5080", "rog ally") replaces Brand › Series ›
Model, with free text for anything else.
- Old `brand|series|model` values are migrated (editor v19, profiles v3,
templates v2, and on load/import); unknown cards keep their full name.
- RAM: 24/48/192 GB, LPDDR4/4X/5/5X, optional speed ("32 GB DDR5-6000");
no DDR6/DDR7; plain "DDR"; "48GB GB" fixed; changing the size no longer
clears the type. OS: SteamOS, Bazzite, CachyOS, Nobara, openSUSE,
Fedora 43/44; Linux reads "Ubuntu 24.04 LTS". CPU: suggestions, and
Windows' "Intel(R) Core(TM) … CPU @ 3.60GHz" is tidied on blur.
- The rig block uses translated labels in a fixed order (CPU, GPU, RAM…)
in both the description and the social captions.
Tags
- Measured the way YouTube counts (quotes around multi-word tags, one
comma between): 15 of 51 real tag sets were over 500 by YouTube's count
while showing under. Counters and the limit warning use the same count.
- Trimming keeps trying shorter tags after one that doesn't fit.
- "Elden Ring Steam", "itch.io gameplay" (was STEAM / ITCHIO); no platform
tags for a publisher site; "best open world games" (was "openworld");
RPG/simulation/card pools no longer carry other genres' tags.
Timestamps
- Keywords need a word boundary: "Final Fantasy VII" stays a title (was
"Ending Fantasy VII"), "Introduction" stays whole.
- Accepts [0:00], 0:00 - label and editor frame counts; pt-BR and
Indonesian keywords; a Tidy up button; a live check of YouTube's
chapter rules (0:00 first, 3+, 10 s apart, in order).
Output and data
- History keeps one entry per video (updated in place) instead of one per
Output visit; existing duplicates are folded (history v3). The History
Limit is healed on every load.
- A field over its limit blocks only its own copy button (Copy All: title
or description); a warning when YouTube would reject "<" or ">".
- Validation: Steam /sub/, /bundle/ and s.team links, GOG/Humble/xbox.com
without www, regional Nintendo sites, Microsoft Store, Luna; social
links with www./m./twitter.com; phone, YouTube Music and
video-in-playlist links (normalised); email domains need a TLD; the live
URL is validated; no bare "#" hashtag.
- The engine takes the year from the caller; "Ending N" follows the output
language.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
New checks
- security.yml: dependency-review blocks PRs that add a high/critical
advisory; actionlint + zizmor lint the workflows themselves (template
injection, permissions, credential persistence, unpinned uses); OpenSSF
Scorecard weekly and on main (published, not uploaded as alerts).
- compliance.yml: REUSE lint over the whole repo (REUSE.toml + LICENSES/,
no per-file headers) and Conventional-Commit PR titles.
- rust.yml (src-tauri changes + weekly): rustfmt, clippy -D warnings,
cargo test, and cargo-deny for RustSec advisories, licenses and sources.
- ci.yml `check` gains: coverage thresholds (src/engine, worker),
check:licenses, check:bundle, and a `wrangler deploy --dry-run`.
Licensing
- THIRD_PARTY_NOTICES.md is now generated from package.json, the installed
packages and Cargo.toml/Cargo.lock (`npm run generate:third-party`); CI
fails when it is stale or when anything bundled into the app carries a
license outside the allowlist. It had drifted to React 18 / Vite 7 /
Tailwind 3.
- Vite's build.license emits the full text of every bundled package's
license to /licenses/third-party.md (served publicly, before the gate).
Bundle budget
- scripts/check-bundle-size.ts measures what CLAUDE.md's "500KB" never
defined: initial load (everything index.html references) <= 280 KB gzip
(197 KB today) and no JS chunk over 500 KB raw.
Coverage
- @vitest/coverage-v8; thresholds sit just under today's numbers. The
engine is at 89% lines / 64% functions — not the 100% CLAUDE.md claimed.
Supply chain
- Every third-party action pinned to a commit SHA (Dependabot updates the
SHA and its version comment); checkout never persists credentials.
- Release workflows: a `verify` job (typecheck, tests, version sync, Tauri
alignment, tag == package version) gates the build; no dependency caches
in release jobs; permissions granted per job.
- Reusable Discord workflows receive only the secrets they declare instead
of `secrets: inherit` (which exposed the Android signing keys to them).
- Rust: cargo-deny found RUSTSEC-2026-0194/0195 (quick-xml DoS, via plist)
that Dependabot had not raised; plist 1.10 brings quick-xml 0.41.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A Worker (worker/) now sits in front of the static build, configured from the
same wrangler.jsonc. Cloudflare builds and deploys it; nothing in GitHub
Actions does.
Gate
- First visit shows a branded check page (8 languages, Accept-Language) with
Cloudflare Turnstile. The token is verified server-side against
TURNSTILE_SECRET: success, hostname, action "enter", age <= 300 s. Only
Cloudflare's own test-key results skip the hostname/action check, so
`npm run cf:dev` works with the published test keys.
- Pass -> `__Host-ytg_gate` (HttpOnly, Secure, SameSite=Lax, 24 h): an HMAC
over expiry + a user-agent hash, keyed from the Turnstile secret, so no
second secret exists and a cookie copied into a scraper is useless.
- The page reloads in place instead of redirecting, so there is no `next`
parameter to open-redirect with; /__gate/status lets the page tell a
cookie-blocking browser what is wrong instead of looping; after one
failure it waits for a click rather than resubmitting.
- Missing secret = deployment mistake: the site stays up without the gate and
the Worker logs it, instead of locking every visitor out.
- The agree box on the gate records `ytg_terms`, which the app reads on boot
so web visitors meet one blocking screen, not two.
Headers and static files
- worker/headers.ts sets CSP (nonce + strict-dynamic on the gate, no script
at all on legal pages), nosniff, Referrer-Policy, Permissions-Policy, COOP,
CORP, X-Frame-Options on everything the Worker returns; _headers covers
the files served directly; a test keeps the two baselines identical.
- `not_found_handling: "404-page"` (a static 404.html) instead of the SPA
fallback, which would have handed index.html past the gate for any
excluded path. The Worker serves the shell itself by fetching "/" - not
"/index.html", which html_handling would 307 back to the home page.
- security.txt (RFC 9116) is generated per build so Expires stays ~6 months
ahead; the Web Analytics beacon is injected into the web build only.
- theme-init.js applies the saved theme before first paint (no inline script).
Legal in-site
- build-plugins/legal-docs.ts renders TERMS, PRIVACY, DISCLAIMER (+ vi),
LICENSE, THIRD_PARTY_NOTICES, SECURITY, NOTICE and CODE_OF_CONDUCT at build
time into static /legal pages (public, before the gate) and a lazy
`virtual:legal-docs` module for the in-app Legal Center, which works
offline on desktop and Android and never leaves the webview.
- PRIVACY, TERMS and SECURITY rewritten for Cloudflare hosting, Turnstile,
Web Analytics and the two cookies; contacts moved to the poli0981.dev
aliases (privacy@, legal@, dmca@, copyright@, security@, code@).
- CURRENT_TERMS_VERSION 1 -> 2: the Privacy Policy changed materially.
App
- Web uses BrowserRouter (real paths; analytics can count them), Tauri keeps
HashRouter; old /#/x bookmarks are rewritten to /x before the router reads
them. Consent is a layout route; /legal sits outside it.
- <html lang> follows the UI language; a stale chunk after a deploy triggers
one reload instead of an error page.
.gitattributes pins LF everywhere so Windows checkouts stop failing Prettier.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two new locales, 1,562 strings each, complete: titles, every description
block, all 248 content warnings, tech notes, playthrough notes, pinned
comments, playlist copy, and the whole interface.
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.
**docs/I18N.md was wrong about what registering a locale takes**, and this
release is where that bit. It claimed `SUPPORTED_LANGUAGES` was "the only
registration step". It is one of four, and they fail differently:
SupportedLanguage union compile error
CORE_TAGS_BY_LANG compile error (there are TWO such records,
MULTILINGUAL_TAGS compile error not one — the doc mentioned one)
detectBrowserLanguage SILENT
The silent one matters most: the language works perfectly and simply never
auto-selects for a visitor whose browser is set to it. `SUPPORTED_LANGUAGES`
also wasn't type-bound to the union, and every consumer casts, so a mismatch
between the first two compiled cleanly — it now carries a `satisfies` clause.
`tests/i18n/locale-registration.test.ts` exists to close those gaps: it checks
the picker list against the locale directories on disk in BOTH directions, plus
namespace files, flags, native names and tag pools.
Browser-language detection 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 resolves to pt-BR rather than falling through to English.
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.
Deliberately left in English, matching what the Spanish locale already does:
vendor product names (NVIDIA DLSS, AMD FSR, Intel XeSS, Fluid Motion Frames),
platform brands, hardware acronyms, genre terms that are loanwords in both
languages, and example URLs/emails in placeholders. So pt-BR reads 1,344/1,562
and id 1,308/1,562 "differing 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.
Also replaces `__dirname` in the Vite and Vitest configs with
`import.meta.dirname` — Vite 8's native config loader doesn't provide the CJS
global and warned on every run.
v0.36.0 is skipped: the dependency release shipped first and took 0.37.0.
Tests 692 → 698. Validator now 1,562 keys x 8 locales.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The first cut had each input register its own error into a shared store as it
rendered, clearing on unmount. That read as reasonable and was quietly useless:
the fields live on the Editor page, the gates live on Batch / Social / Output /
Profiles, and unmounting the Editor took every issue with it. Verified in the
browser — typing a malformed Steam URL, navigating to Batch, and finding
Generate perfectly enabled with no banner.
Replaced with two sources that between them cover what the setting promises:
- `collectEditorIssues` (pure, `@utils/editor-issues`) walks the editor STATE
against the same validators and the same `PLATFORMS` / `SOCIAL_FIELDS` config
the inputs use — one rule set, two consumers, no duplicated regexes. This is
what catches data that never passed through an input at all: an imported
profile, a preset shared by someone else, a draft persisted before a
validator got stricter. Since `ValidatedInput` refuses to commit invalid
text, imports are in fact the main way bad data reaches the store.
- `pending-invalid-store` holds text that is invalid and therefore *not*
committed. Without it, a field showing a red error would still be invisible
to every gate, because the store behind it holds the last good value. It has
no unmount cleanup — that was the original bug — so an entry lives until the
field is valid again.
Both are filtered through one relevance check, so a field nobody can see never
blocks: `adEmail` / `gameKeyEmail` while the split toggle is off, `zaloGroupLink`
outside Vietnamese output. Without that, Strict Mode could become an
unresolvable dead end — blocked on a field with no visible input to fix it.
Dropping the registry also removes the render-loop hazard it carried: the
effect published on every render of every input, guarded only by a deep-equal
bail-out.
Verified end to end in the browser: a bad Steam URL now disables Generate on
Batch and names the field in the banner; fixing it re-enables; and a Ko-fi link
on a vanity domain shows its inline prefix warning without blocking anything.
Tests 687 → 696.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Completes the field-limit work: `maxLength` is now wired at 53 call sites
across every editor form, the Settings genre-playlist inputs, the save dialogs
and the Playlist notes — grouped by what the field holds rather than named one
by one, so a new input inherits a sensible cap instead of inventing a number.
Two gaps that a `maxLength` attribute alone cannot close:
- **Imports bypass it entirely.** `maxLength` constrains typing and pasting;
a profile, preset or template — including one saved before the caps existed
— never passes through an input at all. `normalizeEditorPatch` now clamps on
the way in, covering the flat fields plus the nested `social` and
`storeLinks` URL maps. Without this the cap was decorative for exactly the
path most likely to violate it.
- **Strict Mode could not see any field.** The registry landed in the previous
commit, but nothing registered with it. Every `ValidatedInput` now carries a
stable `fieldId` (composed for loop-rendered fields: `editor.social.twitch`,
`settings.genrePlaylists.horror`), so the banner can name the offending
input rather than saying "something is wrong".
Also fixed: `liveUrl` was a plain `Input` with no validation at all — the only
URL field in the app that would accept anything and pass it straight into the
description.
Tests 681 → 687.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
**Over-limit output could always be copied.** `renderAll` has returned
`warnings: CharLimitWarning[]` since v0.5 and nothing in the UI ever read it.
Three ad-hoc checks had grown up in the components instead, each with a
different blind spot:
- `CopyButton` turned red and stayed clickable.
- `CopyAllBar` checked title and description but not tags — and bailed out of
every check when its `extraText` prop was set. Exactly one caller set that
prop: OutputPage, whenever more than one language was selected. So picking
a second language silently disabled limit checking on the main copy path.
- BatchPage passed no limits at all, so a 6000-character description copied
without a word.
`src/engine/limits.ts` is now the single derivation, and the requested rule is
all-or-nothing per output: if any one of title / description / tags is over,
none of them can be copied. Copying two fields and silently leaving the third
is how a half-populated description gets published.
Scoping decisions worth stating:
- Batch blocks the offending part's own buttons plus Copy All Batch, but not
the other 99 parts. Freezing an entire batch because part 7 is three
characters long would be useless.
- On Output, per-field buttons use the ACTIVE TAB's status while Copy All
uses the merge — an over-long Japanese title must not disable the English
copy button the user is looking at, but it must block the blob containing it.
- `OutputExtras` (thumbnail text, pinned comment) and Playlist stay ungated:
different YouTube surfaces with different limits, so reusing YT_LIMITS
there would be wrong.
Batch also gained the description and tag counters it never had — a row could
be 1500 characters over with nothing on screen saying so. Social bulk Copy All
now respects each platform's own cap (TikTok 4000, Reels 2200).
**Strict Mode** (Settings → Guardrails, default OFF). Blocks Generate, Copy and
Export while any field carries a hard error. This needed something that did not
exist: an app-wide view of which fields are invalid. Every error lived in the
private `useState` of the input that produced it, so no caller could ask the
question. `src/store/validation-store.ts` is that registry — ephemeral, not
persisted, since an error rehydrated from disk would describe text the user can
no longer see.
Errors only. `validateUrlWithPrefix` returns a soft warning for a link that
works but doesn't match a platform's usual prefix; blocking on that would
strand anyone on a vanity domain or a regional mirror.
Two exemptions: the log .txt/.json export stays ungated (a debugging export
must not be held hostage by an unrelated bad URL), and the Editor gets the
banner but no gate — it is where you go to FIX the fields, so disabling
anything there would be backwards. Unmounted fields deregister, so a hidden
`adEmail` or a swapped-out video-type field can never block.
**Settings sections are collapsible.** 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) because a page mixing bare headings with chevrons reads
as broken, and unknown ids default open so a section added later cannot vanish
for an existing user.
Settings persist v11 → v12 (`strictMode`, `settingsAccordionState`), with
`SCHEMA_VERSIONS.settings` bumped in lockstep. Both are coerced, not just
back-filled: a hand-edited `"strictMode": "yes"` is truthy in JS, and silently
switching a seatbelt on is the opposite of an opt-in. Also corrected
`SCHEMA_VERSIONS.profile` 1 → 2, left behind when profile-store bumped in v0.34.0.
16 UI keys across all six locales (validator 999 ui / 563 templates).
Tests 665 → 681.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Two independent guardrails; both were missing outright rather than broken.
**Exports never asked where to save.** There were two writers that disagreed:
`saveFile` branched correctly per platform but had exactly one caller (the log
.txt export), while every JSON export went through a private blob-download
helper with no platform branch at all. So "Export" on Settings, Profiles,
Presets, Templates, Social and the log JSON dumped straight into Downloads —
even on desktop, where a native Save As dialog had been available and
capability-approved the whole time.
Now one writer, `saveTextFile`, with three branches:
1. Tauri desktop — native Save As, then the existing `save_to_file` command.
No Rust or capability change was needed; the permissions were already there.
2. Web with the File System Access API — a real picker. It must be the FIRST
await in a click handler because it needs transient user activation, so
every call site now builds its payload synchronously first. A
`NotAllowedError` from a spent activation degrades to (3) instead of
losing the file.
3. Everything else (Android WebView, Firefox, Safari) — blob download.
`exportTypedToJsonFile` is now async and returns the outcome, so **cancelling
is silent**: dismissing a save dialog is a decision, not a failure, and
toasting "Export failed" at someone who pressed Escape is how people learn to
ignore toasts. The shared `useFileExport` hook holds that rule in one place and
retires the hardcoded English "Exported!" / "Export failed" strings.
Settings Import/Export is no longer desktop-only. That gate was a leftover from
when export meant dumping the on-disk settings.json; import has always been a
plain <input type="file">, and export now offers a real dialog on the web too.
**No field had a length cap** — `maxLength` appeared nowhere in the codebase, so
a pasted novel in the game-name field produced a title YouTube would reject.
`FIELD_LIMITS` groups caps by what a field holds (URL 200, email 320, short
name 100, label 300, long text 2000, timestamps = the 5000 description budget)
so a new input inherits a sensible limit instead of inventing one. `clampField`
covers the paths `maxLength` cannot: profile/preset/template import and
paste-autofill.
**Emails hard-stop at three per field.** The cap is enforced on the increase,
not the absolute count, which buys two things: a field that already holds four
(legacy profile, hand-edited import) stays editable down to three instead of
freezing, and a half-typed `a@b.com,c@` is never punished. Per field rather
than across the split — each of the three renders its own labelled line, so
filling the advertising address must not retroactively invalidate the contact.
**`ValidatedInput` no longer destroys good input.** On an invalid value it used
to call `onChange("")`, wiping the stored value while the box still showed the
user's text — so backspacing one character out of a complete URL silently
emptied the field, and autosave then persisted the empty value with no signal.
It now simply doesn't commit, leaving the last valid value in place; bad input
is kept out just as effectively. Also fixed while here: `displayValue` never
re-synced when the prop changed, so applying a profile or preset left the box
showing stale text that disagreed with the store.
i18n keys for the new strings land in the following commit.
Tests 629 → 655.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Reported: with Settings → "Split contact email by purpose" ON, the Batch tab
showed only the old single "📧 Business inquiries:" line, while the Output tab
correctly showed the grouped 📧 BUSINESS / CONTACT block with all three
addresses.
Root cause is not in the engine. `renderAll` had three call sites, each
hand-copying the same twelve settings fields into an options object, and
BatchPage's copy was missing two: `splitContactEmail` and `showThirdPartyAds`
(plus `tEn`). An absent flag defaults to `false` inside `buildDescription`, so
the else-branch emitted the legacy single line — silently, with no type error
and no failing test, because the engine tests call `buildDescription` directly
with an explicit options object and never exercise the wiring.
Rather than add a third copy of the list, the mapping now lives in one place:
- `SettingsRenderOptions` (settings-derived) is split from
`RenderOptionOverrides` (per-caller: `tEn`, `bilingualContentBlocks`), and
`RenderOptions` is their intersection. Same shape as before for `renderAll`.
- New `useRenderOptions` / `buildRenderOptions` produce the settings half; all
three call sites consume it and layer only their own overrides.
Two guards, both verified to fail when the original bug is reintroduced:
- Compile-time: `buildRenderOptions` builds a `Required<SettingsRenderOptions>`,
so dropping a key is `TS2741: Property 'splitContactEmail' is missing`.
- Runtime: `tests/hooks/render-options-parity.test.ts` diffs the produced keys
against `SETTINGS_DERIVED_RENDER_KEYS` in both directions and names the
offending key in the failure message.
Also fixed by the same change, since Batch was dropping it too:
`showThirdPartyAds` — the SPONSORS & PARTNERS block now renders in Batch.
Batch deliberately still passes no `tEn`: its rows are one language each, so
the bilingual `EN · LOCAL` treatment would duplicate every content-warning line.
Note for the changelog: Batch descriptions get *longer* for anyone who had
either toggle on, because those blocks were being silently dropped.
Tests 621 → 629.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The first attempt at this alert swapped the bare host substring for the full
URL, which CodeQL still flags — `js/incomplete-url-substring-sanitization`
fires on `.includes()` against any URL-shaped value, not on the needle's
length, so the change produced two alerts where there had been one.
A store line renders as `🎮 {label}{suffix}: {url}`, so asserting
`(free): <url>` against the whole description tests the actual adjacency the
case is about, drops `.includes()` entirely, and no longer needs to locate a
line by host at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
CI ran typecheck/lint/locales/test/build. Everything else the repo owned was
configured but never executed — `knip` was installed and configured yet ran
nowhere, Prettier had a config and no gate, and the six version fields the
release ritual bumps by hand had nothing watching them. This wires all of it
into the pipeline.
Correctness gaps this immediately caught:
- `tsconfig.json` covers only `src`, so tests/ and scripts/ were NEVER
type-checked. Adding `tsconfig.check.json` (+ `typecheck:all`) surfaced 53
errors, including three fields silently missing from the editor→engine
parity fixture: `videoStyleEra` (v0.22.0), `adEmail` + `gameKeyEmail`
(v0.34.0), and the four `endings*` fields (v0.16.0/v0.17.1). The fixture is
the guard against exactly that class of drift, and it had drifted itself.
- `vitest.config.ts` `include` matched only `*.test.ts`, so any `.test.tsx`
would have been collected by nobody and "passed" silently. Now `{ts,tsx}`.
New gates in ci.yml: `typecheck:all`, `format:check`, `knip`, `check:version`,
and an advisory `npm audit --audit-level=high` (advisory so a fresh transitive
advisory cannot redden every unrelated PR before Dependabot opens its fix).
Plus least-privilege `permissions: contents: read` — which also clears the
`actions/missing-workflow-permissions` code-scanning alert — and a
concurrency group that cancels superseded runs everywhere except `main`.
New scripts:
- `scripts/check-version-sync.ts` — asserts all SIX version fields agree
(package.json, package-lock root AND packages[""], tauri.conf.json,
Cargo.toml, Cargo.lock self-entry). Nothing else notices a missed one, and a
stale tauri.conf.json ships an installer that disagrees with its tag.
- `scripts/generate-locale-template.ts` — `npm run generate:locale` has been
advertised in package.json and docs/I18N.md step 1 since v0.1, but the file
was never committed, so the documented first step of adding a language
failed outright. Blocks the planned pt-BR + id work.
Dead code removed: the Rust `ensure_dir` command and its two scoped `opener:`
capabilities. Its documented caller, `openSettingsFolder()`, no longer exists
in `src/` — `opener:default` (all `openExternal` needs) is untouched. Also
`@tauri-apps/plugin-opener` left knip's ignore list now that it is genuinely
imported, and `DroppedReasonId` went from unused export to typing
PlaylistPage's dropped-reason state.
Security: the `js/incomplete-url-substring-sanitization` alert in
description-builder.test.ts was a real (if low-stakes) weak assertion —
`includes("itch.io")` also matches `https://itch.io.example.com/`, so the
test could pass on the wrong line. Now matches the full URL.
CHANGELOG: v0.31.0, v0.32.0 and v0.32.1 shipped as tagged releases but were
never logged, leaving the file jumping v0.33.0 → v0.30.0. Reconstructed from
the release commits in the file's existing house style.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
`prettier --check` failed on 81 files: the repo had a Prettier config and a
`format` script from day one, but nothing ever enforced them, so formatting
drifted file by file. This is that pass, isolated in its own commit so the
CI gate added alongside it lands on an already-clean tree and no future
feature diff has to carry whitespace noise.
Formatting only — no behavioural change. Verified by `npm run test:run`
(621 passing, unchanged) and `npm run typecheck`.
Markdown, `_schema.json` and the workflow YAML are deliberately excluded:
Prettier reflows prose and expands the locale schema's compact arrays by
~1600 lines, which makes both harder to review for zero benefit. The
`format` script is scoped to `{src,tests,scripts}/**/*.{ts,tsx,css}` to
match.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add a Settings "Split contact email by purpose" toggle (off by default).
When on, the editor exposes three email fields — Contact, Advertising,
and Game keys & playtest — and the description renders a grouped
"BUSINESS / CONTACT" block with one labeled line per non-empty field.
Off keeps the single "Business inquiries" line unchanged.
- New editor fields adEmail/gameKeyEmail (persist v17->v18); contactEmail
is reused as the Contact line, so no saved data moves. The
splitContactEmail toggle mirrors showThirdPartyAds end-to-end
(settings persist v10->v11). Profiles persist v1->v2. All migrations
are additive back-fills.
- +8 ui / +4 templates i18n keys across all six locales (983/563).
- 621 tests pass (613 + 8), typecheck/lint/locale validation green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Grow the description's COMMUNITY block into the channel's full "join the
chat" hub. Two new dedicated invite fields — Signal
(https://signal.group/#<id>) and the Instagram group chat
(https://www.instagram.com/j/<id> or https://ig.me/j/<id>) — plus
Facebook Group moved out of the generic Social list into its own
facebookGroupLink community field. All three render for every output
language (like Messenger); Zalo stays Vietnamese-only. Block order:
Messenger, Signal, Instagram, Facebook Group, Zalo.
Each new link hard-rejects off-format input via a strict validator
(validateSignalGroupUrl / validateInstagramInviteUrl /
validateFacebookGroupUrl). The three fields thread through defaults, the
store (persist v16 -> v17), GeneratorInput, the editor -> engine mapper,
and template snapshots. The v17 migration lifts a legacy social.fb_group
value into facebookGroupLink and drops the dead key; normalizeEditorPatch
does the same for profiles/presets/templates.
i18n: 9 keys added / 1 removed across all 6 locales + schema
(975 ui / 559 templates). 613 tests pass (was 583). Five manifests
bumped 0.32.1 -> 0.33.0.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
v0.32.0 accepted `https://m.me/[id]` (a personal-page link) for the
Messenger Community field. A community/channel invite is actually
`https://m.me/ch/[id]` (e.g. https://m.me/ch/Abb1hmBhU_97UMCF/).
- Tighten MESSENGER_URL_REGEX to require the /ch/ segment (trailing
slash optional) and hard-reject the old bare form.
- Update the shown example (MESSENGER_URL_EXPECTED) + the 6-locale
placeholder to https://m.me/ch/yourid; refresh stale doc comments.
- Update validation/engine/migrate tests; add trailing-slash accept
and bare-form reject cases.
Engine and store are unchanged (the link is printed verbatim, and the
field type/persist shape is untouched). Bump to v0.32.1.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add two "join the chat" community links that render into a single
"💬 COMMUNITY" description block:
- Messenger community (https://m.me/[id]) — shown for every language.
- Zalo group (https://zalo.me/g/<code>) — Zalo is a Vietnam-audience
app, so the editor input only appears (and the description line only
renders) when the output language is Vietnamese, mirroring the VN
donate block. A value entered while in Vietnamese is preserved if the
creator switches language.
Both links are hard-validated (validateMessengerUrl / validateZaloGroupUrl)
so a malformed URL never reaches the output. New editor-store fields
persist via a v15→v16 migration and round-trip through saved templates.
i18n across all 6 locales (967 ui / 559 templates). Tests 560→581.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Playlist Generator now produces a status-adaptive pinned comment for the
latest video, and when a series is marked dropped, a multi-select of
reasons (predefined checklist + free-text) that render in both the
playlist description and the comment. Localized across all 6 locales.
New buildPlaylistComment engine fn + first tests for playlist-builder.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Playtest section (Store & Social): a signup link + platform dropdown
(Steam Playtest / Epic / itch.io / Discord / Other) + invite count
capped per-platform (≤100). Renders a localized "🧪 PLAYTEST" block in
the description only when a link is set, like Store Links. New config
playtest-platforms.ts; 3 editor fields thread through the store (persist
v14→v15 migration), GeneratorInput, and the editor→engine mapping.
Invalid-number guarding: validateIntegerInRange + validateBatchRange
reject negative / decimal / out-of-range / end<start / >100-span inputs.
Batch and Social bulk disable Generate + warn on a bad range; Playlist
"Total videos" and Playtest invites warn inline and guard the output.
Input primitive gains optional errorText/helpText.
60 new i18n strings across all six locales (validator 948/544). 544
tests (517 + 27), typecheck, lint, and locale validation pass; verified
live. Five manifests bumped 0.29.3 → 0.30.0.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Multi-language Output tabs were rendering content warnings / tech notes / playthrough notes bilingually after v0.29.2 forwarded the shared `tEn` translator. New `bilingualContentBlocks` render option (default true) lets the multi-language hook keep those blocks single-language while the AI-translation disclaimer stays bilingual. Single-language output unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Build and package the app for Android from the same Tauri 2 codebase, shipping
an installable, sideloadable signed APK alongside the desktop binaries.
Build / packaging
- cfg-gate desktop-only tray / single-instance / hide-to-tray / exit-prevention
in lib.rs behind #[cfg(desktop)]; move tauri-plugin-single-instance to a
desktop-only target table so the library compiles for Android.
- `cargo tauri android init` -> committed gen/android Gradle project; release
signingConfigs read keystore.properties (gitignored, from CI secrets locally).
- .github/workflows/release-android.yml: JDK 17 + Android SDK/NDK + rust targets,
decode keystore from secrets, build --apk, upload to the same draft release.
- vite.config.ts: es2020 build.target for Tauri builds (older-WebView safety).
Runtime fixes (found via on-device testing)
- External links: a real tap on `<a target="_blank">` makes the Android WebView
fire onCreateWindow, which Tauri tries to satisfy via the shell plugin's open
(no such binary on Android -> uncaught error, nothing opens). Strip
target="_blank" from external anchors and route clicks through the opener
plugin in the capture phase. (open-external.ts, main.tsx)
- Boot black screen on old WebViews: crypto.randomUUID() (Chrome/WebView 92+)
ran at module load and threw on WebView 91. Fall back to a manual RFC 4122 v4
built on getRandomValues. (uuid.ts; +4 regression tests, 509 -> 513)
- File export on Android routes through the in-WebView blob download. (IS_MOBILE)
Compatibility
- minSdk 30 (Android 11+), targetSdk 36 (Android 16): covers the large majority
of active devices with a modern, patched WebView + Google Play system updates.
Release: bump manifests 0.28.0 -> 0.29.0; docs (README, FEATURES, PACKAGING,
CHANGELOG). Verified on an Android 13 emulator (render, links, export).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Render a full-screen, non-dismissible consent gate in place of the router
until the user reviews the legal docs (Terms/Privacy/Disclaimer/License,
linked to the GitHub copies) and ticks one 'I agree' box. Acceptance is
recorded in the settings store (legalConsentVersion + timestamp) — no
cookie, no new storage key — and re-prompts only when CURRENT_TERMS_VERSION
is raised, so it is one-time in normal use and re-appears in fresh/incognito
storage.
Also: surface all four docs in About -> Legal (only License was linked
before); add a Windows MSI/NSIS installer license page via bundle.licenseFile;
add an accessible Checkbox primitive; and apply the persisted theme on boot
in main.tsx (fixes a pre-existing dark flash for light-theme users, and makes
the gate render in the right theme before the app shell mounts).
Consent state is additive (no persist version bump); healSettings coerces a
malformed value to 0 so a corrupt file re-shows the gate. 60 new locale
strings (10 keys x 6 languages); validator now 937 ui keys. +9 tests (500 ->
509).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a reusable, router-agnostic ErrorPage (404/403/419/500/offline/runtime)
driven by a pure config/error-pages.ts kind->meta map. Wire standalone
error routes (/403, /419, /500, /offline) plus a catch-all '*' -> 404 as
siblings of the AppShell group, so they render full-screen with no shell —
closing the long-standing gap where unknown hash routes rendered blank.
Add a navigator.onLine hook + non-blocking, dismissible OfflineBanner (the
app works fully offline, so it never blocks input). Redesign the
ErrorBoundary fallback to reuse ErrorPage's 'contained' runtime variant, so
render crashes share the same localized visual language.
120 new locale strings (20 keys x 6 languages) + _schema.json; validator
now expects 927 ui keys per locale. +6 pure config tests (494 -> 500).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Only English ships in the main chunk (fallbackLng + the engine's
bilingual tEn must resolve synchronously); the 10 non-English locale
JSONs become Vite async chunks fetched on first use via
i18next-resources-to-backend. Main chunk: 594.0 -> 264.0 kB min
(204.3 -> 82.0 kB gzip), back under the 500 kB warning threshold.
Every reactive getFixedT site gates on the new useLanguagesReady hook
(an unloaded language would silently render English — and OutputPage
would save that as a wrong-language history entry); Batch/Social bulk
handlers preload all selected languages before their loops; main.tsx
preloads the persisted UI + output languages before first paint. A
failed chunk fetch is retried once via direct import (i18next pins
failed languages permanently), then logged, degrading to English.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two new warning groups — Dialogue / Language (10) and Internet / Digital
life (18) — plus 5 color phobias, 5 suggestive-imagery disclosures, 2
body-image phenomena, and an educational/PSA-purpose disclosure: 207 -> 248
ids across 12 groups. 504 new locale strings (84 keys x 6 locales), VI
flag-prone labels masked per the v0.21.0 precedent. Backfills the
content-inventory docs (audio group + v0.23.0 VFX items were never
documented) and replaces the stale v0.7 warning lines in FEATURES.md.
Adds 8 tests incl. a CONTENT_WARNINGS <-> groups parity guard. Five
manifests bumped 0.24.2 -> 0.25.0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adds a cross-post caption generator (TikTok 4000 / Instagram Reels 2200 / Facebook Reels 2200) with single + bulk modes and JSON import/export, a header dark/light theme toggle synced with Settings, an opt-in translation-quality notice for non-trusted (non EN/VI) output languages, and a Telegram social link. Fixes a stray 'Pick a DDR generation' warning on the OS Rig field via a pure validateCompositeField helper. Extracts a shared buildBilingualBulletSection helper reused across content warnings, tech notes, the translation notice, and the social-post builder. +28 tests (482 total). Gates green: typecheck, lint, validate:locales, knip, build.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Three concerns bundled per the per-version plan:
1. CHANGELOG catch-up — v0.22.0 was shipped without a `CHANGELOG.md`
entry. Backfilled the missing section (Added / Changed / Removed /
Under the hood) matching v0.21.0's structure.
2. +8 VFX warnings in the `photosensitive` group. 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 warnings and AAA / horror games that ship
intense VFX passes (bloom, particles, post-processing) without ever
triggering a strobe-style flash. Total warnings 187 → 195;
photosensitive group 5 → 13. Engine renders each automatically.
3. macOS + Linux in the OS Rig field. `CompositePart.options` widened
from a static array to a union with `(previousParts) =>
RigFieldOption[]`, plus new optional `labelKeyResolver` (swap
"Version" ↔ "Distro") and `hiddenWhen` (macOS has no Edition slot)
per-part predicates. macOS: 7 versions (10 Mojave-era through 26
Tahoe — the 15 → 26 jump is intentional, matching Apple's 2025
year-aligned numbering). Linux: 7 distros gameplay creators
actually use via Proton (Ubuntu / Fedora / Debian / Arch /
Manjaro / Pop!_OS / Mint) with per-distro version cascading. RAM
(the existing 2-part static composite) is unaffected — the union
accepts arrays unchanged. `RigEditor.renderComposite` walks parts
with a `previousValues` accumulator and resets all downstream
parts on parent change so the form can't end up in an invalid
state (e.g. macOS 11 Pro).
Stats: ui.json 835 → 844 keys (+9 = 8 VFX + 1 os_distro), templates
487 → 495 keys (+8 VFX). 6 locales updated in parallel.
454 tests pass (was 445, +9: 7 OS cascading cases + 1 empty-name
fallback + 1 RAM regression check). Gates green: lint, typecheck,
validate:locales (12/12), test, build. Five manifests bumped
0.22.0 → 0.23.0.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Group A — Warnings expansion + UX cleanup:
- New "audio" content-warning group (12 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 from
photosensitive into this dedicated group. Total warnings 175 → 187.
- Remove "Default Genre" from Settings (UI + state + legacy v1→v2
migration + migration tests). `healSettings` now strips both
`defaultGenre` and `defaultGenres` from persisted blobs.
- Remove "Dev Environment" block from About (locked hardcoded specs
that drift on every box upgrade; their wiki link survives in repo).
Group B — Editor additions:
- Video Style era toggle (12 eras: 1980s/90s/00s/10s/20s + modern,
cinematic, retro, vhs, film_noir, anime_mv, documentary). Combines
with `rig.video_editor` to emit a one-line credit like
"Edited in 1990s VHS style using DaVinci Resolve". Renders even
when `skipGraphicsSettings` is on (2D/pixel-art creators still
edit footage). New `src/config/video-styles.ts`; editor-store
persist version bumped 13 → 14 (additive, defensive coercion).
- OS field in My Rig — composite_dropdown following the RAM pattern
(name + version + edition → "Windows 11 Pro"). Windows 10/11 +
Home/Pro/Enterprise/Education/IoT for now; macOS/Linux can be
added later by extending the option arrays.
- `rig.os` locale key added across 6 locales (the rig.* namespace
itself already existed — only the new field's label is new).
Locale stats (per locale): ui.json 816 → 835 keys (+19),
templates.json 473 → 487 keys (+14). 6 locales updated in parallel
(en/vi/ja/es/ko/zh).
Tests: 416 → 445 passing (+29 — audio warnings touch no test, but
new OS composite tests + new video style line tests + reworked
default-genre migration test).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>