@open-agent-toolkit/cli 0.2.4 → 0.2.5

package/assets/docs/workflows/projects/implementation-execution.md

@@ -117,14 +117,39 @@ event, and bookkeeping commit before marking receive complete. Missing,
 contradictory, or ambiguous correlation fails closed. A valid accepted run or
 completed receive is never duplicated.
 
-Freshness is bound to the reviewed HEAD and an implementation fingerprint.
+Freshness is bound to the reviewed HEAD and a versioned implementation
+fingerprint. New generations use an `effective-delta-v1` fingerprint over
+Git's canonical NUL-delimited raw tree delta. The generation persists the
+logical PR/default-branch base ref, requires one merge base, and hashes full
+base and final modes and object IDs with rename detection disabled. This makes
+same-file base changes visible while excluding commit history and human diff
+context. Every effective-delta path is included except the exact project
+`state.md` file that carries the digest and would otherwise be self-referential;
+that structured state is validated independently.
+
 Recognized closeout-only descendants preserve a valid result: gate artifacts
 and receipts, project tracking and project-log appends,
 summary/documentation/PR sequence outputs, final HiLL bookkeeping, and
-completion bookkeeping. An implementation, test, skill, template, workflow
-configuration, or unknown path change is substantive. It makes the gate result
-stale, requires a current final lifecycle review for the new basis, and starts
-a new gate generation.
+completion bookkeeping. Recognition also requires the corresponding persisted
+gate or sequence transition; a matching path category alone is insufficient.
+After each authorized closeout boundary, the workflow advances a rolling
+checkpoint to the complete effective delta at that HEAD. The checkpoint records
+the last non-checkpoint commit; a following persistence commit is ignored only
+when its diff changes that exact state carrier and nothing else.
+
+A merge, rebase, or base update preserves the result only when its full
+effective delta matches that rolling checkpoint. Conflict resolution or
+branch-owned implementation, test, skill, template, or workflow changes that
+alter the delta make the result stale, require a current final lifecycle review,
+and start a new gate generation. No implementation or closeout output path is
+excluded from the comparison. Legacy unqualified fingerprints retain the older
+fail-closed descendant-path behavior and are not migrated in place.
+
+This narrow merge-only exemption relies on fresh repository CI, automated
+review such as Bugbot, and lifecycle self-review to cover integration risk.
+Those checks do not substitute for the semantic gate on the full
+implementation; they avoid repeating that expensive review when the
+implementation outcome itself did not change.
 
 Only an allowed and fresh gate disposition can enter the pre-approval sequence,
 cross final HiLL, run the post-approval sequence, mark implementation complete,

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.2.4",
-  "docs-config": "0.2.4",
-  "docs-theme": "0.2.4",
-  "docs-transforms": "0.2.4"
+  "cli": "0.2.5",
+  "docs-config": "0.2.5",
+  "docs-theme": "0.2.5",
+  "docs-transforms": "0.2.5"
 }

package/assets/skills/oat-project-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-implement
-version: 2.1.5
+version: 2.1.6
 description: Use when plan.md is ready for execution. Dispatches one phase implementer per phase, owns independent phase review and bounded fix routing, and supports plan-declared worktree-isolated parallel phases.
 oat_gateable: true
 argument-hint: '[--retry-limit <N>] [--dry-run]'

package/assets/skills/oat-project-implement/references/completion-and-closeout.md

@@ -310,7 +310,10 @@ oat_implement_exit_gate:
   max_attempts: 2
   attempts_completed: 0
   reviewed_head: null
+  implementation_base_ref: null
   implementation_fingerprint: null
+  freshness_head: null
+  freshness_fingerprint: null
   launch_state: not_started # not_started | intent_persisted | accepted | result_persisted | not_accepted
   launch_attempt_id: null
   launch_started_at: null
