Configurable compression quality settings per org
epic-receipt-capture-and-attachment-foundation-task-015 — Extend ReceiptImageCompressor to accept an OrgCompressionConfig that allows overriding max dimension, JPEG quality, and maximum allowed file size in bytes. Provide a default config that targets under 500KB output. Expose the config as an injectable Riverpod parameter so per-org storage cost policies can be applied without code changes.
Acceptance Criteria
Technical Requirements
Execution Context
Tier 2 - 518 tasks
Can start after Tier 1 completes
Implementation Notes
Define OrgCompressionConfig as a const-constructible immutable class using the @immutable annotation. Use copyWith() for override scenarios. The iterative size reduction loop should be clearly commented with the termination condition. Clamp all incoming config values at the point of use: jpegQuality.clamp(1, 100), maxDimensionPx.clamp(100, 4096).
Expose the config provider as a family if multiple orgs can be active simultaneously: compressionConfigProvider.family
Testing Requirements
Extend task-016 tests to cover: custom maxDimensionPx (e.g., 400px) produces output within that dimension; jpegQuality override produces measurably different file sizes; maxFileSizeBytes constraint triggers iterative quality reduction and final output is within the limit; invalid config values (quality=0, dimension=50) throw ArgumentError. Test the Riverpod provider override mechanism with ProviderContainer.
Supabase Storage RLS policies using org/user/claim path scoping may not enforce correctly if claim ownership is not present in the JWT or if path segments are constructed differently at upload vs. read time, leading to data leakage or access denial for legitimate users.
Mitigation & Contingency
Mitigation: Define and test RLS policies in isolation before wiring to app code. Write integration tests that assert cross-org and cross-user access is denied. Use service-role key only in edge functions, never in client code.
Contingency: If client-side RLS proves insufficient, route all storage reads through a Supabase Edge Function that validates ownership before generating signed URLs, adding a controlled server-side enforcement layer.
Aggressive image compression may reduce receipt legibility below the threshold required for financial auditing, causing claim rejections or compliance failures despite technically successful uploads.
Mitigation & Contingency
Mitigation: Define minimum legibility requirements with HLF finance team before implementation. Set compression targets conservatively (e.g., max 1MB, min 80% JPEG quality) and validate with sample receipt images. Provide compression statistics in verbose/debug mode.
Contingency: If post-compression quality is disputed by auditors, increase the quality floor at the cost of larger file sizes, and add a manual override allowing users to skip compression for PDFs and high-quality scans.
The Flutter image_picker package behaves differently on iOS 17+ (PHPicker) vs older Android (Intent-based), particularly for file types, permission flows, and PDF selection, which may cause platform-specific failures not caught in development.
Mitigation & Contingency
Mitigation: Test image picker integration on physical devices for both platforms early in the sprint. Pin the image_picker package version and review changelogs before updates. Write widget tests using mock file results for each platform branch.
Contingency: If PHPicker or Android Intent differences cause blocking issues, implement separate platform-specific picker delegates behind the unified interface, allowing platform-specific fixes without breaking the shared API.