owlrunkit 0.18.2 → 0.18.4

package/docs/architecture/OWLCODA_RUNKIT_018_PROJECT_DRIVER_PRODUCT_DEFINITION.md

@@ -34,11 +34,13 @@ The ordinary user-facing flow is a typed direct CLI surface:
 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`
+5. `project reject-and-return` preserves a current failed checkpoint and opens
+   one evidence-linked rework assignment atomically.
+6. `project decision` opens or resolves a decision with rationale and evidence.
+7. `project integrate` records an integration-gate result with evidence.
+8. `project status` projects the current team state.
+9. `project takeover` builds the next bounded action for a successor Agent.
+10. 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
@@ -65,6 +67,11 @@ checkpoint.
 ## Continuity actions
 
 A handoff preserves the outgoing assignment and records the successor action.
+A reject-and-return event binds the current failed checkpoint, failed
+assignment, reviewer, evidence, target Agent, and new rework assignment in one
+append-only write. The failed event stays terminal and immutable; the WorkItem
+continues from a new derived active rework attempt. It cannot target completed,
+active, implicit execution-only failure, or historical failure state.
 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
@@ -132,6 +139,10 @@ untrusted control state. Normal project coordination retains
 `authorizationGranted=false` unless a separately authorized boundary says
 otherwise.
 
+The new atomic rework record uses `OwlCodaRunKitTeamProjectEventV2`; existing
+Event V1 bytes and meanings are unchanged and remain readable. This avoids
+silently adding a new event meaning to the versioned V1 contract.
+
 ## Assurance boundary
 
 Multiple Agents coordinating a project do not make project coordination Formal

package/docs/architecture/OWLCODA_RUNKIT_USAGE_MODE_SELECTION_PRODUCT_DECISION_20260811.md

@@ -1,6 +1,6 @@
 # OwlCoda RunKit 使用模式选择：Sierac MES Dogfood 产品决议
 
-状态：**0.18.1 已发布；本文主体保留发布前产品决议，文末追加 0.18.2 dogfood 补丁候选**
+状态：**0.18.3 已发布；本文主体保留既有产品决议，0.18.4 外部候选纳管决议另见同日架构文档**
 日期：2026-08-11
 
 ## 已验证现场事实
@@ -162,5 +162,56 @@ RunKit contract/package gate、Core 身份同步、pack 内容检查和安装 sm
 - profile 纯格式规范化计划显式返回 `normalizationOnly: true`；
 - package README 与五模式、profile reconcile 的已实现真值一致。
 
-当前这些内容只是本地 `owlrunkit@0.18.2` 候选。它不代表 commit、tag、npm 发布、
-全局 Skill 更新、OwlChen/OwlFootball 迁移或任何业务授权已经发生。
+上述 0.18.2 内容已经发布；准确 Git/npm 身份以 `docs/PRODUCT-TRUTH.md` 和独立发布
+回执为准。发布本身没有更新全局 Skill、迁移外部项目或授予业务权限。
+
+## 0.18.3 Sierac recovery dogfood 修复（已发布）
+
+### 新增现场事实
+
+Sierac MES 三轮 0.18.2 实测继续支持“普通小任务少用、跨窗口使用 Project Driver、
+高价值状态转换使用 Quick”的模式决议。冷启动 takeover 约 0.4 秒恢复了当前 truth，
+并正确识别陈旧 handoff；一次 W1.8 回滚与 W1.9 恢复在串行读回后留下 GO Quick
+attestation，且没有扩大到 Formal、生产、Git 或业务验收。
+
+同一轮暴露了五个可复现的 Quick 产品缺口：
+
+- 为把远端脚本精确交给 SSH，操作者只能把 base64 放进 argv；单个参数达到
+  14,469 bytes，整条 argv 约 14,539 bytes，receipt 为 79,591 bytes。
+- 顶层摘要只保留最后三行，无法同时展示前半段 W1.8 回滚与后半段 W1.9 恢复。
+- 项目现存 13/13 Quick 都携带固定 `quick_ignored_artifact_unbound`，没有可行动差异。
+- 日常 Quick 仍需第二次调用 `quick-attest`。
+- `quick-metrics --help` 返回通用 invalid-input，默认结果无条件展开全部 receipt 路径。
+
+### 本轮实现
+
+- `quick-verify --stdin-file <file>` 将最多 1 MiB 的 regular non-symlink 输入复制到
+  receipt store，以路径、大小和 SHA-256 生成 `OwlCodaQuickVerificationReceiptV2`，
+  再把已保存字节作为 exact stdin；脚本内容不进入 argv 或 receipt JSON。
+- `outputSummary` 同时返回有界 head 与 tail，完整 stdout/stderr 仍是唯一证据材料。
+- 新 Quick 不再生成固定 ignored-artifact issue；历史 receipt 仍严格可读，但 attest
+  不再把该推测性代码作为问题输出。未声明 ignored output 仍不属于 Quick 证明范围。
+- `quick-verify --attest` 在一个高层调用中返回独立 attestation 对象，不把 Quick
+  提升为 Formal。
+- `quick-metrics --local` 默认只返回聚合；`--verbose` 才返回 receipt 路径，并新增
+  action-specific help。
+- 后续真实候选复核证明 RunKit 能保存“测试全绿但版本合同错误”的 rejection、Quick
+  receipt、源码未变事实和重新责任人。`project reject-and-return` 因此作为同一
+  0.18.3 候选的原子 Project Driver 动作：只接受当前显式 failed checkpoint，保留
+  失败事件，记录 reviewer/reason/evidence，并创建新的 rework assignment。新记录使用
+  Event V2，不改写 Event V1 合同。
+- standalone npm 构建把 Contract v0.1/v0.2 的权威字节复制到 Skill 自身的
+  `references/`，使发布包内相对链接和之后的 managed Skill 安装保持一致。
+
+### 后续缺口
+
+`project takeover` stale-handoff 与外部候选 delta 已进入未发布的 0.18.4 源码候选；
+recovery evidence 的 `captured_before` / `restores_to` 语义字段仍未实现。Project Driver 自动 ID、时间戳、
+单项完成与 integrate 合并，以及路径范围指纹仍保留在既有 backlog。
+
+### 不能声称
+
+`0.18.3` 已在后续独立发布 Gate 中完成 commit、tag、npm publication 与 registry
+consumer smoke；安装、项目 adoption、共享 Skill 激活和业务结果仍是不同事实。
+`0.18.4` 的 controller/target 分离与外部 DeliveryPacket 纳管边界见
+`OWLCODA_RUNKIT_0184_EXTERNAL_DELIVERY_INTAKE_PRODUCT_DECISION_20260812.md`；该版本当前仍只是源码候选。

package/docs/architecture/OWLCODA_RUN_KIT_CONTRACT_V0_2.md

@@ -471,6 +471,13 @@ project-owned receipt store and performs no telemetry or network access. A
 Quick `GO` remains `captured_verification`; it cannot satisfy the Formal
 Contract v0.2 acceptance gate.
 
+Core `0.18.3` adds `OwlCodaQuickVerificationReceiptV2` only when the caller
+uses `quick-verify --stdin-file`. RunKit copies at most 1 MiB from a regular
+non-symlink file into the receipt store before execution, supplies those stored
+bytes as exact stdin, and binds their workspace-relative path, byte size, and
+SHA-256. V1 remains the no-stdin receipt and stays readable. Neither schema
+binds undeclared ignored outputs or grants any authority.
+
 Deterministic `repair` persists a reviewable plan before replay, reuses only
 fresh receipt-bound coverage, replays pending exact argv, and appends
 replacement lineage. Failed and orphaned attempts remain inspectable. Repair

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

@@ -1,16 +1,16 @@
 ---
 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, 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.
+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, atomically return failed work for evidence-linked rework, import an external DeliveryPacket from a frozen target worktree, 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.18.2`, bundling Contract `0.2` and
-Core `0.18.2` with manifest
-`sha256:abe17ff794b4019d8d476f09eb5d4105bae1070b1df0aab53e6c94c7ec8b65a6`.
-The published `owlrunkit@0.18.1` package is the trusted prior for rollback;
+Bundled release: standalone `owlrunkit@0.18.4`, bundling Contract `0.2` and
+Core `0.18.4` with manifest
+`sha256:372d4c247e4b40b0fd2f3fe0f5bf928548095bfb7e2e92e9ac66790e2717f77d`.
+The published `owlrunkit@0.18.3` 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
@@ -24,8 +24,11 @@ The session is an execution interface. Project artifacts are the system of recor
 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
