agent permissions: one set, tool groups included, set at agent creation

mara on #5170: "dont split caps and perms. its all perms. / dont include
the now empty tool groups / nothing set -> default / also add perms to
agent creation screen".

- hive-sh4re: one `Permission` enum (messaging, meta, inbox, execution,
  web_tools, manage_root_agent) replaces `ToolGroup` and `Capability`;
  `lifecycle`/`forge` are gone. `Permission::default_for` is the default
  for an agent the swarm sets nothing for.
- The record is `{ "permissions": [...] }`. Missing key, unset field or
  no successful read yet = default; `[]` = none; a failed read after a
  good one keeps the last value.
- hive-agent reads its own key every 10s and builds each turn's --tools,
  --allowedTools and MCP config (rewritten before every turn) from it;
  the subagent daemon reads it on each start/continue. Agents get a
  read-only grant on their own key.
- hive-c0re restarts an agent only when its manage_root_agent changes.
  The import now merges meta/capabilities.json and meta/tool-groups.json
  into one list per agent and deletes both; the "import pending, don't
  read" decision is `ImportOutcome::read_allowed`, table-tested.
- swarm-controller: `GET /api/permissions` (names + default) and an
  optional `permissions` on `POST /api/agents`, stored before the job is
  queued. swarm-ui's create-agent form gets a permissions field.
- Deleted: HIVE_TOOL_GROUPS and its forward to the subagent daemon,
  tool_groups.rs, ruth's tool-group seed, the permissions rebuild job
  (PermPayload/WritePermFile/perm_change), the dashboard permissions tab
  and its stale-entries panel.

Part of #5170.

docs/web-ui/dashboard.md

@@ -20,7 +20,7 @@ from the dashboard tab strip.
 - **← home back-link**: top-left of the chrome, links to the H0M3 hub
   at `/`. Every surface links back to the hub rather than to each other.
 - **Tab strip**: `◆ 4G3NTS ◆`, `◆ R3BU1LD QU3U3 ◆`, `◆ M3T4 1NPUTS ◆`,
-  `◆ BUILD L0GS ◆`, `◆ P3RM1SS10NS ◆`. In-page tabs only —
+  `◆ BUILD L0GS ◆`. In-page tabs only —
   the SYST3M panels live on the
   standalone **C0R3** page (`/core.html`), and FL0W / ST4TS
   live on their own pages too, all reachable from the
@@ -77,19 +77,15 @@ H0M3 hub (served at
 `/core.html`), with minimal chrome: a `← home` back-link and a single pane,
 **K3PT ST4T3**. The page is its own esbuild bundle (`core.js`) that
 cold-loads `/api/state` and subscribes to `/api/dashboard/stream` for
-`tombstones_changed` and `tool_groups_changed`
-(the latter re-renders the stale-perms sub-section when permission
-data changes). (Rebuild queue and meta inputs are dashboard tabs — see
-below.)
+`tombstones_changed`. (Rebuild queue and meta inputs are dashboard
+tabs — see below.)
 
 Per-container CPU, memory and disk load isn't shown in the hive UI. The
 same figures go out as OTEL metrics and appear in Grafana (see
 [observability](../scheduler/observability.md)). An agent's CPU and memory
 caps live per agent in the swarm UI.
 
