**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>