+The normal mainline is `init`, `assign`, `checkpoint`, `handoff`,
+`reject-and-return`, `decision`, `verification`, `integrate`, `status`, and
+`takeover`. External source lanes use `target-snapshot` and `import-delivery`
+without installing RunKit or writing control artifacts into the frozen target.
+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
@@ -40,8 +43,17 @@ remains available for existing automation and compatibility.
 - "I decided ...": append a decision resolution with rationale and evidence.
 - "Hand this to another Agent": append the handoff, then a successor assignment;
   never overwrite the old assignment.
+- "Reject this failed candidate and return it": use one `project
+  reject-and-return` event. Preserve the failed checkpoint, bind the review
+  evidence, create the rework assignment, and never rewrite failure as active.
 - "Continue/take over": build `project takeover` for the current Agent and use
-  its bounded next action and evidence refs.
+  its bounded next action and evidence refs. Report stale handoffs as obsolete,
+  and use the projected current external candidate plus its predecessor delta
+  instead of reconstructing source identity from chat.
+- "Import Luna/Cursor delivery": capture the target entry before source work
+  when possible, then verify and import its exact DeliveryPacket. Without the
+  entry snapshot, report `candidate_only`; never claim an entry-to-candidate
+  overlay proof that was not captured.
 - "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
@@ -66,35 +78,53 @@ Completion requires evidence. If an assignment binds an execution, derive its
 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" --assignment-id "$ASSIGNMENT_ID" \
+npx --no-install owlrunkit project init --workspace "$PROJECT_ROOT" --definition "$PROJECT_JSON"
+npx --no-install 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" \
+npx --no-install 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" \
+npx --no-install 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 \
+npx --no-install owlrunkit project reject-and-return --workspace "$PROJECT_ROOT" \
+  --rework-id "$REWORK_ID" --at "$OCCURRED_AT" --work-item "$WORK_ITEM_ID" \
+  --reviewer-agent "$REVIEWER_AGENT_ID" --to-agent "$AGENT_ID" \
+  --reason "$REJECTION_REASON" --next "$NEXT_ACTION" --evidence "$EVIDENCE_REF"
+npx --no-install 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 \
+npx --no-install 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 \
+npx --no-install 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" \
+npx --no-install 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" \
+npx --no-install owlrunkit project status --workspace "$PROJECT_ROOT" --json
+npx --no-install owlrunkit project takeover --workspace "$PROJECT_ROOT" --agent "$AGENT_ID" --json
+npx --no-install owlrunkit project successor --workspace "$PROJECT_ROOT" \
   --transition-id "$TRANSITION_ID" --at "$OCCURRED_AT" \
   --definition "$NEXT_PROJECT_JSON" --reason "$SUCCESSOR_REASON" --json
