Replace the simulated image provider and wire the real storage pipeline #10

Open
opened 2026-03-10 14:40:55 +03:00 by sirily · 0 comments
Owner

Problem
packages/providers/src/nano-banana.ts is still a simulated adapter, and successful generations only create database asset rows without an actual object-storage upload/download path.

Why this matters
The current generation pipeline proves control flow, but not the real provider transport, asset persistence, or retrieval contract needed for the product.

Acceptance criteria

  • Implement a real provider adapter in packages/providers.
  • Add storage adapter support for upload/download to S3-compatible storage.
  • Persist provider outputs and expose retrievable asset references to the web app.
  • Keep provider-specific HTTP logic out of packages/domain.
Problem `packages/providers/src/nano-banana.ts` is still a simulated adapter, and successful generations only create database asset rows without an actual object-storage upload/download path. Why this matters The current generation pipeline proves control flow, but not the real provider transport, asset persistence, or retrieval contract needed for the product. Acceptance criteria - Implement a real provider adapter in `packages/providers`. - Add storage adapter support for upload/download to S3-compatible storage. - Persist provider outputs and expose retrievable asset references to the web app. - Keep provider-specific HTTP logic out of `packages/domain`.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sirily/nroxy#10