Szpont Engine 0.2.0

Szpont Engine 0.2.0 makes setup easier to diagnose and interrupted work safer to recover.

Install with Docker

docker pull ghcr.io/dalkedev/szpont-engine:0.2.0

For repeatable deployment, pin the verified multi-platform image:

ghcr.io/dalkedev/szpont-engine@sha256:719fed34c0421837719c528bad38b1a98a32869acc1b48028416ae5ce8853407

The image supports Linux amd64 and arm64. It runs as a non-root user with separate private workspace, queue, artifact, and Codex authentication volumes. The supplied Compose configuration keeps the application filesystem read-only and runs an actual Codex sandbox preflight before connecting to Discord.

Follow the Docker setup guide for private configuration, login, sandbox prerequisites, and persistence. Your own Codex authentication and model access are required. The optional Camoufox browser service is configured separately.

Work and recovery

• Task completion and conversation blocking now commit atomically. Session reset also rolls back as a unit if it cannot complete.
• Recovery rejects overlapping requests and replay of work already recovered successfully.
• !status explains blocked queues, worker activity, session presence, and uncertain response delivery without exposing another thread's data.
• !help lists controls. Invalid command arguments return usage before changing work or sessions.
• npm run doctor checks local deployment prerequisites with sanitized text or JSON output. Login status is checked only when explicitly requested.

Project experience

New logo and reusable brand assets, a documentation index, contributor and issue templates, active offline CI, and native container tests for both architectures. The attached brand kit includes the mark, banners, usage guide, and license.

Verification and upgrades

118 offline Node/Python tests pass, together with native amd64 and arm64 container checks. Release publishing promotes the exact tested OCI artifacts, retains their provenance and SBOM, and checks the resulting runtime and attestation manifests. The published image was pulled anonymously and its exact digest passed an additional offline arm64 smoke test. Offline checks do not establish your Discord permissions, model quota, or account actions.

This release does not migrate the state schema or update an existing deployment automatically. Stop the old instance and back up its private state before switching images. Keep one worker per state volume. Interrupted actions still require deliberate reconciliation; no automatic external replay was added.

Full details: changelog · release process and rollback.