check-impl

Read the Controller or Handler source code to confirm the real response structure instead of relying on memory. Check whether the response is a plain array, a paginated object like { items, total }, or wrapped in an envelope like { success, message, data }, then write a request test covering normal and empty paths.

Modal and Drawer containers typically destroy child components on close, so component state is lost by default. To preserve state, use options like keepDOM or destroyOnClose={false}, and check how existing components in the same container are configured in your project.

Historical records will have empty, zero, or null values for the new field, so filters relying on it may silently exclude old data. Verify query behavior against real legacy records and add a fallback query path, such as joining a detail table, when aggregated data lacks the needed dimension.

check-cross-layer verifies structural completeness of a change across layers, while check-impl verifies assumption correctness in the implementation. They are complementary: run cross-layer for structure and check-impl as a post-implementation safety net for wrong premises.

Write verification tests whenever a change touches API contracts, data models, or cross-layer data flows. Prioritize the most fragile assumptions such as parameter names and nesting levels, cover null and zero-value paths, and actually run the tests rather than only reviewing code statically.