Skip to content

v0.5.22 — Intent-Aware Assistant Workflow

Choose a tag to compare

View all tags
@silbaram silbaram released this 05 Sep 15:17
· 11 commits to main since this release
v0.5.22
0fece19
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

Plan2Agent v0.5.22 sharpens the harness into a more reliable development assistant: the user’s current request stays ahead of lifecycle routing, planning does not silently continue an older scope after a competing request, and recovery keeps verification proportional to the change.

Shared closeout guidance is now smaller and loaded only when review, retrospective, issue publication, or explicit iteration close is actually requested. Repeated provider and subagent instructions were consolidated while preserving approval, evidence, and workspace boundaries.

What changed

  • Prioritize explicit review, explanation, status, and Git-operation requests over unrelated lifecycle advancement.
  • Stop a clean read-only review after reporting the result; leave iteration close to an explicit user request.
  • Detect a competing request during Gate A/B planning and pause before advancing or replacing existing planning records.
  • Preserve the original full or relevant verification scope when retrying environment-only final evidence.
  • Close unavailable final evidence immutably and start a replacement run even when the command becomes available before retry.
  • Separate implementation-run confinement from later foreground Git operations that the user explicitly authorizes.
  • Consolidate optional closeout behavior into one shared conditional reference and reduce duplicated skill and subagent guidance.
  • Continue to accept supported existing artifact roots only when their approvals and source hashes remain current.

Compatibility and safety

  • Node.js 22 or newer remains required.
  • Existing projects, approvals, task graphs, and run evidence remain compatible.
  • Competing requests are saved without rewriting the current plan or consuming prior approvals.
  • Environment retries keep the implementation task complete and preserve unavailable evidence.
  • Remote push, pull request, merge, deployment, and other external writes are never implied by an implementation run; they require a separate explicit request.

Validation

  • Unit and integration test suite: 485/485 passed.
  • npm package and upgrade tests: 17/17 passed.
  • Full fixture validation, skill validation, generated-provider parity, and git diff checks passed.
  • GitHub CI passed on Node.js 22, 24, and 26.
  • Full fixture gate, macOS package/upgrade smoke, and Windows package/upgrade smoke passed.
  • Regression coverage includes competing requests at every planning stage, started and already-closed environment retries, and preservation of both full and relevant verification scopes.

Upgrade

The npm package is not published yet; the public npm latest version is currently 0.5.21. After plan2agent@0.5.22 is available:

npm install --global plan2agent@0.5.22
p2a --version
p2a upgrade --target . --dry-run
p2a upgrade --target . --apply --prune
p2a doctor --target . --dev --strict

Related

  • Development-assistant workflow and recovery improvements: PR #203
Assets 2
Loading