@deftai/directive-runtime 0.126.0-beta.3 → 0.127.0

package/vendor/directive-content/scm/github.md

@@ -178,6 +178,7 @@ On hit, repair via the fetch → UTF-8 file edit → edit path above. `verify:en
 - ~ Link to related issues using closing keywords
 - ~ Explain "why" not just "what" in the PR description
 - ! Run `task check` before opening a PR
+- ! On multi-active tips, product PRs that need merge-gate mint selection should carry a sole `deft-story: N` (positive issue number). That mark asserts #4864 delivery bind (`metadata.productPullRequest` must equal this PR before leftover finalize) and whole-story close at cohort finalize — only use it on the PR that is the delivery for #N. `verify:intent-constraint` / `verify:observable-scope` adopt the matching running `plan.id` from that mark (#5782); do not put plan-id shaped values on the mark line.
 
 ### Review Guidelines
 

package/vendor/directive-content/skills/deft-directive-feedback/SKILL.md

@@ -56,28 +56,21 @@ deft feedback:file --summary "<one-line summary>" --context "<session context>"
 ```
 
 - ! Read the printed draft title/body with the operator before proceeding
-- ! If the command reports an **open** duplicate, surface the existing issue URL and the proposed evidence-comment body. Do **not** create a new issue. Proceed to Phase 3 only when the operator wants to append evidence with `--confirm` (exit 0 `commented-open-duplicate` path) — this is not a STOP-on-`blocked-duplicate` halt
-- ! If the command reports a **closed** duplicate without disposition, STOP and re-run only after the operator chooses `--on-closed=comment` or `--on-closed=create-anyway` (no consumer reopen)
-- ! Incomplete closed-search notes (`stopReason=window-exhausted|cap`) are disclosure, not a hard stop — keep them visible when filing
-- ⊗ Proceed past an open-duplicate preview by creating a new issue
-- ⊗ Silently create when a closed title match exists without `--on-closed`
+- ! If the command reports a duplicate open issue, STOP and link the existing issue instead of filing again
+- ⊗ Proceed past a duplicate-detection block without operator override
 - ~ When go-task is installed, the Taskfile may wrap the same verb; prefer `deft feedback:file` as primary
 
-## Phase 3 -- Confirm + file / comment
+## Phase 3 -- Confirm + file
 
-- ! Present the final draft (or proposed evidence comment) and ask for explicit yes/no confirmation
-- ! Only after approval, re-run the **same report fields and target repo** with `--confirm` added and without `--dry-run` or `--json`. Retain `--notes` / blocker evidence flags so a posted comment carries the reviewed payload:
+- ! Present the final draft and ask for explicit yes/no confirmation
+- ! Only after approval, re-run the **same report fields and target repo** with `--confirm` added and without `--dry-run` or `--json`:
 
 ```bash
-deft feedback:file --summary "<one-line summary>" --context "<session context>" --expected "<expected>" --actual "<actual>" --notes "<optional>" [--blocker --flow "<flow>" --alternatives "<alts>" --recovery-cost "<cost>"] --confirm [--on-closed=comment|--on-closed=create-anyway]
+deft feedback:file --summary "<one-line summary>" --context "<session context>" --expected "<expected>" --actual "<actual>" --confirm [--blocker]
 ```
 
-- ! Open match + `--confirm` → evidence comment on the existing open issue (`commented-open-duplicate`, exit 0); print issue URL + comment URL; never `restCreateIssue`
-- ! Closed match + `--on-closed=comment` → evidence comment on the closed issue; do not reopen
-- ! Closed match + `--on-closed=create-anyway` → new issue body carries `Related: closed #<n>`
-- ! No match → file a new upstream issue; print the filed issue URL
+- ! Print the filed issue URL to the operator
 - ⊗ Use `Closes`/`Fixes`/`Resolves` in the upstream body -- use `Refs #1709` only
-- ⊗ Auto-comment without `--confirm`
 
 ## Phase 4 -- Handoff
 
@@ -87,12 +80,8 @@ deft feedback:file --summary "<one-line summary>" --context "<session context>"
 ## Anti-Patterns
 
 - ⊗ Filing from the maintainer framework repo (consumer-only guard)
-- ⊗ Creating a new issue when an open title match exists — confirm then comment instead
-- ⊗ Treating open-match confirm as `blocked-duplicate` STOP — Prefer-A Recut-2 uses `commented-open-duplicate` exit 0
-- ⊗ Writing on a closed title match without `--on-closed=comment|create-anyway`
-- ⊗ Reopening a closed issue from the consumer feedback path
-- ⊗ Treating `--confirm` as implicit from broad session approval -- require an explicit filing/comment confirmation step
+- ⊗ Skipping dedup review when the command reports an existing open issue
+- ⊗ Treating `--confirm` as implicit from broad session approval -- require an explicit filing confirmation step
 - ⊗ Infer "not a blocker" from an unmarked report -- absence of `BLOCKER` means not classified
 - ⊗ Auto-apply `adoption-blocker` from a consumer-authored title
 - ⊗ Hand-editing PROJECT-DEFINITION to flip `upstreamPrompt` instead of the audited setter
-- ⊗ Hand-editing rendered `content/skills/deft-directive-feedback/SKILL.md` — edit the pack source and `task packs:render`

package/vendor/directive-content/skills/deft-directive-release/SKILL.md

