ace-assign 0.67.0 → 0.69.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1f6ba010a4412023430bf6af940f87d2cdf806abd3ac47cfc5201df8a83518ff
-  data.tar.gz: 359c0be3f4801434b4b46c1fd12b0effa98802a5db215e79969d7b0a606ab240
+  metadata.gz: 407eb167c22a0bac683f3ac5db391b535f6200f420a38d458cc13bf36590d930
+  data.tar.gz: ef23045c1b5c2915768a21110675121dd390a896347dba0f6be90f134eb5fe12
 SHA512:
-  metadata.gz: '08989a936f88d77989af31f77d58f11602537c5ea2d6d7c1e661f965fe44378add8afe4b4ac9971994a6e6118d55051f9fa3a72d5abf21eb36852bc8e730e99d'
-  data.tar.gz: 73774791f39165b91735d1e716f2fafc1fd3982383f2513abf4e03ba2c4763172559c4e5ea60c0f2649b769a11dc181a4cdb37fed50e990627d9f0f3faeb98e8
+  metadata.gz: 217a25d646c1499d23196d0d43e1eed171914b01fa91532cf2d996f728eb1ef2b60a7126e3cc46aa8b58d0e7015c844637ee67e18c8fb3cfb36b900c81ee4342
+  data.tar.gz: 4de219ae9bdf137b84d813c599643a459961fd0337b7de987b69ac6edd8cbc4c483bd63def33a30f7bbbb075df66030843dbe71cab847f863edeb2f483ad2c26

data/CHANGELOG.md

@@ -7,6 +7,23 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.69.0] - 2026-10-16
+
+### Changed
+
+- Require ace-review 0.60.2 to keep the coordinated Forgejo 0.7 dependency graph compatible.
+
+### Added
+
+- Expose read-only `AttemptCoordinator#fixed_merge_records` so the ordinary merge receiver can reconcile its pending canonical records after restart without another journal or repeated effect.
+
+## [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

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`.