Repository navigation
Draft: restore Order Forge scoped image artifact retention (direct generations first) - #61
Conversation
…y-20261025' into integration/orderforge-image-retention-20261025
…y-20261025' into integration/orderforge-image-retention-20261025
|
2026-10-25 fork image preservation progress (parallel branches reconciled, no production deployment): base #61 scope-gated storage + direct generations passed hosted run 40165254621; #64 implements direct/custom/combo image edits; #67 adds the previously missing Firefly edit callback (hosted run 40171833029 GREEN); #68 adds normalized successful Responses API nonstream + SSE capture at the new upstream split modules (hosted run 40172264744 GREEN); #69 handles winning-target image generation combo payload only, with real SQLite/fake-provider success/fallback/failed-storage tests (hosted run 40172657329, in progress at comment time). Overlapping draft #65 intentionally CLOSED as duplicate of #64 + #67 to avoid divergent same-feature implementations. Independent #66 ports module-only Codex image quota telemetry (hosted run 40171767874 GREEN) and still requires final-account, actual-route wiring. ALL PRs are Draft; don't merge them out-of-order or deploy. Full CI/security/typecheck, copied old-SQLite upgrade/rollback, end-to-end provider mocks and canary remain blocked. |
Upstream-first fork migration, customer-specific preservation — NOT a release
Stacked on draft #60 documentation stabilization and its ancestors through #51. Do not merge/deploy to
production. No customer image data, active credentials, or production database content included.Included
orderForgeImageArtifactSink.ts, with bounded PNG/JPEG/WEBP base64 validation (25 MiB maximum), atomic 0600 files, private metadata with hashes (not prompts or raw request text), 72h / 2 GiB cleanup, and a tee-drain helper./v1/images/generationshook to current official upstream afterenforceClientApiRouteAuth, policy enforcement and allowed-connection scope. A caller must possess the authenticated API key's specialimage_artifact_retentionscope and present a validated artifact ID; otherwise no persistence. No change to the image response, quota accounting or connection selection; storage exceptions do not break a successful provider response.docs/maintenance/ORDER_FORGE_IMAGE_RETENTION_PORT_20261025.md.Must finish before release
image_generation_callcapture and safe client-disconnect tee handling in current upstreamchatCore.ts./v1/images/editsdirect, combo and custom-provider paths; dedicated generation combo path (this PR covers direct generations only).This patch is fork-specific; it is not proposed as a generic upstream PR. Initial core commit
2d009a9662, composed branch361ca60923.