+npx --no-install owlrunkit project target-snapshot --workspace "$PROJECT_ROOT" \
+  --snapshot-id "$ENTRY_SNAPSHOT_ID" --at "$OCCURRED_AT" \
+  --work-item "$WORK_ITEM_ID" --target-workspace "$TARGET_WORKTREE" --apply
+npx --no-install owlrunkit project import-delivery --workspace "$PROJECT_ROOT" \
+  --delivery-id "$DELIVERY_ID" --at "$OCCURRED_AT" \
+  --assignment-id "$ASSIGNMENT_ID" --work-item "$WORK_ITEM_ID" \
+  --producer "$AGENT_ID" --target-workspace "$TARGET_WORKTREE" \
+  --packet "$DELIVERY_PACKET" --entry-snapshot "$ENTRY_SNAPSHOT_ID" --apply
 ```
 
+Controller and target must be disjoint real directories, and the target must
+be its exact Git worktree root. Import rechecks packet bytes and stable target
+identity, including both sides of renames. Do not use legacy raw project event
+requests to represent an external delivery; Event V3 is admitted only through
+`project import-delivery`.
+
 `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,
@@ -141,11 +171,16 @@ Git, release, deployment, or production action.
 4. Never include `.owlcoda/runkit/**` in delivery changed files, profile rules or lease owned paths.
 5. Read [references/contract-v0.2.md](references/contract-v0.2.md) for new executions and accepted closeouts. Read [references/contract-v0.1.md](references/contract-v0.1.md) only when interpreting historical v0.1 artifacts.
 
