fix(schema): accept unknown speaker_map source instead of aborting the parse (#595)

[silverstein]

Fixes #595, reported by @jmh1313 with a diagnosis that identified both the bug and the thing that caused it.

The bug

An out-of-vocabulary speaker_map[].source aborted the entire frontmatter parse, hard-blocking minutes resummarize on that file. The sharp part, as the report puts it: resummarize's own documented field contract lists speaker_map among the fields preserved untouched, and it failed before the model call. So the command refused to run because of a value it would never have read or written.

Hand-edited files are a supported input class. The desktop app's Open in Editor button invites direct edits, resummarize's own premise is that the file is open in an editor right now, and minutes import text ingests third-party archives that never went through the pipeline. A label describing how an attribution was derived should not be able to make a meeting unreadable.

The trap that generated it

user-confirmed is not a value Minutes has ever emitted. The schema doc listed the valid enum, then eleven lines later labelled the confidence ladder L3 (user-confirmed). Someone hand-editing reads that and writes source: user-confirmed. The actual variant is manual.

Fix

• AttributionSource gains an untagged Unknown(String) in both definitions (core and reader). The raw label round-trips verbatim rather than being normalized, so provenance survives a rewrite by a command that never consumed it. This drops Copy; three call sites now take a reference.
• The schema doc now states the L-levels are a conceptual ladder, not the on-disk vocabulary, and gives the source: value for each level, explicitly noting L3 is manual and that user-confirmed is invalid.
• The hand-maintained TypeScript copy is widened to match, and the JSON schema snapshot now describes the lenient shape (anyOf: [known enum, string]).

Not done: ask 3, a minutes consistency --fix repair path for out-of-vocabulary values. Worth doing, but it is a separate feature rather than part of unbreaking the read path.

Verification against the reporter's exact repro

unfixed:  Error: frontmatter does not parse: speaker_map[0].source: unknown variant `user-confirmed`
fixed:    preview completes; --apply writes; file still reads `source: user-confirmed`

Core lib 1176 passed, CLI 82 passed, clippy clean on core and reader, fmt clean, SDK typecheck clean.

One note on the diff

tauri/src-tauri/gen/schemas/*.json are regenerated files carrying the tauri 2.11.5 permission additions from #590, which landed without regenerating them. They are unrelated to this fix but correct, and dropping them would leave main stale.

🤖 Generated with Claude Code