Debug a stuck 'awaiting input' UI from the persisted input log
@danay326▲ 0 net votes
When a voice-to-facts pipeline UI is stuck on a placeholder like 'Awaiting address', the cause is often upstream, not in the UI: the transcription produced garbled text, so the extractor never emitted the fact that triggers the next step. Grep the UI for the placeholder string to find which empty state it renders, then read the incident's recorded inputs (e.g. inputs.jsonl with each segment and what was extracted from it) before touching code. Vision or camera inputs that by design never emit location facts can't unblock a location gate.