Initializer catalog failure falsely marks configured entries as unregistered

[romanlutz]

Describe the bug

When /api/initializers/settings succeeds but the registered-Initializer catalog request transiently fails, the Initializers page preserves configured baseline settings but describes valid entries as Initializer is no longer registered. A temporary metadata availability failure is therefore presented as a definitive registration/configuration problem.

Users may incorrectly conclude that their valid configuration is stale or broken. The relevant code is in Initializers.tsx lines 41-67 and initializerLookup.ts lines 10-25.

Steps/Code to Reproduce

1. Return the normal /api/initializers/settings response containing the baseline technique initializer.
2. Make only the registered catalog request fail:

GET /api/initializers?limit=200
HTTP/1.1 503 Service Unavailable

{"detail":"Synthetic initializer catalog failure"}

3. Open Initializers.
4. Observe both the explicit catalog error and the valid technique row described as Initializer is no longer registered.
5. Restore the catalog and choose Refresh; the normal description returns.

Expected Results

The configured row remains visible, while its catalog metadata is clearly described as temporarily unavailable. The UI should not claim that the Initializer is unregistered unless a successful catalog response confirms that state.

Actual Results

The page shows the catalog failure but also substitutes the definitive catalog-miss fallback:

Synthetic initializer catalog failure
Baseline initializers
technique
Initializer is no longer registered.

Screenshots

N/A. The exact visible output is included above.

Versions

• OS: Windows
• Browser: Playwright Chromium (@playwright/test 1.62.1)
• Python: 3.14.4
• PyRIT: main at 37bb7377ec3f8ed547b9a52f4536447c097e0f33

[feiiiiii5]

I'd like to work on this. The fix is straightforward: track catalog fetch success/failure in Initializers.tsx, pass the availability flag through to BaselineInitializers/AdditionalInitializers, and show "Catalog metadata temporarily unavailable." instead of the definitive "no longer registered" fallback when only the catalog request failed. Could you assign this to me? Thanks.