chore(task-board): mothball it; superseded by the High Seat and ledger

Operator ruling 2026-09-24. On ana-docker the stack is `docker compose
down`: the container is removed and port 7878 is closed. Kept for revival:
- the data dir /opt/docker/conf/task-board/data (tasks.db, last written
  2026-09-11)
- the task-board:local image
- stacks/task-board/ and the host's compose + .env

The Uptime Kuma monitor (id 3) was deleted before the stop so it could
not page, and its row is removed from monitors.yaml. Homepage drops the
card on its own, since it reads the container's labels.

Hooks: the container log showed no hook POSTs in 30 days. The only
traffic was open browser tabs holding /events, and the plugin was already
uninstalled on nh3-dev. Removed the paragraph that told sessions to call
task_* tools (CLAUDE.md, and the fork-fleet.sh template that seeds new
repos), the vestigial TASK_BOARD_SESSION env in .claude/settings.json, and
the listings in README and FLEETTOOLS.

stacks/task-board/compose.yaml

@@ -1,5 +1,12 @@
 # task-board — MCP + web dashboard for assistant task state.
 #
+# ⚠ MOTHBALLED 2026-09-24 (operator): superseded by the High Seat (SVOS) and
+# ledger. On ana-docker the container is `docker compose down`ed; the data dir
+# (/opt/docker/conf/task-board/data, tasks.db last written 2026-09-11), the
+# task-board:local image and this compose + .env are KEPT. To revive:
+# `cd /opt/docker/compose/task-board && docker compose up -d`, then re-add its
+# Uptime Kuma row. Its Claude Code hooks had sent no traffic for 30+ days.
+#
 # Image is built on the host from the task-board git repo by the deploy
 # playbook (`playbooks/deploy-task-board.yaml`), which clones into
 # /opt/docker/build/task-board and runs `docker build -t task-board:local .`