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>
useMultilangOutput had drifted out of sync with useGeneratedOutput and never
forwarded showTranslationQuality, showThirdPartyAds, or the always-English tEn
translator to renderAll. As a result the AI-translation disclaimer (and the
identical third-party-ads disclaimer) never appeared when the Output page showed
two or more languages, and the bilingual blocks rendered target-language-only.
Bring the hook to parity with the single-language hook: destructure both
settings, build a memoized tEn, and pass all three into renderAll. Single-language
output and the Batch page were already correct. No engine/store/config/i18n
changes; 513 tests + locale validation (937/542) pass; verified live.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
GitHub deprecated the Node.js 20 Actions runtime on 2026-06-16 (removal
from runners 2026-09-16). release-android.yml was the only workflow still
pinning actions whose latest-supported runtime was node20; each has a
newer major declaring `runs.using: node24`, so bump to the floating major:
actions/setup-java v4 -> v5 (node20 -> node24)
android-actions/setup-android v3 -> v4 (node20 -> node24; defaults
cmdline-tools 20.0, NDK install
via sdkmanager unaffected)
actions/cache v4 -> v5 (node20 -> node24)
softprops/action-gh-release v2 -> v3 (node20 -> node24)
All four bumps are pure runtime migrations with unchanged inputs. The
node24 majors require Actions Runner >= 2.327.1, which GitHub-hosted
ubuntu-latest already satisfies. ci.yml and release-desktop.yml use only
checkout@v6 / setup-node@v6 (already node24) plus composite actions
(rust-toolchain, tauri-action) that have no Node runtime, so no changes
there. App build node-version (22) is unaffected — this is action
runtimes only. Verified with actionlint (clean) + YAML parse.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Side-by-side rows that never collapsed on narrow mobile (~360-400px) made
the Batch and Profile screens overrun the viewport horizontally on Android
and web mobile. Make those rows responsive (flex-col -> sm:flex-row) and
sweep a few adjacent overflow spots. Layout-only; desktop is unchanged
(every change gated behind the sm: breakpoint).
- Batch: part-range row stacks below sm (full-width Generate); copy-button
rows wrap.
- Profile: tab pill + Export/Import stack onto separate rows; Profile/
Preset/Template cards stack action buttons below content and let long
names wrap (min-w-0).
- Sweep: Settings responsive padding + wrapping header (Import/Export shows
on Android), VideoSettingsForm grid 1-col below sm, Modal pinned to
calc(100% - 2rem).
Bumps five manifests 0.29.0 -> 0.29.1 (package-lock.json resynced from a
0.28.0 drift). typecheck/lint/locales/513 tests/build all green; verified
live at 375px and 1280px with zero horizontal overflow.
Co-Authored-By: Claude Opus 4.8 <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>
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>
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>
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>
Node 20 reached end-of-life in April 2026 and GitHub is removing it
from runner images (actions/runner-images#14029), so setup-node now
downloads it on every run. Node 22 satisfies Vite 7's engine range
(^20.19 || >=22.12) and matches the docs/TECH-SPEC.md snippets.
Also sync the two doc mentions of CI's Node version.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Build-only run 27388695090 on windows-2025-vs2026 produced both MSI
and NSIS bundles cleanly, so windows-latest stays unpinned.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
windows-latest redirects to this image from June 15, 2026. Build-only
(no tagName), so no release is touched. Reverted before merge.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
GitHub forces the Node 24 runtime for actions on June 16, 2026 and
removes Node 20 from runners September 16, 2026. checkout v4,
setup-node v4, configure-pages v5, upload-pages-artifact v3 and
deploy-pages v4 all declare node20; their current majors (v6/v6/v6/
v5/v5) declare node24. tauri-action@v0 already runs node24 and
dtolnay/rust-toolchain is composite, so both stay.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dependabot cargo security-update jobs for rand and glib fail with
security_update_not_possible every time Cargo.lock changes on main
(runs 27387346373, 27387346324). Both are transitive deps of tauri:
rand 0.7.3 is pinned to ^0.7 by phf_generator 0.8 (via kuchikiki),
fix is 0.8.6; glib 0.18.5 is pinned by the gtk-rs 0.18 stack, fix is
0.20.0. Cargo cannot resolve the patched versions until tauri bumps
those subtrees, so ignore both to stop the recurring red runs.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>