FIX: report initializer catalog outages as unavailable, not unregistered

[fei (feiiiiii5)]

Purpose

Fixes #2442.

When /api/initializers/settings succeeds but the registered-Initializer catalog request transiently fails, the Initializers page kept the configured rows but described valid entries as Initializer is no longer registered. — presenting a temporary metadata availability failure as a definitive registration/configuration problem.

What changed

• resolveRegisteredInitializer gains a catalogAvailable flag (default true, so existing call sites are unaffected). When the catalog could not be loaded, rows get an UnverifiedInitializer placeholder whose copy says the catalog is temporarily unavailable and that registration state cannot be confirmed. The "no longer registered" claim is now only made when a successful catalog response actually lacks the name.
• Initializers.tsx tracks catalog availability across loads and refreshes and threads it through BaselineInitializers / AdditionalInitializers.

Validation

• New unit tests for both placeholder paths (initializerLookup.test.ts): catalog-unavailable copy never contains "no longer registered"; available-catalog unknown names still produce the unregistered placeholder.
• New component regression (Initializers.test.tsx): with settings succeeding and the catalog returning 5xx, the baseline row shows "temporarily unavailable" copy, does not show "no longer registered", and a Refresh after the catalog recovers restores the real description ("Registers targets.").
• Full Initializers suite: 75 passed (8 suites); tsc --noEmit clean; ESLint clean on all touched files.

AI usage disclosure

• This PR was developed with AI assistance. All code was human-reviewed and verified locally via the test suites listed above.

[hannahwestra25]

I’m thinking we could replace catalogAvailable with a catalog status union such as:

type CatalogStatus = 'loading' | 'loaded' | 'error'

We could then keep the catalog entries separately and have the lookup return RegisteredInitializer | undefined instead of constructing synthetic RegisteredInitializer objects:

const initializer = registeredInitializers.find(
  (item) => item.initializer_name === initializerName,
)

The renderers could handle each state explicitly: error shows the unavailable message without rendering catalog-derived metadata, loaded with no match shows “no longer registered,” and loaded with a match renders the real metadata. Browse, Add, and Edit could require loaded, while Apply and Remove remain available.

This would avoid interpreting placeholder empty arrays as “Required env vars: None” or “No declared parameters,” and would also prevent cached catalog data from enabling controls after a failed refresh. Could we also cover initial failure, recovery, and loaded-then-failed-refresh transitions?

[fei (feiiiiii5)]

Agreed on all points — the status union is strictly better than the boolean. Plan: introduce CatalogStatus = 'loading' | 'loaded' | 'error', keep catalog entries separate, return RegisteredInitializer | undefined from the lookup, and drop the synthetic placeholder objects entirely. Renderers will branch explicitly (error → unavailable message without catalog-derived metadata; loaded+miss → 'no longer registered'; loaded+hit → real metadata), Browse/Add/Edit gate on loaded, Apply/Remove stay available. For transitions we'll cover initial failure → recovery and loaded → failed-refresh (stale cache must not re-enable controls after a failed refresh, which also answers your cached-data concern). Picking this up now.

[fei (feiiiiii5)]

Closing in favor of #2464, which covers the same fix for #2442 and carries the full review history. My apologies for the duplicate — it was unintentional.

hannahwestra25 your status-union suggestion is implemented there in 20a5d7c: CatalogStatus = 'loading' | 'loaded' | 'error', the lookup returns RegisteredInitializer | undefined with the synthetic placeholders removed, and only a successfully loaded catalog renders the definitive "no longer registered" copy. Thanks for the review — the union is a strict improvement over the boolean.