chore: remove stale SQLite references after retirement

SQLite was retired as the server metadata store in d490dbe4.
Remove dead sqlx workspace dep, better-sqlite3 trustedDependencies,
and update docs that still referenced SQLite persistence.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Bryan Helmkamp 2026-04-05 21:29:24 -04:00
parent 17c65b4c6c
commit 5575988d26
5 changed files with 184 additions and 442 deletions

View file

@ -46,7 +46,6 @@ walkdir = "2"
regex = "1"
semver = "1"
aho-corasick = "1"
sqlx = { version = "0.8", features = ["runtime-tokio", "sqlite", "chrono"] }
dirs = "6"
mac_address = "1"
md5 = "0.7"

618
bun.lock

File diff suppressed because it is too large Load diff

View file

@ -20,7 +20,7 @@ Both interfaces use the same workflow engine, the same Graphviz files, and the s
| **Execution** | Synchronous, one run per process | Asynchronous, queued with configurable concurrency |
| **Human-in-the-loop** | Terminal prompts | Web UI or HTTP endpoints |
| **Events** | Printed to stderr | Streamed via SSE |
| **Persistence** | Checkpoint files only | SQLite database + checkpoint files |
| **Persistence** | Checkpoint files only | Persistent run store + checkpoint files |
| **Web UI** | Not available | Full React interface |
| **Authentication** | None | JWT and/or mTLS |

View file

@ -28,7 +28,7 @@ CLI mode is ideal for:
fabro server start
```
`fabro server start` starts an HTTP server (default `127.0.0.1:3000`) backed by SQLite for run persistence. Runs are submitted via the REST API and executed asynchronously.
`fabro server start` starts an HTTP server (default `127.0.0.1:3000`) with persistent run storage. Runs are submitted via the REST API and executed asynchronously.
### Configuration

View file

@ -1,5 +1,4 @@
{
"private": true,
"workspaces": ["apps/*", "lib/packages/*"],
"trustedDependencies": ["better-sqlite3"]
"workspaces": ["apps/*", "lib/packages/*"]
}