v0.3.1 — auto V2->V1 fallback and proper CLI exit codes
A minor CLI-only follow-up to v0.3.0. The default CLI invocation now
handles mixed Gemini-3.5+ and pre-3.5 inputs in one shot, and scripts
can rely on the exit code to chain retries.
Default behaviour: try the current Gemini-3.5+ profile first; on skip,
automatically retry with the legacy (pre-3.5) profile before reporting
the final outcome.
- --legacy V1 only (no current-profile attempt)
- --no-legacy V2 only (no legacy fallback) -- matches the 0.3.0
default behaviour - --legacy --no-legacy conflict, exits 2
Exit codes:
- 0 = file processed (or batch directory completed without errors)
- 1 = single-file invocation skipped (no watermark detected on any
profile tried by the chosen flag combination) - 2 = real failure (bad args, missing input, IO/write error)
Batch directory runs keep lenient semantics (exit 0 unless an actual
failure occurs).
Drag-and-drop (simple) mode now accepts --legacy and --no-legacy
directly. Previously these were rejected by the dispatcher.
GUI, reverse alpha blending math, and watermark profiles are unchanged.
Addresses GitHub issue #34.