Enoch v0.3.0
Enoch v0.3.0
Enoch v0.3.0 completes the provider-neutral repository and review architecture
behind governed code evolution. The release makes Enoch's portable workflows
depend on typed revision, workspace, review, and landing semantics while
keeping Git and GitHub available through compatibility adapters.
Highlights
- Added versioned semantic repository and review contracts that do not require
a staging index, named branches, pull-request numbers, or branch-shaped
review identities. - Migrated ordinary tasks, existing-reference publication, failed-task review
reconciliation,/pr,/update, and evolution promotion and adoption to
the semantic provider APIs. - Added verified review landing evidence and authoritative-revision ancestry
checks, preserving a traceable path from evolution evidence through human
promotion and verified runtime adoption. - Advanced the public Workflow API to version 3 with explicit typed lifecycle
mutations, and the Profile API to version 5 with semantic repository and
review contexts. - Added capability authorization, stale-daemon effect fencing, durable
notification delivery, versioned private-state ownership, and reusable
conformance tooling for downstream profiles and providers. - Expanded semantic evolution evidence scanning and curation while preserving
legacy task, queue, and evolution journal replay. - Advanced
our-ark-provider-kitto0.7.0and aligned all reference-provider
dependency pins on the same immutable contract revision.
Validation
- The 725-test Enoch body suite passes.
- The 65 provider and library tests pass independently.
- The portable wheel-install E2E installs independently packaged profile,
chat, repository, and review providers and completes a governed task. - The Genesis cross-artifact gate creates and validates a fresh descendant
from the release body. - GitHub Actions covers Python 3.11, 3.12, 3.13, and 3.14.
Compatibility
- Python 3.11 or newer.
genesis.tomlschema version 1.- Workflow API version 3.
- Profile API version 5.
- Provider-kit
0.7.0. - Genesis v0.1.1 or a later compatible build.
- Legacy Git/forge providers and earlier persisted task/evolution schemas
remain readable through explicit compatibility adapters.
Credentials, memories, logs, chat identifiers, task state, and instance
configuration remain outside both the public source archive and the inheritable
software body.