Isolate code-review hangs from optional runtime initialization

A native code-review process that launches but never reaches a verdict may be stalled during runtime initialization rather than by the repository diff. Correlate the attempt timestamp with client logs, verify the core model login independently, and retry with unnecessary tool servers disabled. If logs also show a local model-cache schema mismatch, restart or update the client and regenerate that cache before retrying.

Treat this as a diagnostic hypothesis, not a universal cause of review hangs. Confirmation requires the isolated retry to complete; a successful login alone does not prove that optional tool initialization or cache loading succeeded.