Context
Flight's Phase 2 review found that ParseError and ProviderError are declared in the StateError hierarchy but never thrown. IO parsers delegate to existing functions that throw generic Error objects, so callers can't discriminate parse failures using instanceof ParseError.
What to do
At the facade boundary (in collections.ts and handles.ts), catch parser exceptions and wrap them with ParseError for consistent error discrimination.
Branch
Work should be done on diberry/sa-phase1-interface
Severity
Nice-to-have (Phase 3 enhancement)
Context
Flight's Phase 2 review found that
ParseErrorandProviderErrorare declared in theStateErrorhierarchy but never thrown. IO parsers delegate to existing functions that throw genericErrorobjects, so callers can't discriminate parse failures usinginstanceof ParseError.What to do
At the facade boundary (in
collections.tsandhandles.ts), catch parser exceptions and wrap them withParseErrorfor consistent error discrimination.Branch
Work should be done on
diberry/sa-phase1-interfaceSeverity
Nice-to-have (Phase 3 enhancement)