Schema (applied via migration imagen_series_init):
- imagen.series parent table (prompt + params + count CHECK 1..10 + selected_image_id)
- imagen.jobs += series_id (FK) + series_idx
- imagen.images += series_id (FK)
- Owner-scoped RLS on series (SELECT/INSERT/UPDATE) + grants
- Partial indexes WHERE series_id IS NOT NULL on both child tables
Worker pipeline:
- worker.Job += SeriesID, populated from imagen.jobs.series_id via the
claim query.
- cloud.SyncRequest += SeriesID; insertRow writes series_id when non-empty,
omits the key when empty so solo runs leave the column NULL.
- maybeCloudSync threads seriesID from job.SeriesID through to the cloud
sink. generate.go (CLI) always passes "" — solo path unchanged.
Tests:
- worker: SeriesID propagates from Job to fakePipeline.lastJob unchanged,
solo job keeps it empty.
- cloud: SyncRequest.SeriesID lands as row.series_id in the POST body;
empty SeriesID omits the key entirely.
Refs ImaGen#9.
Async write path for the flexsiebels owner-mode UI: flexsiebels INSERTs into
imagen.jobs, the worker on mRiver claims pending rows via LISTEN/NOTIFY +
5s safety poll, runs the same generate pipeline imagen generate uses, and
writes the result through internal/cloud into imagen.images.
- Schema migration imagen_jobs_init: table + status CHECK + two indexes +
owner-scoped RLS + grants + AFTER INSERT trigger publishing on the
imagen_jobs channel via pg_notify.
- internal/worker: DB-agnostic loop over a Queue interface. Drains the
whole pending backlog on each wake. Job-scoped contexts are derived
from Background so SIGTERM lets the in-flight generation finish (no
half-state). ResetStaleRunning at startup unsticks rows left over from
a previous crash. Eight unit tests cover the done / failed / missing-id /
drain / NOTIFY-wake / shutdown / transient-error paths against a fake
queue (no real Postgres in CI).
- cmd/imagen/worker.go: pgx-backed Queue (one dedicated conn for LISTEN +
UPDATE), plus the workerPipeline that reuses buildBackend +
attachUsageSink + prompt.Apply + buildWriter + maybeCloudSync. The
per-job owner_user_id overrides the env-level fallback so each row in
imagen.images is attributed correctly.
- maybeCloudSync now returns (*cloud.SyncResult, error) so the worker can
link imagen.jobs.image_id to the inserted imagen.images row. The CLI
generate path keeps printing its stderr summary unchanged.
- scripts/imagen-worker.service + .env.example for the systemd --user unit
on mRiver. EnvironmentFile lives in ~/.dotfiles and is never committed.
- docs/setup-worker-mriver.md walks through installation + the spec's
SQL-INSERT smoke; docs/architecture.md grows an "async write path"
section.
- worker_integration_test.go (env-guarded by IMAGEN_WORKER_INTEGRATION=1)
drives one real job through the full pipeline against msupabase using
the mock backend, then verifies imagen.images + Storage object landed
and the row flipped to done with image_id linked. Verified end-to-end:
pickup latency ~7ms, total 74ms, failure path captures error text.
