plompy-engine.Docs
Historical releaseAll 16 releases ↗

Plompy 0.8.0

Evidence for every reviewed step

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#

  • Bind a code repository to a supervised goal with --repo <absolute path>. Capture its working-tree contents before and after each worker step, so commits and staging cannot hide code or test changes from the fresh supervisor.
  • Persist the baseline before execution and seal the resulting patch with the worker candidate. Pause, restart and reviewer recovery retain the original evidence; later live edits cannot silently replace it.
  • Give supervisors a bounded patch, changed-file inventory, explicit coverage limits, a private evidence file and the two most recent candidate/review receipts. Test-only changes remain valid when they match the goal; weakened assertions do not prove a behavior fix.
  • Bound capture time, file sizes, inventory and patch output. Keep ignored secrets out, avoid following symlinks or hard links, disable Git diff/filter helpers, and report incomplete or unavailable captures explicitly.
  • Migrate public SQLite state to schema 6 while retaining existing sessions, jobs, images and goal history. Existing goals have no implicit repository binding. Take a coordinated backup before upgrading; older binaries cannot open schema 6.

Downloads and source#

This GitHub release has no separately uploaded download assets. Its source and published distribution details are linked from the release page.

Original GitHub release · Source at v0.8.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.

Full release history · Upgrade and rollback guide

Find your next step

Search titles and guide content.