review-flow-graphlisted

# Review — Flow Graph Abstractions Reviewer for reusable ReactFlow/graph integration layers. Use it when a repository has a shared graph surface consumed by domain modules. --- ## Scope Applicable to shared graph/flow abstraction folders such as `src/core/flow/**`, `src/graph/**`, `src/shared/flow/**`, and consumers adding a new graph surface through the shared public API. If the repository has local graph docs, read them first and treat this checklist as a neutral baseline. --- ## Checklist ### Public Surface - Domain modules consume the documented public graph surface instead of mounting internal shell or bridge modules directly. - New exports are added only when more than one domain consumer needs them. - Public graph components own common setup such as loader/splitter/viewport wiring/toolbars. ### Store and Lifecycle - Static viewers and expandable/progressive graphs use the appropriate base store or abstraction. - Subclasses initialize base state before local observability/reactivity. - Domain side effects preserve base selection/click/reset behaviour. - Expand/collapse graphs define fetch and direction/availability contracts explicitly. - Independent graph data fetches run in parallel and merge through a deduplication helper. ### Internal Boundary - Layout helpers, shell components, bridge hooks, SVG/canvas geometry helpers, export helpers, and popup/container utilities stay internal unless there is a real shared public need. - New pure node/edge helper