[GH-ISSUE #566] Remaining duplicated helpers, fixture aliases and dead guards #293

New issue

Closed

opened 2026-10-15 18:23:32 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:23:32 +00:00

Owner

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

Remaining scope

The empty-process-capture fixture already delegates to the canonical example; that is no longer a pair of independent factories. Remaining work is the misleading Hopper-named Ghidra dossier fixture, duplicated comparator digest/completeness rules, browser frame-tree/navigation rules, and the redundant CLI output guard. Share semantic owners where the rule is actually identical; preserve meaningful provider differences. Comparator correctness is tracked by #558.

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/566 ## Remaining scope The empty-process-capture fixture already delegates to the canonical example; that is no longer a pair of independent factories. Remaining work is the misleading Hopper-named Ghidra dossier fixture, duplicated comparator digest/completeness rules, browser frame-tree/navigation rules, and the redundant CLI output guard. Share semantic owners where the rule is actually identical; preserve meaningful provider differences. Comparator correctness is tracked by #558. ## 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.

bsakaguchi

2026-10-15 18:23:32 +00:00