v2.1.0

Changed

• Use the same short command set for plans and goals: status, resume,
  pause, cancel, hide, and help. Advanced recovery flags and
  compatibility commands remain available through /exec help advanced.
• Cancelled runs disappear from the strip and footer immediately, including
  after reload, branch navigation, and new sessions. No separate clear or
  cleanup command is needed. Existing cancelled records are hidden too.
• /goal stop now means final cancellation, matching /exec stop.
  stop remains a compatibility name for cancel in both commands.
• hide toggles progress display without changing execution. Goals also
  accept the compatibility display controls ui on|off, show, and clear.

Fixed

• Share the lease, mutation, and recovery gates for goal and plan controls.
  Implicit goal controls select eligible work in the current project instead
  of a newer finished or unrelated goal.
• Prevent resume and optional review waivers from restarting a finally
  cancelled run whose worker retirement failed.

Upgrade

• After upgrading, restart Pi sessions sharing the registry. Saved work,
  branches, worktrees, and worker ownership evidence are preserved.
• Change scripts that used /goal stop for resumable pauses to
  /goal pause. Otherwise, stop now ends the goal finally.
• Use ui off for repeated idempotent hiding in scripts.
  Repeating hide now restores the display.
• Cancellation is not successful completion or proof of worker exit. Shutdown
  tracking continues safely in the background; unresolved ownership stays
  reserved.

Full changes

v2.0.0

Changed

• Run plans, goals, reviews, fixes and statistics directly through released
  pi-subagents 0.76.1 public workflows. Bridge, pi-tasks and cc-thingz are no
  longer required. Task summaries use the execution registry, not a separate
  task store.
• Keep launch identity and cancellation in one registry. Lost replies and
  restarts recover the original operation when evidence permits; unknown
  ownership never authorizes a replacement writer.
• Use a built-in readonly reviewer with commit-bound structured reports.
  Missing, contradictory or oversized results cannot pass review. Launch
  admission rejects missing selected skills and denied agents before dispatch.
• Hold tasks on confirmed provider/model failures instead of repeatedly
  launching the same bad model. Explicit /exec resume <id> --model <provider/model>
  or --model current selects one new attempt without changing frozen
  configuration. Independent tasks retain their own recovery evidence.
• Preserve permanent force-stop, quarantine, checkout reservations and explicit
  pause/resume. Legacy operations can use an explicitly supplied read-only
  schema-7 journal snapshot; import never launches work.

Upgrade

• Before upgrading, quiesce old controllers and back up the registry and a
  consistent Bridge SQLite snapshot, including committed WAL data. Do not infer
  that unresolved children exited merely because their parent stopped.
• Install pi-subagents 0.76.1 and plan-exec 2.0.0, then restart every Pi session
  sharing the registry. Do not hot-reload mixed old/new controllers. Keep
  explicitly configured or frozen agents available; they are not silently
  replaced. Custom agents must be discoverable by native preflight; migrate
  runtime-only custom definitions to agent files before upgrading.
• Existing bound native IDs need no journal. For an unbound historical launch,
  use /exec resume <id> --legacy-journal /absolute/offline.sqlite.
  Missing identity or retirement proof remains reserved.
• Do not downgrade while any native record or artifact remains, including
  terminal history. Older cleanup can delete that evidence. Use the
  read-only rollback preflight; never erase
  records just to make it pass.

Limits

• Native RPC does not enforce requested maxTurns; unbounded workflow requests
  retain native child defaults. Unknown retirement after parent loss remains
  fenced. Separate Linux acceptance was waived; local validation used macOS.

Full changes

v1.8.0

Changed

• /exec stop now requests final cancellation without a pause-or-cancel dialog.
  Use /exec pause for resumable work, and /exec ui on|off for display only.
  Legacy cancel/hide/show/clear commands remain supported.
• /exec stop <full-run-id> --force permanently abandons controller management,
  including legacy unknown launches. No automatic retries, restoration or
  resume follow abandonment. The run disappears from progress displays and
  the default status list, including other open observing sessions.
• Force-stop attempts cancellation only for the exact tracked ownership.
  Unknown workers are not reported as stopped; their operation evidence and
  checkout reservations remain. A live foreign controller refuses the action.
• Eligible registry artifacts are removed only after controller quiescence and
  flushed backups. Worktrees, branches, progress files and provider journals
  are preserved. Repeat the command to retry partial cleanup.
• Late callbacks cannot revive abandoned runs or report successful completion.
  Pending archive mutations recheck stop authorization.

Upgrade

• Restart every Pi session sharing the registry after upgrading. Change scripts that relied on the old stop
  chooser to /exec pause for resumable stops.
• Force-stop is irreversible abandonment, not recovery or proof of worker
  death. Inspect retained records by full ID or status --all; do not
  downgrade or use older cleanup while abandoned records remain: older versions
  reject the new status but their corrupt-record cleanup can erase its reservation.
• No dependency upgrade or live journal migration is required.

Full changes

v1.7.1

Fixed

• Show paused operations as paused, not working. Keep active work visible when
  another task waits on an external prerequisite.
• Preserve user-pause intent in recovery guidance, including stale and
  renamed-host leases. A paused state no longer implies a supervisor question.
• Keep execution state visible alongside the Snapshot qualifier, including
  pending cancellation and pause cleanup.
• Log stage transitions only after their saved state changes successfully.
• Preserve completion and cancellation cleanup timestamps across task-projection
  repair and lease release. Older final records keep their previous cleanup age.

Documentation

• Describe Fusion 0.9.3 as the tested baseline, not the current version.
  Strict review compatibility depends on advertised runtime capabilities.

Upgrade

