Skip to main content

Release Notes — v0.7.11

AgentPlane 0.7.11 completes lifecycle convergence around the Task Kernel. One application coordinator now owns ordinary, managed, Recipe V1, direct, and branch-PR progress while preserving the existing authority, context, verification, review, recovery, hosted-integration, and effect-in-doubt boundaries.

Summary​

  • Make the Task Kernel the sole live domain reducer and mutation gateway, with one shared advance-one-step coordinator for every supported execution route.
  • Unify scheduling, semantic WorkOrder dispatch, result admission, context preparation, native verification, independent review, recovery, and terminal completion around the same canonical state and evidence boundaries.
  • Remove superseded lifecycle engines, duplicate outer supervisors, reverse synchronization, obsolete exports, and no-information terminal writes after replacement behavior is proven.
  • Qualify the converged implementation through installed-package, migration-race, safety, architecture, compatibility, replay, and post-convergence test-topology gates.

Added​

  • Add an explicit lifecycle-owner map that identifies the canonical writer, scheduler, admission boundary, completion owner, and effect owner for every production entrypoint.
  • Add guarded preview and apply flows for lifecycle-owner migration into the Task Kernel, including source-digest, authority, revision, quiescence, and rollback-proof fences.
  • Add executable post-convergence behavior-to-test and test-to-CI-route ledgers for retained authority, concurrency, recovery, migration, and effect-in-doubt invariants.
  • Add deterministic 0.7.10 versus 0.7.11 replay evidence with equal mandatory role obligations and all assigned attempts retained. No paid-provider efficiency claim is made.

Improved​

  • Route Plan and WorkItem mutations through one backend transaction and Kernel command/event contract; compatibility status and README fields are projections rather than competing writers.
  • Reuse one dependency, output, optional-item, and resource-claim readiness calculation instead of maintaining parallel schedulers.
  • Use one WorkOrder and semantic result-admission boundary across managed and external transports, including exact lease, fingerprint, identity, authority, freshness, and structure checks.
  • Preserve CURATOR and bounded context preparation in the common path without allowing an executor to treat requested knowledge as already present.
  • Run native verification before independent review where required, reuse only matching immutable evidence, and keep EVALUATOR independence and rework semantics intact.
  • Route direct finalization, branch worktree preparation, hosted checks, integration, close-tail transitions, and Recipe V1 execution through shared coordinator operations.
  • Reconcile completed, pending, failed, and uncertain effects before new scheduling so restart and recovery cannot duplicate external work.
  • Make managed task run a transport loop around canonical one-step advancement instead of a second lifecycle engine.
  • Document the sole lifecycle contract and the formal-versus-semantic decision boundary without introducing optional mandatory stages in this release.
  • Consolidate equivalent test fixture setup and assign retained cases to the smallest correct suite while preserving their behavior-level oracle.

Fixed​

  • Persist branch-PR terminal Task Kernel completion before the terminal task-artifact commit, so a clean committed task README records DONE and COMPLETED rather than lagging canonical state.
  • Resolve registered branch worktrees by parsed task identity and fail closed on ambiguity, while preserving fresh-worktree bootstrap and deterministic validation-rework behavior.
  • Project canonical plan approval into compatibility fields used by branch routing instead of leaving an approved Kernel plan invisible to the route.
  • Prevent terminal replay from rewriting checkpoints, generated views, timestamps, or commits when authoritative state is already complete and no effect remains unresolved.
  • Reject conflicting outer and Kernel state, stale or cross-task semantic results, forged approval, missing required outputs, and unsafe migration races instead of choosing a permissive path.
  • Keep the public compatibility candidate synchronized with the exact current source provenance while leaving the immutable published 0.6.24 baseline unchanged.

Upgrade Notes​

  • The CLI, @agentplaneorg/core, @agentplaneorg/recipes, and @agentplane/testkit move together to 0.7.11 with exact internal dependency versions.
  • Existing ordinary, managed, direct, branch-PR, and Recipe V1 commands remain the supported public entrypoints; engine-selection and superseded lifecycle APIs are no longer active execution paths.
  • Historical records remain readable through the retained cold compatibility and migration boundaries. Do not hand-edit task state or recreate removed supervisors.
  • Preview managed-file changes with agentplane upgrade --dry-run, then apply the reviewed upgrade with the repository's normal agentplane upgrade flow.

Verification​

  • The candidate is required to pass release parity, registry availability, release notes, package reference generation, packed-install smoke, release-critical tests, architecture, compatibility, clone, unused-export, schema, documentation, replay, and full local CI gates.
  • Hosted publication remains bound to the exact protected-main SHA and its successful release-ready artifact before npm packages, tag, GitHub Release, standalone distributions, and package-manager evidence are created.
  • The measured replay disposition is evidence-only: lifecycle convergence is qualified, but a paid token, cost, or latency improvement is not established by this release.

Included Change Records​

