YTDescGen is feature-complete; from 1.6.0 on it is maintained, not
extended. Still accepted: scheduled dependency updates; fixes for high or
critical CVEs and serious runtime issues; major language / runtime /
framework upgrades; bug, UI/UX and accessibility fixes, and options added
to or removed from the app's lists when people really need them;
translation fixes; Cloudflare / Worker changes the platform forces and
website incidents.
- README: status, CI, Qodana and SonarCloud badges; a Project status
section; Contributing and the Roadmap row follow it.
- CONTRIBUTING: a Maintenance mode section, Option requests, issue and
pull request rules, What We Want / Don't Want.
- SECURITY, MAINTAINERS, CLAUDE.md: the policy where each one needs it.
- ROADMAP: status block, a Maintenance mode section, Phase 5 and the
backlog frozen. FEATURES: the extension points are frozen.
- Issue forms: Feature request removed; Option request and Translation or
wording fix added; Bug report and Accessibility barrier now carry the
`needs-triage` label (`triage` never existed). config.yml points feature
ideas at Discussions → Ideas. The PR template gains a Scope checklist.
- maintenance-triage.yml closes, with a bilingual comment and the
`out-of-scope` label, feature issues and `feat:` pull requests from
outside contributors (scopes options, a11y and i18n stay open) and
anything labelled `out-of-scope`. pull_request_target without checkout;
listed under zizmor's dangerous-triggers ignore with the reason.
Labels created on the repository: out-of-scope, needs-triage, i18n,
option-request.
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>
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>
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>
- CHANGELOG: the v1.0.0 entry (moving house, new interface, data fixes,
backup & restore, faster entry, catalogs, desktop hardening, CI).
- README: the web app at ytgenerator.stream, what moved from GitHub
Pages, current features, privacy as it is now (Cloudflare delivery,
Turnstile, cookieless analytics on the web only), contacts by purpose;
the dead Discord invite and the old email are gone.
- docs/HOSTING.md (new): Worker routing, cookies, headers, secrets,
one-time dashboard settings, local dev, previews and rollback.
- CLAUDE.md rewritten for the real stack, layout, commands and rules.
- CONTRIBUTING / PR template / issue templates: main-only branching,
the required checks, 8 locales, Android and current versions; issue
links to security advisories, the wiki, Discord and poli0981.dev/links.
- DISCLAIMER (+ Vietnamese), NOTICE: current model disclosure and the
copyright / DMCA contacts. PRIVACY: backup locations and the moving
notice on the old address.
- Version 1.0.0 in package.json, package-lock.json, tauri.conf.json,
Cargo.toml and Cargo.lock.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Three things had gone stale or were never quite right:
- **Tech stack** still said React 18 / Tailwind 3. v0.37.0 moved to React 19,
Tailwind 4, Zustand 5 and i18next 26.
- **AI disclosure** named "model 4.7 Opus, 1M-context variant", two
generations old. Now names the family rather than pinning a version that
goes stale on every model release.
- **"~8 MB native desktop app"** was optimistic and incomplete. Measured
against the v0.37.0 assets: the Windows exe is 2 MB, the msi and macOS
bundle 4 MB, deb/rpm 5 MB — but the Linux AppImage is 76 MB because it is
self-contained, and the APK is 54 MB. Says "2–5 MB installers" and calls out
the AppImage rather than quoting one number that only holds for some
platforms.
Checked and left alone: "248 content-warning IDs across 12 groups" is exactly
right (`CONTENT_WARNINGS` has 248 unique ids, `CONTENT_WARNING_GROUPS` has 12).
Co-Authored-By: Claude Opus 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>
**docs/I18N.md was wrong in a way that would waste a contributor's afternoon.**
It said adding a locale to `SUPPORTED_LANGUAGES` was "the only registration
step". It is one of four, and the missing ones fail differently: the
`SupportedLanguage` union is a compile error, `MULTILINGUAL_TAGS` is a compile
error, 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. Also noted: `SUPPORTED_LANGUAGES` is not type-bound
to the union and every consumer casts, so a mismatch compiles cleanly.
Also documents the `--copy-english` / `--force` flags on the locale generator,
which only started existing in v0.35.0 despite having been advertised in
package.json since v0.1.
Elsewhere:
- **DEVELOPMENT.md** — the five new npm scripts, including why `format:check`
excludes markdown and locale JSON, and why `typecheck:all` exists.
- **TECH-SPEC.md** — the real CI job, a new Field Limits section, and how
over-limit enforcement derives from the engine's long-ignored `warnings`.
- **ARCHITECTURE.md** — the settings→engine mapping and its two guards, the
two-source validation state, and an honest note that the first Strict Mode
implementation typechecked, passed tests, and did nothing.
- **FEATURES.md** — the settings table still listed `Default Genre` and
`Auto-save Draft`, removed in v0.22.0 and v0.3. Replaced, plus a guardrails
section.
- **README.md** — guardrails in the feature list, and a link to the wiki.
The wiki itself (12 pages: quick start, glossary, field reference, guardrails,
batch/social, import-export, languages, privacy, troubleshooting, FAQ, release
process) is published separately — it lives in its own repository.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add an explicit "Requirements & tested versions" section for the Android build:
- Minimum Android 11 (minSdk 30), target Android 16 (targetSdk 36), universal ABIs.
- Tested Android 11 -> 16 on emulators, plus a real device on Android 12.
- Rationale for the Android 11 floor: device coverage, a modern auto-updating
WebView (why the Android 12 real device worked but a stale WebView-91 emulator
black-screened), and component-level security upkeep (Play system updates /
Play services / WebView) since OS bulletins for 11-13 have ended.
Touches docs/PACKAGING.md, docs/FEATURES.md, README.md only — no code change.
Co-Authored-By: Claude Opus 4.8 (1M context) <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>
Resolves the 4 high-severity esbuild advisories (GHSA-gv7w-rqvm-qjhr,
GHSA-g7r4-m6w7-qqqr) deferred from v0.27.0. esbuild 0.17.0-0.28.0 is
vulnerable; the fix (0.28.1) is only reachable via vite 8 -- vite 7.3.3
pins esbuild ^0.27.0 and cannot reach it. Dev-server-only; the shipped
static bundle was never affected. npm audit: 4 high -> 0.
- vite ^7.3.3 -> ^8.0.16, @vitejs/plugin-react ^4.3.0 -> ^5.2.0,
tsx ^4.16.0 -> ^4.22.4 (vitest 4.1.8 already supports vite 8)
- vite 8 bundles with Rolldown: manualChunks object form -> function
form (vite.config.ts) is the only source change required
- Full gate chain green (typecheck, lint, knip, validate:locales,
500/500 tests, build); dev/preview + Tauri-context build verified
- Bump 5 manifests 0.27.0 -> 0.27.1; CHANGELOG + stack-version docs
Co-Authored-By: Claude Opus 4.8 (1M context) <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>
Security/deps: react-router 6.30.3→6.30.4 (moderate open-redirect patch, non-breaking) and vitest 3.2.4→4.1.8 (clears the dev-only critical Vitest-UI advisory); all 482 tests pass unchanged on the new major. npm audit now reports 0 vulnerabilities. Removed unused serde/serde_json from src-tauri/Cargo.toml (no refs in src-tauri/src/; cargo check confirms the crate still compiles). Documented the cross-post caption generator (Social tab) in README + docs/FEATURES.md. Five manifests bumped 0.24.0→0.24.1.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bundles five changes for the v0.19.0 release:
- Content warnings: +28 IDs (25 clinical phobias in the phobias group,
3 discrimination terms in the sensitive group); 97 -> 125 total,
fully translated across all 6 locales. Purely additive.
- Dead-code sweep: add knip tooling (knip.json + npm run knip); remove
the unused use-debounce.ts hook and ~13 unreferenced exports; tighten
~12 symbols to module-private.
- Security: npm audit fix for the brace-expansion moderate DoS
(transitive dev dependency, 5.0.5 -> 5.0.6).
- UI: scroll-to-top floating button that scrolls the AppShell <main>.
- Docs: accuracy pass across TECH-SPEC, ROADMAP, FEATURES,
CONTENT-INVENTORY (+ vi mirror), CHANGELOG, README.
Version bumped 0.18.0 -> 0.19.0 across all five manifests.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Bundles one new feature, two persistence-layer bug fixes, one cleanup,
and a transparency doc:
- feat: Vietnamese bank dropdown in VietnameseDonateEditor when output
language is `vi`. 30 banks from the SBV 2026 list (Big 4 state-owned
+ top 22 joint-stock + 4 foreign), plus a "Khác (nhập tay)" option
that reveals a free-form text input for unlisted banks. Persisted
shape (`vnBankName: string`) is unchanged.
- fix: UI language reverted to English on every app relaunch because
i18next initialised synchronously while the Zustand persist hydration
was async and nothing bridged the persisted value back to i18n.
App.tsx now reads `appLanguage` at mount and subscribes for future
changes (covers both the synchronous localStorage path and the async
Tauri settings.json path).
- fix: Settings JSON export was dumping the entire on-disk
`settings.json` — which contains every Zustand store's data. The new
exporter writes only the Settings store through the envelope-typed
flow already used by the Profiles tab. Importer rejects pre-v0.18.0
multi-store dumps with a friendly toast instead of silently injecting
profile / template / history rows into the Settings store.
- cleanup: removed the "Open Folder" button from Settings (low usage,
Tauri-only). The `ensure_dir` Rust command stays for other paths.
- docs: new `docs/CONTENT-INVENTORY.md` + Vietnamese mirror listing
every video type (20), genre (41), and content warning (96 across 8
groups) the editor surfaces. Linked from README's Documentation table.
Locale schema +2 keys × 6 locales (vnBankNameSelectPlaceholder,
vnBankNameOther). 720/720 ui keys per locale. 426/426 tests pass.
Bundle 427.46 kB (under 500 kB cap).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>