One tab called Processes, showing what Top showed

The two read the same data and answered the same question. Procs.tsx is gone; a rail
order saved before this keeps the merged page in Top's slot. The mouse back-button item
is dropped from the plan.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

PLAN.md

@@ -252,6 +252,13 @@ something long in one, switch away and back, refresh — it's all still there.
   use", and "Remove unused" takes every image no container uses. Nothing is ever forced:
   Docker refuses what is still in use, and that refusal is the answer. Still absent:
   removing networks.
+- **Top merged into Processes** — **2026-09-23.** The two tabs answered the same question
+  from the same data (Top already read `/api/procs`, the endpoint the Processes table was
+  built on), so at Mitchell's instruction there is now one tab, **Processes**, showing what
+  Top showed: the btop-style whole-machine screen. `Procs.tsx` is deleted; the `top` view
+  id and its route are gone. A rail order saved before this keeps its shape — `railorder.ts`
+  maps the retired `top` to `procs` and drops the duplicate, so the merged page sits where
+  Top sat rather than falling to the bottom.
 - **Skins** — 13 since 2026-09-19 (`themes.ts`: a palette is one `mk(…)` line): Dark,
   Light, Cyberpunk, Retro, **HUD** (hairlines of cyan on near-black, corner ticks, thin
   type), Nord, Gruvbox, Catppuccin + Latte, Dracula, Tokyo Night, Solarized Dark + Light;
@@ -487,16 +494,6 @@ something long in one, switch away and back, refresh — it's all still there.
   - *Not app work, but the trigger:* nothing here blocks starting the migration except the
     inventory. Do that first.
 
-- **Keep Processes or Top, not both** — asked for 2026-09-23, not started. They answer the
-  same question and read the same data: `Top.tsx` already fetches `/api/procs` for its
-  process panel, the same endpoint `Procs.tsx` is built on, and both draw the same CPU,
-  memory, load and network numbers. Top is the btop-style whole-machine screen; Processes
-  is the sortable table with filter, kill and signal. Decide which survives and fold the
-  other's worth into it — most likely Top stays and gains Processes' sorting, filtering and
-  signal actions, since one screen beats two. Whichever goes, its rail entry, its `View` id
-  and its hash route go with it, and any saved rail order naming it must degrade quietly
-  (`railorder.ts` already ignores ids it does not recognise).
-
 - **Rename the Space tab** — asked for 2026-09-23, not started. "Space" is vague; the tab
   is WizTree for a disk or pool. Candidates: **Usage**, **Disk Usage**, **Storage**. Note
   `Disks` already exists and `Storage` would muddle with it, so Usage is probably the one.
@@ -535,10 +532,10 @@ something long in one, switch away and back, refresh — it's all still there.
   at all, which is every host here today. Worth scoping as its own plan before starting.
 
 - **Deprecate the Dashboard tab** — asked for 2026-09-23, not started. Mitchell: it is nice
-  but the app repeats itself, and this goes together with choosing between Processes and
-  Top. Dashboard is the customisable module list (CPU, memory, load, uptime, temps, fans,
-  network, disks, filesystems, UPS) plus custom sensor widgets; Top shows most of the same
-  numbers on one screen. **Widgets stays**, reframed: its page should say plainly that the
+  but the app repeats itself — the same reasoning that merged Top into Processes the same
+  day. Dashboard is the customisable module list (CPU, memory, load, uptime, temps, fans,
+  network, disks, filesystems, UPS) plus custom sensor widgets; the Processes tab shows
+  most of the same numbers on one screen already. **Widgets stays**, reframed: its page should say plainly that the
   widgets there are for **external dashboards** (Glance, Home Assistant, a wall display)
   via `/embed/widget` and read-only sensor tokens, not a second copy of this console's own
   screens. Care needed on the way out: the dashboard layout is per-user in `state.json`
@@ -547,13 +544,7 @@ something long in one, switch away and back, refresh — it's all still there.
   source. `dashboard` is also the default view after login and after switching machines.
 
 - **Files explorer: cleanup and ease of use** — asked for 2026-09-23, not started.
-  Specifically named: **the mouse's back button must go up a directory**. Why it does not
-  today — `hashsel.ts` navigates with `history.replaceState`, which deliberately leaves no
-  history entry, so there is nothing for the browser (or the mouse's back button, which is
-  just `history.back()`) to return to. Fixing it properly means Files pushing a history
-  entry per folder and answering `popstate`, which `useHashSel` already listens for; doing
-  it in `hashsel.ts` would change every page that uses it, so decide whether history is
-  per-page opt-in. Beyond that the ask is general polish, and the **Deprecate copyparty**
+  General polish and ease of use. The **Deprecate copyparty**
   item names the heavier pieces (multi-select and bulk actions, folder download, resumable
   uploads, a gallery, search) — worth doing the two together, since they are the same tab.