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.

harness/tht/config.py

@@ -327,6 +327,9 @@ class PathsConfig(BaseModel):
     # Revision-qualified curated FK annotations root (P5). When absent, legacy
     # `artifacts/mschema/annotations.yaml` remains the annotations source.
     annotations_root: Path | None = None
+    # Runtime-only, backend-derived effective relationship snapshot. When present,
+    # it is the exclusive FK source; it is not an authored workspace artifact.
+    effective_relationships: Path | None = None
 
 
 class RuntimeIdentityConfig(BaseModel):
@@ -676,6 +679,7 @@ def load_config(path: Path) -> Config:
                     indexes=resolved.indexes,
                     memory=cfg.paths.memory,
                     annotations_root=cfg.paths.annotations_root,
+                    effective_relationships=cfg.paths.effective_relationships,
                 )
             }
         )