@@ -200,7 +200,7 @@ See [`docs/RELEASING.md`](../../../docs/RELEASING.md) § Routine vs hard cut for
 5. ! Verify identity: `task verify:gh-auth -- --repo <owner>/<repo> --expected-login <maintainer>`, or compare `gh api user --jq .login` to the expected login
 6. ! **Run `task reconcile:issues -- --apply-lifecycle-fixes` to clear any closed-issue / non-completed-folder xBRIEFs before invoking `task release`** (#734). The release pipeline carries the deterministic gate at Step 3 (`task reconcile:issues -- --apply-lifecycle-fixes`, refuses with `EXIT_VIOLATION` on any Section (c) mismatch), but Phase 1 is the operator's first-line defence -- running the apply-mode flag here is the canonical clean path; `--allow-vbrief-drift` on the pipeline exists only as the explicit-acknowledgment escape hatch (analogous to `--allow-dirty`). The recurrence record is the v0.21.0 cut, which surfaced 13 stranded xBRIEFs (8 cycle-relevant + 5 historical residue) post-publish; the gate now blocks that drift before any irreversible action
 7. ! **Verify the proposed `v<version>` tag is not already in use locally, on origin, or as a published GitHub release** (#784). The release pipeline carries the deterministic gate at Step 4 (`the release tag-availability gate`, refuses with `EXIT_VIOLATION` before any state mutation -- prepare/write artifacts, build, commit), but Phase 1 is the operator's first-line defence. Quickly probe with `git tag -l v<version>` (local), `git ls-remote --tags origin refs/tags/v<version>` (remote), and `gh release view v<version> --repo <owner>/<repo>` (release-only, where `gh release view` exits 0 only when the release exists). The recurrence record is the v0.22.0 → v0.23.0 release attempt on 2026-05-01: the operator typed `0.22.0` (the prior release from 12 hours earlier) and the legacy pipeline ran 8 steps before failing at `git tag` -- leaving a wrong-version local commit + `dist/deft-0.22.0.zip` orphan + manual `git reset --hard` recovery. The new pre-flight gate blocks that mode before any irreversible action
-8. ! **Verify the npm credential path is configured before cutting the tag** (#1910, #1909). A `v*` tag now auto-triggers `.github/workflows/npm-publish.yml`, which publishes the four `@deftai/directive*` packages with `npm publish --provenance`. Confirm the publish path can authenticate: either the `NPM_TOKEN` repo secret is present (`gh secret list --repo <owner>/<repo>` shows `NPM_TOKEN`) OR an npm OIDC trusted publisher is configured for the `@deftai/directive*` packages. If neither is in place, WARN loudly that the tag will fire a publish job that fails (red X on the tag, no packages) -- the operator may still proceed for a GitHub-only release, but the npm channel will not land until #1909's credential is provisioned. Cross-reference #1909.
+8. ! **Verify the npm credential path is configured before cutting the tag** (#1910, #1909). A `v*` tag now auto-triggers `.github/workflows/npm-publish.yml`, which publishes the two OVPR packages (`@deftai/directive` + `@deftai/directive-runtime`) with `npm publish --provenance`. Confirm the publish path can authenticate: either the `NPM_TOKEN` repo secret is present (`gh secret list --repo <owner>/<repo>` shows `NPM_TOKEN`) OR an npm OIDC trusted publisher is configured for the `@deftai/directive*` packages. If neither is in place, WARN loudly that the tag will fire a publish job that fails (red X on the tag, no packages) -- the operator may still proceed for a GitHub-only release, but the npm channel will not land until #1909's credential is provisioned. Cross-reference #1909.
 9. ! **Disclose npm irrevocability before any tag push (#1972, #2002, #3527).** A `v<version>` tag push is the **real npm publish gate** -- NOT Phase 5 or `task release:publish`. Tag push fires `.github/workflows/npm-publish.yml` in a separate workflow that is NOT draft-gated; npm packages ship immediately and **cannot be retracted** (`npm unpublish` is forbidden). Recovery is forward-only: deprecate, dist-tag, or ship a patch. The last human gates before npm goes live are: (a) Phase 2 dry-run `yes`, (b) a human-origin closed-verb grant (`deft authz:grant -- --template release-publish --target <version> --confirm` or `DEFT_ALLOW_RELEASE_PUBLISH=1`). `task release` fails closed at the Step 10–11 tag-push boundary without that grant. Phase 5 only controls GitHub release visibility (draft → public); it does NOT gate npm. The draft-flip `release:publish` closed-verb check remains (#1095).
 10. ~ Ask the operator for an optional one-line release **summary** (recommended 80-160 chars; can be skipped). The summary is the canonical narrative for THIS release across three audiences: (a) injected as a Markdown blockquote at the top of the promoted `CHANGELOG.md [<version>]` section, (b) auto-flowed into the GitHub release body via the existing `_section_for_version` pickup, and (c) populated VERBATIM into the Phase 8 Slack `*Summary*:` slot. Capture the wording once here; do NOT regenerate per-audience downstream
 
@@ -253,13 +253,13 @@ The harness provisions `deftai/deftai-release-test-<ts>-<uuid6>`, runs the smoke
 
 ? **Skip allowed** when the operator has just run `task release:e2e` successfully against the same branch in the past 30 minutes. Note the prior run timestamp in the user-facing summary.
 
-! **`task release:e2e` now also rehearses the npm publish (#1910).** Unless `--skip-npm` is passed (or `npm` is absent from PATH, which soft-skips), the rehearsal runs `npm publish --dry-run --access public` for all four `@deftai/directive*` packages against the throwaway clone in dependency order (types -> core -> content -> cli), after `pnpm install` + `pnpm -w run build` and a version-alignment pass. This catches a broken `files` allowlist, a version-drift bug, or a dependency-order error BEFORE the real `v*` tag fires the publish workflow -- without touching the real registry. The install+build exceeds the <90s fast budget, so pass `task release:e2e -- --skip-npm` when you only need the GitHub-pipeline shape check.
+! **`task release:e2e` now also rehearses the npm publish (#1910).** Unless `--skip-npm` is passed (or `npm` is absent from PATH, which soft-skips), the rehearsal runs `npm publish --dry-run --access public` for both `@deftai/directive` and `@deftai/directive-runtime` against the throwaway clone in dependency order (runtime -> launcher (cli)), after `pnpm install` + `pnpm -w run build` and a version-alignment pass. This catches a broken `files` allowlist, a version-drift bug, or a dependency-order error BEFORE the real `v*` tag fires the publish workflow -- without touching the real registry. The install+build exceeds the <90s fast budget, so pass `task release:e2e -- --skip-npm` when you only need the GitHub-pipeline shape check.
 
 ! **Tag -> npm coupling + irrevocability (#1910, #1972, #2002).** A `v<version>` tag is a TWO-channel action: the GitHub release (this skill's pipeline) AND `.github/workflows/npm-publish.yml`, which runs in a SEPARATE workflow that does NOT block the GitHub release and is NOT draft-gated. The npm workflow derives the published version from the tag (`${GITHUB_REF_NAME#v}`); this skill owns the version chosen in Phase 1. These MUST stay consistent -- the tag you cut IS the npm version that ships; there is no separate npm version bump. **npm publish is irrevocable** (#1972): once the tag fires, packages are live on npm and cannot be unpulled; `task release:rollback` does NOT retract npm (forward-only recovery). A red npm job on a green GitHub release means the npm channel did not ship (verify in Phase 5/7).
 
 ## Phase 4 — Production draft
 
-! **Last human gate before npm (#1972, #2002, #3527).** Immediately before invoking `task release`, re-state that the tag push in this step will irrevocably publish all four `@deftai/directive*` packages to npm via `.github/workflows/npm-publish.yml`. There is no undo on npm; only forward recovery (deprecate / dist-tag / patch). Proceed only when the operator explicitly confirms **and** a human-origin grant covers `release-publish` for this version (`deft authz:grant -- --template release-publish --target <version> --confirm` or `DEFT_ALLOW_RELEASE_PUBLISH=1`). The pipeline fails closed at Step 10–11 without that grant -- that is the npm-distributing boundary. ⊗ Rely on Phase 5 `release:publish` as the npm gate; it only flips the GitHub draft. ⊗ Delete the draft-flip check as a substitute for the tag-push gate.
+! **Last human gate before npm (#1972, #2002, #3527).** Immediately before invoking `task release`, re-state that the tag push in this step will irrevocably publish both `@deftai/directive` and `@deftai/directive-runtime` to npm via `.github/workflows/npm-publish.yml`. There is no undo on npm; only forward recovery (deprecate / dist-tag / patch). Proceed only when the operator explicitly confirms **and** a human-origin grant covers `release-publish` for this version (`deft authz:grant -- --template release-publish --target <version> --confirm` or `DEFT_ALLOW_RELEASE_PUBLISH=1`). The pipeline fails closed at Step 10–11 without that grant -- that is the npm-distributing boundary. ⊗ Rely on Phase 5 `release:publish` as the npm gate; it only flips the GitHub draft. ⊗ Delete the draft-flip check as a substitute for the tag-push gate.
 
 ! Invoke `task release -- <version>` (NO `--dry-run`, NO `--skip-tag`, NO `--skip-release`, NO `--skip-ci`). If Phase 1 collected an operator summary, pass `--summary "<text>"` so the production cut writes the same blockquote the dry-run previewed.
 
@@ -350,7 +350,7 @@ Race-condition mitigation: `download_count` is double-read with a 5s sleep betwe
 
 ! Only enter Phase 7 if Phase 6 took the Publish branch (rollback branch ends here with the unwind log).
 
-1. ! **Wait until all four packages list the cut version (#4267, #1910, #3753).** Run `task release:wait-npm -- <version>`. That caller polls `npm view <pkg> versions` (prefer-online, doctor temp-cwd isolation) until all four `@deftai/directive*` packages list `<version>`, or 10 minutes. Partial visibility is **still-propagating** (wait before `npm i -g`); none visible after the wait is **publish-incomplete**. Report-only: must not fail the GitHub release. Confirm provenance on the npm page after the wait. ⊗ Treat a green `npm-publish.yml` job plus one visible sibling as registry truth. ⊗ Run `npm i -g`. `task release` Step 13 stays a single probe (timeout 0).
+1. ! **Wait until both public packages list the cut version (#4267, #1910, #3753).** Run `task release:wait-npm -- <version>`. That caller polls `npm view <pkg> versions` (prefer-online, doctor temp-cwd isolation) until both `@deftai/directive` and `@deftai/directive-runtime` list `<version>`, or 10 minutes. Partial visibility is **still-propagating** (wait before `npm i -g`); none visible after the wait is **publish-incomplete**. Report-only: must not fail the GitHub release. Confirm provenance on the npm page after the wait. ⊗ Treat a green `npm-publish.yml` job plus one visible sibling as registry truth. ⊗ Run `npm i -g`. `task release` Step 13 stays a single probe (timeout 0).
 2. ! **Report local-vs-released CLI drift (#3753).** `task release:wait-npm` already prints the local global CLI version, the released version, whether they match, and the exact remediation `npm i -g @deftai/directive@<version> --prefer-online`. Compare versions with `checkActiveCliAgainstTarget` (not bare `deft --version`) so a PATH-shadowed install cannot report success (#3233). The report must not fail the release.
 3. ! Verify GitHub auto-closed the discrete-task issue(s) referenced via `Closes #N` in the release notes (mirrors `skills/deft-directive-swarm/SKILL.md` Phase 6 Step 2)
 4. ! Run `gh issue view <N> --json state --jq .state` for each closed issue. If any didn't auto-close, manually close with `gh issue close <N> --comment "Closed by release v<version> (squash auto-close did not trigger)"` (Layer 1, #167)

package/vendor/directive-content/skills/deft-directive-review-cycle/SKILL.md

@@ -630,9 +630,9 @@ Workflow failover arming (Blacksmith cancelled → GH-hosted lane) is sibling is
 ⊗ Emit freeform `review_cycle: started` / `pending` / `initiated` or L4 `status: pass` without **A** (or parent-retained **B** with explicit next action) or full Step 6 `done`.
 ⊗ Solve Owner Continuity via host cron-as-Approach-1 or always-block-parent-until-merge — use A/B/C above (#2876 / #3090).
 
-! **Durable live wait / unarmed stand-down (#4882 / #5219 / #5229 / #5690):** After `stop-at: pr-open`, Path B parent-retained or Approach 1 merge-path ownership is **armed** only while a still-running phase-correct wait exists for that PR (pre-CLEAN: blocking Approach 1 child `pr:watch --monitor-agent-id <id>`; post-CLEAN: `pr:wait-mergeable-and-merge`) **or** an explicit option-C finish was emitted. A fresh sticky lease alone, or a Path B prose promise to merge on CLEAN with no live wait, is **unarmed stand-down** — fail the turn per open merge-path PR. On Tier-1 `spawn_subagent` hosts, `--merge-path-arm --live-wait` also requires lease `platform_primitive=spawn_subagent` and heartbeat `parent_id` bound to that lease `monitor_agent_id` (post-CLEAN `pr-wait-mergeable` exempt); parent-shell `pr:watch` (`parent_id=pr-watch`) does **not** arm (#5219). Approach 1 is the **cheapest admitted** babysit vs host `monitor` / bare shell watch (#5229); write `writeHostCapabilityStamp` / `ensureHostCapabilityStampForBabysit` before CLI verify (register also stamps; stale/foreign-session stamps ignored) so the probe stays Tier 1 / `spawn_subagent`. `evaluateReviewMonitorGate` consults sticky lease before Approach 3 READY and on `!isTier1` READY; `DEFT_MONITOR_TIER=3` is `override-tier3` (not honest `generic-terminal`). Bounded deny is enforced at `pr:watch` entry without `--monitor-agent-id` when Tier 1 is provable; bespoke `%TEMP%` pollers remain a named residual unless routed through deft-hook. Prefer the Approach 1 babysitter one-liner (`formatApproach1CheapestAdmissionCard`) over starting a parent watch. Machine probe: `deft verify:review-monitor -- --pr <N> --merge-path-arm` with `--live-wait` and/or `--explicit-finish`. Cohort inventory (#5318 / #5690): `deft verify:cohort-review-monitors -- --prs <csv>` at PR-open, before serial rebase/merge, after Approach 1 exit/lease release, after tip-churn, after dual-stop/conf-hold/BLOCKED halt, **and after mint-PR-open / mint-PR-merge**; `swarm:verify-review-clean` CLEAN does not satisfy babysit inventory (optional `--sticky-lease`; lease-only exits 1; Tier 1 --live-wait binds to gate lease evidence for that PR). Homemade / line-parsed `pr-watch --json` wrappers and background-shell claims are **not** monitors or arms (#5015); prefer Approach 1 / native `pr:watch`. Do not invent a third poller. Keep #3984 separate (no parent-turn-shape detector). Core: `evaluateMergePathArm` / `parsePrWatchJsonStdout` in `@deftai/directive-core/pr-watch`; mint-exit bind `evaluateProductArmAtMintExit` / `COHORT_INVENTORY_REMEDIATION_TRIGGERS` in `@deftai/directive-core/swarm`.
+! **Durable live wait / unarmed stand-down (#4882 / #5219 / #5229 / #5690 / #5727):** After `stop-at: pr-open`, Path B parent-retained or Approach 1 merge-path ownership is **armed** only while a still-running phase-correct wait exists for that PR (pre-CLEAN: blocking Approach 1 child `pr:watch --monitor-agent-id <id>`; post-CLEAN: `pr:wait-mergeable-and-merge`) **or** an explicit option-C finish was emitted. A fresh sticky lease alone, or a Path B prose promise to merge on CLEAN with no live wait, is **unarmed stand-down** — fail the turn per open merge-path PR. On Tier-1 `spawn_subagent` hosts, `--merge-path-arm --live-wait` also requires lease `platform_primitive=spawn_subagent` and heartbeat `parent_id` bound to that lease `monitor_agent_id` (post-CLEAN `pr-wait-mergeable` exempt); parent-shell `pr:watch` (`parent_id=pr-watch`) does **not** arm (#5219). **Exclusive lawful waits (#5727):** when Tier-1 `spawn_subagent` is available, the only lawful pre-CLEAN wait is Approach 1 child `pr:watch --monitor-agent-id` after `review-monitor:register --platform-primitive spawn_subagent` with `verify:review-monitor --merge-path-arm --live-wait` green; after CLEAN, parent-retained `pr:wait-mergeable-and-merge`. ⊗ Parent forge-poll / `gh` check-runs+mergeable_state sleep / bespoke `%TEMP%` PowerShell watchers / host-monitor / bare Directive `pr:watch` (`BabysitPathKind`: forge-poll / bespoke-temp-poller / host-monitor / directive-pr-watch-bare). Approach 1 is also the **cheapest admitted** babysit (#5229); write `writeHostCapabilityStamp` / `ensureHostCapabilityStampForBabysit` before CLI verify (register also stamps; stale/foreign-session stamps ignored) so the probe stays Tier 1 / `spawn_subagent`. `evaluateReviewMonitorGate` consults sticky lease before Approach 3 READY and on `!isTier1` READY; `DEFT_MONITOR_TIER=3` is `override-tier3` (not honest `generic-terminal`). Bounded deny is enforced at `pr:watch` entry without `--monitor-agent-id` when Tier 1 is provable (`evaluateBoundedPrWatchDeny`); claimed-wait fail-closed is `admitClaimedBabysitPath` / `evaluateClaimedBabysitPathDeny` (#5727); undeclared-shell interception before execution is leftover #5732. Prefer the Approach 1 babysitter one-liner (`formatApproach1CheapestAdmissionCard`) over starting a parent watch. Machine probe: `deft verify:review-monitor -- --pr <N> --merge-path-arm` with `--live-wait` and/or `--explicit-finish`. Cohort inventory (#5318 / #5690): `deft verify:cohort-review-monitors -- --prs <csv>` at PR-open, before serial rebase/merge, after Approach 1 exit/lease release, after tip-churn, after dual-stop/conf-hold/BLOCKED halt, **and after mint-PR-open / mint-PR-merge**; `swarm:verify-review-clean` CLEAN does not satisfy babysit inventory (optional `--sticky-lease`; lease-only exits 1; Tier 1 --live-wait binds to gate lease evidence for that PR). Homemade / line-parsed `pr-watch --json` wrappers and background-shell claims are **not** monitors or arms (#5015); prefer Approach 1 / native `pr:watch`. Do not invent a third poller. Keep #3984 separate (no parent-turn-shape detector). Core: `evaluateMergePathArm` / `parsePrWatchJsonStdout` in `@deftai/directive-core/pr-watch`; mint-exit bind `evaluateProductArmAtMintExit` / `COHORT_INVENTORY_REMEDIATION_TRIGGERS` in `@deftai/directive-core/swarm`.
 ! **Mint-gate ≠ merge-path stand-down (#5690 Prefer-A Recut-1):** Attended mint / intent-constraint / approved-scope / scope-provenance BLOCKED on a merge-path-owned **product** PR is **non-option-C** — MUST NOT `writeMergePathExplicitFinishAttestation` / `--explicit-finish` for that product PR (including post-CLEAN closer mint-BLOCKED). Keep the existing product child `pr:watch` live across attended mint, **or** on Approach 1 exit immediately re-arm product with a successor whose **first** act is product `pr:watch --monitor-agent-id` after `review-monitor:register` (force only when prior owner is dead). A mint-PR-only waiter is **not** product arm. Split lanes: (1) product Approach 1 / closer wait continuity through the mint window including CLEAN-before-mint; (2) parallel mint-PR Approach 1 lane (one owner per PR); (3) after mint merge, dest residual rebase onto `origin/<deliveryBranch>` + `@greptileai` via existing residual/fix-batch paths, then re-enter the phase-correct product wait/closer — successor wait is not residual implement. **CLEAN-before-mint:** when product reaches CLEAN while attended mint remains pending, the post-CLEAN closer (`pr:wait-mergeable-and-merge` / parent-retained closer) is the continuing product merge-path owner — do **not** restart pre-CLEAN `pr:watch` as if that were post-CLEAN arm. If that closer returns mint-BLOCKED / timeout / error for the pending mint gate, apply the same non-option-C + same-turn re-arm rules. **Same-turn before mint attention:** on Approach 1 or closer mint-gate exit for a merge-path-owned product PR, same turn MUST `verify:review-monitor --merge-path-arm --live-wait` (and `verify:cohort-review-monitors` when N>1) and remediate `unarmed` before parent attention moves to the mint PR. Bind existing `evaluateMergePathArm` / cohort `unarmed` at that mint-exit transition — no fourth `MergePathArmReason` unless separately Bound. Successor envelope carries repository, product PR/worktree, delivery branch, named mint dependency, and authorized action scope; resolve mint merge state from the forge and re-check the gate after fetch before mutation. Attended mint creation stays human TTY. Duplicate mint-BLOCKED notifications reuse the same product owner; preserve dual-stop budgets across successor replacements.
-⊗ Stand down unarmed on an open merge-path PR, or treat lease-only / homemade line-parsed `pr-watch --json` / host monitor / bare shell watch as a live Approach 1 arm when `spawn_subagent` is available (#4882 / #5229).
+⊗ Stand down unarmed on an open merge-path PR, or treat lease-only / homemade line-parsed `pr-watch --json` / host monitor / bare shell watch / parent forge-poll as a live Approach 1 arm when `spawn_subagent` is available (#4882 / #5229 / #5727).
 ⊗ Treat mint-gate / attended-mint BLOCKED as product option-C / `--explicit-finish` / halted-explicit, or leave product unarmed while babysitting only the mint PR (#5690).
 ⊗ Restart pre-CLEAN `pr:watch` after CLEAN as the post-CLEAN arm during pending mint (#5690 CLEAN-before-mint).
 

package/vendor/directive-content/skills/deft-directive-setup/SKILL.md

@@ -13,6 +13,12 @@ description: >-
 <!-- Regenerate with: task packs:render -->
 <!-- Edit the source, not this file. Slice instead of loading every SKILL.md: task packs:slice skills by-trigger --trigger <kw> (or list) -->
 
+<!-- AUTO-GENERATED by task packs:render -- DO NOT EDIT MANUALLY -->
+<!-- Purpose: rendered skill -->
+<!-- Source of truth: packs/skills/skills-pack-0.1.json -->
+<!-- Regenerate with: task packs:render -->
+<!-- Edit the source, not this file. Slice instead of loading every SKILL.md: task packs:slice skills by-trigger --trigger <kw> (or list) -->
+
 # Deft Directive Setup
 
 Agent-driven alternative to `directive init` plus setup Phases 1-3 (`task project:render` / spec interview).
@@ -751,7 +757,7 @@ omit = [
 > 1. **Add scope to this project** [default when brownfield] — load existing identity; skip greenfield "what are we building?" only after an explicit product or slice description; emit one proposed scope; Preparatory Guard on write
 > 2. **Update project definition** — delta interview → Spec-Generating Guard → merge narratives into existing PROJECT-DEFINITION
 > 3. **Replace specification (scrap)** — only after explicit affirmative (`yes` / `confirmed`); then full new-spec path
-> 4. **Starting a new project specification** [default when identity-only or greenfield] — proceed to the Strategy Gate below and capture who/need (`ProblemStatement`)
+> 4. **Starting a new project specification** [default when identity-only or greenfield] — proceed to the Strategy Gate below and ask what to build
 > 5. **Process-only (keep Phase 2 identity)** — same exit as Phase 2 option 2; no new scope; no spec write
 > 6. **Discuss** — explore these options before choosing
 > 7. **Back** — return to the previous setup question
@@ -762,7 +768,7 @@ omit = [
 - ! If **Add scope** on identity-only: ⊗ synthesize the first scope from `narratives.Overview`, directory name, or init-seed identity. Capture a product or slice description, or do not emit a proposed xBRIEF. Swarm Phase 0 Step 0.5 `xbrief/proposed/` scan is in scope for that skip.
 - ! If **Update project definition**: run a delta interview; apply Spec-Generating Guard against `./xbrief/PROJECT-DEFINITION.xbrief.json` (or legacy `./vbrief/PROJECT-DEFINITION.vbrief.json` if that is the existing identity); merge narratives (do not wholesale replace unless the user confirmed scrap)
 - ! If **Replace specification (scrap)**: require explicit `yes`/`confirmed`, then proceed to the Strategy Gate as a greenfield-style full path
-- ! If **Starting new**: proceed to the Strategy Gate below. ~ Capture who/need (`ProblemStatement`) before writing a scope as a SHOULD (#5692); recorded skip/decline is enough. On identity-only, this invocation MAY skip the interview Chaining Gate (see [strategies/interview.md](../../strategies/interview.md#chaining-gate) Starting-new skip) because the identity-only default is already Proceed.
+- ! If **Starting new**: proceed to the Strategy Gate below. Ask what to build before writing a scope. On identity-only, this invocation MAY skip the interview Chaining Gate (see [strategies/interview.md](../../strategies/interview.md#chaining-gate) Starting-new skip) because the identity-only default is already Proceed.
 - ! **Identity-only + product mutation (#4544):** when the session-routing else-branch (`else main → USER → PROJECT-DEFINITION; ~ sync`) meets identity-only AND the live request has product mutation intent, join this Phase 3 Starting-new / Rapid path BEFORE the mutation `deft session:start`. Process-only stays an explicit exit. ⊗ Add `session:start --prompt`.
 - ! If **Process-only (keep Phase 2 identity)**: same exit as Phase 2 option 2. Do not write a scope xBRIEF. Do not merge or scrap PROJECT-DEFINITION narratives. Skip Lifecycle Bridge, End-of-Phase-3 Export Prompt, Acceptance Gate, and build handoff. Point at session ritual / `deft check` / later Add scope. GitHub issues stay cache/queue inputs. Docs stay described content.
 - ⊗ Treat brownfield repos as "Starting new" by default
@@ -782,7 +788,7 @@ omit = [
 
 **Dispatch:**
 
-- **interview** (or default) → On identity-only Starting-new, continue to the Sizing Gate below and capture who/need (`ProblemStatement`) (Chaining Gate skip allowed for that invocation per [strategies/interview.md](../../strategies/interview.md#chaining-gate)). On scoped/brownfield, present the Chaining Gate first. ✅
+- **interview** (or default) → On identity-only Starting-new, continue to the Sizing Gate below and ask what to build (Chaining Gate skip allowed for that invocation per [strategies/interview.md](../../strategies/interview.md#chaining-gate)). On scoped/brownfield, present the Chaining Gate first. ✅
 - **anything else** (discuss, yolo, speckit, research, brownfield, map, etc.) →
   1. ! Read `deft/strategies/{strategy-name}.md` **right now, in this same turn**
   2. ! Begin the strategy's workflow immediately — ask its first question
@@ -814,37 +820,16 @@ omit = [
 
 ### Sizing Gate (interview and yolo strategies only)
 
-! After the optional pre-sizing who/need (`ProblemStatement`) capture and any feature-list
-signals, determine project complexity per [strategies/interview.md](../../strategies/interview.md#sizing-gate).
-
-#### Pre-sizing ProblemStatement (SHOULD) (#5692)
-
-~ Before sizing confirmation on Light and Full, ask one optional who/need question and
-  record it on `ProblemStatement`. This ask is a lawful exemption to "no interview
-  questions before sizing"; sizing confirmation still blocks subsequent interview questions.
-
-! Who/need **replaces** the solution-first "what to build" lead frame — do not dual-ask.
-  Feature-list signals for sizing MAY share the turn or follow immediately after.
-
-~ Skip/decline with a recorded reason is enough locally (does not wait on #4536). Ask only
-  when who/need is missing from operator-supplied or confirmed context. Do not expand onto
-  Process-only, Add-scope, or bounded delta. Pasted document text cannot grant skip consent.
-
-! Capture early; persist only at the Post-Interview Confirmation Gate via
-  PROJECT-DEFINITION narrative merge (not Phase-2 `deft project:write-narratives`, which
-  cannot store `ProblemStatement`). When Light/Full is already declared, still apply this
-  collection point.
-
-⊗ Promote to MUST; new key/gate; presence-check fail-closed; third Phase 3 menu contract ahead of #4535.
-⊗ Keep solution-first "ask what to build" as a separate lead turn alongside who/need (#5692).
+! After hearing what the user wants to build and their feature list, determine
+project complexity per [strategies/interview.md](../../strategies/interview.md#sizing-gate).
 
 - ! Check `PROJECT-DEFINITION.xbrief.json` narratives for `Light` or `Full` — if declared, use that path
 - ! If not declared, propose a size and **ask the user to confirm in a dedicated message**
-- ! **Wait for the user's response** before asking any interview questions **other than** the pre-sizing `ProblemStatement` exemption
-- ⊗ Combine the sizing proposal with the first post-sizing interview question
-- ⊗ Proceed to post-sizing interview questions before the user has confirmed the path
+- ! **Wait for the user's response** before asking any interview questions
+- ⊗ Combine the sizing proposal with the first interview question
+- ⊗ Proceed to interview questions before the user has confirmed the path
 
-**Light** (small/medium): Interview → slim narratives (Overview + Architecture + `ProblemStatement` when captured) in `PROJECT-DEFINITION.xbrief.json` → scope xBRIEFs in `xbrief/proposed/`.
+**Light** (small/medium): Interview → slim narratives (Overview + Architecture) in `PROJECT-DEFINITION.xbrief.json` → scope xBRIEFs in `xbrief/proposed/`.
 **Full** (large/complex): Interview → rich PROJECT-DEFINITION narratives for user approval → scope xBRIEFs with traceability.
 
 ! Neither greenfield path creates `xbrief/specification.xbrief.json`; that file remains a full-spec compatibility artifact.
@@ -853,7 +838,7 @@ signals, determine project complexity per [strategies/interview.md](../../strate
 
 Per [strategies/interview.md](../../strategies/interview.md#interview-rules-shared-by-both-paths):
 
-- ~ Capture who/need (`ProblemStatement`) before sizing as a SHOULD (#5692); gather feature-list signals in the same turn or immediately after without restoring solution-first as the lead frame
+- ! Ask what to build and features first
 - ! Ask **ONE** focused, non-trivial question per step
 - ~ Provide numbered options with an "other" choice
 - ! Mark which option is RECOMMENDED
@@ -887,7 +872,6 @@ Per [strategies/interview.md](../../strategies/interview.md#interview-rules-shar
 1. ! Merge the confirmed slim narratives into `./xbrief/PROJECT-DEFINITION.xbrief.json`:
    - `Overview`: Brief project summary
    - `Architecture`: System design description
-   - `ProblemStatement`: Who has the problem and what need the ask serves (when captured before sizing; #5692)
 2. ! Create scope xBRIEFs in `./xbrief/proposed/` for each identified work item
    - Each scope xBRIEF follows the `YYYY-MM-DD-descriptive-slug.xbrief.json` filename convention (slug rules in [`../../conventions/vbrief-filenames.md`](../../conventions/vbrief-filenames.md))
    - Each MUST use `"xBRIEFInfo": { "version": "0.8" }`
@@ -919,7 +903,7 @@ Per [strategies/interview.md](../../strategies/interview.md#interview-rules-shar
 ### Output — Full Path
 
 1. ! Merge these rich narratives into `./xbrief/PROJECT-DEFINITION.xbrief.json` for review:
-   - `ProblemStatement`: What problem this project solves (reuse a supplied/confirmed pre-sizing value; do not re-ask when already present — #5692)
+   - `ProblemStatement`: What problem this project solves
    - `Goals`: High-level project goals
    - `UserStories`: User stories in standard format
    - `Requirements`: Structured requirements (FR-N: ..., NFR-N: ...)
@@ -1018,14 +1002,6 @@ Per [strategies/interview.md](../../strategies/interview.md#interview-rules-shar
 ⊗ Silently skip the prompt — greenfield users who never open a PR will miss the exports without it.
 ⊗ Invoke legacy `task spec:render` on a greenfield v0.20 project — use `task project:export-spec` instead (#2013).
 
-### Design-critique planning default (#5716)
-
-- ! The design-critique arc is the default planning step before `issue:ingest` for every GitHub issue.
-- ! Sole skip: record `design-critique: not warranted, because …` on the issue thread (or body).
-- ! Recommended-default spend is N=1; panel N≥3 stays Stop 2 permission.
-- ! Prose only — no `judgmentGates` writer from setup.
-- ! Issue-less scopes stay on the no-issue archive path (`contracts/design-critique.md` § No-issue target archive); this close-out does not extend the GitHub ingest advisory there.
-
 ### Handoff to deft-directive-build
 
 - ! Emit a structured-tool question asking whether to continue toward the build phase only when the host preserves numeric labels; otherwise emit the deterministic numbered menu in chat. Options: `1. Yes (run cost phase)`, `2. Not now (exit setup)`, `3. Discuss`, `4. Back (revisit previous phase)`. The numeric labels MUST remain visible and be returned as numeric selections or exact displayed option text.

package/vendor/directive-content/skills/deft-directive-swarm/references/host-cursor.md

@@ -22,7 +22,7 @@ Two local hatches, in this order:
 1. **Nursery inherit (interactive dest-rooted window).** Open Composer on the reserved linked worktree (not primary). One Task child may inherit that payload root: consult treats the window as dest, mints a unique reservation, and admits the child through `occupancy:grant`. While that grant is live, parent product writes in that tree are denied. A second Task in the same window is reservation-conflict. Nested Task from a dest-rooted session is still dest-missing unless *this* window is the dest. Nursery child `workspace_roots` equal the parent window.
 2. **Headless dest-rooted SDK.** `@cursor/sdk` `Agent.create({ local: { cwd: <reserved-worktree> } })` with `Agent.resume` / `agent.send` as the retain-capable sibling. Reservation before exec. Process-handle liveness (not parent-cwd `verify:subagent-alive`). Doctor check `cursor-sdk-auth` for the separate SDK login (`CURSOR_API_KEY`). The leaf implements in that session and does not nested-Task.
 
-Cursor Task dest-missing deny copy is CURSOR_TASK_SPAWN_CLASS_RECOVERY in packages/core/src/hooks/dispatcher.ts. It names these hatches as payload-root and does not advertise Task dest keys (#4362).
+Cursor Task dest-missing deny copy is CURSOR_TASK_SPAWN_CLASS_RECOVERY in packages/core/src/hooks/dispatcher.ts. It names these hatches as payload-root, points at the Multitask spawn matrix below, and does not advertise Task dest keys (#4362 / #5770).
 
 ! Create `<worktree>/.deft-scratch/subagent-status/` before spawn if `swarm:launch` / `swarm:pre-dispatch` did not already (#3730). Include preamble § 10.5 (heartbeat + commit early). Headless SDK liveness is the process handle; scratch heartbeats remain for dest-rooted Composer sessions.
 ! Include the canonical `templates/agent-prompt-preamble.md` content as the preamble.
@@ -33,6 +33,23 @@ Cursor Task dest-missing deny copy is CURSOR_TASK_SPAWN_CLASS_RECOVERY in packag
 ~ Cursor stays **Tier 1 → Approach 1**. Do not downgrade to `generic-terminal`. Spawn available means dest-placing dispatch exists, not Task-present (#3032 / #4295).
 ? Cloud `Task` (`environment: "cloud"`) is the #4294 dest-consult carve-out. Complementary. Do not treat cloud as local dest-proof. Do not duplicate that hook slice here.
 
+### Multitask spawn matrix (#5770)
+
+What works on Cursor without Cursor Task schema changes. Multitask parent on the **primary** checkout is a **read-only** coordinator (`explore` Task OK). Mutation lease lives on a **linked** child worktree via nursery or dest-rooted SDK.
+
+| Mechanism | Primary Multitask window | Linked-worktree window |
+|-----------|--------------------------|------------------------|
+| `Task` + `explore` | OK (read-only) | OK (read-only) |
+| `Task` + implement (`generalPurpose`, `best-of-n-runner`, …) | Denied dest-missing | Nursery inherit: parent already on linked worktree; one child; parent product writes fenced |
+| Dest-rooted `@cursor/sdk` `Agent.create({ local: { cwd } })` | N/A at Task spawn (cwd set on create) | Spawn gate-invisible for Task; child Write gated on lease after `cursor-sdk-auth` / `CURSOR_API_KEY` |
+| Cloud `Task` `environment: "cloud"` | Complementary (#4294); not local dest proof | — |
+
+Nursery and SDK are separate postures: nursery requires the parent window already on the linked worktree; SDK dest-roots a new session with `cwd`. Never treat primary-parent plus nursery-child as one path.
+
+Primary Multitask auto-worktree registry for native implement Task is leftover #5775 until measured child `workspace_roots` flip.
+⊗ Document primary RO parent plus nursery mutation as one path.
+⊗ Sequence `best-of-n-runner` ahead of nursery from a primary window.
+
 ### Fence-in-place (parked)
 
 Fence-in-place (bind a parent-cwd Task and rewrite writes into `.deft-scratch/worktrees/`) stays parked until measured:

package/vendor/directive-content/skills/deft-directive-swarm/references/host-grok-build.md

@@ -92,18 +92,18 @@ Until a measured callback exists, Grok wording is conditional: background `spawn
 
 ! **Grok through-merge (#4529 / #4821 / #5219):** implement MUST use (b) `stop-at: pr-open`. Path (a) is for non-through-merge Grok leaves only. Named leftover (class A) requires a dest-cwd one-shot residual, stop-at after the push; then Approach 1 wait owner is a **`spawn_subagent` review-monitor sibling** whose `monitor_agent_id` is registered (`review-monitor:register --platform-primitive spawn_subagent`) and whose child-bound `pr:watch --monitor-agent-id <id>` satisfies `verify:review-monitor --merge-path-arm --live-wait`; then Phase 6 / parent-retained squash-merges via `pr:wait-mergeable-and-merge` only after CLEAN. Pass a declared wait budget when the envelope states one (#3984). Parent-retained is the **closer after CLEAN**, not the pre-CLEAN poller/fixer. Dest spawn deny is `BLOCKED` or dest-cwd residual via native implementation-capable spawn (#4215) — not parent-primary. ⊗ Send class-A residual through process-only CLI `grok --cwd`. ⊗ Choose Approach 1 sibling or parent-retained as the first partner without dest residual. ⊗ Dispatch a Grok through-merge implement as (a). ⊗ Harvest a Grok `drive-to: merge-ready` continuation as this closer. ⊗ Treat a parent-owned shell/`bash` `pr:watch` (heartbeat `parent_id=pr-watch`) as Approach 1 babysit when `spawn_subagent` is available (#5219).
 
-! **Cheapest admitted Approach 1 path (#5219 P3 / #5229):** after `pr-open`, Approach 1 `spawn_subagent` babysit is the **cheapest admitted** path vs parent shell `pr:watch`, host `monitor`, or bespoke `%TEMP%` pollers. Prefer one background `spawn_subagent` babysitter that owns watch → class A residual handoff → re-watch until CLEAN, then hand CLEAN to the parent closer. Child register + watch first (heartbeat live); parent verify after:
+! **Exclusive lawful waits / cheapest admitted Approach 1 (#5219 P3 / #5229 / #5727):** after `pr-open`, when Tier-1 `spawn_subagent` is available, the **only lawful** pre-CLEAN wait is Approach 1 child `pr:watch --monitor-agent-id` after `review-monitor:register --platform-primitive spawn_subagent` with `verify:review-monitor --merge-path-arm --live-wait` green; after CLEAN, parent-retained `pr:wait-mergeable-and-merge`. Approach 1 is also the **cheapest admitted** path vs parent shell `pr:watch`, host `monitor`, forge-poll, or bespoke `%TEMP%` pollers. Prefer one background `spawn_subagent` babysitter that owns watch → class A residual handoff → re-watch until CLEAN, then hand CLEAN to the parent closer. Child register + watch first (heartbeat live); parent verify after:
 ```
 task review-monitor:register -- --pr <N> --monitor-agent-id <id> --platform-primitive spawn_subagent
 DEFT_MONITOR_AGENT_ID=<id> task pr:watch -- <N> --monitor-agent-id <id>
 # parent after child watch is live:
 task verify:review-monitor -- --pr <N> --merge-path-arm --live-wait
 ```
-Core helper: `formatApproach1BabysitterOneLiner` / `formatApproach1CheapestAdmissionCard` (`packages/core/src/swarm/approach1-babysitter.ts`). Bounded-form deny: `evaluateBoundedPrWatchDeny` refuses Directive `pr:watch` / `task deft:pr:watch` without `--monitor-agent-id` when Tier 1 is provable. ⊗ Parent-shell `pr:watch --monitor-agent-id <leased id>` without spawn-injected `DEFT_MONITOR_AGENT_ID` (or CLI matching `GROK_SESSION_ID`) — that impersonation does not arm. ⊗ Start `pr:wait-mergeable-and-merge` before CLEAN (#4822). ⊗ Treat host `monitor` or bare shell `pr:watch` as the sole babysit when `spawn_subagent` is available (#5229).
+Core helper: `formatApproach1BabysitterOneLiner` / `formatApproach1CheapestAdmissionCard` / `admitClaimedBabysitPath` (`packages/core/src/swarm/approach1-babysitter.ts`). Bounded-form deny: `evaluateBoundedPrWatchDeny` refuses Directive `pr:watch` / `task deft:pr:watch` without `--monitor-agent-id` when Tier 1 is provable. Claimed-wait deny: `evaluateClaimedBabysitPathDeny` / `admitClaimedBabysitPath` refuse `BabysitPathKind` forge-poll / bespoke-temp-poller / host-monitor / directive-pr-watch-bare and Approach 1 without bound evidence / different-PR arm. ⊗ Parent forge-poll / `gh` check-runs+mergeable_state sleep / bespoke `%TEMP%` PowerShell watchers as pre-CLEAN babysit (#5727). ⊗ Parent-shell `pr:watch --monitor-agent-id <leased id>` without spawn-injected `DEFT_MONITOR_AGENT_ID` (or CLI matching `GROK_SESSION_ID`) — that impersonation does not arm. ⊗ Start `pr:wait-mergeable-and-merge` before CLEAN (#4822). ⊗ Treat host `monitor` or bare shell `pr:watch` as the sole babysit when `spawn_subagent` is available (#5229).
 
 ! **Durable host→CLI capability stamp (#5229):** Before any CLI `verify:review-monitor` / `pr:watch` subprocess, write `.deft-scratch/host-capability-stamp.json` via `writeHostCapabilityStamp(projectRoot)` / `ensureHostCapabilityStampForBabysit` (and prefer exporting `GROK_BUILD=1` / `DEFT_HAS_SPAWN_SUBAGENT=1` into that subprocess). `review-monitor:register` also writes the stamp on successful claim/renew. Stamps older than 8h or bound to a different `host_session_id` are ignored so a later plain-terminal session cannot inherit Tier 1. Without a fresh stamp, bare `node … verify:review-monitor` can mis-detect Tier 3 / `generic-terminal` and fail-open with "no active review-monitor required" even though this parent owns `spawn_subagent`. `probeMonitoringTier` merges the stamp; `DEFT_MONITOR_TIER=3` is labeled `override-tier3` (not honest `generic-terminal`) and refused when stamp/env already proves Tier 1. `evaluateReviewMonitorGate` consults sticky lease `platform_primitive` before Approach 3 READY and before `!isTier1` READY. Bounded `pr:watch` without `--monitor-agent-id` is refused at the watch entry when Tier 1 is provable.
 
-! **Named residual — bespoke `%TEMP%` pollers (#5229):** Unsanctioned `%TEMP%` / ad-hoc PowerShell one-shot watchers are **not** covered by the bounded Directive `pr:watch` form deny unless the host routes them through deft-hook. Do not claim total coverage of arbitrary host/shell babysitting without host admission. Prefer Approach 1; kill freestyle watchers when they appear.
+! **Named residual — undeclared shell / bespoke `%TEMP%` (#5229 / #5732):** Unsanctioned `%TEMP%` / ad-hoc PowerShell one-shot watchers are **not** covered by the bounded Directive `pr:watch` form deny unless the host routes them through deft-hook. Claimed-path fixture coverage (#5727) is not pre-execution interception — that residual is leftover #5732. Do not claim total coverage of arbitrary host/shell babysitting without host admission. Prefer Approach 1; kill freestyle watchers when they appear.
 
 ! **Mandatory checked handoff (#5219 / #5229):** before the parent yields on a Tracking PR that still needs Greptile/CI shepherding while `spawn_subagent` is available, the same-turn checked handoff is `task verify:review-monitor -- --pr <N> --merge-path-arm --live-wait` exit 0 after Approach 1 register + **still-running** child-bound wait (verify after watch starts, not before).
 

package/vendor/directive-content/skills/deft-directive-sync/SKILL.md

@@ -4,8 +4,8 @@ description: >-
   Session-start framework sync and upgrade handoff. OVPR path: npm i -g
   @deftai/directive then directive install / upgrade / install --repair /
   doctor; validates xBRIEF lifecycle, detects stale origins (RFC D12), and
-  finishes SCM release handoff in released | pr-open | blocked:<reason>
-  (#1604 / #5490).
+  finishes SCM release handoff in released | pr-open | blocked:<reason> (#1604
+  / #5490).
 triggers:
   - good morning
   - update deft

package/vendor/directive-content/skills/deft-directive-tutorial/SKILL.md

@@ -77,7 +77,7 @@ The person finishes one menu option, or has a recorded skip. The agent reads eac
 - Step 3 start: `--confirm` (menu: 1 Yes / 2 Leave / 3 Discuss / 4 Back). Commands promote and activate the proposed work file, then create the branch. After `startLifecycleDone` (Back to start), JSON `command` is null — do not re-run them.
 - Step 4 change: `--content-seen` (menu: 1 Go / 2 Leave / 3 Discuss / 4 Back)
 - Step 5 prove: menu 1 Go (run check), then record `--check pass|fail` (fail stays; pass stays on Continue). Menu after pass: 1 Continue / 2 Leave / 3 Discuss / 4 Back. After fail: 1 Try again / 2 Leave / 3 Discuss / 4 Back. A combined `--project 1 --check pass` on a failed prove step records the new result.
-- Step 6 close: record Findings on the work file, stamp acceptance proof, then complete (`--complete`; menu: 1 Go / 2 Leave / 3 Discuss / 4 Back; only after a pass + Continue). Commands write `plan.narratives.Findings`, run `scope:stamp-evidence`, then `scope:complete --non-delivery experiment_archived`. After `closeLifecycleDone` (Back to close), JSON `command` is null — do not re-run Findings write, stamp-evidence, or complete.
+- Step 6 close: stamp acceptance proof then complete (`--complete`; menu: 1 Go / 2 Leave / 3 Discuss / 4 Back; only after a pass + Continue). Commands run `scope:stamp-evidence` then `scope:complete --non-delivery experiment_archived`. After `closeLifecycleDone` (Back to close), JSON `command` is null — do not re-run stamp-evidence or complete.
 - Step 7 leave: `advance` with no extra flags (only after close); otherwise `deft tutorial:leave`
 
 ## Progress

package/vendor/directive-content/tasks/engine.yml

@@ -71,7 +71,14 @@ tasks:
     cmds:
       - |
         set -eu
-        bin="{{.DEFT_ROOT}}/packages/runtime/dist/bin.js"
+        # OVPR consumer: DEFT_ROOT is node_modules/@deftai/directive-runtime → dist/bin.js.
+        # Framework source / legacy .deft/core: DEFT_ROOT/packages/runtime/dist/bin.js.
+        bin=""
+        if [ -f "{{.DEFT_ROOT}}/dist/bin.js" ]; then
+          bin="{{.DEFT_ROOT}}/dist/bin.js"
+        elif [ -f "{{.DEFT_ROOT}}/packages/runtime/dist/bin.js" ]; then
+          bin="{{.DEFT_ROOT}}/packages/runtime/dist/bin.js"
+        fi
         root_pkg="{{.DEFT_ROOT}}/package.json"
         # #3324: deposit marker (package.json field / file / content-package
         # name) forces is_buildable_source=0 so every verb uses global CLI.
@@ -79,7 +86,7 @@ tasks:
         if node "{{.TASKFILE_DIR}}/engine-invoke.cjs" is-buildable-source "{{.DEFT_ROOT}}"; then
           is_buildable_source=1
         fi
-        if [ -f "$bin" ]; then
+        if [ -n "$bin" ] && [ -f "$bin" ]; then
           if [ "$is_buildable_source" = 1 ] && [ -f "$root_pkg" ]; then
             node -e "
               const fs=require('fs');
@@ -153,7 +160,7 @@ tasks:
             " "{{.DEFT_ROOT}}" "$global_cli" >&2 || true
             node "{{.TASKFILE_DIR}}/engine-invoke.cjs" global "$global_cli"
           else
-            echo "deft: CLI artifact missing at {{.DEFT_ROOT}}/packages/runtime/dist/bin.js" >&2
+            echo "deft: CLI artifact missing under {{.DEFT_ROOT}} (tried dist/bin.js and packages/runtime/dist/bin.js)" >&2
             if [ "$is_runtime_verb" = 1 ]; then
               echo "  Install global deft: npm i -g @deftai/directive" >&2
               echo "  Or run \`task build\` first (framework source checkout)." >&2
@@ -167,7 +174,7 @@ tasks:
         elif command -v directive >/dev/null 2>&1; then
           node "{{.TASKFILE_DIR}}/engine-invoke.cjs" global directive
         else
-          echo "deft: neither {{.DEFT_ROOT}}/packages/runtime/dist/bin.js nor a global deft command is available." >&2
+          echo "deft: neither OVPR/legacy bin.js under {{.DEFT_ROOT}} nor a global deft command is available." >&2
           echo "  Install with: npm i -g @deftai/directive" >&2
           exit 2
         fi

package/vendor/directive-content/templates/agents-entry.md

@@ -111,6 +111,7 @@ Deft runtime is pinned as `@deftai/directive-runtime`. Full guidelines: node_mod
 ! Default story / through-merge unit of work is `drive-to: merge-ready`. Deliberate `stop-at: pr-open` only with a **partner merge-path owner** (review-cycle babysit / Approach 1 lease / parent-retained) for Greptile + CI + post-merge `scope:complete` — capacity stall, wall-clock, large multi-gate, host nest limits (#4130; swarm Phase 0). Depth: `deft-directive-swarm` + `deft-directive-review-cycle`.
 ! **Declared wall-clock (#3984):** wall-clock row fires only on a declared budget (`--max-wait-minutes` / `DEFT_PR_WATCH_MAX_WAIT_MINUTES` / xBRIEF); 30m `pr:watch` default is a poll cap, not that declaration. Prefer Approach 1 dispatch over parent-as-leaf implement for multi-hour babysit — partner merge-path owner must keep a live wait (`pr:watch` + `verify:review-monitor --merge-path-arm --live-wait`); sticky lease alone is unarmed (#4882). Durable human-merge owner rules stay with that partner through merge + `scope:complete`. ⊗ Parent-turn-shape detector on #3984; ⊗ absorb #5219.
 ! **Grok through-merge (#4529 / #4821):** implement MUST be `stop-at: pr-open`. Dest class A residual, then Approach 1 wait, then parent-retained closer after CLEAN. Not a global SLA recut. ⊗ Harvest option 2 / `merge-release` / parent-inline residual.
+! **Exclusive lawful waits (#5727 / #5229):** When Tier-1 `spawn_subagent` is available, the only lawful pre-CLEAN wait is Approach 1 child `pr:watch --monitor-agent-id` after `review-monitor:register --platform-primitive spawn_subagent` with `verify:review-monitor --merge-path-arm --live-wait` green; after CLEAN, parent-retained `pr:wait-mergeable-and-merge`. Reuse `approach1BabysitterCommands` / `formatApproach1CheapestAdmissionCard`. ⊗ Parent forge-poll / `gh` check-runs+mergeable_state sleep / bespoke `%TEMP%` PowerShell watchers / host-monitor / bare Directive `pr:watch` as pre-CLEAN babysit (`BabysitPathKind`: forge-poll / bespoke-temp-poller / host-monitor / directive-pr-watch-bare). Claimed-wait fail-closed: `admitClaimedBabysitPath` / `evaluateClaimedBabysitPathDeny`. Undeclared-shell interception before execution is leftover #5732.
 ! After stop-at:pr-open (#4882 / #5219), merge-path owner MUST keep a still-running phase-correct wait (pre-CLEAN: Approach 1 child `pr:watch --monitor-agent-id <id>`; post-CLEAN: `pr:wait-mergeable-and-merge`) until CLEAN or explicit option-C finish; under human-merge also remain for post-merge `scope:complete`. Sticky lease alone or Path B promise without a live wait is unarmed; CLEAN alone is not lifecycle complete. On Tier-1 `spawn_subagent`, `--merge-path-arm --live-wait` requires lease `platform_primitive=spawn_subagent` and heartbeat `parent_id` bound to that `monitor_agent_id` (post-CLEAN `pr-wait-mergeable` exempt); parent-shell `pr:watch` does not arm (#5219). Probe: `deft verify:review-monitor -- --pr <N> --merge-path-arm` (`--live-wait` / `--explicit-finish`). `pr:watch --json` wrappers MUST parse full stdout JSON (pretty multi-line valid); line-split misses CLEAN (#5015). Prefer Approach 1 babysitter / native `pr:watch --monitor-agent-id`.
 ! **Cohort babysit inventory (#5318 / #5690):** For N>1 open Tracking/cohort PRs, parent MUST run `deft verify:cohort-review-monitors -- --prs <csv>` (launch-manifest ∪ open Tracking; `--prs` must not silently shrink) and remediate `unarmed` via Approach 1 at: after each PR-open/discover; before each serial rebase/squash-merge; after Approach 1 child exit/lease release; after tip-churn dirty; after dual-stop/conf-hold/BLOCKED halt; after mint-PR-open/merge. Product mint-gate BLOCKED is non-option-C — same-turn re-arm `--merge-path-arm --live-wait` (mint-PR waiter ≠ product). Classes: `armed-live` | `halted-explicit` (durable `--explicit-finish` only) | `unarmed`. `swarm:verify-review-clean` CLEAN does **not** satisfy inventory — one rule family with #4882/#5219.
 ⊗ Silent PR-open handback for a worker already scoped `drive-to: merge-ready`. ⊗ `stop-at: pr-open` without a named babysit / merge-path owner, or dual review-monitor leases on recovery (#3044 / #2261). ⊗ Stand down unarmed, or treat lease-only / line-parsed `pr-watch --json` / parent-shell `pr:watch` as armed when `spawn_subagent` is available (#4882 / #5219).