David's problem: UI state must tell the truth

Kerra has many long-running states: preparing lecture notes, generating workspaces, waiting for an LMS session, prefetching files, retrying failed jobs, and marking work ready. if the UI lies about any of those states, users lose trust.

his transcripts show repeated focus on stale cards, false success toasts, hidden preparing states, extension-missing popups, and whether a card is actually connected to a live background run.

you cant just show it blindly

the product principle is that UI state should be a faithful state machine, not a hopeful label.