Plompy 0.9.0
Install, inspect, verify
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#
- Add guided private setup for Codex and the experimental host adapters, hidden token input, explicit token-file/stdin automation and shell-quoted mode-0600 configuration. Preserve existing resources and failed/concurrent workspaces of uncertain ownership.
- Add opt-in read-only
doctor --check-discordchecks for bot identity, guild owner, private forum and effective reply permissions, with bounded requests and credential-safe diagnostics. Default doctor remains offline. - Ship a self-contained first-goal Git fixture and independent 25-case checker. Distinguish its expected negative-quantity failure from setup failures, and reject weakened tests or altered evidence.
- Exercise setup, the actual pinned Codex version, offline doctor, independent fixture RED/GREEN and tamper controls inside both container architectures. Keep live Discord/model acceptance and soak evidence separate from offline checks.
- Refresh guild ownership and roles from Discord before authorization instead of trusting an incomplete or stale Gateway cache. Preserve owner/privacy rejection when the fresh read fails.
- Retain SQLite schema 6 and current recovery/provider semantics. The known Node 24 SQLite finding remains open; this release does not claim runtime remediation.
Downloads and source#
- image-verification.json (1,078 bytes)
- published-index.json (1,611 bytes)
Original GitHub release · Source at v0.9.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.