[GH-ISSUE #562] Error handling: swallowed causes and thrown errors at provider and application seams #287

Closed
opened 2026-10-15 18:23:29 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/562

Remaining scope

Removed CommandShimReplay, LoopbackReplayRecorder, ProcessCheckpoints and related replay paths are no longer in scope. Live work remains in process ownership observations, reference reads, provider/application target resolution and leases, and CLI error projection. Preserve actual causes and distinguish cancellation, invalid input, unavailable dependencies, and normal process disappearance. Do not replace every catch or invariant throw mechanically, and do not hide useful local diagnostics.

Verification

Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable.

This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/562 ## Remaining scope Removed CommandShimReplay, LoopbackReplayRecorder, ProcessCheckpoints and related replay paths are no longer in scope. Live work remains in process ownership observations, reference reads, provider/application target resolution and leases, and CLI error projection. Preserve actual causes and distinguish cancellation, invalid input, unavailable dependencies, and normal process disappearance. Do not replace every catch or invariant throw mechanically, and do not hide useful local diagnostics. ## Verification Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable. This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#287
No description provided.