HACK-546: integrate Hack App curation and hardening work

.cursor/rules/hack.mdc

@@ -37,6 +37,12 @@ hack down
 hack global status
 hack session
 hack tickets list
+hack node list
+hack node status --watch
+hack node ssh setup --node <id>
+hack node routes status
+hack node routes repair
+hack dispatch run --project <name|id> --node default --branch <branch> --runner generic -- "pwd"
 hack internal extra-hosts list
 hack internal extra-hosts set <hostname> <target>
 hack internal extra-hosts unset <hostname>

.hack/README.md

@@ -7,8 +7,8 @@ This repo is dogfooding the tickets extension.
   - `hack x tickets setup`
   - `hack x tickets create --title "..." --body-stdin`
   - `hack x tickets list`
-  - `hack x tickets show T-00001`
-  - `hack x tickets status T-00001 in_progress`
+  - `hack x tickets show T-AB12CD34EF`
+  - `hack x tickets status T-AB12CD34EF in_progress`
   - `hack x tickets sync`
 
 No services are required for this repo; `docker-compose.yml` is intentionally empty.

AGENTS.md

@@ -202,7 +202,7 @@ Most formatting and common issues are automatically fixed by Biome. Run `bun x u
 <!-- hack:agent-docs:start -->
 ## hack CLI (local dev + MCP)
 
-Use `hack` as the single interface for local runtime orchestration (compose, DNS/TLS, logs, sessions).
+Use `hack` as the single interface for local runtime orchestration (compose, DNS/TLS, logs, persistent project workspaces).
 
 Operating rules:
 - Prefer `hack` over raw `docker` / `docker compose` for project workflows.
@@ -270,12 +270,12 @@ Lifecycle + startup:
 - Use `lifecycle.up.before` for pre-start hooks and `lifecycle.processes` for long-running host tasks.
 - Inspect lifecycle status via `hack projects --details` and stream via `hack logs <service-or-process>`.
 
-Sessions (mux-managed):
-- Picker: `hack session`
-- Start/attach: `hack session start <project>`
-- Force isolated agent session: `hack session start <project> --new --name agent-1`
-- Execute in session: `hack session exec <session> "<command>"`
-- Stop session: `hack session stop <session>`
+Workspaces (mux-managed):
+- Picker: `hack session` for persistent project workspaces.
+- Reuse/create: `hack session start <project>`
+- Force isolated agent workspace: `hack session start <project> --new --name agent-1` (`<project>--agent-1`).
+- Execute in workspace: `hack session exec <workspace> "<command>"`
+- Stop workspace: `hack session stop <workspace>`
 
 Tickets (git-backed):
 - Create: `hack tickets create --title "..." --body-stdin`

CLAUDE.md

@@ -97,7 +97,7 @@ This project uses Obsidian for project context, specs, research, and progress tr
 <!-- hack:agent-docs:start -->
 ## hack CLI (local dev + MCP)
 
-Use `hack` as the single interface for local runtime orchestration (compose, DNS/TLS, logs, sessions).
+Use `hack` as the single interface for local runtime orchestration (compose, DNS/TLS, logs, persistent project workspaces).
 
 Operating rules:
 - Prefer `hack` over raw `docker` / `docker compose` for project workflows.
@@ -165,12 +165,12 @@ Lifecycle + startup:
 - Use `lifecycle.up.before` for pre-start hooks and `lifecycle.processes` for long-running host tasks.
 - Inspect lifecycle status via `hack projects --details` and stream via `hack logs <service-or-process>`.
 
-Sessions (mux-managed):
-- Picker: `hack session`
-- Start/attach: `hack session start <project>`
-- Force isolated agent session: `hack session start <project> --new --name agent-1`
-- Execute in session: `hack session exec <session> "<command>"`
-- Stop session: `hack session stop <session>`
+Workspaces (mux-managed):
+- Picker: `hack session` for persistent project workspaces.
+- Reuse/create: `hack session start <project>`
+- Force isolated agent workspace: `hack session start <project> --new --name agent-1` (`<project>--agent-1`).
+- Execute in workspace: `hack session exec <workspace> "<command>"`
+- Stop workspace: `hack session stop <workspace>`
 
 Tickets (git-backed):
 - Create: `hack tickets create --title "..." --body-stdin`