verify_data_flow
Renders a component route and matches real network traffic against static analysis predictions. Detects unexpected API calls and confirms mutations by driving user interactions.
Instructions
Render a component's route and check the REAL network traffic against the endpoints that static analysis (get_data_flow, including child components and stores) predicts. Matching is method-aware. The key output is unexpectedApiCalls — observed calls that map to NO predicted endpoint, i.e. real source-vs-runtime drift (dynamic URLs, app-level fetches, or genuine divergence). verdict is 'confirmed' when every observed call is accounted for. Pass actions to drive interactions (fill/click/...) before the network is read — that's how predicted MUTATION endpoints (POST/PUT/DELETE) get exercised and verified. Requires the dev server to be running.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | Optional path substring to disambiguate when the name matches multiple files | |
| name | Yes | Component or composable name whose data flow to verify (e.g., "PatientDetail"). | |
| depth | No | How deep to trace the child component tree for predictions (default 3). | |
| params | No | Values for dynamic route segments, e.g. {"id": "123"}. | |
| actions | No | Optional interactions to run after the route loads and BEFORE network traffic is evaluated (e.g. fill a form and click Save to exercise a POST). | |
| settleMs | No | Extra milliseconds to wait before reading the observed network traffic (default 500). |