• Restart Pi after updating plan-exec. Dependencies and dispatch/retry policy
  are unchanged. Bridge and native background-work registration are unchanged.

Full changes

v1.7.0

Added

• Compact, theme-aware progress strip with status-colored progress and accepted
  task counts. Locally observed work and completion are green; unpolled
  in-flight runs are amber snapshots, not claims of worker health.
• /exec hide, show [run-id], and clear [run-id] display controls without
  --apply. They do not stop workers or delete recovery evidence. Preferences
  follow the active transcript branch and survive reload.
• On-demand worker lifetime, review backend and bounded advisory activity in
  /exec status. Advisory telemetry is not verified progress or retirement proof.

Fixed

• Retry stop delivery after intent-only acknowledgements and late child binding.
  Preserve correlated cancellation refusals across successful observations and
  restart; distinguish delivered stops from confirmed worker exit.
• Keep recovery history and progress logging independent. Logging no longer
  recreates a deleted execution checkout.
• Keep background-work tracking independent of optional task/Fleet failures.
  Use native transcript-path identity, bound terminal display retention, reject
  stale snapshots, and handle no-session projection explicitly.
• Avoid redundant worktree handoff for path aliases and nonexistent fresh-session
  transcripts. Preserve stop-state precedence and task retry waits in the strip.
• Read colors from the active Pi theme, fit narrow terminals, and remove terminal
  escape and bidirectional control characters from display titles.

Upgrade and limits

• Use Pi 1.0.4+, pi-subagents 0.76.1 (compatible 0.76.x), and Bridge 0.5.5
  (compatible 0.5.x). Restart Pi after package upgrades; /reload is for local
  source/config changes.
• Before upgrading Bridge, stop Bridge-owning Pi processes and back up its
  journal. Schema 7 cannot be reopened by older Bridge versions. Stopping Pi
  owners does not prove unknown workers exited.
• Paused/queued native RPC stops and legacy launches without identity evidence
  remain blocked. Hiding UI never clears execution ownership.

Full changes

v1.6.4

Fixed

• Reattach an exactly bound live child after controller restart without launching a replacement.
• Preserve unrelated task prerequisites and accepted progress during explicitly confirmed recovery.

Added

• /exec recover-isolated previews and confirms continuation of the same logical run in an independent checkout. It uses the accepted commit and checked plan, fences old redispatch and acceptance, and preserves the old operation, tree, partial work and progress as quarantined lineage.
• Show task/check/bootstrap details, old HEAD/commit delta and ignored-file metadata before recovery. Stop/cancel and crash recovery preserve ownership; preparation failures pause for explicit repair/retry.

Upgrade and limits

• Install Bridge 0.5.4 and reload Pi. It retains exact RPC request identities for lost-reply recovery; existing unbound records without evidence still cannot use ordinary resume.
• Isolated recovery changes the target, not the old worker's retirement state. It supports local implementation tasks only, leaves the new target paused, and does not copy unaccepted edits, bypass required checks, or provide a security sandbox. Quarantined targets remain reserved.

v1.6.3

Fixed

• Preserve original Bridge launch errors and structured upstream codes across restart and later lookup failures.
• Validate owner-bound, correlated pre-launch rejection receipts from Bridge before requesting a durable cancellation fence and retrying the preserved task. Lost replies, mismatched identities, and late cancellation remain fenced.
• Show the request digest and lookup diagnostic in status; explain missing proof instead of recommending repeated resume.

Upgrade

• Install Bridge 0.5.3 and pi-subagents 0.76.0 or compatible later versions, then reload Pi. Admission now requires Bridge's pre-launch rejection capability.

Known limits

• Legacy unresolved launches without a persisted correlated rejection remain blocked. This release does not prove that those workers never started; no force-resume or retrospective evidence importer is provided.

v1.6.2

Changed

• Validate the host API against Pi 1.0.2 and bound the Pi SDK development and peer range to ^1.0.2. Keep host SDK/TUI/TypeBox packages out of runtime and bundled dependencies; packaging checks now accept the tested Pi peer range and verify the runtime-only tarball.
• Controller, child RPC, lifecycle, cancellation, and recovery behavior are unchanged.

Upgrade

• Upgrade Pi to 1.0.2 or later in the 1.x series before installing this release, then reload Pi. Older hosts are no longer supported.

v1.6.1

Changes

• Validate the development stack against Pi 0.99.1 and pi-subagents 0.73.1, including package loading, detached workers and native terminal proofs. The newer subagent runtime fixes async recovery, prompt-cache retention and a shutdown race.
• Reject private Pi SDK, TUI and TypeBox dependencies during packaging; add regression checks for host-module warnings. Existing plan-exec host dependencies remain wildcard peers. Warnings from other installed extensions require fixes in those packages.
• Correct setup commands and installation docs to use released runtimes without Git pins. Limit optional pi-tasks compatibility to the adapter's supported 0.9.x range.
• Publish GitHub release notes from this changelog with the version tag as the title.

Known limits

• Strict Fusion review and released Revmux still lack required ownership/lifetime contracts. Native child execution is not guaranteed to be unbounded.
• Dependency audit findings remain unresolved; the suggested force fix downgrades below the required terminal-proof baseline. See upstream audit.

Full comparison

@alexeiled/pi-plan-exec 1.6.0

Package

• Name: @alexeiled/pi-plan-exec
• Version: 1.6.0
• Tag: v1.6.0
• Commit: a75ae4d717401369abea8d14e576910a76466f77
• npm provenance: enabled

What's Changed

• feat: consume released native workflow proofs by @alexei-led in #9

Full Changelog: v1.5.0...v1.6.0