Genesis v0.2.0

Genesis v0.2.0

Genesis v0.2.0 adds composition to lineage. Builders can now create a new
independently versioned agent body with genesis create, or add a bounded
domain capability to an existing Enoch runtime with genesis extend.

Highlights

• Added genesis extend, a transactional scaffolder for independently
  packaged AgentExtensions.
• Generated packages include an our_ark.extensions entry point, an
  agent-extension.toml provenance manifest, a governed example command, and
  an Enoch conformance test.
• Pinned generated packages by default to the immutable Enoch v0.4.0 release
  commit and AgentExtension API version 1.
• Added --enoch-ref for later compatible Enoch bodies while requiring a full
  40- or 64-character commit SHA.
• Added --dry-run so builders can inspect the complete extension file plan
  before writing a target.
• Kept extension generation atomic and non-destructive: non-empty targets are
  rejected and failed generation preserves a pre-existing empty directory.
• Expanded the normally installed-package gate to exercise extend.
• Expanded the Genesis × Enoch gate to verify that AgentExtension API v1
  survives descent and that a freshly generated package passes Enoch's public
  conformance suite.
• Updated the stable public pairing to Enoch v0.4.0.

Compatibility

• Python 3.11 or newer.
• genesis.toml body schema remains at version 1.
• Generated agent-extension.toml manifests use schema version 1.
• Generated extensions target AgentExtension API version 1.
• Enoch v0.4.0 is the default public reference body and extension host.
• genesis create, inspect-source, and recycle retain their v0.1.1
  behavior.
• Extension packages are trusted Python code rather than sandbox boundaries.

Genesis continues to keep credentials, memories, logs, chat identifiers, and
instance state outside inherited bodies and generated extension packages.