Plompy 0.3.0
Durable bounded work sessions
This is a historical release. Its notes describe this version, not the current setup. See the latest stable release before starting a new installation.
This version predates Plompy Local. It covers the Discord engine; the separate local MCP gateway and starter kit arrive in 0.13.0.
GitHub notes and assets for this version may use the earlier Szpont name. Historical filenames and source links are preserved.
What changed#
Durable work sessions#
- Add explicit
!work 30m <goal>and!work 2h <goal>sessions with a fixed owner goal, active execution budget and 32-step cap. - Validate typed JSON checkpoints against a shipped schema; resume the exact session only after a successful, completed process turn.
- Requeue verified steps fairly between threads while retaining per-thread ordering and one global worker.
- Distinguish verified budget pauses from uncertain failures, and retain charged time across manual recovery chains.
- Conservatively consume a crashed running workflow's uncheckpointed allowance instead of silently refunding unknown execution time on restart.
Reliable state and memory#
- Retry transcript export and scoped local Git commits durably, independently of model execution and authentication.
- Keep committed intake and task results authoritative when progress messages or export operations fail.
- Add transactional versioned SQLite migration preserving existing jobs, results, controls and sessions.
- Add verified online state backup and no-overwrite restore tooling, with upgrade and rollback documentation.
- Show current-thread workflow checkpoints and maintenance health without exposing other threads.
Release scope#
- Include the work output schema and state snapshot CLI in the non-root container image.
- Keep uncertain external actions subject to manual reconciliation; no automatic replay, parallel browser workers or private-deployment upgrade is introduced.
- Publish explicit 1.0 readiness criteria instead of treating a version number as evidence of production stability.
Downloads and source#
- release-manifest-0.3.0.json (1,245 bytes)
Original GitHub release · Source at v0.3.0 · Changelog at this tag
Before you upgrade#
Back up private state and credentials, review the version's migration boundaries, and retain a compatible rollback snapshot. A release does not update an existing deployment automatically.