Run computers with resources and health checks, add settings for bots, workspaces, computers and users

- Computers get CPUs and memory (default 1 CPU, 2 GB), set at creation and
  editable; new resources stop, remove and recreate the container, its home
  dir kept. Every computer container has a docker health check and stays
  "creating" until it passes; only healthy computers are reached, by
  hostname, else by their IP on the network (dev outside docker).
- Docker is required: the app creates the cobble network on startup and
  exits without docker.
- Production container: deploy/run-app-container.sh mounts .env, the data
  dir and the docker socket; the database (DB_DIR), media, computers' homes
  and bun-sqlite's live schema now live on the data volume.
- Settings pages for bots, workspaces, computers and users, sharing list
  components; bots can be deleted; users are created with a password and
  confirmation, edited and deleted through RBAC-gated APIs.
- User types trimmed to super_admin, admin, member, read_only and revoked;
  admins manage members. UserAvatar shows profile photos from the user row.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

src/utils/computer-status-label.test.ts

@@ -0,0 +1,16 @@
+import { describe, expect, test } from "bun:test";
+import computerStatusLabel from "./computer-status-label";
+
+describe("computerStatusLabel", () => {
+    test("names the state", () => {
+        expect(computerStatusLabel({ computer: { id: 1, status: "running" } })).toBe("Running");
+        expect(computerStatusLabel({ computer: { id: 1, status: "creating" } })).toBe("Setting up…");
+        expect(computerStatusLabel({ computer: { id: 1 } })).toBe("Unknown");
+    });
+
+    test("says why setup failed", () => {
+        expect(computerStatusLabel({ computer: { id: 1, status: "failed", error: "no docker" } })).toBe(
+            "Setup failed: no docker",
+        );
+    });
+});