# Plugin Registry Readiness And Bootstrap Plan

**Goal:** Make switching from the built-in Feature Plugin registry to database publication safe and repeatable by reporting every publication gap and initializing trusted installed releases without overwriting existing operator decisions.

## Task 1: Readiness Contract

- [x] Assess every installed trusted release against its database definition and immutable version row.
- [x] Detect missing definitions, provider conflicts, disabled definitions, missing versions, Manifest or fingerprint drift, and unpublished current releases.
- [x] Require the latest installed release to be the current published version while accepting older executable releases in publication history.

## Task 2: Idempotent Bootstrap

- [x] Create missing definitions from the in-process trusted Registry only.
- [x] Store canonical Manifest JSON and the installed descriptor fingerprint for missing release versions.
- [x] Publish initialized versions only when a definition has no current publication.
- [x] Preserve existing current publications, disabled definitions, provider ownership, and conflicting release rows.
- [x] Return created, published, repaired, unchanged, and skipped counters.

## Task 3: Publication Center Integration

- [x] Display database readiness counts beside the active Registry resolution mode.
- [x] Add a readiness detail view with release-level state and reason information.
- [x] Add a confirmed bulk bootstrap action protected by a dedicated permission.
- [x] Extend the standalone menu migration with the bootstrap permission.

## Task 4: Verification

- [x] Cover missing, ready, first-run bootstrap, and repeated-run behavior with service tests.
- [x] Extend frontend API, workflow, and menu contract tests.
- [x] Run the frontend production build and backend focused regressions.
- [x] Run the full generator baseline and admin critical-path regression.