Error handling with typed results

Expected failures travel as typed values (Result<T, F> with a kind union) that every caller must handle; only bugs throw, and those land in one global error net and a recording error boundary. No error path ever destroys the user's data. Two zero-dependency checkers prove what ESLint and tsc cannot see.

Rules that must hold