ace-assign 0.66.1 → 0.68.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f3a7677c3fb1ce863011485e2d0b2274f447f444292eecd60dc19a5b6df2a53a
-  data.tar.gz: 4519d9fd2fac314f8f2769e63e13a06d05b915061ef1993147ce56c352262f06
+  metadata.gz: e21e0378ad7810b04e9a92cbac849a7e7ce09b9add705c668a826dc9e3cd87f6
+  data.tar.gz: 0d56587d4589765dbc83758e882a9482a9ce4a12dc9c803aaeacc7cc0314cb57
 SHA512:
-  metadata.gz: 2b7cc2b8df1826250baa869d8ecac05474ee2cc0762737b3cf848e51f310436df47517a8370ffced04a82cd398f8b817f63b1fc9de9e081efcfd0331e7c2f339
-  data.tar.gz: 3003f3e3cf8729d99d1810aa5cb152c58dd6a50f182f8321b782a7dcd5f96e89fd9558bfe582e213b5108add78d8a213c2b4f5d0317e85a07a12e3f8d3f643d5
+  metadata.gz: 93380ddd286cd79c67fad691e875f703e60282f585746dbc3da8b04b5145310cc94ff1577416ba4164db25e90a30a1481588ae1b070ce196daea709ba8c55c25
+  data.tar.gz: e9ac0d6ef4ac39f6812e1c8f276f64dab32d15aa023830b2bf563a2211addd4353d875736506d2103a6d2b4c01efbdcf66bb205dd2e091e08e361a4146140476

data/.ace-defaults/assign/presets/close-delivery.yml

@@ -0,0 +1,57 @@
+# Close only an accepted delivery scope after preservation and writer checks.
+# Usage: ace-assign create --task TASK[,TASK...] --preset close-delivery
+
+name: close-delivery
+description: Preserve delivery evidence and work, prove quiescence, and close only accepted delivery scope
+
+parameters:
+  taskrefs:
+    required: true
+    type: array
+    description: Producer task references whose accepted delivery scope is being closed
+
+steps:
+  - name: preserve-delivery-record
+    number: "010"
+    instructions: |
+      For producer task references {{taskrefs}}, preserve accepted evidence and work
+      before any cleanup: exact source heads, decision records, tests, independent
+      review, integration/release manifests, operation references, callbacks, receipts,
+      blockers, and uncertain effects. Verify the durable destinations and retain the
+      delivery tag and producer references so archived delivery remains discoverable.
+      Do not change producer task status or reparent producer tasks.
+
+  - name: verify-no-surviving-writers
+    number: "020"
+    instructions: |
+      Execute current canonical status checks for every assignment, attempt, worker,
+      reviewer, integrator, publisher, callback handler, worktree, and other scoped
+      actor. Require positive evidence of no surviving writers. Missing, unreadable,
+      active, or uncertain lifecycle state blocks closure and cleanup; a quiet terminal
+      or completed worker is not proof.
+
+  - name: verify-accepted-scope
+    number: "030"
+    instructions: |
+      Compare the requested closure against the accepted delivery scope and project
+      decision record. Confirm every intended outcome has an attributable accepted
+      receipt and every excluded, deferred, blocked, or uncertain item remains visible.
+      Close only the accepted delivery scope; never close producer work, unrelated
+      delivery tasks, or a broader release because one path succeeded.
+
+  - name: reference-host-operations
+    number: "040"
+    instructions: |
+      Preserve references to host-owned root installation, deployment, service, and
+      cleanup operations. This preset neither performs nor claims those effects. A
+      missing root receipt remains attributable to the host owner and blocks only the
+      scope that requires it.
+
+  - name: close-accepted-delivery
+    number: "050"
+    instructions: |
+      After preservation, no-surviving-writers proof, and full accepted-scope
+      reconciliation, close and archive only this delivery record through the existing
+      task/Assign owner. Preserve the delivery tag, producer references, and evidence
+      links. Do not infer implementation-parent or producer task status changes.
+

