ace-overseer 0.21.0 → 0.22.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '082a92945b75309e414e0b5761c7839add6438503a02ca230c9843781e8f7125'
-  data.tar.gz: 8cd83b89e7720bd7706c48a091d0ca2e28452725621b6774263cb37dfd3993bf
+  metadata.gz: 3913e2fb5bdc611dec02a5cb33fca48a5395e216a09ae477e4bb452e8e4ec3ef
+  data.tar.gz: fffdbb4d1b7cd1c28ad81595ce9bb064a23e8a7c708e1c693ccad7c1d54d99a1
 SHA512:
-  metadata.gz: a29d77171476bd446104545ea467eb83dd2115d40d1036ccc1c279f14488341b8d75d5672fb683bfdc6e4aedb7c9e003c65b783315d70e68ab105b1c65b3b678
-  data.tar.gz: afd0cf96a084bc83030c2d4acbf627bbb709017838b16f54970139d1f2b167be273a6b3cae23f49fe952fc208b0ba950a0eebb7179bb0ee6814311c38f1fca5e
+  metadata.gz: 979a9f3a8f9eff1155f458fa0c54112b01c234078a93f9e4c3eddc1b1b758b3608c30694ce9054b94b27c907cce0efd3fede25c37ba12e1ce85e1810f6820373
+  data.tar.gz: 4853d86cf0df5b06f3b5ed689ccd94483ea017c006836b358b1c805a337f85cccff266e353079766ac84bf4ffacb76508bf79f91ecf421429e57d145b6ab52d9