-Use the `owlrunkit` command for normal work. Its bootstrap resolves the
+Use `npx --no-install owlrunkit` for every command after the exact project
+dependency is installed. A bare `owlrunkit` may resolve an older global binary
+that cannot trust a newer project Core, so do not use it for project status,
+verification, or Project Driver actions. The package bootstrap resolves the
 project's exact locally bound OwlRunKit CLI before interpreting project control
-state. The currently installed package handles bootstrap-only operations such
+state. A current package may still be used for bootstrap-only operations such
 as initialization, exact adoption and Core-successor migration. Do not bypass
-that resolver with a global CLI or a copied Skill Core. Project-local
+the project-local entry with a global CLI or a copied/shared Skill Core. If a
+process-level Skill declares an older release, use this installed package Skill
+and report the activation drift; do not silently apply the old rules. Project-local
 delegation requires the canonical official npm tarball URL and SHA-512 SRI,
 an installed Core identity trusted by the current bootstrap, and the same Core
 identity in project Config; any mismatch fails closed.
@@ -155,9 +190,9 @@ below has no CLI entry.
 ## Initialize and inspect
 
 ```bash
-owlrunkit init --workspace "$PROJECT_ROOT"
-owlrunkit inspect --json --workspace "$PROJECT_ROOT"
-owlrunkit status --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit init --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit inspect --json --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit status --workspace "$PROJECT_ROOT"
 ```
 
 Initialization may write only `.owlcoda/runkit/`. It must not modify business source.
@@ -196,29 +231,41 @@ repair surfaces. OwlRunKit uses its own version lifecycle: the standalone
 For one low-risk exact command, use the Core v0.13 Quick path:
 
 ```bash
-owlrunkit quick-verify \
+npx --no-install owlrunkit quick-verify \
   --workspace "$PROJECT_ROOT" -- "$ABSOLUTE_EXECUTABLE" "arg-one"
 
-owlrunkit quick-attest \
+npx --no-install owlrunkit quick-verify \
+  --workspace "$PROJECT_ROOT" --stdin-file "$SCRIPT_FILE" --attest \
+  -- ssh test-host /bin/sh
+
+npx --no-install owlrunkit quick-attest \
   --workspace "$PROJECT_ROOT" --receipt "$QUICK_RECEIPT"
 
-owlrunkit quick-metrics \
-  --workspace "$PROJECT_ROOT" --local
+npx --no-install owlrunkit quick-metrics \
+  --workspace "$PROJECT_ROOT"
+
+npx --no-install owlrunkit quick-metrics \
+  --workspace "$PROJECT_ROOT" --verbose
 ```
 
-Quick receipts are `captured_verification`, not Formal acceptance. Metrics are
-local-only and perform no telemetry or network request.
+`--stdin-file` copies and SHA-256-binds at most 1 MiB of regular non-symlink
+input before supplying the stored bytes as exact stdin. `--attest` returns the
+separate attestation object in the same high-level invocation. Quick receipts
+remain `captured_verification`, not Formal acceptance. Metrics are aggregate by
+default; `--verbose` adds receipt paths. Metrics are always local-only and
+perform no telemetry or network request; the former `--local` flag remains an
+accepted compatibility no-op.
 
 Core v0.13 also adds deterministic repair and exact-byte offline transport:
 
 ```bash
-owlrunkit repair \
+npx --no-install owlrunkit repair \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID"
 
-owlrunkit offline-export \
+npx --no-install owlrunkit offline-export \
   --workspace "$PROJECT_ROOT" --receipt "$RECEIPT" --output "$BUNDLE"
 
-owlrunkit offline-import \
+npx --no-install owlrunkit offline-import \
   --workspace "$PROJECT_ROOT" --bundle "$BUNDLE" --store "$OFFLINE_STORE"
 ```
 
@@ -253,7 +300,7 @@ loaded into the current session and grants no update authority.
 The install manifest binds every Skill, Core, contract and attest file.
 Unknown installed drift fails closed instead of being overwritten. A changed
 process-wide Skill requires a registered complete fleet. Register each coverage