data/.ace-defaults/assign/presets/deliver-release.yml

@@ -0,0 +1,57 @@
+# Prepare a stable release cut from an explicitly accepted producer set.
+# Usage: ace-assign create --task TASK[,TASK...] --preset deliver-release
+
+name: deliver-release
+description: Prepare and bind a stable release cut without exercising publication authority
+
+parameters:
+  taskrefs:
+    required: true
+    type: array
+    description: Producer task references contributing to the accepted release source set
+
+steps:
+  - name: bind-release-cut
+    number: "010"
+    instructions: |
+      From producer task references {{taskrefs}}, record one immutable release manifest
+      containing the exact accepted source set (repository/ref and commit SHA for every
+      member), every package name and version, every artifact digest with algorithm,
+      the decision actor and timestamp, and the policy/plan revision plus evidence
+      references that accepted the cut. Reject incomplete or ambiguous bindings.
+      Once accepted, do not add later merges or silently replace a source, version, or
+      artifact; make a new release-cut decision instead.
+
+  - name: verify-release-evidence
+    number: "020"
+    instructions: |
+      Verify tests and independent review are current for every exact source head in the
+      manifest. Reconcile target movement and provenance before preparation. A moved or
+      rebuilt source requires renewed evidence and a newly bound artifact digest.
+
+  - name: prepare-release-artifacts
+    number: "030"
+    instructions: |
+      Perform only project-authorized local release preparation. Build artifacts from
+      the bound source set, verify the declared package name and version, compute the
+      final artifact digest, and update the manifest before it is accepted. Preparation
+      is not publication, installation, deployment, or proof of any of those effects.
+
+  - name: publication-authority-placeholder
+    number: "040"
+    instructions: |
+      Publication placeholder only. Do not run a publish command in this preset. Route
+      the exact manifest to the separate publication authority named by project policy.
+      Missing credentials, publisher identity, or admission is
+      BLOCKED(provision, owner). If that authority accepts a request and returns a
+      durable operation reference plus reconciliation path, record
+      WAIT(reference, next-check); otherwise preserve uncertainty and do not retry.
+
+  - name: record-release-outcome
+    number: "050"
+    instructions: |
+      Record only attributable publication, installation, or deployment receipts from
+      their owning authorities, each bound to the exact manifest. Host-owned root
+      effects remain referenced external operations. Keep later merges outside this
+      release outcome.
+

data/.ace-defaults/assign/presets/integrate-batch.yml

