v0.14.0

Venat v0.14.0

Status: Released

v0.14.0 makes agent definitions executable and durable, then carries their
governance, coordination, and recovery contracts through the runner and storage
boundaries.

Executable agent definitions

• api.AgentDefinition now declares explicit executable tools, skills, hooks,
  schemas, loop limits, context sources, triggers, and governance.
• worker.DefinitionDeployment validates and materializes immutable definition
  revisions. Unsupported configured fields fail deployment instead of becoming
  display-only metadata.
• Definition snapshots use canonical JSON and SHA-256 digests. Run and task
  state retains the revision needed for deterministic resume.
• worker.SingleRunner provides the durable single-agent lifecycle, including
  admission, checkpointed recovery, cancellation, and definition continuity.

Governance and coordination

• Usage accounting distinguishes model, tool, action, and legacy execution
  records, with pricing state and idempotency metadata.
• Budget composition, policy obligations, approval routing, and action replay
  enforce fail-closed behavior at their durable boundaries.
• Transactional admission reservations enforce aggregate concurrency, window,
  credit, and failure-breaker limits.
• Shared and exclusive resource claims are acquired with task leases to prevent
  conflicting workers from dispatching the same protected work.
• Admission settlement derives priced usage and durable outcome inside one unit
  of work; caller-provided settlement totals are not authoritative.

Storage contract

api.StoreProvider remains application-implemented under Position D. Optional
capabilities now cover immutable definition snapshots, admission reservations,
and resource claims. contract.RunStoreProviderContractTests validates these
extensions when an adapter declares support.

Public API and reliability

• Runner.StartRunWithResult returns typed api.StartRunResult, including the
  Created bit needed by idempotent callers.
• Durable action commands, hook and policy composition, replay, provider
  fallback, streaming, lifecycle recovery, and trace paths are hardened around
  persisted identity and fail-closed behavior.
• Context builders and coding-agent integration carry definition-derived
  instructions, schemas, tools, skills, and governance into execution.

Upgrade

After the release tag is published:

go get github.com/Viking602/venat@v0.14.0
go install github.com/Viking602/venat/cmd/venat@v0.14.0
go mod tidy

Applications using custom StoreProvider implementations should run the full
contract suite and implement every optional capability they declare. Existing
v0.8.0 product specifications and release notes remain historical records; the
v0.14.0 deltas are documented in
docs/product-spec/v0.14.0/.

What's Changed

• feat(v0.14.0): ship durable agent control plane by @Viking602 in #46

Full Changelog: v0.13.0...v0.14.0