-root once with `owlrunkit fleet register-root --fleet-root <absolute-root>`.
+root once with `npx --no-install owlrunkit fleet register-root --fleet-root <absolute-root>`.
 Inspect and correct a broad or stale registry through the official
 `fleet inspect-registry` and evidence-bound `fleet replace-registry` workflow;
 never hand-edit the registry. Replacement is dry-runnable and append-only
@@ -311,11 +358,11 @@ made inactive 0.13/0.14 ConfigV2 upgrades and exact rollback safe. Historical
 projects, profiles, executions, packets, receipts and closeouts remain readable.
 
 ```bash
-owlrunkit doctor --workspace "$PROJECT_ROOT"
-owlrunkit profiles detect --workspace "$PROJECT_ROOT" --dry-run
-owlrunkit profiles validate --workspace "$PROJECT_ROOT"
-owlrunkit profiles impact --workspace "$PROJECT_ROOT" --changed path/to/file
-owlrunkit adopt --workspace "$PROJECT_ROOT" --exact owlrunkit@0.15.1
+npx --no-install owlrunkit doctor --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit profiles detect --workspace "$PROJECT_ROOT" --dry-run
+npx --no-install owlrunkit profiles validate --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit profiles impact --workspace "$PROJECT_ROOT" --changed path/to/file
+npx --no-install owlrunkit adopt --workspace "$PROJECT_ROOT" --exact owlrunkit@0.15.1
 ```
 
 Exact adoption requires the official npm registry `shasum`, `integrity` and
@@ -334,15 +381,15 @@ authority.
 Core 0.16 makes the safe path the ordinary path without weakening its gates:
 
 ```bash
-owlrunkit fleet register-root --fleet-root /absolute/declared-projects
-owlrunkit fleet discover
-owlrunkit profiles detect --workspace "$PROJECT_ROOT" --dry-run
-owlrunkit profiles detect --workspace "$PROJECT_ROOT" --apply
-owlrunkit profiles reconcile --workspace "$PROJECT_ROOT" --dry-run
-owlrunkit mode recommend --workspace "$PROJECT_ROOT"
-owlrunkit assurance route --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit fleet register-root --fleet-root /absolute/declared-projects
+npx --no-install owlrunkit fleet discover
+npx --no-install owlrunkit profiles detect --workspace "$PROJECT_ROOT" --dry-run
+npx --no-install owlrunkit profiles detect --workspace "$PROJECT_ROOT" --apply
+npx --no-install owlrunkit profiles reconcile --workspace "$PROJECT_ROOT" --dry-run
+npx --no-install owlrunkit mode recommend --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit assurance route --workspace "$PROJECT_ROOT" \
   --request "$ASSURANCE_REQUEST_JSON"
-owlrunkit status --workspace "$PROJECT_ROOT"
+npx --no-install owlrunkit status --workspace "$PROJECT_ROOT"
 ```
 
 Fleet discovery is complete only within all registered coverage roots, an
@@ -353,14 +400,18 @@ adopts only unambiguous high-confidence, project-local regular-file launchers;
 `profiles reconcile` previews or atomically updates an existing profile set
 with a rollback receipt. Low-confidence candidates remain untouched. Lock-bound npm and exact
 project-installed pnpm, Yarn, and Bun launchers are supported; PATH-only
-package managers remain review-required. `assurance route`
+package managers remain review-required. A V2 dry-run reports
+`profiles_insufficient` when real Git-visible source paths remain uncovered or
+there is no actionable primary. Use its `minimalSuggestedProfile` and copyable
+`repairCommands`; do not invent absent conventional directories as blockers.
+`assurance route`
 deterministically selects No RunKit, Quick Verification or Formal Delivery
 from explicit risk facts and fails closed to Formal when required facts are
 missing.
 
 ## Choose continuity and assurance independently
 
-Start with `owlrunkit mode recommend --workspace "$PROJECT_ROOT"`. The five
+Start with `npx --no-install owlrunkit mode recommend --workspace "$PROJECT_ROOT"`. The five
 user-facing modes are presets over two independent dimensions:
 
 - continuity: `none | project_driver`
