Docs: sync the wiki with the audited behaviour - Home: one release/one prefix (the full run renames its source to 1_source.<ext>), and loudness changes only with -loudness/-master/-album. - Recipes: an unusable album.txt entry is an error, not a skipped warning. - Full-Run-Contract: the rename contract, the min(SHORT_MP4_CLIP_SECONDS, 58) cap and the 0.01 s companion epsilon. - Commands, Configuration, Troubleshooting: cap and loudness wording. Mirrors the #0030 documentation sync in the repository.
Document release naming, orientation-based inputs and the portrait stills - Source images are chosen by orientation, not filename: one landscape master of any size, optionally one portrait for the fitted shorts. - Every generated file carries the track name, so a release keeps one prefix. Source files keep their own names. - Both short framings also ship as stills at full portrait resolution.
Document centre-cut shorts and refresh for productive use Every short is now produced in two framings, so the pages that described a single fitted short were understating what a run returns. - Home: "you get four shorts, not one", with what distinguishes them - Recipes: both framings shown where you actually choose between them - Commands: -full, -short and -nfttoshort rows corrected - Full Run Contract: deliverables rewritten for the four shorts - Troubleshooting: four entries added or corrected - "Source already exceeds delivery QC …" explained as informational — it looks alarming but means converter declined to alter your audio - which short has black bars and which fills the frame - encoder-ladder errors now list every rung; notes that h264_videotoolbox cannot open a session at 4320x7680 - "expects exactly one source image" now explains that rerunning -full in its own output directory is fine, since a derived family is collapsed
Refocus wiki as a usage reference The wiki mixed usage documentation with development tracking (test counts, CI status, package internals, build/lint/deployment notes). Those belong in the repository, not in the reference people consult while using the tool. - Add Recipes: task-first workflows ("publish one track", "normalize a batch") - Add Troubleshooting: the errors converter actually emits, and what to do - Add Installing: setup, getting a binary, opt-in auto-install, env vars - Rewrite Home around what the tool does and where to go next - Remove Architecture and Building-and-Testing (development documentation) Corrections carried over from the audit: - Auto-install is off by default and needs CONVERTER_AUTO_INSTALL_DEPS=1; the wiki previously said it installed silently with =0 to disable - Archival set is *_RF64.flac, *_RF64.wav, *_BW64.wav; there is no *_BW64.flac - Platform floor is macOS 15+ - Dropped test counts and CI status as development tracking