@@ -343,6 +346,29 @@ pending` before any gate launch. Missing state means unresolved, never no gate.
 A `null` resolution persists `allowed/no_gate` with `disposition: no_gate`,
 null run/artifact/receive provenance, and the current implementation basis.
 
+New generations persist `implementation_fingerprint` as
+`sha256:effective-delta-v1:<digest>`. Resolve the logical integration base from
+the tracked PR's exact base ref, then the repository's configured remote default
+branch; missing or ambiguous resolution fails closed. Persist the logical base
+ref as `implementation_base_ref`; require exactly one merge base between that
+ref and each compared HEAD.
+
+Prefix the fingerprint input with the bytes `effective-delta-v1\0`. Hash the
+exact NUL-delimited byte stream from Git
+`--raw -z --no-renames --no-abbrev` output, which includes both base and final
+modes and full object IDs for blobs, symlinks, deletions, and gitlinks. Run with
+`LC_ALL=C` from the unique merge base to the compared HEAD. Git's raw `-z`
+format owns path framing and byte ordering; do not parse and reserialize it,
+abbreviate object IDs, enable rename detection, or hash human patch output.
+
+Exclude only the exact `$PROJECT_PATH/state.md` checkpoint carrier to avoid a
+self-referential digest. Use Git's literal exclusion pathspec, not a glob.
+Validate that file independently as the structured transition above. Every
+other path remains fingerprinted. Set `freshness_head` to `reviewed_head` and
+`freshness_fingerprint` to `implementation_fingerprint` when the generation
+starts. These rolling fields preserve the accepted tree outcome after later
+authorized closeout transitions without changing the immutable reviewed basis.
+
 An in-flight `pending` or `blocked` generation reuses its persisted resolved
 configuration and never re-resolves it. Recompute the fingerprint from those
 persisted inputs before resume. If the persisted resolved configuration does
@@ -476,19 +502,43 @@ disposition.
   policy, or persistence boundary.
 - A fresh `allowed` result resumes after the gate without executing the gate or
   receive a second time. Reuse requires a valid disposition, complete
-  configured-gate provenance when configured, an unchanged implementation
-  fingerprint, and any eligible receive marked complete.
+  configured-gate provenance when configured, an unchanged immutable
+  implementation fingerprint, a valid rolling freshness checkpoint, and any
+  eligible receive marked complete.
 - Closeout-only descendants include configured gate artifacts and receipts,
   project tracking, `project-log.md` appends, summary/documentation/PR sequence
   outputs, final HiLL bookkeeping, and completion bookkeeping. Classify
   gate-owned `oat project log append` mutations introduced with PR #156 as
-  closeout-only; they do not invalidate the reviewed implementation basis.
-- Determine freshness from every path changed after `reviewed_head`, and require
-  each descendant commit to contain only recognized closeout work. An unknown
-  changed path fails closed as substantive implementation change.
-  Implementation, test, skill, template, or workflow configuration changes
-  make the prior result `stale`. Preserve its provenance for audit, require a
-  current final lifecycle review for the new basis, and start a new generation.
+  closeout-only. A path category alone is insufficient: the corresponding
+  persisted gate or sequence transition must own that descendant boundary;
+  unknown or mixed work is substantive.
+- For a qualified `sha256:effective-delta-v1:<digest>` value, require the
+  persisted `implementation_base_ref`, `freshness_head`, one current merge base,
+  and 64-character lowercase hexadecimal implementation and freshness digests.
+  Missing or malformed inputs fail closed. Walk descendants after
+  `freshness_head` in commit order. Ignore a checkpoint-persistence commit only
+  after verifying its diff changes the exact state carrier and nothing else.
+  After a corroborated closeout-only transition, hash the complete current
+  effective delta and persist the rolling freshness checkpoint. Record the
+  transition's last non-checkpoint commit as `freshness_head`; the following
+  state-only persistence commit is the verified carrier exception above. For a
+  merge, rebase, or base-update boundary, recompute the complete effective delta
+  against the current merge base. A merge, rebase, or base update is not
+  substantive by itself. When it matches the rolling fingerprint, preserve the
+  allowed generation and persist an advanced rolling checkpoint without
+  rerunning gate or receive. A mismatch, unknown commit, or mixed
+  closeout/substantive boundary marks the generation `stale`.
+  Conflict resolution or branch-owned implementation, test, skill, template, or
+  workflow changes that alter the effective delta are substantive.
+- Legacy unqualified `sha256:<digest>` values keep the descendant-path policy
+  and are never reinterpreted or migrated in place. Determine freshness from
+  every path changed after `reviewed_head`, and require each descendant commit
+  to contain only recognized closeout work. An unknown changed path fails closed
+  as substantive implementation change. Implementation, test, skill, template,
+  or workflow configuration changes make the prior result `stale`.
+- Every stale transition preserves prior provenance for audit, requires a
+  current final lifecycle review for the changed basis, and starts a new
+  generation using the qualified fingerprint format.
 
 Before approval-aware sequencing, final HiLL approval, implementation
 completion, or success output, run the configured gate:
@@ -683,6 +733,14 @@ A pre-approval failure leaves `approval: pending`; a post-approval failure
 retains `approval: approved`. Fail fast with the boundary, failed step, and
 exact resume command: `oat-project-implement`.
 
+For qualified gate state, treat each committed sequence step as a corroborated
+closeout boundary. Recompute the complete effective delta, record that step
+commit as `freshness_head`, and persist `freshness_fingerprint` in a separate
+state-only checkpoint commit before dispatching the next step. Apply the same
+checkpoint protocol to gate bookkeeping, final HiLL bookkeeping, and completion
+bookkeeping. A mixed commit, missing child transition, or non-state path in the
+checkpoint-persistence commit fails closed as stale.
+
 1. Dispatch incomplete `pre_approval` steps in stored order.
 2. When they succeed and a final checkpoint exists, commit `status:
 awaiting_approval` with `approval: pending` before asking for final HiLL

package/assets/skills/oat-project-next/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-next
-version: 1.0.10
+version: 1.0.11
 description: Use when continuing work on the active OAT project. Reads project state, determines the next lifecycle action, and invokes the appropriate skill automatically.
 disable-model-invocation: true
 user-invocable: true
@@ -270,9 +270,13 @@ Before every other post-implementation route, inspect
 or not fresh, route to `oat-project-implement`.
 
 This override applies even when `oat_phase_status` is `complete` or `pr_open`,
-and before the summary, document, PR, or `oat-project-complete` routes. Announce
-exactly: "Implementation exit gate unresolved or stale — resume with
-`oat-project-implement` before post-implementation routing."
+and before the summary, document, PR, or `oat-project-complete` routes. When a
+qualified allowed result matches but its rolling checkpoint trails HEAD,
+announce exactly: "Implementation exit gate freshness checkpoint pending —
+resume with `oat-project-implement` before post-implementation routing." For all
+other unresolved or stale cases, announce exactly: "Implementation exit gate
+unresolved or stale — resume with `oat-project-implement` before
+post-implementation routing."
 
 Only an `allowed` and fresh exit-gate disposition falls through to the normal
 post-implementation checks.
@@ -282,11 +286,13 @@ alone:
 
 - `allowed/no_gate` is valid only with `disposition: no_gate`, null gate-run and
   artifact provenance, and current `reviewed_head` and implementation
-  fingerprint fields.
+  fingerprint fields. Qualified state also requires `implementation_base_ref`,
+  `freshness_head`, and `freshness_fingerprint`.
 - `allowed/configured` is valid only with `disposition: passed`, `warned`, or
   `prompt_approved`; matching `config_fingerprint`, `reviewed_head`,
-  `implementation_fingerprint`, and configured gate-run provenance; and any
-  eligible receive durably completed.
+  `implementation_fingerprint`, configured gate-run provenance, and any eligible
+  receive durably completed. Qualified state also requires the complete rolling
+  freshness fields.
 - `pending`, `blocked`, malformed, contradictory, or legacy-absent state never
   falls through. Pending and blocked generations resume their persisted
   configuration; configuration-fingerprint mismatch fails closed.
@@ -294,10 +300,24 @@ alone:
   paths and substantive changes route as stale. The recognized set is limited
   to configured gate artifacts and receipts, project tracking and
   `project-log.md` appends, summary/documentation/PR sequence outputs, final
-  HiLL bookkeeping, and completion bookkeeping.
-- Any implementation, test, skill, template, workflow configuration, or other
-  unrecognized change after `reviewed_head` invalidates the implementation
-  fingerprint and routes to `oat-project-implement`.
+  HiLL bookkeeping, and completion bookkeeping. A category match without its
+  persisted transition boundary is unknown, not closeout-only.
+- For qualified state, require `implementation_base_ref`, `freshness_head`, and
+  a valid `freshness_fingerprint`. Exactly one merge base and 64-character
+  lowercase hexadecimal implementation/freshness digests are mandatory.
+  Missing or malformed inputs route as stale. When HEAD differs from
+  `freshness_head`, use the full raw Git byte algorithm from
+  `oat-project-implement` with only its literal state-carrier exclusion. Verify
+  and ignore state-only checkpoint commits before classification. An unchanged
+  qualified fingerprint preserves freshness across a merge, rebase, or base
+  update but routes to `oat-project-implement` to persist the advanced rolling
+  checkpoint; a mismatch routes as stale. This read-only router never advances
+  state or invents another fingerprint algorithm.
+- Legacy unqualified fingerprints retain the closeout-only descendant-path
+  check. Any implementation, test, skill, template, workflow configuration, or
+  other unrecognized change after `reviewed_head` invalidates the implementation
+  fingerprint and routes to `oat-project-implement`. Do not reinterpret or
+  migrate legacy state while routing.
 
 Routing is read-only: announce stale or malformed state, but leave transition
 repair, gate execution, receive, and persistence to `oat-project-implement`.

package/assets/templates/state.md

@@ -40,7 +40,10 @@ oat_workflow_origin: native # native | imported
 #   max_attempts: 2
 #   attempts_completed: 0
 #   reviewed_head: null
-#   implementation_fingerprint: null
+#   implementation_base_ref: null # exact logical base ref for effective-delta-v1
+#   implementation_fingerprint: null # new generations use sha256:effective-delta-v1:<digest>
+#   freshness_head: null # rolling accepted tree checkpoint
+#   freshness_fingerprint: null # full effective delta at freshness_head
 #   launch_state: not_started # not_started | intent_persisted | accepted | result_persisted | not_accepted
 #   launch_attempt_id: null
 #   launch_started_at: null

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-agent-toolkit/cli",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "private": false,
   "description": "Open Agent Toolkit CLI",
   "homepage": "https://github.com/voxmedia/open-agent-toolkit/tree/main/packages/cli",
@@ -34,7 +34,7 @@
     "ora": "^9.0.0",
     "yaml": "2.8.2",
     "zod": "^3.25.76",
-    "@open-agent-toolkit/control-plane": "0.2.4"
+    "@open-agent-toolkit/control-plane": "0.2.5"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",