aaron
70e87e3ab5
Mistral pass now produces two concerns in a single flat JSON output:
(a) orientation context (existing four fields, unchanged semantics)
(b) state-type classification: state_type (current/reference/historical),
state_type_confidence (low/medium/high), supersedes_prior_state (bool),
state_type_rationale (text)
Routing fields written as explicit columns on stage_3_queue (separate
ALTER TABLE migration adds them: state_type, state_type_confidence,
supersedes_prior_state, state_type_rationale + index on supersedes).
Safe-cheap defaults on malformed Mistral output: state_type='reference',
confidence='low', supersedes=false. All defaults route to bulk pathway
(no temporal invalidation cost) so Mistral parse drift can't accidentally
trigger expensive single-episode ingest.
Phase A item 2 of three. Sidecar (item 1, commit 8b0a163) already plumbs
custom_extraction_instructions through to /episodes/bulk. Stage 3 routing
logic (item 3) follows.