Skip to content

0.55.0

Choose a tag to compare

View all tags
@b10x-bot b10x-bot released this 10 Sep 12:25
· 236 commits to main since this release
0.55.0
28abe09

Added

  • Pinned public Gates security and privacy checks, signed local evidence and
    coordinated hooks. Bot delivery no longer requires an Atlas checkout.

  • Optional ess_conformance_coverage_v1 evidence admits exact original suite/5
    lineage and complete selected coverage. Its separate opt-in profile requires
    independent task, model, suite, selection, producer and freshness expectations;
    incomplete, empty or unknown coverage cannot satisfy completion requirements.
    Typed input, driver replay, inspection and planning preserve the original bytes.

  • Optional paired ess-conformance-report/2 and suite readers preserve exact counts,
    original source bytes and completion time. Evidence is re-admitted before recording
    or restoring it. The opt-in adp-ess-conformance/1 protocol and
    development.ess-conformance-v2 profile require independent task expectations;
    count-stage coverage remains unknown and cannot satisfy complete conformance.

  • Planning --from accepts report version 2 with its original suite through
    --suite; evidence inspection exposes exact count values. Invalid pairs refuse
    before storage changes.

Changed

  • Concrete model driving, native execution hooks and live evaluation move to
    metaharness aep drive. AEP exposes its neutral CLI library and retains command/operator
    driving, governance, run storage and offline evaluation. Model-backed invocations through
    AEP refuse before allocating a run and name the replacement command.
  • Pin Entity Runtime and the documentation build package to verified source revisions.
    Entity Runtime's stricter replay validation refuses imported AEP audit events without
    an emitting kernel definition; persisted AEP state and audit records remain available.
  • Direct evidence recording returns a checked result and takes an explicit reading
    instant so malformed or stale source evidence is refused before mutation.
  • Source releases retain correctness and artifact checks while documentation publication
    proceeds independently.

Fixed

  • Execution hosts can name the runnable resume command in refusal messages, so callers are
    directed to the host that can actually resume the run.

This source release was published without running gates, tests or binary packaging.

Assets 7
Loading