owlrunkit 0.17.1 → 0.18.0

package/CHANGELOG.md

@@ -1,5 +1,58 @@
 # Changelog
 
+## 0.18.0
+
+- Introduces the Project Driver product path for continuity across Agents and
+  sessions, with typed direct `init`, `assign`, `checkpoint`, `handoff`,
+  `decision`, `verification`, `integrate`, `status`, `takeover`, and
+  bounded `successor` actions.
+- Projects a deterministic dominant gap, next action, next actor, and headline
+  from durable project artifacts without accepting guessed percentages or
+  inventing completion.
+- Keeps legacy `--request` event input for compatibility while removing the
+  need for normal users to author request, event, receipt, or hash JSON.
+- Clarifies that ordinary multi-Agent coordination does not automatically mean
+  Formal; the assurance boundary follows the underlying risk and authority.
+- Adds a deferred-verification ledger that records stable unrun check IDs,
+  reason, owner, and due integration gate without executing tests. Due open
+  checks block only their declared gate; closure requires verification evidence
+  or an already resolved project decision that says the check is no longer
+  required.
+- Keeps coverage reuse in the existing verification-plan/receipt substrate, so
+  Project Driver status exposes the remaining gap instead of creating a second
+  test engine or repeatedly rerunning covered checks.
+- Defines the 0.18 Project Driver as a bounded surface for new projects and
+  controlled dogfood. Its product name does not claim to be a general
+  long-running, multi-phase, or enterprise control plane.
+- Adds an Owner-invoked Project Successor for one derived-completed active V1
+  project: archive the exact prior bytes under a content-addressed identity,
+  install one different empty V1 project at the same active path, and recover
+  the atomic transition from a durable journal after interruption.
+- Rejects incomplete or changed project truth, the same project identity,
+  symlinked inputs, archive collisions, and competing successor transactions.
+  Completed archives are sealed against ordinary writes; exact retry and the
+  next successor boundary validate every completed journal's archive bytes and
+  seal before active truth or a new journal can change. Status and takeover do
+  not perform that historical scan. Incomplete projects stay on their current
+  truth. The receipt grants no Git, release, publication, deployment, or
+  adoption authority. Handoff and takeover do not automatically promote an
+  authoritative writer.
+- Keeps Core successor, release compatibility, publication, Project Successor,
+  and project adoption as separate authority boundaries.
+- Preserves the published `0.17.2` Core and package as the trusted rollback
+  prior for the independent `0.18.0` candidate.
+
+## 0.17.2
+
+- Treats valid profile launcher portability warnings as non-blocking maintenance,
+  allowing an adopted project to finish onboarding.
+- Separates lifecycle, maintenance, and optional-review actions while keeping one
+  lifecycle-prioritized top-level next action.
+- Reports trusted unlinked closeouts as non-blocking independent histories rather
+  than implying damaged or ambiguous control state.
+- Collapses repeated profile launcher warnings into one machine-readable summary
+  while retaining detailed launcher diagnostics under the profile check.
+
 ## 0.17.1
 
 - Prevents a completed checkpoint with `nextAction: null` from reviving an

package/README.md

@@ -1,14 +1,26 @@
 # OwlRunKit
 
-OwlRunKit is OwlCoda's project-owned execution and evidence engine, released
-with its own version lifecycle. It makes the correct workflow the ordinary
-path: choose the assurance level, run bounded work, preserve source and
-evidence, then close out once.
+OwlRunKit is OwlCoda's Project Driver for cross-Agent project continuity and
+progression. Its execution, evidence, verification, and recovery substrate
+makes that continuity inspectable and recoverable. RunKit 0.18 keeps work
+moving across Agents and sessions through a typed direct flow while preserving
+the existing assurance, source, and evidence boundaries.
+
+The 0.18 Project Driver is a bounded surface for new projects and controlled
+dogfood. Its product name does not claim to be a general long-running,
+multi-phase, or enterprise control plane. Version 0.18 adds one bounded
+Project Successor operation: an Owner may archive the exact prior bytes of a
+derived-completed active project and install a different, empty V1 project as the sole
+active project. It is not a general migration or multi-project writer system.
+Incomplete projects stay on their current truth. Handoff and takeover do not
+automatically promote an authoritative writer. Core successor, release
+compatibility, publication, Project Successor, and project adoption remain
+separate authority boundaries.
 
 ## Install
 
 ```bash
-npm install --save-exact owlrunkit@0.17.1
+npm install --save-exact owlrunkit@0.18.0
 ```
 
 The `owlrunkit` bootstrap uses the project's exact locally bound CLI for
