[FEATURE] Push corrections from Skaldleita to opted-in users

[deucebucket]

Summary

When Skaldleita discovers it gave wrong metadata (e.g., narrator mismatch via voice fingerprinting), push corrections to opted-in Library Manager users.

Split from #110 Part 3.

Blocked on

deucebucket/skaldleita#127 - Corrections API, identification_log table, and /api/corrections endpoint must be built on the Skaldleita side first.

Requirements (Library Manager side)

• Periodic correction check (on startup + every 24h)
• Settings: receive_corrections (opt-in) and auto_apply_corrections
• Match affected books by SL_ID or audio hash
• Queue corrections for review or auto-apply based on setting
• Dashboard indicator: "X corrections available"

Related

• Smart Pre-Processing Pipeline: Validation, Triage, and Corrections #110 (parent issue - now closed, this was split out)
• Narrator voice fingerprinting integration

[deucebucket]

Ecosystem Link

This issue is linked to deucebucket/skaldleita#127 — feat: Corrections API - push metadata fixes to opted-in Library Manager instances

Both issues are tracked on The Mead Hall project board.