- 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>
Upscaled video (#235): "Upscaled from" in Video settings, the
[4K Upscaled] title badge, the Upscale line in VIDEO SETTINGS and an
automatic tech note about upscaled detail.
- CHANGELOG v1.5.0, ROADMAP entry and status
- docs: FEATURES, CONTENT-INVENTORY (+ Vietnamese), ARCHITECTURE and
TECH-SPEC (upscale.ts, store v21, test count), CLAUDE.md
- version references: PACKAGING, DISCLAIMER + Vietnamese, the
bug-report template
- six manifests 1.4.0 -> 1.5.0
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>
GitHub retired the macOS 14 runner image on 2026-11-02. The v1.4.0 tag's
Release Desktop run had its macOS job cancelled before any step ran
("The configuration 'macos-14-arm64-us-default' is not supported"); the
Windows and Linux builds went through. macos-15 is the direct Apple
silicon successor.
The macOS .app.tar.gz for v1.4.0 will come from the workflow's manual
`workflow_dispatch` re-run with tag v1.4.0, which takes the job matrix
from main and checks out the tag's code. PACKAGING's runner table and
the v1.4.0 CHANGELOG entry say so.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A LUT field in My Rig (#230), the boss's name as a tag in boss videos
(#231), and this week's dependency updates (#228, #229).
- CHANGELOG v1.4.0, ROADMAP entry and status
- version references: ARCHITECTURE, TECH-SPEC (+ test count), PACKAGING,
FEATURES, DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.3.2 -> 1.4.0
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>
Folds #223-#227 into one change. Each of them failed the required
`check` job the same way: a new version makes THIRD_PARTY_NOTICES.md
stale, and merged one by one they would conflict with each other in
package-lock.json and the notices.
- i18next 26.5.3 -> 26.5.11, react-i18next 17.1.0 -> 17.1.9
- lucide-react 1.59.0 -> 1.64.0, zustand 5.0.15 -> 5.0.16
- knip 6.42.1 -> 6.44.0
- wrangler 4.151.2 -> 4.152.0 (miniflare 5.20261019.2-beta)
- @tauri-apps/cli 2.12.3 -> 2.12.4 (matches the tauri 2.12.4 crate)
Installed with `npm install --before=2026-10-30`, the same 7-day
cooldown Dependabot uses; lucide-react and knip land on the newest
releases past it (1.64.0, 6.44.0) rather than Dependabot's 1.61.0 and
6.43.0. The undici override stays: miniflare 5.20261019.2-beta still
pins undici 7.29.1. THIRD_PARTY_NOTICES regenerated.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rate limiting for the website: Workers Rate Limiting bindings in front
of the gate, behind a WAF rate limiting rule at the zone (#220).
- CHANGELOG v1.3.2, ROADMAP entry and status
- version references: ARCHITECTURE, TECH-SPEC (+ test count), PACKAGING,
FEATURES, DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.3.1 -> 1.3.2
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>
Tauri 2.12.4, the desktop's Save / Open dialogs off the async workers
(#216), SonarCloud in CI (#215) and this week's dependency updates with
alert #49 closed (#217).
- CHANGELOG v1.3.1, ROADMAP entry and status
- version references: ARCHITECTURE, TECH-SPEC, PACKAGING, FEATURES,
DISCLAIMER + Vietnamese, the bug-report template
- six manifests 1.3.0 -> 1.3.1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- undici 7.30.1 through `overrides` (alert #49, GHSA-xjj6-f33q-929c,
dev only): miniflare pins undici exactly, so Dependabot's security
job fails with security_update_not_possible. The note in
dependabot.yml says when to drop the override.
- npm, newest releases at least seven days old (the Dependabot
cooldown): react + react-dom 19.3.1, i18next 26.5.3,
react-i18next 17.1.0, lucide-react 1.59.0, simple-icons 16.35.0,
eslint 10.13.0, typescript-eslint 8.72.0, knip 6.42.1,
postcss 8.5.31, @types/node 26.6.5, wrangler 4.151.2
- tauri crates to match @tauri-apps/api 2.12.4: tauri 2.12.4,
tauri-build 2.7.3, tauri-plugin-dialog 2.8.3, -opener 2.7.2,
-single-instance 2.5.4, -fs 2.7.1
- THIRD_PARTY_NOTICES regenerated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PACKAGING (the dialog commands, the unit tests) and CLAUDE.md's design decision on paths say how the dialog commands run, so the next command doesn't bring rust:S7493 back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's first CI analysis of main, the first one that reads Rust,
flagged rust:S7493 in export_text_file: a blocking fs::write inside an
async command holds one of the async runtime's worker threads. Waiting
for the native Save / Open dialog blocks the same way, for as long as
the user takes to choose.
Both commands now validate the filter first, then run the dialog and the
file I/O through tauri::async_runtime::spawn_blocking. Writing the
picked file moves into write_picked, next to read_picked, with a test.
The dialogs' blocking API only needs to stay off the main thread, which
the blocking pool is, as the runtime's workers were.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The coverage scope is spelled out in TECH-SPEC, vitest.config.ts and sonar-project.properties; the table row only says what the command does.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scanner indexed every PNG, ICO, ICNS and the Gradle wrapper's jar and warned about each one it read as UTF-8 text (about seventy warnings per run). There is nothing in them to analyse.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
SonarCloud's Automatic Analysis is off. The new `sonarcloud` job in
ci.yml runs SonarSource/sonarqube-scan-action v8.3.0 after `check`, with
the LCOV report that `check` now uploads; it never installs npm packages,
so SONAR_TOKEN never shares a job with them, and it fails with the
quality gate. Fork and Dependabot PRs skip it (no repository secrets).
sonar-project.properties analyses the tests as tests, imports the
coverage and excludes from it everything Vitest does not measure. Vitest
now also measures src/config, src/store and src/utils, next to the
engine, the Worker and the build plugins. The job passes package.json's
version as sonar.projectVersion, so the "previous version" new-code
period starts again at every release.
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>
React 19 passes `ref` to function components as an ordinary prop, and the
React team has said forwardRef will be deprecated in a future release.
Button, IconButton, Input, Select and Textarea become plain function
components whose props extend ComponentProps<"button" | "input" | …>,
which already carries `ref`; each passes it on (Button to both Slot.Root
and <button>; IconButton through its props to Button). Their displayName
lines go too: the function names show in DevTools.
IconButton and RigEditor import the ReactNode type instead of reaching for
the global `React` namespace.
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>
- .node-version 22 -> 26 (CI, the release workflows and Workers Builds
read it; Workers Builds also has NODE_VERSION=26 set)
- package.json engines: node >=26
- vitest: run workers with --no-experimental-webstorage. Node 25+ defines
a global `localStorage` that is undefined without --localstorage-file;
zustand's persist only falls back to memory when reading the storage
throws, so every store `set` crashed on undefined.setItem (39 tests in
4 files). Without Web Storage the stores fall back as they did on 22.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>