Record the packaging work and what it left open

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

ROADMAP.md

@@ -113,6 +113,18 @@ external interfaces. See `docs/architecture/structure.canvas` → *Backend – M
       the engine runs only the published files, and publishing promotes the
       draft. Saves carry the version they were based on, so a second client
       editing the same flow is refused rather than overwritten
+- [x] Installable with pip, and startable with no infrastructure: `fluksio` and
+      `fluksio-worker` are two distributions, `fluksio serve` makes its own data
+      directory, key, SQLite database and admin account, and `fluksio enroll
+      <code> --portal …` pairs a machine with no browser pointed at it. Proven
+      in a bare `python:3.12-slim`: installed, paired, dialled out, and the hub
+      proxied requests back through the tunnel. `git` and a Redis are both
+      optional — the flows are files and the state falls back to memory
+- [x] SQLite as the database, on the data volume beside the flows. One process
+      owns it, which the single uvicorn worker already said; Postgres stays in
+      the stack only for the optional Umami profile. `DATA_DIR` is the one
+      setting the rest derive from, the schema is prepared in-process at
+      startup, and the ten Postgres-only revisions are one portable baseline
 - [ ] Import/export of a flow as human-readable code plus a JSON structure
 - [x] Per-input/-output discretization interval setting: a port publishes, or
       wakes its node, at most every n seconds. State keeps the latest value, so