Enoch v0.2.1
Enoch v0.2.1 strengthens the first public agent body with durable task execution, clearer operational controls, richer extension contracts, and a smaller application core. The release focuses on making long-running work safe to recover, inspect, and publish without changing Enoch's provider-neutral architecture.
Highlights
- Added durable chat inbox receipts and idempotent task acceptance so updates can be retried without silently duplicating completed work.
- Hardened task execution with worker leases, structured outcomes, timeouts, cancellation, automatic retry classification, pause/resume behavior, and resumable commit, push, and pull-request stages.
- Added isolated task-worktree inspection and management through
/worktree,/worktree show,/worktree cleanup, and explicit forced discard. - Unified Telegram command metadata and routing in one registry, removed aliases, made
/help <command>discoverable, and eliminated stale help text. - Expanded provider and profile contracts with typed runtime results, progress/cancellation controls, provider-neutral configuration, lifecycle hooks, prompt contributors, and task policy.
- Added semantic evolve-candidate curation, richer provenance and event reporting, and clearer governance for scheduled and inherited evolution.
- Expanded Doctor to distinguish code health, environment readiness, and operational readiness while reporting actionable provider diagnostics.
- Extracted isolated task execution and the commit/push/PR handoff from
EnochApplicationinto an explicitly wired task workflow.
Validation
- The 621-test Enoch body suite passes.
- GitHub, launchd, provider-kit, skill-catalog, systemd, Telegram, and Telegram vision provider suites pass independently.
- GitHub Actions covers Python 3.11, 3.12, 3.13, and 3.14.
- Import smoke covers the CLI, application core, daemon, Doctor, lineage, memory, skills, providers, and update tooling.
Compatibility
- Python 3.11 or newer.
genesis.tomlschema version 1.- Genesis v0.1.0 or a later compatible build.
Credentials, memories, logs, chat identifiers, task state, and instance configuration remain outside both the public source archive and the inheritable software body.