[taskboard] add direct host dispatch targets

README.md

@@ -6,7 +6,8 @@ It tracks and visualizes:
 
 - OpenClaw swarm agents on `ubuntu`
 - ZeroClaw host runtimes on `grizzley` and `ice`
-- shared task assignment and dispatch across both families
+- direct SSH host targets for `pve`, `truenas`, and `panda`
+- shared task assignment and dispatch across all families
 - wiki pages and architecture documentation rendered in the UI
 - dispatch audit history, failure queues, heartbeat overlays, and task templates
 
@@ -21,7 +22,7 @@ It tracks and visualizes:
 ## Key Pages
 
 - `/tasks` - unified Kanban board
-- `/agents` - configured OpenClaw and ZeroClaw runtimes
+- `/agents` - configured OpenClaw, ZeroClaw, and direct host targets
 - `/openclaw` - focused OpenClaw swarm view
 - `/zeroclaw` - focused ZeroClaw host-runtime view
 - `/dispatch` - dispatch audit log and failure queue
@@ -35,10 +36,11 @@ It tracks and visualizes:
 - dispatch lifecycle states and SQLite audit history
 - OpenClaw swarm dispatch into `~/.clawdbot/active-tasks.json`
 - ZeroClaw webhook dispatch for `grizzley` and `ice`
+- direct SSH dispatch for `pve`, `truenas`, and `panda`
 - task callback API for remote completion/result sync
 - OpenClaw registry sync API for swarm task state reconciliation
 - failure queue and dispatch history views
-- family-specific runtime views for OpenClaw and ZeroClaw
+- family-specific runtime views for OpenClaw and ZeroClaw plus unified direct-host visibility
 - architecture documentation rendered directly from tracked config
 
 ## Fleet Model
@@ -64,7 +66,21 @@ It tracks and visualizes:
 - Channels:
   - paired HTTP gateway access
   - Homelab-Ice forum topics
-  - remote gateway routing from `ice`
+- remote gateway routing from `ice`
+
+### Direct SSH Targets
+
+- Execution host: `ubuntu` taskboard container
+- Transport: `ssh` using the mounted host key
+- Configured targets:
+  - `pve` via `root@192.168.50.11`
+  - `truenas` via `christopher@192.168.50.12`
+  - `panda` via `bear@192.168.50.196`
+- Dispatch model:
+  - select a direct target agent
+  - dispatch a built-in safe action
+  - capture stdout/stderr
+  - write completion through the same callback pipeline as remote runtimes
 
 ## Important Environment Variables
 
@@ -80,6 +96,8 @@ It tracks and visualizes:
 - `ZEROCLAW_GRIZZLEY_TOKEN`
 - `ZEROCLAW_ICE_URL`
 - `ZEROCLAW_ICE_TOKEN`
+- `DIRECT_SSH_KEY_PATH`
+- `DIRECT_SSH_TIMEOUT_MS`
 
 ## Development
 
@@ -106,11 +124,15 @@ npm start
 - ZeroClaw architecture:
   - rendered from the tracked fleet model in this repo
   - optional runtime path overrides can be provided via `ZEROCLAW_PRIMARY_DIR` and `ZEROCLAW_CONTROL_DIR`
+- Direct SSH:
+  - taskboard container mounts `/home/bear/.ssh` as read-only
+  - direct targets use `/root/.ssh/id_ed25519` by default
 
 ## Notes
 
-- The UI intentionally treats OpenClaw and ZeroClaw as separate families with different runtime and channel models.
+- The UI intentionally treats OpenClaw, ZeroClaw, and direct host targets as separate families with different runtime and channel models.
 - `ice` ZeroClaw remains tied to host-local secret/encryption state; the dashboard reads that runtime but does not attempt to rewrite it.
+- Direct targets are intentionally limited to safe built-in actions from `config/fleet.json`, not arbitrary shell commands from the browser.
 
 ## Status Docs