The release plan covers the following exact non-merge commits since v0.7.10. Task-artifact commits are retained here for release traceability; the sections above describe their user-visible result.

  • 51325f6 — JKVHYA applied the canonical release-scope validation result.
  • d519c19 — JKVHYA applied the strict release-scope exclusion implementation.
  • 4734b3d — 5A54M1 recorded the hosted pull request.
  • 8068e6b — 5A54M1 persisted canonical completion.
  • a5d38a8 — 5A54M1 applied the canonical repair result.
  • 8278fa3 — 5A54M1 recorded approval of the release repair plan.
  • 6f44ea7 — YFF78T persisted the claimed repair work item.
  • 722d2b0 — YFF78T recorded approval of the repair plan.
  • a918def — WKCWNP recorded approval of the repair plan.
  • 480658c — X92CWM recorded the hosted pull request link.
  • fe82aa1 — X92CWM refreshed task artifacts after the implementation commit.
  • 3d26e0b — X92CWM refreshed the reviewed task artifacts.
  • 651ef86 — X92CWM recorded canonical completion state.
  • c7b86b1 — X92CWM persisted canonical completion.
  • 3a6c32e — X92CWM applied the first canonical repair result.
  • 3e872a4 — X92CWM applied the completed canonical repair result.
  • 727063e — CC13V3 applied the LC-24 canonical result.
  • 93ba64a — CC13V3 applied the LC-23 canonical result.
  • d0ab4d0 — CC13V3 applied the LC-22 canonical result.
  • 617f73e — CC13V3 applied the LC-21 canonical result.
  • c8baf36 — CC13V3 applied the LC-20 canonical result.
  • 1f7ef7f — CC13V3 applied the LC-19 canonical result.
  • fb421a3 — CC13V3 applied the LC-18 canonical result.
  • 3e8783c — CC13V3 applied the LC-17 canonical result.
  • f8c0f54 — CC13V3 applied the LC-16 canonical result.
  • 662f629 — CC13V3 applied the LC-15 canonical result.
  • 66e8c05 — CC13V3 applied the LC-14 canonical result.
  • d47e4b2 — CC13V3 applied the LC-13 canonical result.
  • ffe2f74 — CC13V3 applied the LC-12 canonical result.
  • c3251ea — CC13V3 applied the LC-11 canonical result.
  • af37b5d — CC13V3 applied the LC-10 canonical result.
  • 0f510fd — CC13V3 applied the LC-09 canonical result.
  • 6a8c276 — CC13V3 applied the LC-08 canonical result.
  • 709052e — CC13V3 applied the LC-07 canonical result.
  • 8f366f7 — CC13V3 applied the LC-06 canonical result.
  • aa07590 — CC13V3 applied the LC-05 canonical result.
  • 64d3af9 — CC13V3 applied the LC-04 canonical result.
  • 47844d7 — CC13V3 recorded the consolidated implementation evidence.
  • a31b9dd — CC13V3 recorded the lifecycle convergence verification state.
  • e366d1c — CC13V3 persisted the admitted roadmap work item.
  • 2a16e8e — CC13V3 initialized the canonical LC-04 through LC-24 execution result.
  • 4998185 — 5R1Q9A fixed Kernel completion ordering before branch workflow completion.
  • 20e2ed0 — 5R1Q9A persisted canonical completion.
  • 1316290 — 5R1Q9A refreshed canonical completion artifacts.
  • eba44c8 — 5R1Q9A applied the LC-03 canonical result.
  • 56a0acf — 0TQ72H recorded current-head quality review evidence.
  • 559289a — 0TQ72H persisted canonical completion.
  • f0be471 — 0TQ72H routed canonical pre-merge evidence.
  • 6d73514 — 0TQ72H refreshed canonical completion artifacts.
  • e156e6d — 0TQ72H applied the LC-02 canonical result.
  • 11cfc37 — ZW7H9X refreshed task artifacts after its implementation commit.
  • 5790c50 — ZW7H9X recorded pre-merge closure.
  • 5dc2079 — ZW7H9X persisted canonical completion.
  • 396b38e — ZW7H9X recorded current-head quality review evidence.
  • 9836760 — ZW7H9X refreshed reviewed task artifacts.
  • 753e211 — ZW7H9X refreshed canonical completion state.
  • 97e32f5 — ZW7H9X refreshed task artifacts after validation.
  • d94efb0 — Lifecycle owner-map lint was repaired without changing its ownership contract.
  • 31b5e3c — ZW7H9X persisted final canonical completion.
  • c85b4e6 — ZW7H9X applied its canonical implementation result.
  • 55e4b51 — ZW7H9X applied its admitted canonical result.
  • 18bfeae — HY96FB refreshed task artifacts after its implementation commit.
  • 35850e7 — HY96FB recorded pre-merge closure.
  • 9dbdd5b — HY96FB persisted canonical completion.
  • ff697ec — HY96FB refreshed canonical completion state.
  • b3fe531 — HY96FB refreshed reviewed task artifacts.
  • 021a6e6 — HY96FB recorded the final pre-merge closure.
  • a1b9f6e — HY96FB persisted reviewed canonical completion.
  • 06e2806 — HY96FB persisted final canonical completion.
  • 82968c9 — HY96FB applied its canonical implementation result.
  • 9b87b20 — W5XKXW recorded pre-merge closure.
  • 6e75fde — W5XKXW persisted canonical completion.
  • 88225df — W5XKXW refreshed canonical completion state.
  • 5a6fd10 — W5XKXW applied its canonical implementation result.
  • 0eb5f61 — W5XKXW applied its admitted canonical result.