v1.0.0

[1.0.0] - 2026-08-29

Added

• Published versioned Event and Message serialization APIs with golden compatibility
  fixtures, bounded JSON parsing, and stable error codes.
• Published the Runtime, Adapter, Plugin, and Context lifecycle contract, including
  transactional reload and generation invalidation semantics.
• Added installable extension discovery, root configuration schema generation, and
  reusable adapter/plugin conformance helpers.
• Added the 1.0 public API compatibility matrix, deprecation policy, and migration guide.

Changed

• Extension discovery now fails closed for duplicate, reserved, invalid, or mismatched
  entry points instead of selecting an ambiguous implementation.
• Runtime startup, shutdown, and reload now provide deterministic ordering, rollback,
  cleanup, admission, and drain behavior.
• Context operations are generation-bound and reject use after reload or shutdown.
• Extension configuration is validated through declared Pydantic or dataclass models and
  contributes to one canonical root schema.

Migration

• Third-party extensions should declare iamai>=1,<2 and run the public conformance
  helpers before publishing a 1.0-compatible release.
• Persisted Event and Message data must use the versioned payload APIs; legacy normalization
  helpers remain available but are not a stable wire format.
• See docs/guides/migration-0.3-to-1.0.rst for the complete compatibility boundary.