Remove legacy-facing UI labels and redundant metadata #24
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The UI should no longer expose implementation/source labels that only made sense during the refactor or legacy migration. Example: labels like Source: SQL are redundant now that Django/SQL is the only source of truth. Audit dashboard, host, run, snapshot, config, retention, self-check, and status pages for similar clutter and simplify the copy around actual operator decisions.