@@ -0,0 +1,67 @@
+# Select and integrate an ordered batch from existing producer tasks.
+# Usage: ace-assign create --task TASK[,TASK...] --preset integrate-batch
+
+name: integrate-batch
+description: Select a dependency-valid integration batch and renew exact-head evidence after candidate movement
+
+parameters:
+  taskrefs:
+    required: true
+    type: array
+    description: Existing producer task references eligible for batch selection
+
+steps:
+  - name: select-integration-batch
+    number: "010"
+    instructions: |
+      Resolve the current project delivery guide and evaluate producer task references
+      {{taskrefs}}. Record the ordered eligible set, selected entries in intended
+      integration order, deferred entries with reasons, decision actor and timestamp,
+      policy/plan revision, and evidence references. Bind each selected entry to its
+      exact candidate head SHA and the current target branch SHA. Do not derive order
+      from completion time and do not reparent producer tasks.
+
+  - name: delegate-candidate-update
+    number: "020"
+    instructions: |
+      When the target branch moved or a selected candidate needs rebase, conflict
+      resolution, or another head-changing update, delegate that update to an
+      attributable executor. Retain the old and new exact candidate head SHA and the
+      declared delta. Do not perform integration from evidence bound to the old head.
+
+  - name: delegate-renewed-evidence
+    number: "030"
+    instructions: |
+      After any candidate movement, delegate renewed evidence for the new exact head:
+      prove replay content identity with range-diff or a stronger project-approved
+      comparison, run fresh relevant tests, and obtain an independent reviewer verdict.
+      The reviewer must be independent of the executor. Content beyond the declared
+      replay delta requires the full project review gate, not a verdict-stands shortcut.
+
+  - name: reevaluate-integration-readiness
+    number: "040"
+    instructions: |
+      Re-read dependency state, candidate and target branch heads, evidence,
+      authorization, transport, and grouping constraints immediately before requesting
+      integration. Any change voids prior eligibility and requires a new complete
+      selection decision record. Defer every candidate whose exact-head evidence is no
+      longer current.
+
+  - name: request-integration
+    number: "050"
+    instructions: |
+      Request integration only through the project's authorized integrator, preserving
+      the exact ordered candidates and target binding. This step grants no merge
+      authority. Missing provision is BLOCKED(provision, owner). After a request is
+      accepted, WAIT requires its durable operation reference and exact reconciliation
+      path. On an uncertain effect, reconcile the original operation and never repeat
+      the merge request blindly.
+
+  - name: record-integration-result
+    number: "060"
+    instructions: |
+      Record the authoritative result and resulting target head for each selected entry,
+      or the attributable blocker. Re-evaluate remaining candidates against the moved
+      target before another effect; successful integration does not select a release cut
+      or authorize publication.
+

data/.ace-defaults/assign/presets/supervise-delivery.yml

@@ -0,0 +1,67 @@
+# Delivery queue supervision over existing producer tasks.
+# Usage: ace-assign create --task TASK[,TASK...] --preset supervise-delivery
+
+name: supervise-delivery
+description: Supervise dependency-aware integration and release decisions for several PR-ready producer tasks
+
+parameters:
+  taskrefs:
+    required: true
+    type: array
+    description: Existing producer task references to observe as delivery queue entries
+
+steps:
+  - name: reconcile-delivery-queue
+    number: "010"
+    instructions: |
+      Reconcile the current canonical Assign attempts, task evidence, candidate heads,
+      dependency state, and project delivery guide for producer task references:
+      {{taskrefs}}.
+
+      These are references to producer tasks; never reparent, duplicate, reopen, or
+      change producer task status. A PR-ready worker remains terminal even while this
+      delivery assignment stays open. No second queue, journal, daemon, or cache may
+      be created. Treat an empty observation as current input only: Transiently empty
+      is not accepted completion.
+
+  - name: supervise-delivery-queue
+    number: "020"
+    instructions: |
+      Act as the one running supervisory step for producer task references {{taskrefs}}.
+      Apply the resolved project decision guide to dependency readiness, integration
+      grouping, evidence freshness, release/demo/production policy, and available
+      authority. Integration order follows dependencies and policy, never completion
+      order or worker finish timestamps.
+
+      Before every integration effect, write a canonical step report containing all
+      mandatory decision-record fields:
+      - ordered eligible set;
+      - selected next entry;
+      - deferred entries, with a reason for every skipped candidate;
+      - decision actor and timestamp;
+      - policy/plan revision and evidence references used for the decision.
+
+      For every entry, evaluate dependency state, exact candidate head SHA, fresh
+      test and independent-review evidence bound to that head, required authority and
+      transport, and grouping constraints. Re-record the decision after dependency,
+      candidate head, evidence, authority, transport, or target-branch movement.
+
+  - name: reconcile-integration-operation
+    number: "030"
+    instructions: |
+      Reconcile each requested integration through its original canonical operation.
+      Use WAIT(reference, next-check) only after an authorized request has a durable
+      operation reference and an exact public poll/reconcile path. Use
+      BLOCKED(provision, owner) when authority, transport, provisioning, or the durable
+      result path is absent. A lost or uncertain response without a durable path is
+      BLOCKED with the responsible host owner; never invent WAIT and never blindly
+      repeat launch, merge, publication, or deployment.
+
+  - name: decide-delivery-continuation
+    number: "040"
+    instructions: |
+      Record the explicit project-policy decision to integrate more candidates, cut a
+      release from the current accepted set, deploy through a separately authorized
+      project workflow, or keep this delivery open. Preserve callbacks and resume from
+      canonical state. Producer completion alone never closes this assignment.
+

