feat: consolidate database management work

Add catalog-owned logical relationships and runtime snapshots, extend the database-management UI and validation coverage, and document the updated operational workflow.

Keep active sensitive-generation status in a tooltip and indicator, and update the layout E2E to follow the history action in its new database-scoped location.

frontend/src/shell/database-management/DescriptionGenerationDrawer.test.tsx

@@ -248,6 +248,33 @@ test("reopens a terminal run from newest-first persisted history", async () => {
   expect(within(drawer).getByText("3", { selector: "[data-count='generated']" })).toBeVisible();
 });
 
+test("styles a successfully completed run with the success background", async () => {
+  const completedRun: DescriptionGenerationRun = {
+    ...runningRun,
+    status: "completed",
+    total: 1,
+    processed: 1,
+    generated: 1,
+    updatedAt: "2026-08-28T08:02:00Z",
+    finishedAt: "2026-08-28T08:02:00Z",
+  };
+  server.use(
+    http.get("/api/catalog/description-generation-runs", () => HttpResponse.json([completedRun])),
+    http.get("/api/catalog/description-generation-runs/:runId", () => HttpResponse.json(completedRun)),
+    http.get("/api/catalog/description-generation-runs/:runId/events-list", () => HttpResponse.json([])),
+  );
+  renderDrawer({ initialRun: completedRun });
+
+  const history = await screen.findByRole("region", {
+    name: "Description generation history",
+  });
+  const completedHistoryItem = within(history).getByRole("button", {
+    name: /Completed.*missing/i,
+  });
+  expect(completedHistoryItem).toHaveAttribute("data-status", "completed");
+  expect(completedHistoryItem).toHaveClass("bg-[oklch(var(--success)/0.1)]");
+});
+
 test("offers Unlock only for an apparently stale active run and explains the interruption", async () => {
   const user = userEvent.setup();
   const staleRun: DescriptionGenerationRun = {