ace-overseer 0.23.0 → 0.25.0

data/CHANGELOG.md

@@ -7,823 +7,43 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.23.0] - 2026-10-16
 
-### Added
-
-- Add explicit ordinary preparation/launch/resume using existing worktree, native pane and provider mechanisms. Preserve original identities and dispatch intent on response loss; use native filesystem watches only as canonical-inspection hints.
-
-### Changed
-
-- Follow ace-review 0.61 campaign head-assessment contracts (dependency floor).
-
-## [0.22.0] - 2026-10-16
-
-### Added
-
-- Package native continuation duties with ten-minute progress and hourly cleanup audits, exact session restoration, independent project progress and explicit unknown outcomes. Align role workflows with canonical Assign ownership and accepted-head review.
-
-## [0.21.1] - 2026-10-14
-
-### Changed
-
-- Package the coordination-contract role-guide updates in the project-overseer and configure-project workflows: serial preparation and serial integration per delivery candidate, queue-item closure as reconciled merge receipt, release-batch lifecycle with separate publication authority, and overseer-owned close-on-accept for delegated panes and worktabs.
-- Follow the ace-lab 0.6 producer line in the dependency manifest; no code or behavior change (constraint-only correction so the coordinated h8x graph resolves).
-
-## [0.21.0] - 2026-10-12
-
-### Added
-
-- Add the `as-overseer-configure-project` skill and packaged `wfi://overseer/configure-project` workflow for idempotent, customization-preserving delivery supervision adaptation.
-
-## [0.20.2] - 2026-10-10
-
-### Fixed
-
-- Require the published producer and consumer patch versions containing the protected context and managed-attempt APIs; exclude incompatible prior dependency graphs.
-
-## [0.20.1] - 2026-10-08
-
-### Changed
-
-- Require the coordinated Assign, Herdr, Lab and Review producer versions for ordinary CLI worker launch and current protected delivery contracts.
-
-- Repair protected work-on composition fixtures to retain the originally provisioned workspace lifecycle resource, exercise the real worker reader, and return the simulated fork before post-readiness steering without changing product admission.
-
-- Route protected delivery through original worker merge request, canonical status and exact result consumption while preserving ordinary delivery and unresolved protected PR policy.
-
-
-### Added
-
-- Consume protected prune preview through the fixed service receiver, persist its complete result for explicitly authorized apply, and query canonical service status without repeating cleanup.
-
-- Package canonical project-overseer, Lab coordinator and second-commander role workflows with scoped authority, responsive delegation and the existing confirmed-delivery decision policy.
-
-- Execute protected candidate review through original launcher delegation, immutable Git snapshot, the maintained review engine and canonical receipt acceptance; expose explicit status/cancel modes without labd forwarding or automatic replay.
-
-- Discover protected project assignments through the actual authority inventory and public topology, preserving pinned pages, restart metadata and partial visibility without a local-journal fallback or proposal effects during status reads.
-
-## [0.20.0] - 2026-10-05
-
-### Added
-
-- Resolve immutable second-commander proposals through confirmed-delivery sixteen-hour policy and canonical Assign authorization.
-- Expose assignment recovery liveness/reasons and show unreadable evidence as unknown rather than omitting it.
-
-### Fixed
-
-- Expose deferred proposal ticks in Lab status diagnostics and object JSON while preserving status availability and array output.
-
-- Keep watch/status alive on proposal tick failure and queue project-scoped HITL reconciliation under the proposer identity.
-
-### Changed
-
-- Declare the required direct dependencies and minimum producer versions for this coordinated release: `ace-assign ~> 0.64`, `ace-git ~> 0.29`, `ace-git-worktree ~> 0.26`, `ace-herdr ~> 0.4`.
-
-## [0.19.1] - 2026-10-04
-
-### Changed
-
-- Install both Herdr and tmux runtime adapters for standalone runtime switching, through an acyclic dependency graph.
-
-## [0.19.0] - 2026-10-04
-
-### Added
-- Work-on and prune manage worktree windows through the `ace-runtime` contract (`TmuxWindowOpener` replaced by `WindowOpener`); the terminal runtime comes from the new `runtime:` config key (`tmux` | `herdr` | `auto`; `ACE_RUNTIME` env wins, detection as fallback, explicit fail when nothing is live).
-- Config key `tmux_window_presets` renamed to `window_presets` (no legacy alias, ADR-024); "tmux window" progress text is runtime-neutral.
-- New dependency: `ace-runtime` (~> 0.1); `ace-tmux` is kept to install the tmux adapter.
-
-## [0.18.2] - 2026-10-02
-
-### Technical
-- Follow the ace-assign 0.61 release line for journal-backed service effects.
-- Updated the ace-tmux dependency to the 0.18 adapter release line.
-
-## [0.18.1] - 2026-10-01
-
-### Technical
-- Follow the ace-assign 0.60 release line for durable review campaign evidence.
-
-## [0.18.0] - 2026-09-29
-
-### Added
-- Preservation manifest for prune: `ace-overseer prune --preservation FILE` accepts a strict `version: 1` YAML manifest declaring cross-repository destinations (source repo/base/head, destination repo/base/head/branch); entries are resolved to exact commits, and duplicate, self-destination, or unmatched entries fail before any apply action.
-- Git preservation proofs on the actual prune path: accepted-ancestor containment against the surviving base branch, or verified-destination proof by full-tree equality or exact path-by-path transition (paths, modes, symlinks, binary content) across separate bases. Patch-range proofs require the independently recorded attempt baseline (`base_head`), and the baseline itself must survive on an accepted ref; empty or truncated ranges are never proof.
-- Fail-closed Lab prune classification: `ace-overseer prune WORK --runtime lab` requires an authoritative terminal Work state plus preservation data (`repo`/`head`/`branch`) provable in the hosted repository; apply re-reads state immediately before `lab work destroy` and blocked Works are never destroyed.
-
-### Changed
-- BREAKING: `--force` no longer removes unsafe worktrees; it only skips the confirmation for already-safe candidates. Missing, failed or ambiguous preservation evidence, dirty tracked or untracked files, active or uncertain attempts, unreadable lifecycle state, and failed rechecks now always block deletion -- including under `--yes` and `--quiet`.
-- Prune preview is read-only (no stale-metadata mutation); apply holds a durable lifecycle exclusion shared with assignment/driver/work-on start paths from final evidence reads through removal, deletes the worktree without force or untracked suppression, and deletes the branch only after re-verifying its tip identity. Removal is recorded so later starts fail closed instead of recreating a deleted identity.
-- Assignment cache prune requires the durable evidence ref (`refs/ace/execution`, never deleted) to confirm every attempt terminal for managed assignments; only the assignment cache directory is removed.
-- Unmatched explicit prune targets are errors, apply exits nonzero when any candidate is blocked or removal fails (independent safe candidates still complete), quiet mode suppresses progress but never failure signaling, and dry-run performs the same proof classification with no cleanup side effects.
-
-## [0.17.0] - 2026-09-29
-
-### Added
-- Added an explicit Lab runtime adapter for listing projects and agents, preparing and dispatching Works, forwarding prompts over stdin, starting exact-head reviews, and stopping workers.
-- Added installed-consumer probe coverage: the suite builds the current gem artifacts, installs them into an isolated consumer environment (fresh gem home, unrelated cwd, sanitized HOME), and proves `ace-nav resolve wfi://overseer` and `ace-bundle wfi://overseer` succeed from packaged content only, with a registration-removal fixture proving the probe detects masking.
-
-### Changed
-- Kept tmux as the default runtime while allowing `work-on`, `status`, and dry-run `prune` to delegate through the system-owned `/usr/local/bin/lab` boundary.
-- Strengthened the overseer prune-safety contract: migrated-work preservation now requires a declared, verified destination plus tree/artifact or patch equivalence (the subject-only successor search is gone), plus a positive executed no-active-writer check from overseer/assignment/Lab status; ambiguity preserves.
-
-
-## [0.16.0] - 2026-09-20
-
-### Added
-- Shipped the overseer lifecycle workflow so `wfi://overseer` resolves for gem consumers: the gem now registers `.ace-defaults/nav/protocols/wfi-sources/ace-overseer.yml` (ace-hitl pattern) and ships real workflow instructions for `work-on`, `status`, and `prune` in `handbook/workflow-instructions/overseer.wf.md`, with prune-safety and status-truth executed-check contracts as first-class non-negotiable steps.
-- Added a packaging test proving the built gem ships both the workflow-instructions payload and the wfi source registration so a future gemspec glob change cannot silently drop them.
-
-## [0.15.6] - 2026-09-02
-
-### Technical
-- Included in the coordinated all-package patch release preparation for ACE monorepo review.
-## [0.15.5] - 2026-08-12
-
-### Technical
-- Raised the `ace-support-core` dependency floor to `~> 0.31` after the principles-first bootstrap guidance release.
-## [0.15.4] - 2026-08-12
-
-### Fixed
-- Updated the `ace-tmux` runtime dependency constraint to `~> 0.17` so overseer stays compatible with the current tmux runtime control release line.
-
-### Technical
-- Aligned gemspec dependency floors with current ACE package minor release lines and safe external minor dependency bumps (no major version jumps).
-
-## [0.15.3] - 2026-04-23
-
-### Technical
-- Tightened retained `status --watch` E2E coverage to use a controlled bounded-session shutdown with explicit command captures, keeping refresh verification aligned with the documented watch contract.
-
-## [0.15.2] - 2026-04-23
-
-### Technical
-- Aligned retained `work-on` E2E verification with the current prepared-assignment contract so post-launch status accepts `paused` plus `next_step` until `/ace-assign-drive` actually starts work.
-
-## [0.15.1] - 2026-04-23
-
-### Technical
-- Updated the `ace-git-worktree` runtime dependency constraint to `~> 0.21` so overseer stays aligned with the current worktree minor release line.
-
-## [0.15.0] - 2026-04-23
-
-### Changed
-- Updated overseer status collection, formatting, and work-on orchestration to consume `ace-assign`'s `active_steps`/`next_step` lifecycle contract instead of the old singular `current_step`/`in_progress` model.
-- Revised overseer test fixtures and resume behavior so existing assignments now prefer the focused active step and otherwise fall back to the next pending step in scope.
-
-## [0.14.14] - 2026-04-23
-
-
-### Changed
-- Reworked tmux window-open behavior to align with shared session targeting and reduce ambiguity when launching and reusing worktree windows.
-- Updated overseer tmux-window coverage to verify the current session/window lifecycle against the improved launcher behavior.
-
-
-## [0.14.13] - 2026-04-22
-
-### Fixed
-- Matched existing tmux windows through the shared `ace-tmux` sanitized window-name policy so worktrees with punctuation are not reopened under duplicate names.
-
-## [0.14.12] - 2026-04-19
-
-### Technical
-- Tightened retained overseer E2E runner and verifier contracts so `work-on` postcondition captures cannot run before the primary command has completed, and preset-override verification requires public `r8x` worktree evidence.
-
-## [0.14.11] - 2026-04-18
-
-### Technical
-- Relaxed retained watch-mode E2E verification to tolerate bounded `Open3` stream-closure noise when the visible `status --watch` behavior and controlled shutdown codes are otherwise correct.
-
-## [0.14.10] - 2026-04-16
-
-### Fixed
-- Normalized `status --watch` interrupt handling so watch-mode exits no longer dump a Ruby stack trace, and aligned retained E2E verification with the bounded termination codes the command now emits.
-
-## [0.14.9] - 2026-04-16
-
-### Fixed
-- Reused the orchestrator task manager when launching default assignments so multi-task `work-on` flows no longer partially provision a task and then fail lookup against a different task-resolution path.
-
-## [0.14.8] - 2026-04-16
-
-### Fixed
-- Relaxed `TS-OVERSEER-001` prune verification to judge the documented public prune flow from captured dry-run/prune artifacts and resulting state instead of requiring echoed command lines.
-
-## [0.14.7] - 2026-04-16
-
-### Fixed
-- Taught tmux window opening to create the target session when it is missing so sandboxed overseer E2E runs can open task windows reliably on the intended socket.
-
-## [0.14.6] - 2026-04-15
-
-### Changed
-- Reworked `TS-OVERSEER-001` into a public-surface goal contract by absorbing standalone help survey into Goal 2 preflight, simplifying prune flow to normal lifecycle commands, and tightening rerun/override checks to stable status/worktree oracles.
-- Added `TS-OVERSEER-002` status-and-operations coverage with watch-refresh and multi-task bundle journeys.
-- Updated `docs/usage.md` with explicit public verification paths for preset override, idempotent rerun, and minimal prune lifecycle checks.
-
-### Fixed
-- Updated the `ace-assign` runtime dependency constraint to `~> 0.53` so overseer remains aligned with the current assign minor release line.
-
-## [0.14.4] - 2026-04-13
-
-### Fixed
-- Rewrote the retained `TS-OVERSEER-001` workflow-value cases around final sandbox state and runner observations so preset-override and prune verification no longer depend on brittle helper artifacts.
-
-## [0.14.3] - 2026-04-13
-
-### Fixed
-- Tightened `TS-OVERSEER-001` preset-override and prune scenario contracts so path-check artifacts are explicit and optional pre-completion status captures no longer fail the workflow before semantic verification.
-
-## [0.14.2] - 2026-04-13
-
-### Fixed
-- Updated the `ace-assign` runtime dependency constraint to `~> 0.49` so overseer remains compatible with the new assign minor release line.
-
-## [0.14.1] - 2026-04-13
-
-### Changed
-- Completed the batch i05 migration follow-through for this package and aligned it with the restarted `fast` / `feat` / `e2e` verification model.
-
-### Technical
-- Included in the coordinated assignment-driven patch release for batch i05 package updates.
-
-
-## [0.14.0] - 2026-04-12
-
-### Changed
-- Migrated package tests to the `fast` / `feat` / `e2e` model by moving deterministic coverage from `test/{atoms,commands,models,molecules,organisms}` into `test/fast/*`.
-- Added E2E migration decision tracking for `TS-OVERSEER-001` via `test/e2e/TS-OVERSEER-001-overseer-workflow/e2e-decision-record.md`.
-- Updated package README testing guidance to teach only `ace-test ace-overseer`, `ace-test ace-overseer feat`, `ace-test ace-overseer all`, and `ace-test-e2e ace-overseer`.
-
-### Fixed
-- Hardened `TS-OVERSEER-001` sandbox setup by loading `mise.toml` from `${ACE_E2E_SOURCE_ROOT:-$PROJECT_ROOT_PATH}`.
-- Updated TC-002/TC-003 verifier expectations to use the JSON status oracle and task-window-scoped tmux duplicate checks, eliminating false negatives in rerun validation.
-
-## [0.13.12] - 2026-04-12
-
-### Fixed
-- Updated the `ace-git-worktree` runtime dependency constraint to `~> 0.20` so overseer remains compatible with the new worktree minor release line.
-
-## [0.13.11] - 2026-04-11
-
-### Fixed
-- Updated the `ace-assign` runtime dependency constraint to `~> 0.47` so overseer remains compatible with the latest assign minor release line.
-
-## [0.13.10] - 2026-04-07
-
-### Fixed
-- Updated the `ace-assign` runtime dependency constraint to `~> 0.44` so overseer remains compatible with the new assign minor release line.
-
-## [0.13.9] - 2026-04-01
-
-### Fixed
-- Updated the `ace-assign` runtime dependency constraint to `~> 0.42` so overseer remains compatible with the new assign minor release line.
-
-## [0.13.8] - 2026-03-29
-
-### Technical
-- Normalized published gem metadata so RubyGems and Ruby Toolbox use current release information instead of the 1980 fallback date.
-
-## [0.13.7] - 2026-03-29
-
-### Fixed
-- Bumped the `ace-git` runtime dependency constraint to `~> 0.19` so ace-overseer stays aligned with the current git workflow release.
-
-## [0.13.6] - 2026-03-29
-
-### Fixed
-- Updated the `ace-assign` runtime dependency constraint to `~> 0.41` to stay aligned with the current released assign API.
-
-## [0.13.5] - 2026-03-29
-
-### Technical
-- Register package-level `.ace-defaults` skill-sources for ace-overseer to enable canonical skill discovery in fresh installs.
-
-## [0.13.4] - 2026-03-29
-
-### Fixed
-- Bumped dependency constraints to currently available `~>` ranges on RubyGems and updated release metadata after dependency synchronization.
-
-## [0.13.3] - 2026-03-28
-
-### Fixed
-- Added an explicit git-repository guard for operational commands so `work-on`, `status`, and `prune` fail cleanly outside a repo or worktree instead of leaking raw `git` errors.
-
-### Technical
-- Added command coverage for non-repo failure paths and updated launcher fixtures to initialize real git repos in temporary worktree test directories.
-
-## [0.13.2] - 2026-03-27
-
-### Fixed
-- Preserved taskref-only preset compatibility by collapsing launcher task refs to the primary task when a preset does not declare `taskrefs`.
-
-## [0.13.1] - 2026-03-27
-
-### Fixed
-- Updated work-on preset guard checks to evaluate active resolved refs after terminal filtering, preventing false single-task preset rejections on mixed terminal/non-terminal inputs.
-- Preserved parent refs during taskref expansion when all subtasks are terminal, preventing empty expansion results from valid parent-task inputs.
-
-## [0.13.0] - 2026-03-27
-
-### Changed
-- Routed `ace-overseer work-on` assignment launch through the shared `ace-assign create --task ...` creation path while preserving the existing CLI and pre-side-effect validation behavior.
-- Updated package docs to describe the shared task-driven assignment creation flow with `ace-assign`.
-
-### Technical
-- Added launcher and orchestrator coverage for the shared creator path and explicit task fixture resolution.
-
-## [0.12.1] - 2026-03-26
-
-### Fixed
-- Tightened `ace-assign` gemspec constraint from `~> 0.16` to `~> 0.38` to match the runtime dependency introduced in v0.12.0.
-
-## [0.12.0] - 2026-03-26
+## [0.25.0] - 2026-10-20
 
 ### Added