data/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [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

data/docs/handbook.md

@@ -37,6 +37,12 @@ ace-docs:
 - Purpose: resolve and review effective delivery presets, workflows, and decision guides, then apply repeatable project-local adaptation while preserving customization
 - Output: per-asset `CREATED`, `UPDATED`, `KEPT`, or `BLOCKED` evidence plus a repeat-run zero-write check
 
+### `wfi://overseer/maintain-continuation`
+
+- Path: `handbook/workflow-instructions/overseer/maintain-continuation.wf.md`
+- Purpose: bootstrap native 600-second progress and 3600-second cleanup duties, then restore the exact persisted session without duplicate registration
+- Evidence: real model turn, persisted ace-wake entries, exact-session restart and consumed wake; Assign remains execution owner
+
 ## Related Documentation
 
 - [Getting Started](getting-started.md)

data/handbook/workflow-instructions/overseer/configure-project.wf.md

@@ -6,8 +6,8 @@ doc-type: workflow
 title: Configure Project Delivery Supervision
 purpose: Resolve and safely adapt project delivery supervision without replacing project policy or duplicating canonical work.
 ace-docs:
-  last-updated: '2026-10-11'
-  last-checked: '2026-10-11'
+  last-updated: '2026-10-12'
+  last-checked: '2026-10-12'
 ---
 
 # Configure Project Delivery Supervision
@@ -40,7 +40,7 @@ Read existing project-owned sources before proposing a change:
 - Current task, Assign, review, release, and delivery records that already own work.
 - Repository guidance such as `AGENTS.md`, architecture decisions, and delivery docs.
 
-Resolve rather than infer protocol ownership. Run `ace-nav explain <URI>` followed by
+Resolve rather than infer protocol ownership. Run `ace-nav resolve <URI> --why` followed by
 `ace-nav resolve <URI>` for every applicable `wfi://` workflow and for
 `guide://delivery-supervision`. Load resolved workflow content with `ace-bundle <URI>`.
 If the expected project decision guide uses another registered URI, record that URI
@@ -87,21 +87,26 @@ contract. Preserve stronger project requirements. Require these minimum invarian
 
 - Worker and implementation-parent terminal behavior remains PR-ready; delivery stays
   a separate explicit decision scope.
-- One canonical Assign tree and attempt/evidence ledger owns state. No second queue,
-  journal, daemon, timer, or fabricated runtime context is introduced.
+- One canonical Assign tree and attempt/evidence ledger owns state. Local objective queues contain goals, next actions, blockers and references only;
+  no duplicate execution state, journal, daemon, timer, or fabricated runtime context is introduced.
 - Integration decisions record the ordered eligible set, selected entry, every
   deferred entry with reason, actor, timestamp, evidence references, and policy/plan
   revision. Completion order is never integration order.
 - Dependency, candidate head, target head, evidence, authority, or transport movement
-  triggers a fresh decision. A moved candidate receives fresh relevant tests and an
-  independent review bound to its new exact head.
+  triggers a fresh decision. Require an initial independent review and fresh relevant
+  tests. For every moved head, record a delta/context/risk assessment: executed content
+  identity may carry review across an identical rebase; minor safe corrections need
+  integrator reasoning/tests; material or uncertain changes need independent delta
+  review. Patch-id alone cannot carry review. Bind the accepted head to the server-side
+  merge guard, and keep formal forge approval distinct from the assessment.
 - `WAIT(reference, next-check)` requires an existing durable operation reference and
   exact reconciliation path. Missing provision is `BLOCKED(provision, owner)`.
   Uncertain effects are reconciled through the original operation and never replayed
   blindly.
 - Release preparation binds the exact accepted source set, package versions, and
   artifact digests. Later merges cannot enter an accepted cut silently. Publication
-  remains a separate-authority placeholder.
+  invokes the existing project-bound workflow through its separate authorized executor;
+  absent executable binding remains BLOCKED with its owner.
 - Closure preserves evidence and work, positively proves no surviving writers, keeps
   producer references and delivery tags discoverable, and closes only accepted scope.
   Host-owned root effects remain referenced external operations.
@@ -147,11 +152,25 @@ The adaptation may select and specialize supervision behavior, but it does not g
 permissions, does not publish, and does not exercise merge, deployment, installation,
 or root authority.
 
+Executable population rule (Captain lifecycle audit, 2026-10-12): project
+adaptation must POPULATE an executable project-specific delivery template +
+decision guide -- not prose placeholders -- and ACTUAL service/capability
+checks: every configured service or command is verified to exist and run in
+the project runtime (invoke its status/read-only path and record the
+observed result; a configured-but-nonfunctional entry is `BLOCKED` with the
+observed failure, never shipped as if working). Release and publication
+REUSE the existing canonical skills as the execution mechanisms -- `as-release`,
+`as-release-bump-version`, `as-release-rubygems-publish`,
+`as-github-release-publish` -- the adaptation configures and binds them to
+the project; it never duplicates or re-implements them. Workers stay
+prepare-only (PR-ready terminal); publication remains the separately
+authorized overseer step.
+
 ### 5. Verify resolution and repeatability
 
 Repeat the complete source inventory after edits:
 
-1. Run `ace-nav explain` and `ace-nav resolve` for every selected `wfi://` and
+1. Run `ace-nav resolve --why` and `ace-nav resolve` for every selected `wfi://` and
    `guide://` URI.
 2. Load every selected workflow with `ace-bundle` and verify it came from the intended
    owner.
@@ -160,6 +179,10 @@ Repeat the complete source inventory after edits:
    writes and no duplicate paths, steps, mappings, registrations, or task references.
 5. Keep genuine unresolved policy or provisioning as `BLOCKED`; idempotence never
    turns a blocker into assumed success.
+6. For every configured service/command or bound release/publication skill,
+   execute its read-only/status path once and record the observed result as
+   executable evidence; a failed or missing executable is `BLOCKED` with the
+   exact failure and responsible owner.
 
 ## Required Report
 
@@ -195,6 +218,10 @@ installation, deployment, or root-operation gates separately from source adaptat
 - The report names every concrete change and every unresolved blocker with its owner
   and evidence; it claims no permission, publication, deployment, installation, or
   host-owned root effect.
+- The adapted delivery template and decision guide are executable (real steps,
+  bound release/publication skills, verified service/command checks) -- every
+  configured service or command has recorded observed-run evidence, and no
+  release/publication skill is duplicated or re-implemented.
 
 ## Error Handling
 

data/handbook/workflow-instructions/overseer/maintain-continuation.wf.md

@@ -0,0 +1,115 @@
+---
+name: maintain-continuation
+description: Bootstrap and resume native coordinator duties without duplicating execution.
+doc-type: workflow
+title: Maintain Coordinator Continuation
+purpose: Own progress audits and cleanup through the existing in-process wake extension.
+ace-docs:
+  last-updated: '2026-10-16'
+  last-checked: '2026-10-16'
+---
+# Maintain Coordinator Continuation
+
+## Goal
+
+Keep authorized project work advancing through native wakes and canonical Assign evidence across coordinator restarts.
+
+## Prerequisites
+
+Use the installed Pi ace-wake extension and the project's reviewed coordinator
+role. The domain launcher owns process startup and its exact session path; ACE
+owns the duty definitions below. A wake adds no execution or cleanup authority.
+The selected runtime must load the reviewed package and effective project guide.
+
+## Project Context Loading
+
+Load the current role, effective `guide://project-delivery`, reviewed objectives,
+and existing Assign, HITL and native runtime status. Resolve assets from the
+selected installed bundle; source files or remembered versions do not prove
+installation. Keep the objective queue's goal, next action, blocker and references
+separate from Assign's execution ownership.
+
+## High-Level Execution Plan
+
+- Inspect the selected session and installed extension.
+- Bootstrap duties only in a deliberately new coordinator session.
+- Resume the exact existing session and verify its persisted subscriptions.
+- Reconcile outcomes on each wake without repeating uncertain execution.
+
+## Process Steps
+
+### 1. Establish the native duties
+
+For a deliberately NEW coordinator session, supply these two complete messages
+to Pi's native command dispatcher before the role prompt. A supported launcher
+may pass each as a separate positional initial message. They are Pi commands,
+not shell commands or messages sent through the inbox/sendUserMessage API:
+
+```text
+/loop add progress-audit --interval 600 --message Run one bounded progress audit under wfi://overseer/maintain-continuation. Reconcile current project objectives with canonical Assign attempts, results and HITL decisions; continue the next authorized action using original references. Keep unknown outcomes open and do not repeat an uncertain effect.
+/loop add lifecycle-cleanup --interval 3600 --message Run one bounded cleanup audit under wfi://overseer/maintain-continuation. Reconcile owned panes and worktrees with accepted Assign results and preserved work; use the existing cleanup owner only when its preservation and no-writer gates pass. Retain active or uncertain work.
+```
+
+Run one harmless model turn to persist the session. Verify the real session file
+contains the extension's custom entries and `/loop list` reports one copy of each
+duty with intervals 600 and 3600. A started process, successful prompt send or
+in-memory definition alone is insufficient. Never synthesize session entries.
+
+### 2. Resume without re-registering
+
+Before stopping an idle coordinator, verify its current session ID and exact
+persisted session file through the native runtime. Use the launcher's supported
+exact-session resume (`--session` with that verified path in Pi). Do not use a
+latest-session selector or create a new session with the old ID.
+
+On resume, let ace-wake restore its existing session entries once. Do not replay
+`/loop add`, reconstruct definitions from these defaults, or recreate deliberately
+removed duties. Report the restored effective subscriptions, including deliberate
+removals. No missed-tick replay, second timer service or alternate scheduler.
+
+### 3. Audit progress every ten minutes
+
+Inspect each selected project's objectives, canonical attempt state, native
+liveness, pending review/integration and delivered HITL outcomes. Observe actual
+process start and accepted results separately from dispatch acknowledgment.
+Reuse the original assignment, attempt, request and mutation after a lost reply;
+query/reconcile before any retry. An uncertain attempt retains its slot.
+
+Update only the objective's next action, blocker and evidence references. Advance
+one serial integration candidate after the previous canonical result; do not
+rebase the entire queue. A blocked project must not prevent an independently
+authorized project from progressing. Report meaningful changes or required human
+action through the existing authorized project route; unchanged state stays quiet.
+
+### 4. Audit cleanup every hour
+
+Reconcile exact pane/session/assignment/attempt identities. Close an owned pane
+only after its result is accepted and work is durably preserved; close its tab
+when that was its last pane. Worktree removal separately requires the existing
+preservation and no-writer checks, including commits and valuable untracked files.
+Use the existing cleanup owner's preview and accepted operation. Do not infer
+permission from apparent idleness, a disappeared process or a closed pane.
+
+### 5. Maintain project watches
+
+When continuation depends on a known local queue or result path, register a named
+`/watch add NAME --path PATH --message TEXT` through the same native dispatcher.
+Use the exact selected project's path and reconcile actual canonical state when
+woken. Watches are hints, not execution receipts. Persist and resume them through
+the same session mechanism; do not create an external poller to replace them.
+
+## Success Criteria
+
+- The installed native session persists and restores each effective duty once.
+- A real wake is consumed by the original session and produces an attributable audit.
+- Repeated wakes and lost replies do not launch a second execution.
+- Active or uncertain work remains preserved; cleanup uses its existing owner.
+- Independent project progress and user conversation remain responsive.
+
+## Error Handling
+
+Missing extension, unresolved effective guide, unavailable canonical state or a
+mismatched session is an explicit blocker. Preserve the original references and
+session file; do not manufacture subscriptions, silently change harness/model or
+claim that a dead process will wake itself. Use the existing domain lifecycle
+owner for a controlled restart and verify the resulting native session.

data/handbook/workflow-instructions/roles/lab-coordinator.wf.md

@@ -29,6 +29,11 @@ state, applicable scoped service grants, and existing HITL proposal history.
 Use `ace-task show TASK` and the installed public status/history interfaces for
 the actual selected project. Do not treat remembered status as current evidence.
 
+For native progress and cleanup duties, follow
+`wfi://overseer/maintain-continuation`: bootstrap 600-second progress and
+3600-second cleanup loops in a new session, then resume its exact persisted
+session without re-adding definitions. Verify real wake consumption and results.
+
 ## High-Level Execution Plan
 
 - [ ] Reconcile current scope, existing executions and proposals.
@@ -75,9 +80,11 @@ the actual selected project. Do not treat remembered status as current evidence.
 
 ## Shared Decision and Responsiveness Contract
 
-Confirmed Hermes delivery starts the sixteen-hour proposal window. Only the
-existing HITL owner's healthy, drained reconciliation and resolved decision admit
-silent approval. Preserve approve/veto/clarify and revised/superseded history.
+Confirmed Hermes delivery starts the sixteen-hour proposal window only for a
+project/operation class delegated before proposal creation. The existing HITL
+owner must recheck that grant during healthy, drained reconciliation; revocation
+or a missing prior delegation prevents silent approval. Elapsed time alone never
+authorizes a decision. Preserve approve/veto/clarify and revised/superseded history.
 A stalled resolver is deferred visibly; keep status and conversation usable and
 coalesce wakes through the existing bounded tick owner. Never wait for long
 implementation or review in the conversation handler. Selecting a role adds no

data/handbook/workflow-instructions/roles/project-overseer.wf.md

@@ -5,8 +5,8 @@ doc-type: workflow
 title: Coordinate Project Work
 purpose: Canonical project-overseer role charter for scoped ACE orchestration.
 ace-docs:
-  last-updated: '2026-10-07'
-  last-checked: '2026-10-07'
+  last-updated: '2026-10-14'
+  last-checked: '2026-10-14'
 ---
 # Coordinate Project Work
 
@@ -29,6 +29,11 @@ state, applicable scoped service grants, and existing HITL proposal history.
 Use `ace-task show TASK` and the installed public status/history interfaces for
 the actual selected project. Do not treat remembered status as current evidence.
 
+For native progress and cleanup duties, follow
+`wfi://overseer/maintain-continuation`: bootstrap 600-second progress and
+3600-second cleanup loops in a new session, then resume its exact persisted
+session without re-adding definitions. Verify real wake consumption and results.
+
 ## High-Level Execution Plan
 
 - [ ] Reconcile current scope, existing executions and proposals.
@@ -50,6 +55,14 @@ the actual selected project. Do not treat remembered status as current evidence.
    effects. After a lost reply, inspect those identities without repeating the
    launch. Automatic selection advances only after attributable zero-effect
    refusal before registration; explicit mapping selection never substitutes.
+   Launch defaults (Captain, 2026-10-12): workers run Pi `zai/glm-5.3-flash:high`;
+   independent reviewers run Pi `zai/glm-5.3:high` under their own separate agent
+   identity. Codex or any other harness is NOT a default or silent fallback and
+   requires an explicit Captain exception. Selection precedence: Captain policy
+   defaults > project launch overrides > explicit Captain exception. Every
+   dispatch receipt records the ACTUAL harness, provider/model (incl. thinking
+   level) and agent/pane/session; a documented default without a matching actual
+   launch violates this policy.
 3. Keep conversation available while delegates work. On each wake, inspect the
    task queue, canonical execution evidence and scoped HITL proposal/callback
    state. Report unavailable observations and deferred resolution explicitly;
@@ -77,11 +90,77 @@ the actual selected project. Do not treat remembered status as current evidence.
    scope, missing evidence and requested decision. Preserve failed callbacks;
    unavailable delivery is not a policy refusal or successful handoff.
 
+## Integration Coordination Contract
+
+Every integration invocation — native integrate command, service call or
+assignment integration step — resolves FRESH repository, PR, candidate exact
+head, target base/head, review/test evidence, dependencies and the authorized
+executor before any mutation, and rechecks target/head immediately before the
+mutation. A detected race invalidates eligibility for that invocation.
+
+If the target (current main) is NOT an ancestor of the candidate head, the
+integration MUST NOT merge and MUST NOT silently rewrite: it returns an
+actionable typed `needs-rebase` outcome to the queue owner. The queue owner
+then delegates `wfi://git/rebase` (as-git-rebase, including CHANGELOG
+preservation) in the candidate's ISOLATED worktree, obtains new exact-head
+checks and a recorded assessment of the head change, updates the PR,
+verifies remote candidate identity and resubmits. A common old base does NOT
+make sibling heads sequentially fast-forwardable.
+
+The low-level privileged integrator ENFORCES gates and returns typed outcomes
+(`merged` / `needs-rebase` / `blocked` / `uncertain`); it never authors,
+rebases or reviews its own candidate. Relay alone is not execution — the queue
+owner monitors until receipt and continuation. An `uncertain` outcome triggers
+reconciliation against the original durable reference, never blind retry.
+
+The project overseer continuously owns and watches the integration queue.
+States `ready` / `needs-rebase` / `reviewing` / `integrating` / `merged` /
+`blocked` / `uncertain` reconcile against actual forge/process receipts; a
+persisted queue adopts on restart without duplicate execution; worker PR-ready
+remains distinct from delivery done. Use the existing goal/wake/watch
+primitives — no new heartbeat service or alternate scheduler.
+
+Integration is serial in PREPARATION as well as in effect — not merely a
+serial merge. The accepted receipt for one candidate causes preparation of
+ONLY the next selected candidate — never a mass rebase of the remaining
+queue. Each candidate, on its turn, runs the full cycle: resolve fresh
+target main; delegate `wfi://git/rebase` in that candidate's isolated
+worktree IF the target moved; run the applicable checks; retain the initial independent review and record an assessment of the new head;
+carry acceptance only with executed evidence of an identical rebase; obtain an
+independent delta review for material or uncertain changes, including security
+changes; verify the remote PR head/base; issue ONE scoped integrator
+request; wait/reconcile the actual integration receipt; refresh main; then
+select and prepare ONLY the next candidate. Queued later PRs keep their
+existing branches and heads untouched until their turn, and prior batch work
+is never rolled back or reset.
+
+Pane and worktab lifecycle is OVERSEER-OWNED cleanup duty — not user or host
+babysitting: the project overseer cleans up its own worker/reviewer panes and
+worktabs as a lifecycle duty; the Lab coordinator owns only its own
+coordination panes/routes. CLOSE-ON-ACCEPT: close an accepted work pane — and
+close the tab when that was its last pane; keep at most 4 panes per tab; and
+never hold an idle tab merely reserved for pending work. The closure gate
+binds to identity and ACTUAL state, never to visual idleness: reconcile the
+exact pane/session/assignment/attempt identity and the actual process state;
+close only after the result is ACCEPTED and the work/evidence is durably
+preserved; never close an active or uncertain attempt merely because it looks
+idle. Review-completed MAY allow pane closure while the PR still waits for
+merge — the review record persists; WORKTREE cleanup is SEPARATE and happens
+only when the preservation/delivery criteria are met. Each wake and restart
+runs a BOUNDED reconcile pass that reports orphan/stale pane/session IDs — it
+never blind-closes.
+
+Hard prohibitions: never push directly to main; never switch the canonical
+checkout to a topic branch; never reuse a stale review as approval for a
+different or moved head without the recorded assessment and required evidence.
+
 ## Shared Decision and Responsiveness Contract
 
-Confirmed Hermes delivery starts the sixteen-hour proposal window. Only the
-existing HITL owner's healthy, drained reconciliation and resolved decision admit
-silent approval. Preserve approve/veto/clarify and revised/superseded history.
+Confirmed Hermes delivery starts the sixteen-hour proposal window only for a
+project/operation class delegated before proposal creation. The existing HITL
+owner must recheck that grant during healthy, drained reconciliation; revocation
+or a missing prior delegation prevents silent approval. Elapsed time alone never
+authorizes a decision. Preserve approve/veto/clarify and revised/superseded history.
 A stalled resolver is deferred visibly; keep status and conversation usable and
 coalesce wakes through the existing bounded tick owner. Never wait for long
 implementation or review in the conversation handler. Selecting a role adds no

data/handbook/workflow-instructions/roles/second-commander.wf.md

@@ -69,9 +69,11 @@ the actual selected project. Do not treat remembered status as current evidence.
 
 ## Shared Decision and Responsiveness Contract
 
-Confirmed Hermes delivery starts the sixteen-hour proposal window. Only the
-existing HITL owner's healthy, drained reconciliation and resolved decision admit
-silent approval. Preserve approve/veto/clarify and revised/superseded history.
+Confirmed Hermes delivery starts the sixteen-hour proposal window only for a
+project/operation class delegated before proposal creation. The existing HITL
+owner must recheck that grant during healthy, drained reconciliation; revocation
+or a missing prior delegation prevents silent approval. Elapsed time alone never
+authorizes a decision. Preserve approve/veto/clarify and revised/superseded history.
 A stalled resolver is deferred visibly; keep status and conversation usable and
 coalesce wakes through the existing bounded tick owner. Never wait for long
 implementation or review in the conversation handler. Selecting a role adds no

data/lib/ace/overseer/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Overseer
-    VERSION = "0.21.0"
+    VERSION = "0.22.0"
   end
 end

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: ace-overseer
 version: !ruby/object:Gem::Version
-  version: 0.21.0
+  version: 0.22.0
 platform: ruby
 authors:
 - Michal Czyz
 bindir: exe
 cert_chain: []
-date: 2026-10-12 00:00:00.000000000 Z
+date: 2026-10-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ace-support-cli
@@ -71,14 +71,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.67'
+        version: '0.70'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.67'
+        version: '0.70'
 - !ruby/object:Gem::Dependency
   name: ace-git
   requirement: !ruby/object:Gem::Requirement
@@ -113,14 +113,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.37'
+        version: '0.40'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.37'
+        version: '0.40'
 - !ruby/object:Gem::Dependency
   name: ace-runtime
   requirement: !ruby/object:Gem::Requirement
@@ -155,42 +155,42 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.5.1
+        version: '0.6'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.5.1
+        version: '0.6'
 - !ruby/object:Gem::Dependency
   name: ace-lab
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.5.1
+        version: '0.8'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.5.1
+        version: '0.8'
 - !ruby/object:Gem::Dependency
   name: ace-review
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.60.1
+        version: 0.60.3
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.60.1
+        version: 0.60.3
 - !ruby/object:Gem::Dependency
   name: ace-support-test-helpers
   requirement: !ruby/object:Gem::Requirement
@@ -275,6 +275,7 @@ files:
 - handbook/skills/as-overseer/SKILL.md
 - handbook/workflow-instructions/overseer.wf.md
 - handbook/workflow-instructions/overseer/configure-project.wf.md
+- handbook/workflow-instructions/overseer/maintain-continuation.wf.md
 - handbook/workflow-instructions/roles/lab-coordinator.wf.md
 - handbook/workflow-instructions/roles/project-overseer.wf.md
 - handbook/workflow-instructions/roles/second-commander.wf.md