@@ -26,22 +38,101 @@ owlrunkit init --workspace /absolute/path/to/project
 owlrunkit doctor --workspace /absolute/path/to/project
 ```
 
-## Coordinate a multi-Agent project
+## Project Driver: Coordinate a multi-Agent project
 
-RunKit 0.17 keeps the project alive independently of any one Agent or chat.
-Define durable milestones, workstreams, WorkItems, dependencies, integration
-gates, and optional measured units, then record append-only assignment and
-checkpoint events:
+RunKit 0.18 keeps the project alive independently of any one Agent or chat.
+Initialize a definition, then use typed direct commands for the normal
+assignment, checkpoint, handoff, decision, integration, status, and takeover
+flow:
 
 ```bash
+cp node_modules/owlrunkit/scripts/runkit-contract/templates/team-project-definition.json ./project-definition.json
 owlrunkit project init --workspace . \
-  --definition scripts/runkit-contract/templates/team-project-definition.json
-owlrunkit project assign --workspace . \
-  --request scripts/runkit-contract/templates/team-project-event.json
+  --definition ./project-definition.json
+owlrunkit project assign --workspace . --assignment-id assign-1 \
+  --at 2026-08-09T00:00:00.000Z --work-item work-item-1 --agent agent-runtime
+owlrunkit project checkpoint --workspace . --checkpoint-id checkpoint-1 \
+  --at 2026-08-09T00:05:00.000Z --assignment-id assign-1 --work-item work-item-1 \
+  --state active --summary 'Implement the bounded work item' \
+  --completed-units 0 \
+  --next 'Run the focused verification'
+owlrunkit project handoff --workspace . --handoff-id handoff-1 \
+  --at 2026-08-09T00:10:00.000Z --assignment-id assign-1 --work-item work-item-1 \
+  --from-agent agent-runtime --to-agent agent-successor \
+  --summary 'Source work is ready for continuation' --next 'Run verification' \
+  --evidence evidence/source.txt
+owlrunkit project assign --workspace . --assignment-id assign-2 \
+  --at 2026-08-09T00:11:00.000Z --work-item work-item-1 \
+  --agent agent-successor --supersedes assign-1
+owlrunkit project decision --workspace . --open --decision-id decision-1 \
+  --at 2026-08-09T00:12:00.000Z --title 'Choose the accepted source path' \
+  --question 'Which source path should continue?' --owner-agent agent-successor \
+  --blocking-work-item work-item-1 --option accepted --option rejected
+owlrunkit project decision --workspace . --resolve --decision-id decision-1 \
+  --at 2026-08-09T00:13:00.000Z --resolution 'Use the accepted source path' \
+  --rationale 'It preserves the project contract' --evidence evidence/decision.txt
+owlrunkit project checkpoint --workspace . --checkpoint-id checkpoint-2 \
+  --at 2026-08-09T00:14:00.000Z --assignment-id assign-2 \
+  --work-item work-item-1 --state completed --completed-units 1 \
+  --summary 'Accepted work is complete' --evidence evidence/completion.txt
+owlrunkit project verification --workspace . --defer \
+  --verification-id release-batch --at 2026-08-09T00:14:30.000Z \
+  --work-item work-item-1 --owner-agent agent-successor \
+  --check typecheck --check full-suite --check package-smoke \
+  --reason 'Run broad checks once after the related changes settle' \
+  --due-gate integration-ready
+# After those checks run once against the frozen candidate:
+owlrunkit project verification --workspace . --close \
+  --verification-id release-batch --at 2026-08-09T00:14:45.000Z \
+  --disposition verified --summary 'The batched release checks passed' \
+  --evidence evidence/release-batch.txt
+owlrunkit project integrate --workspace . --gate integration-ready \
+  --at 2026-08-09T00:15:00.000Z --summary 'Integration gate evidence is complete' \
+  --evidence evidence/integration.txt
 owlrunkit project status --workspace .