-- Terminal task filtering in `WorkOnOrchestrator`: tasks with `done`, `skipped`, or `cancelled` status are automatically excluded before assignment creation, with user-visible skip reporting via progress callbacks.
 
-### Changed
-- `resolve_requested_refs` now returns skipped terminal refs alongside resolved refs, raising an error when all requested refs are terminal.
-- `expand_task_refs_in_order` and `extract_subtask_refs` filter out terminal subtasks during parent-to-subtask expansion.
-
-### Technical
-- Added 4 tests covering single-terminal rejection, all-terminal rejection, mixed-set filtering, and subtask-level terminal filtering.
+- Add the derived attention section to `ace-overseer status` (L7.4): blockers, failures and missing data in one view, clearly distinguished from healthy progress. The one-shot table (and `--format json`) now opens with `-- attention`, and the JSON payload gains `attention: {blockers:, failures:, missing_data:}` — computed live from the already-collected status sources plus the read-only `Molecules::HitlInbox`, no new fetchers and nothing persisted (new organism `Organisms::StatusAttention`). BLOCKER rows list startable tasks (`pending` in the project or `_overseer` tree) whose dependencies are unsatisfied, plus tasks explicitly `blocked`, each with the concrete per-dependency reason from `Atoms::DependencyReadiness` (predecessor status, missing/cyclic dependency) and a next action. FAILURE rows cover source errors (with origin), `failed`/`stalled` assignments, per-worktree executor probe errors, and escalations (pending ace-hitl questions awaiting an answer). MISSING DATA rows make gaps explicit — disabled sources, unknown `status_sources` keys, unreadable task trees (dependency readiness unverified), unrecognized task statuses, unknown executor states (the worktree is not free), an unreachable hitl inbox — because absence of data never confirms a free worktree or a finished task. When nothing needs attention the section states that explicitly.
 
