Szpont Engine 0.3.0 — Durable bounded work sessions

Long-running goals can now continue through verified checkpoints in the same Discord session. The engine keeps one global worker, yields between completed steps, and separates successful execution from delayed transcript and memory maintenance.

What changed

• Explicit !work 30m <goal> / !work 2h <goal> sessions: fixed owner goal, active execution budget, strict JSON outcomes and a 32-step cap.
• Atomic checkpointing, exact session resumption and fair queueing without later messages overtaking their thread's active workflow.
• Verified budget pauses remain available for a fresh explicit budget. Uncertain turns require reconciliation and manual recovery; a host crash conservatively consumes the lost step's remaining allowance.
• Durable transcript export and scoped local Git retries survive restart and work without model authentication. Progress-message failures no longer invalidate accepted or completed jobs.
• Versioned transactional SQLite upgrade, verified online state snapshots and no-overwrite restoration into a new private path.
• Current-thread progress and maintenance diagnostics, with no disclosure of other threads' prompts, identifiers or sessions.
• Container acceptance now exercises the bundled output schema, new/resumed CLI arguments, checkpoint persistence and consistent state snapshots offline.

Upgrade

This release introduces SQLite schema version 1. Take a pre-upgrade schema-0 snapshot before moving from 0.2. Restore compatible pre-upgrade state to a new private path before rolling back to older code. Never point 0.2 at a migrated 0.3 database.

See work sessions, state backups and road to 1.0.

Validation

201 offline tests passed locally: 124 engine/protocol/state tests, 42 tooling tests and 35 Python browser tests. The real non-root Docker runtime passed with networking disabled, including Codex sandbox confinement and synthetic persistent volumes. Secret scans of the public tree and Git history found no findings.

Live Discord/model acceptance, a multi-day soak and actual power-loss simulation remain explicit 1.0 gates. The image contains no credentials, private conversations, browser session or authenticated account. Publishing it does not upgrade an existing private VPS.

Source checks passed on the exact release commit: five CI jobs. The release workflow verified and tested both native architectures before promoting the same OCI artifacts, including SBOM and provenance.

Container

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

Immutable multi-platform reference:

ghcr.io/dalkedev/szpont-engine@sha256:84b2918ec2cb0f34de58feb1d6bd4043908e9f620e12cecf47214c47bb0879b3

Linux amd64 and arm64 are included. Anonymous manifest access and pulling the release were verified; the downloaded arm64 runtime passed the offline sandbox, persistence, workflow and snapshot smoke tests by this exact digest.