completion-check

Infrastructure verification involves tracing execution paths from user intent to code execution, checking hook registrations, validating database connections, and running end-to-end tests to confirm active integration and prevent dead code.

Finding orphaned functions requires searching for implementations that lack execution path tracing. This identifies dead code by confirming which functions are defined but never invoked by user-facing features or system calls.

Hook verification checks if hooks are properly registered in the system and actively invoked. It traces registration paths and execution flows to confirm implemented hooks are functional rather than dormant.

Database connection validation confirms correct backend wiring by testing active connections. It ensures the infrastructure is properly integrated and invoked during end-to-end execution of relevant features.

Execution path tracing follows the flow from user intent to code execution. It validates infrastructure integration by confirming each component is actively called, preventing wasted effort on disconnected implementations.

End-to-end testing for infrastructure integration is needed after implementing new components like microservices. It verifies features invoke the infrastructure correctly, confirming API gateway registration, database connections, and active usage.