todo: drop landed entries — get_open_threads, whoami, oversize-msg, tombstones+meta_inputs

TODO.md

@@ -9,8 +9,6 @@
 - **Broadcast messaging**: allow sending messages with recipient "*" to all agents; deliver with hint "this was a broadcast and may not need any action from you"
 - **Multi-agent restart coordination**: when rebuilding all agents, manager should start first so it can coordinate post-restart confusion (notify agents, suppress unnecessary retries, etc)
 - **Shared docs/skills repo (RO)**: a single repo on the hive forge that every agent has read-only access to — common references, prompts, runbooks, "skills" the operator wants every agent to inherit without baking into the system prompt or `/shared`. Implementation likely: seed an `org-shared/docs` repo on first hive-forge boot, grant every per-agent user a read membership in the org. Agents `git clone` it (or use the API) to read; only the manager + operator can push.
-- ~~**Loose-ends tracker + `get_open_threads` tool**~~ ✓ landed — new `mcp__hyperhive__get_open_threads` MCP tool on both agent + manager surfaces. Wire types in `hive-sh4re`: `AgentRequest::GetOpenThreads` / `ManagerRequest::GetOpenThreads` → `OpenThreads { threads: Vec<OpenThread> }`. `OpenThread` is a tagged enum with `Approval { id, agent, commit_ref, description, age_seconds }` and `Question { id, asker, target, question, age_seconds }`. Shared aggregator at `hive-c0re/src/open_threads.rs`: `for_agent(coord, name)` (sub-agent surface; filters questions by asker == self OR target == self, approvals only for manager) and `hive_wide(coord)` (manager surface; everything pending in the swarm). No caching — fresh sqlite sweep per call. **Per-agent web UI rendering** is a follow-up below.
-    - **Follow-up: surface open-threads on the per-agent web UI** so the operator can see at a glance what each agent has hanging open — same data source as the MCP tool, just rendered into the existing per-agent dashboard page (next to inbox view / model chip / etc).
 
 ## Reminder Tool
 
@@ -20,7 +18,7 @@
 
 ## Dashboard
 
-- **Per-agent reminder rollups**: pending count chip + delivery-error surface landed. Still open: delivered-count chip (last 24h?), per-agent histogram of attempts-vs-successes — both readable from `turn_stats.open_reminders_count` history or via a new `Broker::count_delivered_reminders_since(agent, ts)` helper.
+- **Delivered-reminder rollups**: per-agent delivered-count chip (last 24h) + histogram of attempts-vs-successes on the container row. Needs `Broker::count_delivered_reminders_since(agent, ts)` (cheap COUNT against the `reminders` table, `WHERE agent = ?1 AND sent_at >= ?2`).
 
 ## Security
 
@@ -32,13 +30,6 @@
 Filed by damocles, who actually lives in this thing. Loosely ranked by
 how often the friction bites in normal use.
 
-- ~~**Auto-attach oversize message bodies**~~ — superseded by simply
-  raising the inline cap from 1 KiB → 4 KiB (covers ~95% of
-  conversational overflow). Anything genuinely larger still needs a
-  state file. Blob-in-broker-sqlite was prototyped on paper
-  (`/agents/damocles/state/oversize-msg-proposal.md`) but rejected as
-  future vacuum/sync pain not worth carrying for the long-tail 5% of
-  cases that legitimately belong in a file.
 - **Inbox batching hint in the wake prompt** — when the harness pops a
   message and there are N more waiting, the wake prompt should say so
   (e.g. `"(+3 more queued; consider draining before acting)"`) so claude
@@ -55,7 +46,6 @@ how often the friction bites in normal use.
   and `cancel_ask(id)` on the agent surface, plus `list_my_reminders()`
   / `cancel_reminder(id)`. Bounded by `asker == self` and `reminder.owner
   == self` so no cross-agent meddling.
-- ~~**`whoami` introspection tool**~~ ✓ landed — new `mcp__hyperhive__whoami` on both agent + manager surfaces. Returns `{ name, role, hyperhive_rev }` from coord state (socket identity for `name`, hard-coded per surface for `role`, `auto_update::current_flake_rev`). `operator_pronouns` deliberately omitted — already substituted into every agent's system prompt at boot, so returning it again was duplicate data. `model` + `started_at` deferred — those live in the harness process not the coord, would need extra plumbing for marginal value.
 - **Optional `in_reply_to: <msg_id>` on send** — pure wire addition; no
   behavioural change. The dashboard could render conversation threads
   (already wants this for the agent-to-agent question UI in the
@@ -67,7 +57,7 @@ how often the friction bites in normal use.
 ## Telemetry
 
 - **Per-turn stats: host-side vacuum sweep**: the sink writes to `/state/hyperhive-turn-stats.sqlite` on each agent's state dir; needs a periodic retention sweep mirroring `events_vacuum.rs` so the table doesn't grow forever. Default keep-window: 90 days (turn-stats are denser than events but smaller per-row, ~200B each).
-- **Surface per-turn stats on the agent web UI**: badges sourced from the new sink — `open_threads` count chip, `open_reminders` count chip, "N turns today" chip, rolling tool-call histogram tooltip on the model chip. Both `open_threads` and `open_reminders` are already columns on every row; the badge just reads the latest. The richer histograms read across rows.
+- **Surface per-turn stats on the agent web UI**: "N turns today" chip + rolling tool-call histogram tooltip on the model chip. (`open_threads` and `open_reminders` chips already landed via other paths — open-threads section on the page + reminder count chip on the container row.) Reads the per-agent `turn_stats.sqlite`.
 - **Stats UI on the main dashboard**: per-agent rollups (avg turn duration, tokens-since-boot, top 5 tools) on the container row. Same data source, host-side aggregation query.
 
 ## Bugs