@@ -400,17 +451,17 @@ incremental checks, then finish once:
 ```bash
 NODE_BIN="$(node -p 'process.execPath')"
 
-owlrunkit formal start \
+npx --no-install owlrunkit formal start \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID" --goal "$GOAL_JSON" \
   --work-item "$WORK_ITEM_ID" \
   --owned-path "src/exact-file.ts" --owned-path "tests/feature/**"
 
-owlrunkit formal check \
+npx --no-install owlrunkit formal check \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID" \
   --from-lease "$WORK_ITEM_ID" --check-id "$CHECK_ID" \
   --cwd "." -- "$NODE_BIN" --check "src/exact-file.ts"
 
-owlrunkit formal finish \
+npx --no-install owlrunkit formal finish \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID" --decision accepted
 ```
 
@@ -427,7 +478,7 @@ Formal accepted evidence admits the built-in Node syntax check and real project
 commands executed through a Verification Envelope:
 
 ```bash
-owlrunkit formal check \
+npx --no-install owlrunkit formal check \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID" \
   --work-item "$WORK_ITEM_ID" --check-id "$CHECK_ID" \
   --envelope "$VERIFICATION_ENVELOPE_JSON"
@@ -448,12 +499,12 @@ Freeze, verify and materialize an immutable candidate without requiring a Git
 commit:
 
 ```bash
-owlrunkit candidate freeze --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit candidate freeze --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" --from-lease "$WORK_ITEM_ID" \
   --candidate-id "$CANDIDATE_ID"
-owlrunkit candidate verify --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit candidate verify --workspace "$PROJECT_ROOT" \
   --candidate "$SOURCE_CANDIDATE"
-owlrunkit candidate materialize --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit candidate materialize --workspace "$PROJECT_ROOT" \
   --candidate "$SOURCE_CANDIDATE" \
   --target-workspace "$CLEAN_WORKSPACE"
 ```
@@ -471,10 +522,10 @@ authority.
 Use a frozen SourceCandidateV2 and the registered fleet boundary:
 
 ```bash
-owlrunkit core-successor plan --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit core-successor plan --workspace "$PROJECT_ROOT" \
   --plan-id "$PLAN_ID" --run-id "$RUN_ID" \
   --from-lease "$WORK_ITEM_ID" --candidate-id "$CANDIDATE_ID"
-owlrunkit core-successor apply --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit core-successor apply --workspace "$PROJECT_ROOT" \
   --plan "$SUCCESSOR_PLAN" --owner-authority "$OWNER_AUTHORITY" \
   --receipt-id "$RECEIPT_ID"
 ```
@@ -491,11 +542,11 @@ execute. No execution result is silently inherited.
 Separate build acceptance from permission to mutate a machine:
 
 ```bash
-owlrunkit deployment prepare --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit deployment prepare --workspace "$PROJECT_ROOT" \
   --run-id "$PREPARE_RUN_ID" --artifact "$ARTIFACT" \
   --owner-decision "$OWNER_DECISION" \
   --media-type application/gzip --output "$PREPARE_RECEIPT"
-owlrunkit deployment execute --workspace "$PROJECT_ROOT" \
+npx --no-install owlrunkit deployment execute --workspace "$PROJECT_ROOT" \
   --prepare "$PREPARE_RECEIPT" \
   --owner-decision "$OWNER_DECISION" \
   --owner-authority "$OWNER_AUTHORITY" \
@@ -548,7 +599,7 @@ and protocol contract, not an out-of-the-box privileged VM deployment.
 Acquire one bounded writer lease with repeated explicit paths:
 
 ```bash
-owlrunkit lease acquire \
+npx --no-install owlrunkit lease acquire \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --work-item "$WORK_ITEM_ID" \
@@ -559,10 +610,10 @@ owlrunkit lease acquire \
 Inspect or release it through the Core instead of editing lease JSON:
 
 ```bash
-owlrunkit lease inspect \
+npx --no-install owlrunkit lease inspect \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID"
 
-owlrunkit lease release \
+npx --no-install owlrunkit lease release \
   --workspace "$PROJECT_ROOT" --run-id "$RUN_ID" \
   --work-item "$WORK_ITEM_ID"
 ```
@@ -570,7 +621,7 @@ owlrunkit lease release \
 After implementation, derive the bounded DeliveryPacket from the active lease:
 
 ```bash