-owlrunkit project takeover --workspace . --agent agent-runtime
+owlrunkit project takeover --workspace . --agent agent-successor
+owlrunkit project successor --workspace . --transition-id project-next-001 \
+  --at 2026-08-09T00:16:00.000Z --definition ./next-project-definition.json \
+  --reason 'Archive the completed project and begin the next bounded project'
 ```
 
+Normal users supply the one definition JSON to `init`, then use typed flags and
+values. They do not need to author request, event, receipt, or hash JSON. The
+legacy `--request <event.json>` path remains available for existing automation
+and compatibility. Multiple Agents do not make project coordination Formal by
+themselves. This flow does not make project coordination Formal by itself; the
+assurance lane follows the underlying high-risk integration,
+release, production, migration, destructive, or explicit Formal-acceptance boundary.
+
+`project verification --defer` is a small deferred-verification ledger, not a
+test scheduler. It records stable check IDs, why they were intentionally not
+run yet, the responsible Agent, and the integration gate before which they
+must close. `status` and `takeover` keep that gap visible without repeatedly
+executing anything; the due gate stays blocked while the record is open.
+Closing as `verified` requires evidence. Closing a check that is no longer
+required uses `--disposition no_longer_required` and must reference an already
+resolved project decision. RunKit never turns either disposition into Git,
+release, deployment, or business authority.
+
+The existing coverage-adoption and verification-plan surfaces remain the
+source for reusable receipts and exact pending commands in the Formal lane.
+The Project Driver records the remaining coordination gap; it does not create
+a second test engine or ask an Agent to repeat already covered checks.
+
+`project successor` is available only after the current project derives
+`overall=completed`. It keeps the active path at
+`.owlcoda/runkit/project`, moves the exact prior bytes into a
+content-addressed `project-archives` entry, and installs a new definition with
+an empty event directory. A durable transition journal makes the same request
+restartable after interruption; a competing transition, symlink, archive
+collision, changed truth, same project identity, or incomplete project fails
+closed. Archived regular files and directories are sealed against ordinary
+writes with the receipt-bound `0444`/`0555` policy before completion. Archive
+integrity and that seal are validated on an exact retry and before any later
+successor; `project status` and `project takeover` remain active-truth
+projections and do not perform a broad historical archive scan. The receipt
+always keeps Git, release, publish, deploy, and adoption authority false.
+
 `project status` reports every Agent's active, waiting, completed, and failed
 work; unresolved dependencies and decisions; the ready queue; critical work;
 and integration gates. It does not accept a guessed completion percentage.

package/docs/architecture/OWLCODA_RUNKIT_017_AGENT_NATIVE_PRODUCT_DEFINITION.md

@@ -1,6 +1,6 @@
 # OwlRunKit 0.17 Agent-Native Product Definition
 
-Status: implemented candidate pending Formal acceptance and public release.
+Status: released in `owlrunkit@0.17.2` and integrated into the private mainline.
 
 ## Product purpose
 
@@ -150,5 +150,4 @@ The release is acceptable only when all of these are mechanically demonstrated:
 9. existing 0.16 execution, migration, fleet, deployment, and release contracts
    remain compatible;
 10. the standalone npm artifact is reproducible, scrubbed, identity-bound, and
-    independently verified after publication.
-
+   independently verified after publication.

package/docs/architecture/OWLCODA_RUNKIT_018_PROJECT_DRIVER_PRODUCT_DEFINITION.md

@@ -0,0 +1,165 @@
+# OwlCoda RunKit 0.18 Project Driver Product Definition
+
+Status: public product contract for the standalone `owlrunkit@0.18.0` candidate.
+This document defines the normal project-continuity path; it does not grant Git,
+release, npm, deployment, production, migration, destructive, or business
+authority.
+
+The 0.18 Project Driver is a bounded surface for new projects and controlled
+dogfood. Its product name does not claim to be a general long-running,
+multi-phase, or enterprise control plane. Version 0.18 includes one bounded
+Project Successor lifecycle operation for a derived-completed active V1
+project. It is not a general existing-project migration, multi-project
+registry, or automatic writer-promotion system. Incomplete projects stay on
+their current truth. Handoff and takeover do not automatically promote an
+authoritative writer. Core successor, rollback compatibility, publication,
+Project Successor, and project adoption remain separate authority boundaries.
+
+## Product outcome
+
+RunKit 0.18 is the Project Driver for work that continues across Agents,
+sessions, interruptions, and handoffs. A user should be able to return to a
+blank session, run `status` or `takeover`, and receive a bounded next action,
+the responsible Agent, the dominant gap, and the evidence needed to proceed.
+The normal recovery target is a useful takeover packet within two minutes on a
+local project with an existing definition and event history.
+
+## Normal typed mainline
+
+The ordinary user-facing flow is a typed direct CLI surface:
+
+1. `project init` accepts one project definition JSON file and creates the
+   durable project model.
+2. `project assign` gives a WorkItem to an Agent.
+3. `project checkpoint` records meaningful state and evidence.
+4. `project handoff` transfers a responsibility without overwriting its
+   history.
+5. `project decision` opens or resolves a decision with rationale and evidence.
+6. `project integrate` records an integration-gate result with evidence.
+7. `project status` projects the current team state.
+8. `project takeover` builds the next bounded action for a successor Agent.
+9. After the project derives `overall=completed`, `project successor`
+   archives it and installs one fresh project under explicit Owner invocation.
+
+Except for the one definition supplied to `init`, normal users provide typed
+flags and values. They do not need to author request, event, receipt, or hash
+JSON. The legacy `--request <event.json>` path remains available for existing
+automation and compatibility, but it is not the product's primary interaction.
+
+## Project Driver projection
+
+Every status and takeover projection exposes the same deterministic recovery
+spine:
+
+- `dominantGap`: the highest-priority unresolved decision, failed WorkItem,
+  blocked dependency root, active responsibility, or integration gate;
+- `nextAction`: the next bounded action that is legal from the durable state;
+- `nextActorId`: the Agent responsible for that action when one is known;
+- `headline`: a concise human explanation of the current project state.
+
+The projection derives these fields from append-only artifacts. It never accepts
+a guessed percentage, promotes an evidence candidate into business truth,
+invents completion, or overwrites an earlier assignment, handoff, decision, or
+checkpoint.
+
+## Continuity actions
+
+A handoff preserves the outgoing assignment and records the successor action.
+A decision separates the open question from its later resolution, rationale,
+and evidence. An integration event records that the project gate was reached;
+it is not a Git merge, release, deployment, or publication operation. Status and
+takeover are read-only projections and are safe to repeat after an interruption.
+
+## Bounded Project Successor
+
+`project successor` is the only 0.18 operation that replaces the active
+Project Driver truth. It first requires the current project to derive
+`overall=completed`; a chat summary, checkpoint claim, or caller flag cannot
+substitute for that projection. The target definition must use a different
+project identity and begins with no events.
+
+The operation holds an external lifecycle lock and the active project control
+lock, records a durable transition journal, archives the exact prior bytes of
+every regular file and directory under a content-addressed raw manifest, and atomically installs
+the fresh active project at `.owlcoda/runkit/project`. Exact retries resume
+the journal after the prepared, archived, or active-installed boundaries.
+Before completion, archived regular files and directories are sealed against
+ordinary writes with a receipt-bound `0444`/`0555` policy. An exact retry
+validates that archive's bytes and seal. Before any later successor writes a
+new journal or moves active truth, it validates the archive bound by every
+completed transition journal. Status and takeover remain active-truth
+projections and do not perform this historical scan. Different concurrent
+transitions, leaf or ancestor symlinks, non-regular files, archive collisions,
+truth drift, borrowed events, and ambiguous active state fail closed.
+
+This lifecycle operation does not select a new authoritative Agent, migrate an
+incomplete project, merge project histories, discover multiple projects, adopt
+a package, or grant repository or release authority. Its receipt records all
+Git, tag, publish, and deploy actions as false.
+
+## Deferred verification without test thrash
+
+RunKit may record a `verification_deferred` project event when related changes
+should settle before a focused or broad check is run. The event contains only
+stable check identifiers, the reason for deferral, the responsible Agent, the
+related WorkItem, and the exact integration gate before which it is due. It
+does not contain an executable shell command and does not schedule or run a
+test.
+
+An open record becomes the dominant project gap only after the ordinary work
+needed by that gate is complete. The declared gate cannot pass until the record
+closes. A `verified` close requires evidence; a `no_longer_required` close
+requires a previously resolved project decision. The second disposition is
+reported honestly and is never presented as a passing test.
+
+Coverage adoption, source-bound receipts, and `verify-plan` remain responsible
+for deciding which Formal commands are already covered and which are pending.
+The Project Driver consumes that outcome as coordination truth rather than
+duplicating the verification engine. This allows an Agent team to batch a
+small, explainable group of related changes and verify it once at the correct
+transition while preserving visible, fail-closed debt.
+
+## Hidden trust substrate
+
+The typed surface is backed by the existing trust substrate: immutable project
+definition identity, append-only and idempotent events, canonical bytes,
+regular workspace and path checks, source and evidence references, and
+execution-bound lifecycle truth where a WorkItem binds an execution. Config,
+profiles, leases, fingerprints, receipts, and the `.owlcoda/runkit` directory
+remain internal control data; they are not user-supplied authorization.
+The substrate continues to fail closed on malformed, ambiguous, redirected, or
+untrusted control state. Normal project coordination retains
+`authorizationGranted=false` unless a separately authorized boundary says
+otherwise.
+
+## Assurance boundary
+
+Multiple Agents coordinating a project do not make project coordination Formal
+by themselves. This normal flow does not make project coordination Formal by
+itself; multi-Agent coordination does not automatically mean Formal.
+The assurance lane is selected by the underlying risk and authority: ordinary
+coordination may remain on the typed Project Driver path; high-risk source
+integration, release, production, migration, destructive work, or an explicit
+Formal acceptance request crosses the assurance boundary. Quick and Formal
+verification remain distinct receipts and workflows. Neither grants Git, npm,
+deployment, production, funds, or business authority.
+
+## Performance and operating burden
+
+The Project Driver is local-first and daemon-free. A project needs one
+definition and an append-only event directory; ordinary users do not maintain
+lease, receipt, fingerprint, or request JSON by hand. `status` and `takeover`
+are read-only and deterministic, and repeated calls do not create project
+events. Projection cost grows with the bounded definition and event history,
+while the two-minute takeover target keeps interruption recovery operationally
+small enough for routine Agent changes.
+
+## Authority and compatibility
+
+`owlrunkit@0.18.0` is an independent standalone candidate. The root `owlcoda`
+package keeps its separate `0.15.32` lifecycle, and the published `owlrunkit`
+`0.17.2` package remains the trusted rollback prior. Existing 0.17.x project
+artifacts remain readable through the Core successor and trusted-prior paths.
+The 0.17 Agent-Native product definition remains bundled as historical
+compatibility documentation; this 0.18 document is the current Project Driver
+contract.

package/integrations/codex/skills/owlcoda-runkit/SKILL.md

@@ -1,28 +1,35 @@
 ---
 name: owlcoda-runkit
-description: Run receipt-backed, project-owned work with OwlCoda RunKit. Use when Codex needs to coordinate a large multi-Agent project, show per-Agent progress, manage dependencies or decisions, hand work to another Agent, recover a blank-session next action, initialize or inspect `.owlcoda/runkit/`, plan bounded work with engine pins and leases, capture exact verification evidence, close an execution, produce a ready-for-commit receipt, or perform a read-only foreign-project shadow without widening Git or release authority.
+description: Run receipt-backed, project-owned work with OwlCoda RunKit. Use when Codex needs to coordinate a large multi-Agent project, show per-Agent progress, manage dependencies or decisions, record intentionally deferred verification without repeating covered tests, hand work to another Agent, recover a blank-session next action, initialize or inspect `.owlcoda/runkit/`, plan bounded work with engine pins and leases, capture exact verification evidence, close an execution, produce a ready-for-commit receipt, or perform a read-only foreign-project shadow without widening Git or release authority.
 ---
 
 # OwlCoda RunKit
 
 Use the bundled deterministic Core to coordinate work through project artifacts rather than chat memory. Require Node.js 20 or later.
 
-Bundled release: standalone `owlrunkit@0.17.1`, bundling Contract `0.2` and
-Core `0.17.1` with manifest
-`sha256:5376f3736dd17c07598df8b655a6bbceb3b64b44f3e6630e69f966e420d82e26`.
-Publication and dist-tag state are mutable registry facts: verify the exact
-official npm registry provenance before adoption. The immutable rollback
-baseline for this release is `owlrunkit@0.16.1` with SHA-1
+Bundled release: standalone `owlrunkit@0.18.0`, bundling Contract `0.2` and
+Core `0.18.0` with manifest
+`sha256:2cafa3b76a6b267888b116edfb04d9d6b455db0a7dcd289b30a265d418b7abec`.
+The published `owlrunkit@0.17.2` package is the trusted prior for rollback;
+verify exact official npm registry provenance before adoption. The immutable
+rollback baseline for the prior release is `owlrunkit@0.16.1` with SHA-1
 `1bc119d24879bdd8959af16b364af55ca9d61ea9` and canonical npm tarball URL
 `https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.16.1.tgz`.
 The root `owlcoda` package has a separate version lifecycle.
 
 The session is an execution interface. Project artifacts are the system of record.
 
-## Agent-native project actions
+## Project Driver actions
 
-Translate ordinary user requests into durable project actions. Do not ask the
-user to operate the CLI when the request and authority are already clear.
+Translate ordinary user requests into durable typed project actions. Do not ask
+the user to operate the CLI when the request and authority are already clear.
+
+The normal mainline is `init`, `assign`, `checkpoint`, `handoff`, `decision`,
+`verification`, `integrate`, `status`, and `takeover`. After a project
+derives completed, `successor` is the bounded lifecycle step. `init` accepts one project definition
+JSON; subsequent actions use direct typed flags. Normal users do not author
+request, event, receipt, or hash JSON. The legacy `--request <event.json>` form
+remains available for existing automation and compatibility.
 
 - "Split this large task and run it in parallel": initialize one project
   definition before dispatch, then assign a distinct WorkItem to each Agent.
@@ -35,10 +42,22 @@ user to operate the CLI when the request and authority are already clear.
   never overwrite the old assignment.
 - "Continue/take over": build `project takeover` for the current Agent and use
   its bounded next action and evidence refs.
+- "Start the next project": only after status derives `overall=completed`,
+  invoke `project successor` with a different V1 definition and explicit
+  transition ID. Preserve the content-addressed archive and journal; never
+  use handoff, takeover, install, or publication as successor authority.
 - "Capture this as data": append a data candidate only. Never call it a dataset
   member without a separate admission decision.
-- "Verify/finish": select No RunKit, Quick, or Formal from risk; bind a Formal
-  WorkItem to its actual execution and lease when applicable.
+- "Do not run that check yet": append one deferred verification with stable
+  check IDs, reason, owner, WorkItem, and due integration gate. This records an
+  unrun check; it does not execute or schedule one.
+- "That deferred check is done": close it as `verified` with evidence. If the
+  check is no longer required, first resolve an explicit project decision and
+  close it as `no_longer_required` with that decision ID. Never report the
+  second disposition as a passing test.
+- "Verify/finish": select No RunKit, Quick, or Formal from the underlying risk;
+  bind a Formal WorkItem to its actual execution and lease when applicable.
+  Multi-Agent coordination alone does not select Formal.
 
 For a multi-Agent project, checkpoint meaningful state changes promptly. A
 checkpoint is not a heartbeat and must not contain a guessed percentage.
@@ -47,12 +66,72 @@ state from the closeout and lease rather than trusting the Agent's claim.
 
 ```bash
 owlrunkit project init --workspace "$PROJECT_ROOT" --definition "$PROJECT_JSON"
