Szpont Engine 0.5.0 — Private Discord image input

Szpont can now inspect images attached to a private Discord conversation, including messages without a caption and explicit !work goals. Codex receives native image inputs on both new and resumed turns; the Claude Code and OpenCode adapters explicitly reject images rather than dropping them or switching providers.

• Up to four still PNG, JPEG or WebP files per message: 8 MiB each, 20 MiB total. Authorization precedes downloads, with matching Discord CDN paths, no redirects, and bounded bytes, dimensions and time.
• Image bytes and SHA-256 digests commit atomically with the job and survive queue restart, workflow continuation, manual recovery and state backup. Temporary runner files stay private and are cleaned after the turn.
• Public state advances to SQLite schema 4. Existing jobs, provider bindings and sessions are preserved. Back up before upgrading; rollback to 0.4.0 requires a compatible pre-upgrade snapshot and reconciliation of later actions. Backups now include private image bytes.

The published container remains Codex-only. Its selected model must support image input. Claude Code and OpenCode remain experimental host adapters; no live Discord message, model inference or account action is used as a release smoke test. This release does not update a private deployment automatically.

Verified container (Linux amd64 and arm64):

docker pull ghcr.io/dalkedev/szpont-engine@sha256:1fb1fb10ceb5e24e104ce3814fa4584b3280bce394ac96d28552399ee06163a9

The public manifest contains exactly the native runtimes and SBOM/provenance attestations tested by the release workflow. Anonymous registry access and an isolated smoke test of the published arm64 image passed.

Image input and limits · Backup and rollback · Full changelog