-owlrunkit delivery create \
+npx --no-install owlrunkit delivery create \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --from-lease "$WORK_ITEM_ID" \
@@ -606,7 +657,7 @@ If any path is uncovered, use the declared full profile. Do not interpret an emp
 Before reusing evidence, prepare `OwlCodaRunKitCoverageAdoptRequestV1` and run:
 
 ```bash
-owlrunkit coverage-adopt \
+npx --no-install owlrunkit coverage-adopt \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$COVERAGE_ADOPT_REQUEST_JSON"
@@ -626,7 +677,7 @@ After inspecting the source execution, prepare `OwlCodaRunKitResumeRequestV1`
 and run:
 
 ```bash
-owlrunkit resume \
+npx --no-install owlrunkit resume \
   --workspace "$PROJECT_ROOT" \
   --run-id "$SOURCE_RUN_ID" \
   --request "$RESUME_REQUEST_JSON"
@@ -656,7 +707,7 @@ After freezing a DeliveryPacket, prepare
 SHA-256, then run:
 
 ```bash
-owlrunkit verify-plan \
+npx --no-install owlrunkit verify-plan \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$VERIFY_PLAN_REQUEST_JSON"
@@ -687,7 +738,7 @@ For a model workload, first bind the remaining work to a hashed
 `OwlCodaRunKitResourcePreflightRequestV1` and run:
 
 ```bash
-owlrunkit resource-preflight \
+npx --no-install owlrunkit resource-preflight \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$RESOURCE_PREFLIGHT_REQUEST_JSON"
@@ -732,7 +783,7 @@ labels are not acceptance evidence.
 Prepare `OwlCodaRunKitSnapshotRequestV1`, then run:
 
 ```bash
-owlrunkit snapshot \
+npx --no-install owlrunkit snapshot \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$SNAPSHOT_REQUEST_JSON"
@@ -754,7 +805,7 @@ and after the command.
 Prepare `OwlCodaRunKitVisualSmokeRequestV1`, then run:
 
 ```bash
-owlrunkit visual-smoke \
+npx --no-install owlrunkit visual-smoke \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$VISUAL_SMOKE_REQUEST_JSON"
@@ -774,7 +825,7 @@ After every required snapshot passed and the DeliveryPacket is still fresh,
 prepare `OwlCodaRunKitFinalizeRequestV1` and run:
 
 ```bash
-owlrunkit finalize \
+npx --no-install owlrunkit finalize \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$FINALIZE_REQUEST_JSON"
@@ -791,7 +842,7 @@ this command is available.
 Close only after consuming the current stage receipt and making an explicit controller decision:
 
 ```bash
-owlrunkit closeout \
+npx --no-install owlrunkit closeout \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --decision accepted \
@@ -812,7 +863,7 @@ After an accepted closeout, capture fresh project-root snapshots and start from
 `sourceCandidatePath` or legacy `deliveryPacketPath`, then run:
 
 ```bash
-owlrunkit ready-for-commit \
+npx --no-install owlrunkit ready-for-commit \
   --workspace "$PROJECT_ROOT" \
   --run-id "$RUN_ID" \
   --request "$READY_REQUEST_JSON"

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

@@ -2,9 +2,9 @@
   "schemaVersion": "OwlCodaRunKitConfigV2",
   "core": {
     "contractVersion": "0.2",
-    "coreVersion": "0.18.2",
-    "coreManifestSha256": "sha256:abe17ff794b4019d8d476f09eb5d4105bae1070b1df0aab53e6c94c7ec8b65a6",
-    "coreSourceRef": "artifact:sha256:abe17ff794b4019d8d476f09eb5d4105bae1070b1df0aab53e6c94c7ec8b65a6"
+    "coreVersion": "0.18.4",
+    "coreManifestSha256": "sha256:372d4c247e4b40b0fd2f3fe0f5bf928548095bfb7e2e92e9ac66790e2717f77d",
+    "coreSourceRef": "artifact:sha256:372d4c247e4b40b0fd2f3fe0f5bf928548095bfb7e2e92e9ac66790e2717f77d"
   },
   "authorizationPolicy": "external_explicit_authority_required"
 }