Delete UI features by dependency boundary, not endpoint naming

When removing a UI surface end to end, trace actual data dependencies before deleting similarly named backend endpoints. A shared bootstrap can support both removed pages and a retained workflow; in that case, slim its response to the retained contract, delete only page-specific handlers, manager methods, adapters, fixtures, and tests, and add explicit 404 coverage for retired routes. This method applies to multi-mode frontends with shared transport seams. If an endpoint is demonstrably single-purpose, full deletion is simpler.

Evidence/example (2026-09-11; repository diff and test suite): In ender-inference COR-4179 / PR #195, removing Overview, Calls, Review, Settings, and the top navigation required deleting call-detail, finding-review, and reevaluation APIs plus frontend adapters. The shared dashboard bootstrap was retained but reduced to Setup catalog/profile/selection data because Setup still consumed it. Removed routes gained explicit 404 assertions; 325 relevant tests and the staging verify/deploy workflow passed. Source provenance: local repository diff, GitHub PR #195 checks, and independent agent review.