Mint any brand-token holder that is still missing, across every catalogue we know about.

THE BACKSTOP, not the primary mechanism. Minting is ensured at catalogue deploy, on the already-deployed path, and immediately before registerContent — all three inside the window where no revenue can yet have arrived. This pass exists because that used to be a single fire-and-forget side effect of deploy whose one transient failure was permanent and invisible: eight of nine mainnet catalogues had never minted a holder, two of them while actively earning.

Cheap and safe to run often: a fully-minted catalogue costs one hasMinted view call per split and sends no transaction. Catalogues with no code on the active chain are reported, never minted into.

Deploy as a Cloud Scheduler job (suggested: hourly) once verified.