docs: reconcile catalog run history and fleet state

docs/operations/database-management.md

@@ -15,6 +15,31 @@ nullability, primary-key positions, and ordered foreign-key pairs are observatio
 schema and cannot be manually created, renamed, or structurally edited. Descriptions are the
 editable metadata.
 
+## Navigate the Fleet Ledger surface
+
+Database Management opens Fleet Ledger inside the normal application shell. Only one data grid is
+shown at a time: choose a database to see its tables, choose a table to see its columns, or open the
+database's relationships view. Use the emphasized back control or breadcrumb to return to the parent
+grid.
+
+The KPI strip reports tables, columns, sensitive columns, relationships, and description coverage.
+It uses `GET /catalog/metrics` without `databaseId` for installation totals and with `databaseId` for
+the current database. Choose a selection-scoped operation from the action selector and then press
+**Run**; unavailable operations remain listed with an explanation. Row-specific actions are the icon
+controls in the final column, and each navigation or action icon has an immediate conceptual tooltip.
+
+Configuration, object details, metadata editors, synchronization history, description history,
+sensitive-field review, and suggestion-run history open in right-side drawers backed by the
+production catalog APIs.
+Closing a history drawer does not cancel a durable background run. Existing permission checks,
+dirty/busy navigation guards, stale-state handling, and write-only secret behavior continue to
+apply.
+
+For temporary comparison in development or staging, add `?db-ui=legacy`; the parameter is honored
+only by Vite development or an environment explicitly configured with
+`VITE_DB_MANAGEMENT_LEGACY=true`. The separate prototype on port `5173` is not the application and
+remains available only until the integrated Fleet Ledger surface passes owner acceptance.
+
 ## Configure and test a database
 
 1. Open **Database Management** and choose a workspace.
@@ -54,6 +79,11 @@ administrator can ask the configured model to suggest flags from structural meta
 schema, table and column names, data types, nullability, primary keys, and foreign keys). Suggestions
 remain an unsaved draft until a human reviews and saves them.
 
+The page exposes separate histories for description generation and sensitive-field suggestions.
+Sensitive-suggestion history stores the selected model, scope, status, aggregate counts, timestamps,
+and sanitized events. It does not store the proposed per-column flags, prompts, raw model output, or
+provider diagnostics; closing an unsaved review still discards that draft.
+
 For a column with `sensitive=false`, the worker may read at most five source rows and five
 representative non-null values through a read-only connector. For `sensitive=true`, the source query
 does not request that column's values; deterministic plausible values derived only from its name and