shard_removal_triggers_catalog_cache_invalidation.js uses two routers, removes a shard using one of them, shuts down the shard, then waits for the other router to reload its shard registry and stop targeting the removed shard. The index consistency shutdown hook runs commands on the first router, which isn't guaranteed to have reloaded its shard registry and may fail to target the shut down shard, failing the test. To avoid this, the index hook should be disabled.