-owlrunkit project assign --workspace "$PROJECT_ROOT" --request "$EVENT_JSON"
-owlrunkit project checkpoint --workspace "$PROJECT_ROOT" --request "$EVENT_JSON"
+owlrunkit project assign --workspace "$PROJECT_ROOT" --assignment-id "$ASSIGNMENT_ID" \
+  --at "$OCCURRED_AT" --work-item "$WORK_ITEM_ID" --agent "$AGENT_ID"
+owlrunkit project checkpoint --workspace "$PROJECT_ROOT" --checkpoint-id "$CHECKPOINT_ID" \
+  --at "$OCCURRED_AT" --assignment-id "$ASSIGNMENT_ID" --work-item "$WORK_ITEM_ID" \
+  --state active --summary "$SUMMARY" --next "$NEXT_ACTION"
+owlrunkit project handoff --workspace "$PROJECT_ROOT" --handoff-id "$HANDOFF_ID" \
+  --at "$OCCURRED_AT" --assignment-id "$ASSIGNMENT_ID" --work-item "$WORK_ITEM_ID" \
+  --from-agent "$AGENT_ID" --to-agent "$SUCCESSOR_AGENT_ID" \
+  --summary "$SUMMARY" --next "$NEXT_ACTION" --evidence "$EVIDENCE_REF"
+owlrunkit project decision --workspace "$PROJECT_ROOT" --resolve \
+  --decision-id "$DECISION_ID" --at "$OCCURRED_AT" --resolution "$RESOLUTION" \
+  --rationale "$RATIONALE" --evidence "$EVIDENCE_REF"
+owlrunkit project verification --workspace "$PROJECT_ROOT" --defer \
+  --verification-id "$VERIFICATION_ID" --at "$OCCURRED_AT" \
+  --work-item "$WORK_ITEM_ID" --owner-agent "$AGENT_ID" \
+  --check "$CHECK_ID" --reason "$REASON" --due-gate "$GATE_ID"
+owlrunkit project verification --workspace "$PROJECT_ROOT" --close \
+  --verification-id "$VERIFICATION_ID" --at "$OCCURRED_AT" \
+  --disposition verified --summary "$SUMMARY" --evidence "$EVIDENCE_REF"
+owlrunkit project integrate --workspace "$PROJECT_ROOT" --gate "$GATE_ID" \
+  --at "$OCCURRED_AT" --summary "$SUMMARY" --evidence "$EVIDENCE_REF"
 owlrunkit project status --workspace "$PROJECT_ROOT" --json
 owlrunkit project takeover --workspace "$PROJECT_ROOT" --agent "$AGENT_ID" --json
