ace-overseer 0.21.0 → 0.21.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '082a92945b75309e414e0b5761c7839add6438503a02ca230c9843781e8f7125'
-  data.tar.gz: 8cd83b89e7720bd7706c48a091d0ca2e28452725621b6774263cb37dfd3993bf
+  metadata.gz: 9a94cecc6258f74a611ffb1091359b4a7e2c10709e8a185019929b1a353111ba
+  data.tar.gz: 50d41733c822af101ef77dc369f4450d5466df43e04a0894b22864328b94ba70
 SHA512:
-  metadata.gz: a29d77171476bd446104545ea467eb83dd2115d40d1036ccc1c279f14488341b8d75d5672fb683bfdc6e4aedb7c9e003c65b783315d70e68ab105b1c65b3b678
-  data.tar.gz: afd0cf96a084bc83030c2d4acbf627bbb709017838b16f54970139d1f2b167be273a6b3cae23f49fe952fc208b0ba950a0eebb7179bb0ee6814311c38f1fca5e
+  metadata.gz: d7b93b7a2444123a261351df666dbbb6ff47b16d1972c5e46230cff1418c87c0982ad7adb7309dac7a1f008348f0593042f32168bec1133557b49cc103ac880c
+  data.tar.gz: a48575ea94be30eeb49f8a0244477b47a3c304328ba2cb6ae71ee2b1a4d0b8d3413c846388a648daa3c875165c2b01d6c18e91ec725f8637cbeef85081d69f03

data/CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [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/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
@@ -147,6 +147,20 @@ 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:
@@ -160,6 +174,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 +213,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/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
 
@@ -50,6 +50,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,6 +85,70 @@ 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 an independent review of the resulting exact head, 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; obtain an
+INDEPENDENT EXPLICIT review of the resulting exact head (patch identity may
+support a short delta review but never substitutes the explicit independent
+head approval); 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.
+
 ## Shared Decision and Responsiveness Contract
 
 Confirmed Hermes delivery starts the sixteen-hour proposal window. Only the

data/lib/ace/overseer/version.rb

@@ -2,6 +2,6 @@
 
 module Ace
   module Overseer
-    VERSION = "0.21.0"
+    VERSION = "0.21.1"
   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.21.1
 platform: ruby
 authors:
 - Michal Czyz
 bindir: exe
 cert_chain: []
-date: 2026-10-12 00:00:00.000000000 Z
+date: 2026-10-14 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: ace-support-cli
@@ -169,14 +169,14 @@ 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-review
   requirement: !ruby/object:Gem::Requirement