Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix(mcp-optimizer): harden startup cleanup against edge cases

Addresses review feedback on #2086:

- useMcpOptimizerStartupCleanup no longer latches `hasRunCleanup` before
  awaiting ToolHive readiness. If the 60s readiness wait times out the hook
  can now retry on a subsequent effect re-fire. An `inFlight` ref still
  prevents concurrent starts.
- useCleanupMetaOptimizer parses ALLOWED_GROUPS defensively (trim, first
  non-empty comma entry) and only restores clients when the target group
  still exists in the fetched groups list. Unregister + group delete still
  proceed regardless, so the optimizer state never lingers.
- mcp-optimizer-startup-cleanup.spec.ts bumps the cleanup poll timeout
  from 60s to 120s so slow CI runners don't flake when the app-side
  readiness wait consumes most of the original budget.

Adds a regression test that asserts restoration is skipped when
ALLOWED_GROUPS points to a group that no longer exists.

Made-with: Cursor