data/CHANGELOG.md

@@ -7,6 +7,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.68.0] - 2026-10-14
+
+### Added
+
+- Admit ordinary fixed merge requests through the maintained `ace-lab service request/status --mode ordinary-merge` producer via the closed-argv `OrdinaryMergeCli`, with opaque-reference recovery, exact terminal receipt acceptance, and the canonical request digest defined as lowercase SHA-256 over the full eight-field immutable binding per spec ruling r4 — re-derived from the recorded binding on every poll and validated against every acknowledgment, refusal, status, and receipt echo.
+- Add fixed merge request schemas, opaque fixed-effect references, evidence-journal records, and coordinator primitives (admit/begin/settle/read-only status) so the canonical Assign attempt/evidence state remains the sole durable record: an identical resubmission replays the original acknowledgment, a reused, consumed, expired, or out-of-scope authorization raises the distinct `AuthorizationConflict`, and a restarted receiver can never begin the effect twice.
+
+## [0.67.0] - 2026-10-12
+
+### Added
+
+- Add project-adaptable delivery supervision presets for dependency-aware queue decisions, renewed-evidence integration batches, immutable release cuts, and evidence-preserving closure.
+
 ## [0.66.1] - 2026-10-10
 
 ### Fixed

data/handbook/workflow-instructions/assign/drive.wf.md

@@ -747,6 +747,45 @@ ace-assign attempt reconcile --attempt "$ATTEMPT_ID" --receipt /tmp/attempt-rece
 - Running attempts stay running only while their recorded process is verifiably live; anything else becomes `stopped` or `uncertain`.
 - Never replay `merge`, `publish`, or `deploy` automatically. Reconciliation records evidence; it never re-executes effects.
 
+#### Integration Gate and Typed Outcomes (every integration invocation)
+
+These gates apply at EVERY integration entry point — a native integrate
+command, a service invocation, or an assignment integration step — with
+shared contract validation so no entry point bypasses them.
+
+- Before any mutation, resolve FRESH repository, PR, candidate exact head,
+  target base/head, review/test evidence and the authorized executor; recheck
+  target/head immediately before the mutation. A detected race invalidates
+  eligibility for that invocation.
+- The low-level privileged integrator ENFORCES the gates and returns one typed
+  outcome: `merged`, `needs-rebase`, `blocked` or `uncertain`. It never
+  authors, rebases or reviews its own candidate. Relay alone is not
+  execution: the queue owner monitors until receipt and continuation.
+- If the target (current main) is NOT an ancestor of the candidate head, the
+  outcome is `needs-rebase`: never merge and never silently rewrite. The queue
+  owner delegates `wfi://git/rebase` (as-git-rebase, including CHANGELOG
+  preservation) in the candidate's isolated worktree, obtains refreshed
+  exact-head checks plus independent review of the NEW head, updates the PR,
+  verifies remote candidate identity and resubmits. A common old base does
+  NOT make sibling heads sequentially fast-forwardable.
+- Integration is serial in PREPARATION as well as in effect: 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: resolve fresh target main; delegate `wfi://git/rebase` in that
+  candidate's isolated worktree IF needed; 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; select and prepare ONLY the next candidate. Queued later
+  PRs keep their existing branches/heads untouched until their turn; prior
+  batch work is never rolled back or reset.
+- `uncertain` triggers reconciliation against the original durable reference;
+  it never permits blind retry.
+- 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.
+
 ### Human-in-the-Loop (HITL) Stall Protocol
 
 Canonical source of truth: `wfi://hitl`.