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]>

entrypoint.sh

@@ -1,10 +1,16 @@
 #!/bin/bash
 set -e
 
-echo "=== Bunext SQLite Template ==="
+echo "=== Cobble ==="
 
 cd /app
 
+# bun-sqlite's record of the live schema sits beside the code; keep it on
+# the data volume with the database it describes
+mkdir -p "${DATA_DIR:-/data}/.bun-sqlite"
+rm -rf /app/.bun-sqlite
+ln -sfn "${DATA_DIR:-/data}/.bun-sqlite" /app/.bun-sqlite
+
 bunx bun-sqlite schema -y
 bunx bunext build
 bunx bunext sitemap