You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This patch release refreshes the root and website dependency sets while keeping the AgentPlane package family on the same patch cadence.
It fixes direct-workflow closeout and runner-startup routes so agents receive a clearer next action when finishing direct tasks.
It clarifies non-runner route guidance, no-close-commit cleanup behavior, and staged-safe cleanup handling for branch_pr and direct workflow recovery.
It preserves hosted publish evidence from the previous release cycle so operators can distinguish real release state from local task projection drift.
Added
Added task-local hosted publish evidence for the previous release task, giving future release operators a durable record of the GitHub and npm publication state. (638d0e2)
Improved
Updated the root dependency group across the repository with six package updates, reducing dependency drift before the next published package cut. (8bcce5e)
Recorded the Dependabot lockfile repair task closure so the dependency update is traceable through AgentPlane task artifacts. (a975fd9)
Refreshed the website dependency lockfile after the Dependabot update, keeping the website install state aligned with the dependency manifest. (84dd873)
Updated the website dependency group with two package updates under website, keeping the documentation site dependency set current. (24bdea3)
Refreshed review evidence for the direct workflow closeout regression task so the task artifacts match the implementation under review. (a5566c2)
Recorded evaluator review evidence for the direct workflow closeout route fix, making the quality gate explicit before release. (cf25332)
Clarified non-recipe runner route guidance so agents can tell when a route packet belongs to the current coding agent instead of an external runner. (7286f10)
Recorded route-guidance quality review evidence for the non-recipe runner route task, keeping reviewer state fresh for release readiness. (10e521b)
Clarified non-runner route executor guidance so agents do not introduce runner retry or wait language when next-action delegates local execution. (3cd4cbc)
Clarified the no-close-commit finish cleanup route, making the cleanup path easier to follow when finish is valid but a close commit is intentionally skipped. (5795206)
Recorded evaluator review evidence for the no-close-commit cleanup task so the finish-route change has a current review trail. (604a044)
Refreshed staged-safe verification evidence for cleanup routing, keeping the task proof aligned with the latest implementation state. (0340c5d)
Refreshed verification evidence for the cleanup route after follow-up changes, reducing stale-quality-review ambiguity before release. (9f034b4)
Formatted the route-oracle output for the cleanup task, improving readability without changing the underlying route contract. (12a15fb)
Recorded verification evidence for the cleanup route task so release checks can see the completed validation state. (84d349b)
Fixed
Fixed direct workflow closeout regressions reported through GitHub issues, preserving the expected task finish path for direct-mode users. (7777312)
Fixed direct runner startup routing so direct tasks keep the startup route instead of drifting into an unrelated branch_pr-style path. (8177caa)
Fixed direct closeout routes so task completion follows the intended route packet instead of stale or ambiguous local state. (2a7257c)
Fixed the cleanup route so it remains staged-safe and does not require agents to disturb unrelated index state during closeout. (871adfe)
Fixed the route-oracle cleanup guidance so the no-close cleanup route is visible to agents at the right phase. (b74ce38)
Upgrade Notes
No breaking changes.
The package set remains in lockstep at 0.6.20.
Operators should continue to prepare release candidates through the branch_pr route and publish from the exact merged release commit SHA.
Release readiness still depends on explicit task-state evidence, current release notes, generated release assets, and external GitHub/npm verification.
Verification
agentplane release plan --patch generated .agentplane/.release/plan/2026-06-08T18-21-13-956Z for v0.6.20.
Candidate validation is expected to run through agentplane release candidate --plan /Users/densmirnov/Github/agentplane/.agentplane/.release/plan/2026-06-08T18-21-13-956Z --push --yes.
Final publication must be verified against the external GitHub tag, GitHub Release, and npm package version for 0.6.20.