+owlrunkit project successor --workspace "$PROJECT_ROOT" \
+  --transition-id "$TRANSITION_ID" --at "$OCCURRED_AT" \
+  --definition "$NEXT_PROJECT_JSON" --reason "$SUCCESSOR_REASON" --json
 ```
 
+`project successor` accepts only a derived-completed active project and a
+different fresh V1 identity. It archives the exact prior bytes, never borrows
+old events, and resumes only an identical durable transition. Treat symlinks,
+collisions, competing transition IDs, incomplete truth, and changed truth as
+fail-closed. The archived tree is sealed against ordinary writes. Exact retry
+validates its archive bytes and seal, and each later successor validates every
+completed transition archive before changing active truth or writing its own
+journal. Do not infer a historical archive scan from `status` or `takeover`;
+those remain active-truth projections. The receipt never grants Git, release,
+publication, deployment, package-adoption, or writer authority.
+
+## Batch verification around a small explainable closure
+
+Use a verification micro-batch when two or three related changes share one
+module or contract, one writer, one worktree, one causal hypothesis, and one
+acceptance level. During implementation, run only the smallest smoke or
+falsifier needed to reject a wrong direction. After the related changes settle,
+freeze the candidate and run its focused suite once.
+
+Run typecheck, lint, build, and diff checks once at candidate closeout unless a
+later edit invalidates them. Keep broad suites, installed-package checks,
+deployment checks, production reads, and large data hashes at the actual state
+transition that needs them. Do not run them early just to make an intermediate
+packet look complete.
+
+Independent acceptance first validates candidate identity and trustworthy
+coverage, then adds fresh adversarial or boundary scenarios. It does not repeat
+the implementer's whole covered suite unless the receipt is missing, stale,
+drifted, flaky, or insufficient for the requested acceptance level.
+
+Do not defer an immediate containment, authorization, symlink/realpath,
+rollback-safety, security, money, or data-integrity falsifier. Split a batch
+when ownership, worktree, authority, hypothesis, or acceptance level differs,
+or when a failure would no longer be attributable. An open deferred
+verification remains visible in `status` and `takeover` and blocks its declared
+integration gate; it never grants permission to run the check or any later
+Git, release, deployment, or production action.
+
 ## Start safely
 
 1. Locate the project root and read its AGENTS.md chain.

package/integrations/codex/skills/owlcoda-runkit/assets/templates/config.json

@@ -2,9 +2,9 @@
   "schemaVersion": "OwlCodaRunKitConfigV2",
   "core": {
     "contractVersion": "0.2",
-    "coreVersion": "0.17.1",
-    "coreManifestSha256": "sha256:5376f3736dd17c07598df8b655a6bbceb3b64b44f3e6630e69f966e420d82e26",
-    "coreSourceRef": "artifact:sha256:5376f3736dd17c07598df8b655a6bbceb3b64b44f3e6630e69f966e420d82e26"
+    "coreVersion": "0.18.0",
+    "coreManifestSha256": "sha256:2cafa3b76a6b267888b116edfb04d9d6b455db0a7dcd289b30a265d418b7abec",
+    "coreSourceRef": "artifact:sha256:2cafa3b76a6b267888b116edfb04d9d6b455db0a7dcd289b30a265d418b7abec"
   },
   "authorizationPolicy": "external_explicit_authority_required"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "owlrunkit",
-  "version": "0.17.1",
-  "description": "Project-owned execution, evidence, verification, and recovery for coding agents.",
+  "version": "0.18.0",
+  "description": "Project Driver for cross-Agent project continuity and progression; execution, evidence, verification, and recovery are the underlying trust substrate.",
   "license": "GPL-3.0-or-later",
   "author": "yeemio <owlclaw@163.com>",
   "type": "module",

package/packages/attest/distribution-manifest-v1.json

@@ -36,6 +36,16 @@
     "sha256": "sha256:3972dc9744f6499f0f9b2dbf76696f2ae7ad8af9b23dde66d6af86c9dfb36986"
   },
   "supportedProducerCoreIdentities": [
+    {
+      "contractVersion": "0.2",
+      "coreVersion": "0.18.0",
+      "coreManifestSha256": "sha256:2cafa3b76a6b267888b116edfb04d9d6b455db0a7dcd289b30a265d418b7abec"
+    },
+    {
+      "contractVersion": "0.2",
+      "coreVersion": "0.17.2",
+      "coreManifestSha256": "sha256:67b883b8a763253b873fb6047c7e7e01c81123aa5250a0db5feaabd13cc4d860"
+    },
     {
       "contractVersion": "0.2",
       "coreVersion": "0.17.1",

package/packages/attest/src/quick.mjs

@@ -18,6 +18,16 @@ import { captureWorkspaceSnapshot } from "./workspace-snapshot.mjs";
 export { validQuickReceiptShape } from "./quick-receipt-contract.mjs";
 
 export const SUPPORTED_QUICK_CORE_IDENTITIES = Object.freeze([
+  {
+    contractVersion: "0.2",
+    coreVersion: "0.18.0",
+    coreManifestSha256: "sha256:2cafa3b76a6b267888b116edfb04d9d6b455db0a7dcd289b30a265d418b7abec",
+  },
+  {
+    contractVersion: "0.2",
+    coreVersion: "0.17.2",
+    coreManifestSha256: "sha256:67b883b8a763253b873fb6047c7e7e01c81123aa5250a0db5feaabd13cc4d860",
+  },
   {
     contractVersion: "0.2",
     coreVersion: "0.17.1",

package/registry-release-policy-v1.json

@@ -2,7 +2,7 @@
   "schemaVersion": "OwlCodaRunKitRegistryReleasePolicyV1",
   "status": "release_candidate_unpublished",
   "packageName": "owlrunkit",
-  "candidateVersion": "0.17.1",
+  "candidateVersion": "0.18.0",
   "registry": "https://registry.npmjs.org",
   "registryRequiredBeforeAdoption": true,
   "exactVersionRequired": true,
@@ -23,10 +23,10 @@
   ],
   "currentPublishedRelease": {
     "packageName": "owlrunkit",
-    "version": "0.17.0",
-    "shasum": "fa9eb5cd3ad1b168f36fdca10676a7fa8fe2f584",
-    "integrity": "sha512-ghUnQaCtxA81htdL3LqqMMaQpKnQ9kwW4ELLZ8mo3BTcbLkGJv/QhFa50JtLHdn6n/ti3sBsfQUgKvHVQZQjPA==",
-    "tarballUrl": "https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.17.0.tgz"
+    "version": "0.17.2",
+    "shasum": "73f46ec4db52d74697436900f36eafe72cb67132",
+    "integrity": "sha512-djTV1O/Clm7VCpx7boyXpJCfLfyAjuLUf+zoNLy7xyCG3LnmDiVUWtQcZFEyqWW8ts1ptd9DYyyZFdK5w1dAbA==",
+    "tarballUrl": "https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.17.2.tgz"
   },
   "registryRelease": null,
   "registryEvidenceMustBeExternal": true,

package/sbom.spdx.json

@@ -2,8 +2,8 @@
   "spdxVersion": "SPDX-2.3",
   "dataLicense": "CC0-1.0",
   "SPDXID": "SPDXRef-DOCUMENT",
-  "name": "owlrunkit-0.17.1",
-  "documentNamespace": "https://owlcoda.com/spdx/owlrunkit/0.17.1",
+  "name": "owlrunkit-0.18.0",
+  "documentNamespace": "https://owlcoda.com/spdx/owlrunkit/0.18.0",
   "creationInfo": {
     "created": "2026-07-29T00:00:00Z",
     "creators": [
@@ -14,8 +14,8 @@
     {
       "name": "owlrunkit",
       "SPDXID": "SPDXRef-Package-OwlRunKit",
-      "versionInfo": "0.17.1",
-      "downloadLocation": "https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.17.1.tgz",
+      "versionInfo": "0.18.0",
+      "downloadLocation": "https://registry.npmjs.org/owlrunkit/-/owlrunkit-0.18.0.tgz",
       "filesAnalyzed": false,
       "licenseConcluded": "GPL-3.0-or-later",
       "licenseDeclared": "GPL-3.0-or-later",
@@ -24,7 +24,7 @@
         {
           "referenceCategory": "PACKAGE-MANAGER",
           "referenceType": "purl",
-          "referenceLocator": "pkg:npm/owlrunkit@0.17.1"
+          "referenceLocator": "pkg:npm/owlrunkit@0.18.0"
         }
       ]
     }