-**K3PT ST4T3** — two sub-sections on one pane:
-
-*Tombstones*: agents with kept state and **no container** (size + age +
+**K3PT ST4T3** — agents with kept state and **no container** (size + age +
 claude-creds badge). One action: `PURG3` (wipes state + applied
 dirs; `POST /api/purge-tombstone/{name}`).
 
@@ -104,13 +100,6 @@ container is all hive-c0re can actually prove. Fixing it properly
 needs a recorded destroy — **deferred** to the swarm-controller /
 snapshot-storage rework where the problem changes shape.
 
-*Stale permission entries*: agents with explicit tool-group JSON
-entries but no live container — typically renamed or deleted agents
-whose entries persisted in `tool-groups.json`. Loaded when the page opens;
-autorefreshes on `tool_groups_changed` SSE
-events. Each ghost agent gets a `✕ clear perms` button
-(`DELETE /api/permissions/{name}`).
-
 ## Build tabs (`#rebuild`, `#meta`, `#buildlogs`)
 
 The build lifecycle — rebuild queue, live build log, meta inputs, and
@@ -227,74 +216,6 @@ badge with a ticking elapsed-time chip; expanding streams output via
 (suspends on manual scroll-up). Deep-link: `?id=N#buildlogs` opens the
 entry with that id pre-expanded.
 
-## P3RM1SS10NS tab
-
-Per-agent tool-group configuration, rendered as a column-driven
-checkbox matrix: rows are agents, columns are the group names fetched
-from hive-c0re. The column list is authoritative — adding a new
-tool-group to hive-c0re requires no UI change; the new column appears
-automatically. Capabilities aren't set here: they're the swarm's,
-set with `swarmctl agent permissions` (see
-`docs/process/conventions.md#capabilities`).
-
-The snapshot carries `agents` (the full manageable roster — live
-containers ∪ agents with an explicit entry) and `effective` (per-agent
-explicit-or-role-default values) alongside the explicit `assignments`
-map. Rows come from `agents` so **agents on defaults always appear**
-(not just those with an explicit entry), and checkboxes reflect the
-`effective` values so a default agent shows the groups it actually runs
-with rather than blank — which also means saving it won't silently
-strip those defaults. The `(default)` badge keys off absence from
-`assignments` (no explicit entry).
-
-Fetches fire on tab activation (not page-load) to avoid unnecessary
-work when the operator never visits this tab. Live mutations from the
-rebuild-queue worker are also pushed via the `tool_groups_changed`
-SSE event (same payload shape as the GET endpoint), so an open P3RM1SS10NS tab reflects worker-applied changes
-without requiring navigation. Tab-activation re-fetches remain as a
-safety net for reconnect windows.
-
-<!-- vale write-good.Passive = NO -->
-**T00L GR0UPS** — per-agent tool-group permissions. Tool groups are
-named buckets of MCP tools; each agent starts with a role default
-(sub-agents: `messaging`, `meta`, `inbox`, `execution` —
-`ToolGroup::AGENT_DEFAULT`; hive-c0re seeds the root agent to
-`ToolGroup::MANAGER_DEFAULT` — `messaging`, `meta`, `inbox`,
-`lifecycle`, `execution`,
-that is, every group except `forge` and `web_tools`). Checking /
-unchecking stages which groups are active for the agent; the
-page-level **save all** button (below) commits it. Columns come from
-`GET /api/tool-groups`. hive-c0re queues a rebuild so `HIVE_TOOL_GROUPS`
-takes effect.
-<!-- vale write-good.Passive = YES -->
-
-The current tool groups are: `messaging`, `meta`, `inbox`, `lifecycle`,
-`forge`, `execution`, `web_tools`. All listed in `ToolGroup::ALL` in `hive-sh4re`. The
-`web_tools` group is special: it carries no MCP tools; instead it adds
-Claude's built-in `WebFetch` and `WebSearch` to `--tools` /
-`--allowedTools` for that agent session.
-
-The table's shape: a `.tg-table-wrap` outer scroll container, `thead`
-with a label column (`.tg-agent-col`) + one column per group
-(`.tg-group-col`). Each tbody row is one agent: a name cell
-and its checkbox cells, where each checkbox carries `data-baseline` (its
-render-time state) and the row carries `data-agent` for dirty-tracking.
-
-**Saving — one button for the whole page.** No per-row save
-buttons exist. A single page-level `.perm-save-bar` with a **save all (N
-agents)** button sits at the bottom of the pane, enabled only when some
-checkbox diverges from its baseline. Selecting it diffs every checkbox
-and POSTs one batch to `POST /api/permissions` as
-`{ changes: [ { agent, tool_groups } ] }` — the batch includes only the
-agents whose groups changed (an included array fully replaces the
-agent's groups).
-The batch is atomic: it validates every change first and on any error
-rejects the whole POST (`{error}`, nothing applied); a clean 200 (`ok`)
-flips the bar to a queued→rebuilding state and re-fetches the table.
-Live `tool_groups_changed` events re-render the
-matrix unless it has unsaved edits, so an in-progress edit set
-isn't clobbered.
-
 ## ST4TS page (`/stats.html`)
 
 Hive-wide turn statistics, aggregated across every agent's
@@ -733,31 +654,6 @@ below — some endpoints aren't in it yet.
 - `POST /api/cancel-reminder/{id}` — hard-delete a pending reminder.
 - `POST /api/retry-reminder/{id}` — re-arm a reminder whose delivery
   failed (clears the failure state so the scheduler retries).
-- `GET /api/tool-groups` — returns `{ groups: Vec<String>,
-  assignments: BTreeMap<String, Vec<String>>,
-  descriptions: BTreeMap<String, String> }`. `groups` is the
-  ordered list of all known tool-group names (drives the column
-  headers in the P3RM1SS10NS tab); `assignments` is the per-agent
-  override map (absent agents use the role default); `descriptions`
-  maps each group name to a short human-readable string surfaced as
-  a column-header tooltip on hover.
-- `POST /api/tool-groups/{agent}` — body `{ groups: ["name", …] }`.
-  Writes the tool-group set for `{agent}` to
-  `/var/lib/hyperhive/meta/tool-groups.json` and queues a rebuild so
-  `HIVE_TOOL_GROUPS` takes effect. Agent name validated;
-  `guard_agent_name` applied.
-- `POST /api/permissions` — batch perm apply for the save-all
-  permissions button. Body
-  `{ changes: [{ agent, tool_groups?: ["name", …] }] }`.
-  An omitted `tool_groups` leaves the agent untouched, an empty array
-  clears it, a populated array fully replaces it (same replace
-  semantics as the per-agent endpoint above). Each affected agent gets
-  one `PermChange` queue entry. **Atomic**: the endpoint validates every
-  change first (agent names via `guard_agent_name`, group names) and on
-  any validation error writes or enqueues nothing (non-2xx `{ error }`);
-  it skips rows with the field omitted rather than erroring on them.
-  Returns `200 "ok"` on
-  success.
 - `POST /api/meta-update` — `nix flake update` the selected
   `meta/flake.lock` inputs, then rebuild the affected agents.
 - `GET /api/dashboard/stream` — unified live event channel:
@@ -805,11 +701,6 @@ payload):
   operator cancel / retry (`/api/system/reminders/*`), `cancel_loose_end`
   with Reminder kind, and the scheduler tick after each delivery
   batch (`reminder_scheduler`).
-- `tool_groups_changed` (seq, groups: `Vec<str>`, descriptions: map,
-  assignments: `BTreeMap<String, Vec<String>>`) — full snapshot of
-  tool-group assignments. Emitted from the rebuild-queue worker after
-  a `PermChange` / ToolGroups entry commits the JSON file. Same
-  shape as `GET /api/tool-groups`; P3RM1SS10NS tab subscribes.
 - `tombstones_changed` (seq, tombstones: `Vec<TombstoneView>`) —
   full snapshot of destroyed-but-state-kept agents. Emitted on
   destroy, purge, and revive. C0R3 K3PT ST4T3 tab subscribes.