-## [0.11.0] - 2026-03-23
+- Add configurable status sources to `ace-overseer status` (L7.2): the command aggregates every source configured under `status_sources` (defaults: `worktrees`, `forge` (default OFF), `project_tasks`, `overseer_tree`, `herdr`, `coworkers`) into one live, read-only view — ongoing steps, finished work, dependencies, and available resources. Each source is a thin adapter over its owner's interface (ace-git-worktree WorktreeManager, ace-git forge Providers `recent_pull_requests`, ace-task TaskManager for `.ace-tasks/` and `.ace-tasks/_overseer/`, ace-herdr ControlSurface + StatusComposer read-only, ace-coworker WorktreeExecutorProbe + ActiveExecutorRule). A disabled source is marked `disabled`; a failing source is marked `error` with its origin, rendered NEXT TO the healthy results — missing data never reads as a free worktree or a finished task (an unknown or unparseable coworker commission reports `active: true` with state `unknown`/`unparseable`). `--format json` emits the per-source contract `{sources: {<name>: {status: ok|disabled|error, origin:, data:|error:}}}` for the next role/tool; nothing is persisted (new organism `Organisms::StatusSources`, `StatusCollector#collect_sources`).
 
-### Changed
-- Clarified README intro and How It Works section to describe assignment expansion into `.ace-local/assign/` and agent-driven orchestration.
-- Re-recorded getting-started demo GIF against live project context showing the full worktree dashboard with progress bars, PR status, and failure counts.
-
-## [0.10.3] - 2026-03-23
-
-### Changed
-- Refreshed package README layout, quick-link navigation, and section flow to align with the current package pattern.
-
-## [0.10.2] - 2026-03-22
-
-### Fixed
-- Updated `work_on` orchestration messaging and preset expectations to use the canonical `work-on-task` preset name for taskref-driven batch flows.
-
-### Changed
-- Aligned default tmux window preset mapping and associated test coverage with singular `work-on-task` preset naming.
-
-## [0.10.1] - 2026-03-22
-
-### Changed
-- Remove `mise exec --` wrapper from error message string in worktree provisioner.
-
-## [0.10.0] - 2026-03-22
-
-### Added
-- Added configurable tmux window preset selection for `work-on` when using the `work-on-tasks` assignment preset.
-- Added an overseer-specific `work-on-tasks` layout that launches `cc /as-assign-drive`, opens the active assignment report folder in `nvim`, and runs both `ace-task status` and `ace-assign status`.
-
-## [0.9.0] - 2026-03-22
-
-### Changed
-- Updated task context collection to recognize short task worktree naming prefixes (`t.*`, `ace-t.*`) when resolving task IDs from worktree paths.
-
-## [0.8.2] - 2026-03-22
-
-### Fixed
-- Align README messaging: changed "start an assignment" to "prepare an assignment for execution" to match actual `work-on` behavior.
-
-## [0.8.1] - 2026-03-22
-
-### Fixed
-- Include `docs/**/*` in gemspec so documentation ships with the gem.
-
-## [0.8.0] - 2026-03-22
-
-### Added
-- Reworked package documentation with a new landing-page README, tutorial getting-started guide, full usage reference, handbook catalog, demo assets, and aligned gem metadata messaging.
-
-## [0.7.1] - 2026-03-19
-
-### Changed
-- Refined `TS-OVERSEER-001` E2E verifier structure with explicit impact-first validation and normalized check sections across all goals.
-- Expanded Goal 2 E2E coverage to require both `ace-overseer status --format json` and `--format table` evidence artifacts.
-
-## [0.7.0] - 2026-03-18
-
-### Changed
-- Updated assignment system references from "phase" to "step" terminology: `first_phase` → `first_step`, `current_phase` → `current_step`, `phase_summary` → `step_summary` across launcher, orchestrator, status formatter, and context collector
-
-## [0.6.1] - 2026-03-18
-
-### Changed
-- Migrated CLI namespace from `Ace::Core::CLI::*` to `Ace::Support::Cli::*` (ace-support-cli is now the canonical home for CLI infrastructure).
-
-
-## [0.6.0] - 2026-03-18
-
-### Changed
-- Removed legacy backward-compatibility behavior as part of the 0.10 cleanup release.
-
-
-## [0.5.6] - 2026-03-15
-
-### Fixed
-- Restructured TC-005 prune workflow runner with explicit numbered steps to prevent LLM runner from executing prune before assignment completion
-
-## [0.5.5] - 2026-03-15
-
-### Fixed
-- Removed dead `DryCli::ArgvCoalescer` call that caused NameError after ace-support-cli migration
-
-## [0.5.4] - 2026-03-15
-
-### Changed
-- Migrated CLI framework from dry-cli to ace-support-cli
-
-## [0.5.3] - 2026-03-13
-
-### Fixed
-- Reject tasks with `draft` status at assignment creation time with actionable review guidance, preventing unattended forks from stalling on interactive confirmation.
-
-## [0.5.2] - 2026-03-13
-
-### Changed
-- Updated the canonical overseer skill to explicitly run its bundled workflow in the current project and execute it end-to-end.
-
-## [0.5.1] - 2026-03-12
-
-### Fixed
-- Registered the package WFI source so `wfi://overseer` resolves for the canonical overseer skill.
-
-## [0.5.0] - 2026-03-10
-
-### Added
-- Added the canonical handbook-owned overseer skill and a package workflow for task worktree orchestration.
-
-
-## [0.4.21] - 2026-03-08
-
-### Fixed
-- `WorktreeProvisioner` now recovers from stale worktree metadata by pruning and retrying provisioning, and raises actionable errors when paths remain missing.
-- `PruneOrchestrator` no longer crashes on missing/prunable worktree paths and marks those entries as unsafe candidates instead.
-
-### Changed
-- `prune` now runs a stale metadata prune pass before scanning and defaults to task-associated worktrees when no explicit targets are provided.
-
-## [0.4.20] - 2026-03-05
-
-### Changed
-- Overseer task-workflow fixtures were migrated to non-legacy task IDs and `.ace-tasks` fixture layout.
-
-## [0.4.19] - 2026-03-04
-
-### Changed
-- Assignment launcher temporary job files now use `.ace-local/overseer`.
-
-
-## [0.4.18] - 2026-03-03
-
-### Added
-- `StatusCollector`: show non-task worktrees in status when they have active assignments
-- `WorktreeContextCollector`: support B36TS task ID extraction from worktree paths and branch names
-
-### Fixed
-- `PruneOrchestrator`: allow pruning non-task worktrees when targeted by path (removes `task_associated` filter)
-
-## [0.4.17] - 2026-03-02
-
-### Changed
-- Replace `ace-taskflow` dependency with `ace-task` -- migrate `WorkOnOrchestrator` and `PruneSafetyChecker` to use `Ace::Task::Organisms::TaskManager` API
-- Remove bare `require "ace/taskflow"` import, add `require "ace/task"`
-
-## [0.4.16] - 2026-02-26
-
-### Fixed
-- Fix repeated `--task` flags (`--task 288 --task 287`) being silently dropped by dry-cli; values are now coalesced before parsing
-
-## [0.4.15] - 2026-02-26
-
-### Fixed
-- Raise descriptive error when no valid task references are provided to `WorkOnOrchestrator`, preventing `NoMethodError` on empty input.
-
-## [0.4.14] - 2026-02-26
-
-### Added
-- Support ordered multi-task input for `ace-overseer work-on --task` using repeated flags, comma-separated values, or mixed forms.
-- Add explicit `task_refs` launch parameter support in `AssignmentLauncher` for multi-task presets using `taskrefs`.
-
-### Fixed
-- Validate all provided task references before worktree/tmux/assignment side effects.
-- Fail early with actionable guidance when multiple task refs are provided to a single-task (`taskref`) preset.
-
-### Changed
-- Preserve left-to-right task execution order while expanding orchestrator refs in-place to subtask sequences.
-
-## [0.4.13] - 2026-02-24
-
-### Fixed
-- Isolate `TS-OVERSEER-001` E2E tmux execution per run by switching scenario setup to `tmux-session: { name-source: run-id }`, preventing cross-run/default-session collisions.
-
-### Changed
-- Clarify runner guidance for tmux evidence collection to always target `ACE_TMUX_SESSION` explicitly.
-
-## [0.4.12] - 2026-02-24
-
-### Changed
-- Refine `TS-OVERSEER-001` TC-005 prune workflow runner instructions to explicitly resolve task.001 worktree path and execute `ace-assign` steps from that worktree while writing artifacts to the sandbox `results/` tree.
-
-## [0.4.11] - 2026-02-24
-
-### Changed
-- Update `TS-OVERSEER-001` TC-005 prune workflow instructions to require explicit assignment-completion evidence and post-prune verification artifacts.
-
-## [0.4.10] - 2026-02-23
-
-### Technical
-- Updated internal dependency version constraints to current releases
-
-## [0.4.9] - 2026-02-22
-
-### Changed
-- Migrate CLI to standard dry-cli help pattern with HelpCommand registration
-- Remove custom `start()` method and `KNOWN_COMMANDS` constant in favor of standard pattern
-
-## [0.4.8] - 2026-02-22
-
-### Fixed
-- Standardized quiet, verbose, debug option descriptions to canonical strings
-
-## [0.4.7] - 2026-02-22
-
-### Changed
-- Migrate skill naming and invocation references to hyphenated `ace-*` format (no underscores).
-
-## [0.4.6] - 2026-02-21
-
-### Fixed
-- Fix TC-003 tmux window verification to use `tmux list-windows -a` (all sessions) to avoid env var propagation issues in E2E test agents
-
-## [0.4.5] - 2026-02-21
-
-### Fixed
-- Fix `WorkOnOrchestrator` to pass `task_root_path` (resolved from `PROJECT_ROOT_PATH` env var or `Dir.pwd`) to `TaskLoader`, ensuring tasks are found correctly in worktree environments
-- Fix E2E tests to use `ACE_TMUX_SESSION` variable instead of hardcoded `ace-e2e-test` session name for tmux window verification
-
-## [0.4.4] - 2026-02-20
-
-### Fixed
-- E2E scenarios (TS-OVERSEER-001, TS-OVERSEER-002) now use `tmux-session` setup step for isolated tmux sessions instead of leaking windows into the developer's active session
-- Remove hardcoded `tmux kill-session -t "ace-e2e-test"` from TS-OVERSEER-002 setup that was polluting the developer environment
-
-## [0.4.3] - 2026-02-19
-
-### Fixed
-- Prune orchestrator now passes `delete_branch: true` to worktree manager's `remove` call, ensuring git branches are cleaned up when worktrees are pruned
-
-## [0.4.2] - 2026-02-19
-
-### Added
-- Orchestrator subtask expansion for `work-on-tasks` preset -- when a task is an orchestrator with subtasks, `AssignmentLauncher` expands subtask refs into individual foreach steps (e.g., `work-on-272.01`, `work-on-272.02`) instead of a single `work-on-272` step
-- `extract_subtask_refs` helper in `WorkOnOrchestrator` to extract subtask numbers from orchestrator task data
-- `subtask_refs:` keyword argument on `AssignmentLauncher#launch` for passing expanded subtask references
-
-## [0.4.1] - 2026-02-19
-
-### Added
-- `--watch` / `-w` option for `status` command -- auto-refreshing dashboard with ANSI screen clear
-- Two-tier refresh: fast interval (15s default) refreshes assignment data only, slow interval (5min default) does full git/PR refresh
-- `collect_assignments_only` method on `WorktreeContextCollector` for lightweight assignment-only collection with cached git data
-- `collect_quick` method on `StatusCollector` to reuse previous snapshot's git data while refreshing assignments
-- `format_watch_footer` on `StatusFormatter` showing dim timestamp and countdown to next full refresh
-- Configurable watch intervals via `watch.refresh_interval` and `watch.git_refresh_interval` in overseer config
-
-## [0.4.0] - 2026-02-19
-
-### Added
-- Progress bar visualization in assignment sub-rows -- filled/empty bar segments alongside numeric counts
-- Current step name display for running assignments (e.g., `implement` shown dimmed after progress)
-- Header row and separator line above hierarchical dashboard for column labeling
-- Blank line separators between location groups for visual breathing room
-- `current_step` field propagated from `QueueState` through `WorktreeContextCollector` to status display
-
-### Changed
-- Widen progress column to accommodate progress bar and current step text
-
-## [0.3.1] - 2026-02-19
-
-### Changed
-- Hierarchical status display -- location header rows with assignment sub-rows replace flat single-row format
-- `WorkContext` model uses `assignments` array instead of singular `assignment_status` + `assignment_count`
-- `WorktreeContextCollector` loads all assignments via `AssignmentDiscoverer` instead of only active via `AssignmentExecutor`
-- `StatusFormatter` emits two row types: location header (basename + PR + Git) and indented assignment sub-rows (ID + name + state + progress)
-- IPC serialization in `StatusCollector` uses `assignments` array
-- Main branch inclusion check uses `assignments.any?` instead of `assignment_status`
+- Add `ace-overseer process-reports` (L6.5): interpret every incoming ace-hitl event against the private `_overseer` task tree, record the outcome through the existing `ace-task update` surface, and continue the queue by reusing the existing gates. Matching uses the assignment reference recorded on a step (or the managing task's `project_task` with exactly one non-terminal step); a success report records `processed_report`/`report_result` on the step and advances it to `done`, then continues with the next unblocked step — via `ace-overseer handoff` when the family records a worktree (next role in the SAME worktree) or the work-on gate otherwise. A repeated delivery of a processed report is detected from the recorded `processed_report` and re-runs nothing, and so is a success report under a NEW id whose only assignment match is a terminal step (no reopen path: it resolves to the recorded result instead of re-advancing the done step); ambiguous cross-manager matches stay unmatched instead of silently picking one; an error report or a question never advances a step (questions surface the `ace-hitl update <id> --answer` path); a report matching no open allocation stays for clarification. Continuation refusals (dependency gate, handoff gate) surface as blocked with reasons, never as success (new pure atom `Atoms::ReportInterpretation`, molecule `Molecules::HitlInbox`, organism `Organisms::ReportProcessor`; new runtime dependency `ace-hitl`).
+- Add `ace-overseer handoff --task <ref>` (L6.4): hand the SAME task worktree to the next role in the prepared role sequence. The gate reads only real state — the worktree's role-sequence assignments (ace-assign files, composition order) with their current states, the per-leg start configs from `ace-coworker prepare`, and the worktree's executor truth via the coworker `ActiveExecutorRule` (new runtime dependency `ace-coworker`) — so two active executors are impossible: a failed, in-flight, stalled, or unknown-state predecessor refuses the handoff with reasons (unknown state is never a free resource), and a busy worktree never gets a second executor. On success it opens the next executor's window in the same worktree and prints `ace-coworker start --config .ace-local/coworker/prepare/<role>.yml`; nothing is re-prepared and no worktree is ever created (new pure atom `Atoms::HandoffReadiness`, molecule `Molecules::HandoffProbe`, organism `Organisms::HandoffOrchestrator`).
+- Gate `work-on` starts on dependency readiness (L6.3): a step starts only when every recorded `dependencies` predecessor has status `done` (accepted and integrated result). A finished worker or open PR does not unlock a dependent step; cancelled, skipped, missing, or cyclic predecessors block the start with explicit reasons before any worktree/assignment side effect (new pure atom `Atoms::DependencyReadiness`, wired into `WorkOnOrchestrator`).
 
 ### Removed
-- `assignment_executor_factory` dependency from `WorktreeContextCollector`
-- Flat single-row dashboard format with header/separator lines
 
-## [0.3.0] - 2026-02-19
-
-### Added
-- Assignment-aware status display -- main branch appears in `status` when it has active assignments
-- Assignment count shown in Assign column when location has multiple assignments (e.g., `abc12 (3)`)
-- `--assignment` / `-a` option for `prune` command to remove a specific assignment's cache directory
-- `AssignmentPruneCandidate` model for assignment-level prune safety checking
-- `AssignmentPruneSafetyChecker` molecule to evaluate assignment prune safety
-- `AssignmentManager#delete` method in ace-assign for removing assignment cache and cleaning up symlinks
-- `assignment_count` and `location_type` fields on `WorkContext` model
+- Remove the installed `ordinary` CLI command and `OrdinaryWorkOn` launcher: the `/as-assign-drive --ordinary` handoff is invalid after the local file-based rework.
+- Remove installed journal/attempt dependencies from local prune and status: `WorktreeContextCollector` no longer reads attempt recovery state, and `PruneSafetyChecker`/`AssignmentPruneSafetyChecker` classify candidates from local assignment records (completed state, no active/pending steps), task state, worktree cleanliness, and executed Git preservation proofs only.
 
 ### Changed
-- `StatusCollector` now collects main branch context alongside worktree contexts
-- `StatusFormatter` sorts main branch row last, displays `main` in Task column with dim styling
-- `WorktreeContextCollector` counts assignments per location via `AssignmentDiscoverer`
-- `PruneOrchestrator` supports assignment-level pruning path with safety checks and force override
-- Widened Assign column from 6 to 10 characters to accommodate count display
-- IPC serialization includes `assignment_count` for parallel subprocess collection
-
-## [0.2.17] - 2026-02-19
-
-### Changed
-
-- `TmuxWindowOpener` delegates entirely to `ace-tmux window` CLI -- no longer manages session names, window names, or presets
-- Remove `tmux_session_name`, `window_name_format`, and `window_preset` config options
-- Remove `WindowNameFormatter` atom -- window naming is ace-tmux's responsibility
-- `PruneOrchestrator` uses worktree path basename for window cleanup instead of formatted names
-
-## [0.2.16] - 2026-02-19
-
-### Changed
-
-- `TmuxWindowOpener` no longer manages tmux sessions -- delegates entirely to ace-tmux `WindowManager` for window creation, session detection, and dedup
 
-## [0.2.15] - 2026-02-19
+- Prune-safety and status guidance no longer refer to attempt baselines or terminal attempts; use assignment status and unresolved-work evidence instead.
+- Rename the prune candidate safety field from `attempts_terminal` to `work_terminal` (local assignment work, not attempts).
+- Patch-range preservation proofs derive their creation baseline from Git: the declared source base must equal the fork point of the candidate head and the accepted base tip. A declared base newer than the fork point blocks because it could hide candidate work.
 
 ### Fixed
-- Task ID extraction now recognizes `ace-task.NNN` worktree paths, fixing mismatch where overseer status showed branch-derived task ID instead of the path-derived one
-
-## [0.2.14] - 2026-02-19
-
-### Added
-- `--force` (`-f`) flag for `prune` command to bypass safety checks and force-remove unsafe worktrees
-- Positional target arguments for `prune` to filter by task ref or folder name (e.g., `ace-overseer prune 230 265`)
-- Dry-run output shows `[FORCE]` tag on forced candidates
-
-## [0.2.13] - 2026-02-19
-
-### Added
-- Progress callbacks (`on_progress:`) for `work-on` and `prune` orchestrators -- one-line status output per step
-- Prune now displays safe/skipped candidates with reasons before the "Continue?" confirmation prompt
-
-### Changed
-- `work-on` command output replaced with real-time progress messages instead of post-hoc summary
-
-## [0.2.12] - 2026-02-19
-
-### Fixed
-- Prune workflow now removes safe worktrees with `ignore_untracked: true`, allowing untracked-only trees to be pruned while still protecting tracked changes
-- Tighten prune E2E assertions with task-specific grep patterns and aligned fixture/config expectations for TS-OVERSEER-002
-
-## [0.2.11] - 2026-02-19
-
-### Fixed
-- Add `exit!(1)` safety net after `exec` in forked status worker to prevent child process leaking parent state if exec fails
-- Filter nil contexts from failed parallel workers with `.compact` to prevent `NoMethodError` in dashboard formatting
-
-## [0.2.10] - 2026-02-18
-
-### Changed
-- Right-size `ace-overseer` E2E coverage from 11 to 6 focused test cases by removing command error-path duplicates already covered in package tests.
-- Consolidate prune workflow assertions so retained E2E cases validate dry-run no-side-effects and tmux cleanup in fewer scenarios.
-
-### Fixed
-- Reuse existing tmux windows in `work-on` to avoid duplicate task windows on idempotent reruns.
-- Treat repositories with only untracked files as prune-safe when tracked changes are clean, preventing false `git not clean` outcomes.
-- Return a user-friendly CLI error when `ace-overseer work-on` is invoked without `--task`.
-
-### Added
-- Add command tests for `work-on` missing `--task` and task-not-found error behavior.
-
-## [0.2.9] - 2026-02-18
-
-### Fixed
-- Manage PROJECT_ROOT_PATH environment variable and clear ProjectRootFinder cache when switching worktree contexts to ensure ace-assign and other tools find correct configuration
-
-### Technical
-- Add comprehensive E2E test cases for overseer workflows
-- Add E2E test configuration presets
 
-## [0.2.8] - 2026-02-17
-
-### Changed
-
-- Parallelize worktree context collection using fork/exec for 3-4x speedup (5-7s → 1.5s for 6 worktrees)
-- Use subprocess isolation to avoid Dir.chdir thread-safety issues
-
-### Fixed
-
-- Test expectation for status header ("ASSIGNMENTS" → "Assign")
-
-## [0.2.7] - 2026-02-17
-
-### Added
-
-- Assign column showing compact assignment ID for quick reference
-- Git dirty file count display (e.g., `✗ 3`) instead of just `✗`
-
-### Changed
-
-- Reorder columns: Assign first, Progress last
-- Fix column alignment by pre-padding colored fields before ANSI codes
-- Remove redundant "ASSIGNMENTS" title (table header is self-explanatory)
-
-## [0.2.6] - 2026-02-17
-
-### Changed
-
-- Replace text status labels with Unicode icons and ANSI colors for compact, scannable output
-- Sort dashboard rows by PR number descending; rows without PR appear first (sorted by task desc)
-- Remove Path column (redundant with Task ID) to save horizontal space
-- Colorize PR state (OPN green, MRG blue, CLS dim, DFT yellow) and Git state (✓/✗ with colors)
-
-### Added
-
-- Support for new `:stalled` assignment state icon (◼ yellow)
-
-## [0.2.5] - 2026-02-17
-
-### Fixed
-
-- Set `PROJECT_ROOT_PATH` per worktree in context collector so each worktree resolves its own assignment cache directory instead of all sharing the invoking worktree's data
-- Restore `PROJECT_ROOT_PATH` and clear `ProjectRootFinder` cache after collection to prevent cross-worktree contamination
-
-## [0.2.4] - 2026-02-17
-
-### Changed
-
-- Replace release-centric status view with assignment-focused dashboard showing path, state, progress, and PR columns.
-- Remove release resolver dependency from status collector.
-- Add step summary data (total/done/failed) to worktree context collection.
-- Add PR metadata display with abbreviated state (OPN, MRG, CLS, DFT) in status output.
-
-## [0.2.3] - 2026-02-17
-
-### Changed
-
-- Protect `gem_root` memoization with mutex synchronization.
-- Use atomic tempfile writes for generated assignment job files.
-- Improve task ID extraction robustness in worktree context collector.
-
-## [0.2.2] - 2026-02-17
-
-### Fixed
-
-- Ensure `prune --quiet` still executes prune logic instead of returning early.
-- Add missing runtime dependencies in gemspec for required ACE gems.
-- Handle `SIGINT` in executable with exit code `130`.
-
-### Changed
-
-- Expand assignment preset lookup to include `.ace/assign/presets` before defaults.
-- Use post-action wording in `work-on` command output for accurate UX timing.
-- Improve prune task-done checks to account for repository common root context.
-
-## [0.2.1] - 2026-02-17
-
-### Changed
-
-- Release patch after the valid review cycle with no additional code changes required.
-
-## [0.2.0] - 2026-02-17
-
-### Changed
-
-- Promote the initial `ace-overseer` implementation set to a minor release.
-- Align release metadata for assignment-driven delivery flow.
-
-## [0.1.0] - 2026-02-17
-
-### Added
+- Recover the preparation readiness crash cut (PR393 final audit finding #4): after preparation became `done` with its readiness report recorded (`processed_report` persisted) but the continuation never dispatched (crash between persist and handoff), the re-delivered assignment-less readiness report fell out `unmatched` — worker dispatch never resumed. Matching now checks the already-recorded report identity BEFORE filtering new matches to non-terminal steps, so the exact re-delivered event resolves to the recorded duplicate and the existing duplicate-with-recorded-success path re-evaluates the continuation from current state; a distinct unknown event id still fits no open allocation (no task-only fallback restored).
+- Root the status sources' descendant re-scan at the task manager's actual `root_dir` instead of a hardcoded CWD-relative `.ace-tasks` literal (review fix): `TreeRows.linked_descendants` built its `TaskScanner` from `".ace-tasks"`, disconnected from the manager that produced the tree — a tree rooted elsewhere (e.g. `--root`/configured `root_dir`) was scanned relative to the process CWD. The scanner root now travels from the manager (`TaskManager#root_dir`) through `TreeRows.flatten`, so descendants of any rooted tree resolve against their own root.
+- Restrict report matching to its actual allocation (PR393 P1): an explicit assignment that matches no step is `unmatched` — the previous task-only fallback let any `success` report complete the sole non-terminal step even when it belonged to a different assignment (e.g. a stale planner readiness report completing pending integration). Assignment-less reports (planner readiness) now bind only to the preparation role: the sole non-terminal step whose own assignment is blank; absence of an assignment is never evidence that whichever role remains finished.
+- Recover the queue continuation after a failed or interrupted dispatch (PR393 P2): the report result/ID is persisted BEFORE the continuation, so a handoff failure (or a process death between the write and the dispatch) previously left a recorded duplicate that suppressed the next role forever. A duplicate whose recorded result is success now re-checks the continuation from current task/assignment state through the same gates; duplicate starts stay impossible because the gates read real allocation state (work-on reuses an active assignment, handoff refuses a busy worktree).
+- `process-reports` handoff outcomes no longer claim the worktree "was handed to the next role" when only the window was ensured: per `queue.wf.md` section 4 the overseer agent runs the printed command, so the outcome message now carries the actionable start command (`ace-coworker start --config .ace-local/coworker/prepare/<role>.yml`, exactly what the Handoff CLI prints) instead of asserting the handoff already happened.
+- Flatten the full descendant task tree in the status sources (PR393 P2): `project_tasks` and `overseer_tree` serialized only the root rows of what `TaskManager.list` returns, hiding blocked lifecycle steps and dropping dependencies that name subtasks. Rows now cover every descendant (attached subtasks, plus deeper levels re-read through the owner's own TaskScanner/TaskLoader), and `overseer_tree` rows carry the step's recorded `processed_report`.
+- Stop labeling processed reports as permanently unprocessed in attention (PR393 P2): `StatusAttention` flagged every inbox report `unprocessed_report` without checking that `ReportProcessor` had already recorded it on a step. Processed state is now derived from the existing owner (the `processed_report` metadata carried by the `overseer_tree` source) — no second registry.
+- The `forge` status source now covers issues, not pull requests only (spec `.6.1` "PR/issues GitHub or Forgejo"): the source lists issues through the provider's own `recent_issues` API when it exposes one, and otherwise renders an explicit per-source `issues: UNAVAILABLE` marker (with the reason) instead of silently substituting PR-only data; `format_forge_rows` renders both sections distinctly.
+- Preserve the `main` location label in the new sources-table worktrees section: `context_to_h`/`context_from_h` now round-trip `location_type` (and `tmux_window`), so a main checkout with assignments renders with its dimmed `main` row and sorts last again, like the legacy dashboard.
+- Warn on unknown keys under `status_sources` instead of silently ignoring them: a typo'd source name (`herder:`) renders `-- herder: unknown source (ignored)` and a typo'd option (`enabeld: false`) renders `-- forge.enabeld: unknown option (ignored)`; both also appear as `unknown_keys` in the JSON payload next to `sources`.
+- Forward an injected `config` to the default `StatusCollector` in the `status` CLI command, so source configuration no longer falls back to the global config when a config is injected.
+- Validate the forge source `limit` config: `Integer()` parsing with a fallback to the default (typos, missing values), explicit `0` lists nothing, and negative values clamp to `0`.
+- Restore `ace-overseer prune --preservation` patch-range proofs after the attempt/journal removal: squash/cherry-pick transfers into a destination that also carries unrelated content can be proven and cleaned up again without any attempt-recorded baseline.
 
-- New `ace-overseer` gem scaffold, executable, and CLI registry.
-- `work-on` command orchestration:
-  - provision/reuse task worktree
-  - open tmux window for task context
-  - create assignment from configured preset
-- `status` command with table and JSON output for active task worktrees.
-- `prune` command with safety checks, dry-run mode, and confirmation flow.
-- Core models:
-  - `WorkContext`
-  - `PruneCandidate`
-- Core atoms:
-  - `WindowNameFormatter`
-  - `PresetResolver`
-  - `StatusFormatter`
-- Molecule layer:
-  - `WorktreeProvisioner`
-  - `TmuxWindowOpener`
-  - `AssignmentLauncher`
-  - `WorktreeContextCollector`
-  - `PruneSafetyChecker`
-- Organism layer:
-  - `WorkOnOrchestrator`
-  - `StatusCollector`
-  - `PruneOrchestrator`
-- Test coverage for atoms, models, molecules, organisms, and CLI command registration.