@deftai/directive-content 0.109.1 → 0.111.0

package/skills/deft-directive-triage/SKILL.md

@@ -1,13 +1,9 @@
 ---
 name: deft-directive-triage
 description: >-
-  Triage-cache hygiene and "what's next?" work selection (ordered plan or
-  ranked queue) -- the agent-facing playbook for syncing the triage cache,
-  classifying candidates, presenting a ranked queue or binding to an active
-  plan-sequence, walking per-item decisions (accept / reject / defer /
-  needs-ac / mark-duplicate), and auditing the session. Use when the operator
-  asks what to work on next, wants to build a cohort, work the cache, or run a
-  triage hygiene pass.
+  Withdrawn (#4070). Classify playbook is off. Work selection is
+  plan-sequence:current then a read-only triage:queue listing. Replacement
+  sieve is #4071. Triggers still match so packs:slice finds this stub.
 triggers:
   - triage
   - triage hygiene
@@ -27,120 +23,22 @@ triggers:
 
 # Deft Directive Triage
 
-Triage-cache hygiene + "what's next?" work selection (ordered plan or ranked queue). Operates against the unified `.deft-cache/github-issue/` mirror (#883 Story 2) and the append-only `xbrief/.eval/candidates.jsonl` audit log (#845 Story 2); writes only via the canonical `task triage:*` verbs.
+Withdrawn (#4070). Replacement sieve is #4071. #3579 is transitively withdrawn for the gap.
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-## Platform Requirements
+## When to Use
 
-! Requires **GitHub** as the SCM platform and the **GitHub CLI (`gh`)** authenticated against the active project's repo -- the cache surface (`task cache:fetch-all`) and the read-side gate (`task verify:cache-fresh`) both depend on it.
-
-## Deterministic Questions Contract
-
-! Every numbered-menu prompt rendered in this skill (Phase 2 candidate selection, Phase 3 per-item decision walk, post-Accept offer) ! MUST follow [`../../contracts/deterministic-questions.md`](../../contracts/deterministic-questions.md): render the canonical numbered menu in chat unless the host UI visibly preserves numeric option labels and returns numeric selections or exact displayed option text. The final two numbered options are `Discuss` and `Back`, in that order, and the Discuss-pause semantic from the contract applies verbatim -- on `Discuss` the agent halts the in-progress sequence and resumes only on an explicit user signal.
-
-## Work selection fork (#2542 / #2402)
-
-Directive does not guess your mix: **ordered plan** (`task plan-sequence:*`) when you know the next units in order, or **ranked queue** (`task triage:queue`) when picking from the backlog. Labels bias the queue; they do not override an active plan.
-
-! Before Phase 2 on bare "what's next?", run `task plan-sequence:current`. Active sequence → that entry only; exhausted → fail closed. Explicit "what's the queue?" / "build a cohort" → Phase 2. See `commands.md` § Backlog Triage → Two paths.
-
-## Phase 0 -- Sync
-
-! Probe cache freshness before doing any classification or selection. Stale cache reads produce stale decisions; the gate is the contract.
-
-1. ! Run `task verify:cache-fresh` (D5 / #1127). Exit 0 -> proceed to Phase 1. Exit 1 (stale or blocked) -> refresh per the printed remediation. Exit 2 (no bootstrap) -> run `task triage:bootstrap` first. When the cache has zero entries, read paths auto-fetch from GitHub first (#2575).
-2. ~ Refresh path: `task cache:fetch-all -- --source=github-issue --repo OWNER/NAME` for an already-bootstrapped project; `task triage:bootstrap` for a first-time seed.
-3. ~ If `xbrief/active/*.xbrief.json` references are in play, run `task triage:refresh-active` to surface drift before the queue is rendered.
-4. ~ When the session one-liner carries `[scope-drift] N` (D14 / #1133), run `task triage:scope-drift` and choose subscribe / ignore before walking the queue.
-5. ⊗ Walk the queue against a stale cache -- the audit log will record decisions against bodies the operator never actually saw.
-
-## Phase 1 -- Classify
-
-! Inspect the auto-classification audit log so manually-decided items are not re-walked, and surface anomalies before the queue render.
-
-1. ! Run `task triage:classify --list` (D10 / #1129) to render effective rules and hold-markers.
-2. ! Walk recent `xbrief/.eval/candidates.jsonl` entries for anomalies (classifier disagreement, repeated defer, stale needs-ac); surface before Phase 2; do NOT auto-fix.
-3. ~ Scope widen/narrow via `task triage:scope --list` (D12 / #1131); edits belong in PROJECT-DEFINITION.
-4. ~ Label hygiene: recommend repo labels via `gh label list` when unlabeled; do not invent labels or block creation solely for missing labels.
-5. ⊗ Re-classify terminally decided items without operator approval -- supersession is `task triage:reset <N>` only.
-
-## Phase 2 -- Present
-
-! Apply the Work selection fork gate (#2542): when no ordered-plan is active, render `task triage:queue` before suggesting work (#1149). Active sequence yields to the ordered-plan entry (#2402).
-
-1. ! Run `task triage:queue --limit=N` (D11 / #1128) -- default `N=10`. Groups `[RESUME]` -> `[URGENT]` -> untriaged -> other; ranking via `plan.policy.triageRankingLabels[]`, tiebreak `updated_at` desc.
-2. ! For per-item detail, run `task triage:show <N>` (default) or `task triage:show --format=operator <N>` (#2890) -- cached payload, latest decision, audit timeline, active-xBRIEF flag; operator format is the pasteable Phase 3 brief backbone. Exit 0 on hit, 1 on cache miss (re-sync per Phase 0).
-3. ~ Present the ranked **queue listing** verbatim; do NOT silently re-rank, drop, or annotate the listing beyond the canonical renderer. This queue non-annotation rule does **not** forbid Phase 3 per-candidate operator briefs or leans (see Phase 3 / #2890).
-4. ⊗ Recommend a specific issue without `task triage:queue` first, or an issue absent from the queue without `task triage:show` to surface why.
-
-## Phase 3 -- Decide
-
-! Walk per-item decisions through the canonical `task triage:*` verbs (tasks own audit-log append / schema / `xbrief/proposed/` write).
-
-! **Operator brief (same turn as menu) (#2890 / #3116):** Before every per-item decision menu, present an operator brief in the **same operator-visible message/surface** as the menu, containing at least: **URL-first** lead (canonical issue URL as the first line for that item, or `#N title` + URL); labels (or explicit none); **current-state validity** (`still-open` | `partial` | `likely-shipped` | `needs-re-scope`) + one-line evidence (linked closed PR, code path, or "no evidence of fix"); 2–5 line problem/context summary; AC bullets or explicit "thin body / no AC"; agent **lean** + one-line why (Accept / Defer / Reject / Needs-AC / …). ~ Prefer `task triage:show --format=operator <N>` as the brief backbone (URL-first + validity placeholder); agent still owns validity verdict and lean. ⊗ Menu-only or chip-only Phase 3 turns without that brief. ⊗ Brief-only turn followed by a later chip/menu-only turn that does not restate the brief. ⊗ Body-only summary without validity check against current master, closed children, or linked PRs.
-
-! **Host structured-question adapter:** On chips / `ask_user` / similar UIs (e.g. OpenClaw `ask_user`), keep the prose brief in chat; structured options are **actions only** (Accept / Defer / Reject / Needs-AC / Mark duplicate / Discuss / Back). Option labels ≉ substitute for the brief.
-
-For each candidate, render the canonical numbered action menu and dispatch:
-
-```
-What would you like to do with this candidate?
-  1. Accept         -- `task triage:accept -- --issue <N> --repo OWNER/NAME`
-  2. Reject         -- `task triage:reject -- --issue <N> --repo OWNER/NAME`
-  3. Defer          -- `task triage:defer -- --issue <N> --repo OWNER/NAME [--resume-on <event>]`
-  4. Needs-AC       -- `task triage:needs-ac -- --issue <N> --repo OWNER/NAME`
-  5. Mark duplicate -- `task triage:mark-duplicate -- --issue <N> --of <of-issue> --repo OWNER/NAME`
-  6. Discuss
-  7. Back
-```
-
-- ! Map user replies only to the displayed number (`1`-`7`) or exact displayed option text. ⊗ Do NOT infer from alphabetic host affordances or bare letters such as `d` / `b` unless those letters were visibly rendered as choices.
-- ! On `Discuss`, halt immediately, prompt `What would you like to discuss?`, resume only on explicit user signal. ⊗ Implicit resumption.
-- ! On `Back`, un-buffer prior selection and re-render its action menu only before a `task triage:*` dispatch; after dispatch use `task triage:reset`.
-- ~ Bulk: `task triage:bulk-{accept,reject,defer,needs-ac}`; results still flow through the audit log.
-- ⊗ Write to `xbrief/proposed/` directly -- only `task triage:accept` is authorised.
-- ~ **Accept → pending chain (#1136):** `task triage:accept` ingests into **`proposed/`**. To stage into WIP (`pending/`) in one operator action: `task triage:accept -- --issue <N> --repo OWNER/NAME --auto-promote` (WIP cap still enforced; use `--force` on the accept command for WIP override). Separately, promote an already-accepted proposed scope by issue: `task scope:promote -- --from-issue=<N> [--repo OWNER/NAME]` (gates on latest `candidates.jsonl` decision = `accept`; non-accept refuses unless `--force-no-cache`; no decision soft-warns, `--strict` fails). Path-based `task scope:promote -- <file>` remains ungated for refinement scaffolds.
-- ? **After Accept (#3708):** offer `deft-directive-design-critique`. Optional; same after `--auto-promote` (promote already happened). Decline writes nothing. Menu: 1. Run critique (existing ADR-005 path) 2. Skip 3. Discuss 4. Back. Back = Skip (do not re-open Accept; undo is `task triage:reset`).
-
-## Phase 4 -- Audit
-
-! Confirm the session's decisions landed coherently before exiting the skill.
-
-1. ! Run `task triage:audit --format=json` (D11 / #1128); optional `#1180` filters `--since` / `--action`. Transform with `jq` -- framework does not compute trends.
-2. ! Run `task triage:summary` (D2 / #1122) -- `[triage] N untriaged · S stale-defer · M in-flight · WIP X/Y [⚠] [· [scope-drift] N]`.
-3. ~ Non-zero `[scope-drift]` → surface `task triage:scope-drift` + subscribe/unsubscribe/ignore remediation; then `task triage:bootstrap -- --resume`.
-4. ~ Stale accept (no active xBRIEF ref) → re-ingest or `task triage:reset`.
-5. ⊗ Skip Phase 4 audit.
-6. ! Umbrella/epic status: REST comments → `## Current shape (as of pass-N)` (#2066 / #1152); never body alone.
-
-## Reversibility
-
-! Undo via `task triage:reset <N>` (Layer 5; history never deleted). ⊗ Edit/delete `xbrief/.eval/candidates.jsonl` to "undo".
-
-## Quarterly closed-entry archive vs TTL prune (#1137)
-
-Live walkers (`triage:queue`, scope-drift, bootstrap) scan `.deft-cache/github-issue/`. Closed issues can linger forever. Operators may run an **explicit, reversible** archive pass — never auto on bootstrap/session/check.
-
-| Tool | What it does |
-| --- | --- |
-| `task triage:cache-archive` | Move **closed** + aged (default 30d) entries → `.deft-cache/archived/github-issue/...` with `archive-meta.json`. Skips open lifecycle scopes. `--dry-run` first. |
-| `task triage:archive-list` / `task triage:restore-from-archive` | List / move back to live. |
-| `task cache:prune` | **TTL hard-delete** by `expires_at` — **not** reversible; **not** closed-state archive. |
-
-! Prefer archive for closed clutter; use prune only for expired TTL / cap eviction. ⊗ Wire archive into session-start or `task check`.
-
-## Anti-Patterns
-
-- ⊗ Recommend work without `task triage:queue` (#1149).
-- ⊗ Conclude "nothing to do" from folder scans or live GitHub alone (#2576).
-- ⊗ Stale-cache walk; reimplement audit/`proposed/` writes; treat defer/needs-ac as terminal; edit candidates.jsonl; menu-only Phase 3 without operator brief (#2890); body-only brief without URL-first or current-state validity (#3116).
+- Triggers still match so `packs:slice` finds this stub.
+- ⊗ Do not load the old classify / Phase 1-3 playbook.
 
 ## EXIT
 
-! On opt-out: `deft-directive-triage complete -- exiting skill.` Chain: `deft-directive-refinement` (accepted items) · `deft-directive-swarm` (cohort) · `task cache:fetch-all` then re-enter. ⊗ Silent exit.
+! On any trigger: print `deft-directive-triage withdrawn -- exiting skill.` Point at https://github.com/deftai/directive/issues/4070 and #4071.
+
+! Work selection during the gap: `task plan-sequence:current`, then a read-only `task triage:queue` listing.
 
-## References
+⊗ `task triage:classify -- --mirror` (dry-run or `--apply`).
+⊗ Treat leftover `triaged` / `triage:*` chips as a decision.
 
-- #1119 D6; #1128 D11 (`triage:queue` / `show` / `audit`); #2890 Phase 3 operator brief; #3116 validity + URL-first; #1122 / #1123 / #1127 / #1129 / #1131; #1136 (`scope:promote --from-issue` / `triage:accept --auto-promote`); #3708 (post-Accept design-critique offer)
-- Siblings: `deft-directive-refinement`, `deft-directive-swarm`, `deft-directive-sync`
+`task triage:accept` / `issue:ingest` stay. Do not close #1423, #3579, #2611, or #3923.

package/tasks/policy.yml

@@ -21,8 +21,8 @@ tasks:
     #   --format=text|json    -- machine-stable scripting envelope
     #   --changed-only         -- drop default-source rows
     #   --field=<name>         -- single-field isolation
-    # The legacy `python -m scripts.policy show` CLI continues to work for
-    # any scripts that called it directly (back-compat for #746 consumers).
+    # Inspect via engine:invoke / packages/cli/dist (policy:show). The
+    # retired `python -m scripts.policy` launcher is gone.
     desc: "Inspect every registered typed-policy field on vbrief/PROJECT-DEFINITION.vbrief.json (#1148 / N8). -- task policy:show [-- --format=json] [--changed-only] [--field=<name>]"
     dir: '{{.USER_WORKING_DIR}}'
     deps:

package/tasks/scope.yml

@@ -5,33 +5,24 @@ vars:
 
 # scope lifecycle tasks.
 #
-# IMPORTANT: every task sets ``dir: '{{.USER_WORKING_DIR}}'`` so the Python
-# script's CWD is the consumer project root, NOT ``deft/``. The script path
-# is resolved via ``{{.DEFT_ROOT}}/scripts/`` (DEFT_ROOT is defined locally
-# in this file's `vars:` block via ``{{joinPath .TASKFILE_DIR ".."}}`` --
-# see ../Taskfile.yml for why root-level definition is avoided) so it
-# still points at ``deft/scripts/scope_lifecycle.py`` after the dir switch.
-# The previous ``{{.TASKFILE_DIR}}/../scripts/`` form broke on Windows
-# under `uv --project "{{.DEFT_ROOT}}" run python` (#566) because mixed-separator traversal
-# normalizes incorrectly and drops the deft/ prefix.
+# IMPORTANT: every task sets ``dir: '{{.USER_WORKING_DIR}}'`` so
+# engine:invoke CWD is the consumer project root, NOT the framework tree.
+# DEFT_ROOT is defined locally in this file's `vars:` block via
+# ``{{joinPath .TASKFILE_DIR ".."}}`` -- see ../Taskfile.yml for why
+# root-level definition is avoided.
 #
-# CLI_ARGS: passed to the script raw / unquoted. go-task shell-escapes
-# CLI_ARGS with single quotes on its own, so wrapping the interpolation
-# in Taskfile-level double quotes produces ``"'path'"`` at dispatch time
-# on Windows (pwsh/cmd preserve nested quotes verbatim), and Python's
-# argv receives a literal single-quote-prefixed filename that fails to
-# open (#577). All seven scope:* commands therefore forward
-# ``{{.CLI_ARGS}}`` bare -- matching migrate.yml / prd.yml / issue.yml /
-# reconcile.yml.  ``scope_lifecycle.py`` handles both absolute and
-# relative values via ``_resolve_file_path`` + ``resolve_project_root``
-# -- the script owns path resolution, the task just forwards
-# ``--project-root`` so detection never silently falls back to deft's
-# own tree (#535). Relative paths resolve against the consumer root
-# thanks to ``--project-root``; absolute paths are used as-is.
+# Handler: packages/cli/src/scope-lifecycle.ts via engine:invoke
+# (packages/cli/dist). Help registry:
+# packages/core/src/triage/help/registry-data.ts (edit in place).
 #
-# ``env: PYTHONUTF8: "1"`` is set per-task as a belt-and-suspenders guard
-# for Windows (cp1252 default crashes on -- / -> / x / !); the top-level
-# Taskfile.yml also sets this (#540).
+# CLI_ARGS: passed raw / unquoted. go-task shell-escapes CLI_ARGS with
+# single quotes on its own, so wrapping the interpolation in
+# Taskfile-level double quotes produces ``"'path'"`` at dispatch time
+# on Windows (#577). All scope:* commands therefore forward
+# ``{{.CLI_ARGS}}`` bare -- matching migrate.yml / prd.yml / issue.yml /
+# reconcile.yml. The TypeScript handler owns path resolution; the task
+# forwards ``--project-root`` so detection never silently falls back to
+# the framework tree (#535).
 
 tasks:
 

package/tasks/triage-actions.yml

@@ -20,10 +20,9 @@ version: '3'
 # (#74), `task pr:check-protected-issues` (#702), and `task verify:encoding`
 # (#798).
 #
-# Companion script: scripts/triage_actions.py
-# Companion tests:  tests/test_triage_actions.py
-# Upstream contracts (frozen): scripts/candidates_log.py (#845 Story 2 audit log),
-#                              scripts/cache.py          (#883 Story 2 unified cache).
+# Handler: packages/cli/src/triage-actions.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
+# Audit/cache contracts live in packages/core (candidates log + unified cache).
 
 vars:
   DEFT_ROOT: '{{joinPath .TASKFILE_DIR ".."}}'

package/tasks/triage-bootstrap.yml

@@ -15,8 +15,8 @@ version: '3'
 #   tasks/triage-bulk.yml       (Story 4 -- bulk ops + freshness)
 #   tasks/triage-bootstrap.yml  (Story 6 -- this file)
 #
-# Companion script: scripts/triage_bootstrap.py
-# Companion test:   tests/test_triage_bootstrap.py
+# Handler: packages/cli/src/triage-bootstrap.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 #
 # Per `conventions/task-caching.md` (#574): NO `sources:` / `generates:`
 # declarations on this task because user-facing recovery flags

package/tasks/triage-bulk.yml

@@ -11,13 +11,12 @@ version: '3'
 # are hidden from `task -l`.
 #
 # The disable-gate `cmds:` blocks introduced by PR #916 (#915 hot-fix) were
-# REVERSED once scripts/triage_bulk.py was rewritten to walk the local
-# cache instead of live `gh issue list`. As of #883 Story 3 the cache walk
-# consumes the unified `cache:get` surface
-# (`.deft-cache/github-issue/<owner>/<repo>/<N>/`); the four `bulk-*`
-# targets continue to invoke triage_bulk.py directly. The cache-empty
-# hard-fail (exit 2) and Tier-2 audit-log short-circuit are enforced
-# inside triage_bulk.py itself (#915 fix).
+# reversed once bulk ops walked the local cache instead of live `gh issue
+# list`. As of #883 Story 3 the cache walk consumes the unified `cache:get`
+# surface (`.deft-cache/github-issue/<owner>/<repo>/<N>/`); the four
+# `bulk-*` targets invoke packages/cli/src/triage-bulk.ts via engine:invoke.
+# The cache-empty hard-fail (exit 2) and Tier-2 audit-log short-circuit are
+# enforced inside that handler (#915 fix).
 #
 # Per `conventions/task-caching.md` (#574): every target here accepts user
 # flags via `{{.CLI_ARGS}}` (--label, --author, --age-days, --cluster,

package/tasks/triage-classify.yml

@@ -13,8 +13,8 @@ version: '3'
 # `--validate`, `--project-root`) are forwarded via {{.CLI_ARGS}} and
 # go-task's incremental-build cache layer would silently swallow them.
 #
-# Companion script: scripts/triage_classify.py (+ scripts/_triage_classify_cli.py)
-# Companion tests:  tests/test_triage_classify.py
+# Handler: packages/cli/src/triage-classify.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 # Current Shape:    https://github.com/deftai/directive/issues/1129#issuecomment-4471901622
 
 vars:
@@ -22,7 +22,7 @@ vars:
 
 tasks:
   classify:
-    desc: "Inspect / validate triageAutoClassify + triageLabelMirror; Tier-1 SCM label mirror (#1129 / #1423). -- task triage:classify -- [--list | --validate | --mirror [--apply]]"
+    desc: "Inspect / validate triageAutoClassify + triageLabelMirror. --mirror is withdrawn (#4070)."
     internal: true
     deps: [":engine:_ts-build"]
     dir: '{{.USER_WORKING_DIR}}'
@@ -30,3 +30,13 @@ tasks:
       - task: :engine:invoke
         vars:
           ENGINE_CMD: 'triage-classify --project-root "{{.USER_WORKING_DIR}}" {{.CLI_ARGS}}'
+
+  strip-withdrawn-chips:
+    desc: "Remaining-set strip of withdrawn triaged / triage:* chips (#4070). Dry-run default; --apply writes. --emit-digest prints shadowed vs faithful classify rows for #4071."
+    internal: true
+    deps: [":engine:_ts-build"]
+    dir: '{{.USER_WORKING_DIR}}'
+    cmds:
+      - task: :engine:invoke
+        vars:
+          ENGINE_CMD: 'triage-strip-withdrawn --project-root "{{.USER_WORKING_DIR}}" {{.CLI_ARGS}}'

package/tasks/triage-queue.yml

@@ -17,8 +17,8 @@ version: '3'
 # `--project-root`, `--cache-root`, `--audit-log`) via {{.CLI_ARGS}} and
 # go-task's incremental-build cache layer would silently swallow them.
 #
-# Companion script: scripts/triage_queue.py (+ scripts/_triage_queue_cli.py)
-# Companion tests:  tests/test_triage_queue.py
+# Handler: packages/cli/src/triage-queue.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 # Current Shape:    https://github.com/deftai/directive/issues/1128#issuecomment-4471272093
 
 vars:

package/tasks/triage-reconcile.yml

@@ -12,8 +12,8 @@ version: '3'
 # `--project-root`) are forwarded via {{.CLI_ARGS}} and go-task's
 # incremental-build cache layer would silently swallow them.
 #
-# Companion script: scripts/triage_reconcile.py
-# Companion tests:  tests/test_triage_reconcile.py
+# Handler: packages/cli/src/triage-reconcile.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 # Pattern reference: tasks/triage-bootstrap.yml (#845 Story 6).
 
 vars:

package/tasks/triage-scope-drift.yml

@@ -13,8 +13,8 @@ version: '3'
 # {{.CLI_ARGS}} and go-task's incremental-build cache layer would silently
 # swallow them.
 #
-# Companion script: scripts/triage_scope_drift.py (+ shims).
-# Companion tests:  tests/test_triage_scope_drift.py.
+# Handler: packages/cli/src/triage-scope-drift.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 
 vars:
   DEFT_ROOT: '{{joinPath .TASKFILE_DIR ".."}}'

package/tasks/triage-scope.yml

@@ -14,8 +14,8 @@ version: '3'
 # via {{.CLI_ARGS}} and go-task's incremental-build cache layer would
 # silently swallow them.
 #
-# Companion script: scripts/triage_scope.py (+ scripts/_triage_scope_cli.py)
-# Companion tests:  tests/test_triage_scope.py
+# Handler: packages/cli/src/triage-scope.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 # Current Shape:    https://github.com/deftai/directive/issues/1131#issuecomment-4471901494
 
 vars:

package/tasks/triage-smoketest.yml

@@ -13,9 +13,9 @@ version: '3'
 # `--cache-only`, `--fixture`) are forwarded via {{.CLI_ARGS}} and
 # go-task's incremental-build cache layer would silently swallow them.
 #
-# Companion script:   scripts/triage_smoketest.py (+ scripts/_triage_smoketest_stages.py)
-# Companion fixture:  tests/fixtures/triage_smoketest/
-# Companion tests:    tests/test_triage_smoketest.py + tests/test_triage_smoketest_fixture.py
+# Handler: packages/cli/src/triage-smoketest.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
+# Fixture: tests/fixtures/triage_smoketest/
 # Pattern reference:  tasks/triage-summary.yml (D2 / #1122).
 
 vars:

package/tasks/triage-subscribe.yml

@@ -12,8 +12,8 @@ version: '3'
 # declarations -- user-facing flags (`--label`, `--milestone`, `--issue`,
 # `--issue-note`, `--actor`) are forwarded via {{.CLI_ARGS}}.
 #
-# Companion script: scripts/triage_subscribe.py (+ shim).
-# Companion tests:  tests/test_triage_subscribe.py.
+# Handler: packages/cli/src/triage-subscribe.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 
 vars:
   DEFT_ROOT: '{{joinPath .TASKFILE_DIR ".."}}'

package/tasks/triage-summary.yml

@@ -12,8 +12,8 @@ version: '3'
 # `--no-history`, `--json`) are forwarded via {{.CLI_ARGS}} and go-task's
 # incremental-build cache layer would silently swallow them.
 #
-# Companion script: scripts/triage_summary.py
-# Companion tests:  tests/test_triage_summary.py
+# Handler: packages/cli/src/triage-summary.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 # Pattern reference: tasks/triage-scope.yml (D12 / #1131 / merged via #1190).
 
 vars:

package/tasks/triage-welcome.yml

@@ -13,8 +13,8 @@ version: '3'
 # `--no-subprocess`) are forwarded via {{.CLI_ARGS}} and go-task's
 # incremental-build cache layer would silently swallow them.
 #
-# Companion script: scripts/triage_welcome.py (+ scripts/_triage_welcome_cli.py)
-# Companion tests:  tests/test_triage_welcome.py
+# Handler: packages/cli/src/triage-welcome.ts via engine:invoke (packages/cli/dist).
+# Help registry: packages/core/src/triage/help/registry-data.ts (edit in place).
 # Pattern reference: tasks/triage-summary.yml (D2 / #1122).
 
 vars:

package/tasks/verify.yml

@@ -369,6 +369,19 @@ tasks:
         vars:
           ENGINE_CMD: 'codebase-map-fresh --project-root "{{.USER_WORKING_DIR}}" {{.CLI_ARGS}}'
 
+
+  spec-prd-fresh:
+    desc: "Fail-closed SPECIFICATION.md / PRD.md render-freshness gate (#4086). Re-renders to a buffer and fails on banner or projection diff. Banner canon and full projection freshness are separate assertions. Modeled on verify:codebase-map-fresh."
+    dir: '{{.USER_WORKING_DIR}}'
+    deps:
+      - task: :engine:_ts-build
+    # Per conventions/task-caching.md: no sources/generates because this gate
+    # forwards project-root through CLI_ARGS.
+    cmds:
+      - task: :engine:invoke
+        vars:
+          ENGINE_CMD: 'verify:spec-prd-fresh --project-root "{{.USER_WORKING_DIR}}" {{.CLI_ARGS}}'
+
   session-ritual:
     desc: "Fail-closed session ritual verifier (#1348). Flags: --tier quick|gated / --json. Set DEFT_SESSION_RITUAL_SKIP=1 for headless workers and CI."
     dir: '{{.USER_WORKING_DIR}}'
@@ -401,7 +414,7 @@ tasks:
           ENGINE_CMD: 'verify:tools {{.CLI_ARGS}}'
 
   scm-boundary:
-    desc: "Detection-bound gate against raw `gh` / `ghx` subprocess calls outside `scripts/scm.py` (#1145 / N5). Scans verb-layer Python files (`scripts/triage_*.py`, `scripts/scope_*.py`, `scripts/slice_*.py`, `scripts/_triage_*.py`, `scripts/_scope_*.py`, `scripts/resume_conditions.py`, `scripts/issue_ingest.py`) and fails loud when any of them invoke `gh` directly instead of going through `scm.call(source, verb, args)`. Three-state exit (0 clean / 1 violations / 2 config error). Document an exception via `--allow-list <path>` (file with newline-separated glob patterns)."
+    desc: "Detection-bound gate against raw `gh` / `ghx` subprocess calls (#1145 / N5). TypeScript verbs route through packages/core/src/scm/call.ts. The scanner still globs retired scripts/triage_*.py paths (vacuous; owner packages/core/src/verify-source/scm-boundary.ts SCOPE_GLOBS). Three-state exit (0 clean / 1 violations / 2 config error). Document an exception via `--allow-list <path>`."
     dir: '{{.USER_WORKING_DIR}}'
     deps:
       - task: :engine:_ts-build

package/templates/agent-prompt-preamble.md

@@ -97,6 +97,7 @@ Populate `selected_backend` OR `routing_policy` (or both when the operator sets
 **Role-boundary expectations (all providers):** the same boundaries apply whether the worker runs on Composer, Grok Build, Cursor/cloud, Claude Code, OpenClaw, or a future adapter:
 
 - ! `leaf-implementation` workers implement scoped xBRIEF work in their assigned worktree only -- gates (`task check`, file-scope audit, Greptile review cycle) are model-agnostic and MUST still pass.
+- ! **Spawned mutating workers take their own worktree (#4066).** Implement-class spawn must carry `isolation=worktree` or a linked `worktree_path`/`cwd` before occupancy claim. Sharing the primary checkout with a live occupant is refuse, not `occupancy:grant` across hosts. Master/primary occupancy is the exception (`release-cut`, `policy-restore`, operator-directed default-branch work). `--read-only` never claims. On DONE/terminal the dispatcher compare-and-releases the recorded child tree (incarnation + parent-id); do not steal the parent's lease to recover. Grok `spawn_subagent` cannot rewrite PreToolUse input -- pass cwd to the reserved worktree.
 - ! `orchestrator`, `review-monitor`, and `merge-release` roles MUST run on strong or review-capable agents; dispatchers MUST NOT route these roles to cheap leaf backends.
 - ⊗ Route a cheap leaf backend onto the merge cascade, Phase 5->6 release gate, conflict-resolution rebase, or review-cycle merge-ready decision -- these are irreversible-damage surfaces that stay on the strong tier regardless of provider.
 
@@ -486,10 +487,12 @@ These rules bind **orchestrators** dispatching implementation, fix, or review-cy
 
 **Worker-owns-lifecycle (Gap C):**
 
-- ! When dispatching an implementation worker, the dispatch envelope MUST declare the unit-of-work boundary explicitly: `stop-at: pr-open` (worker opens PR and exits) OR `drive-to: merge-ready` (worker owns PR + Greptile review cycle + fix batches through merge-ready as ONE unit of work, spawning its own review poller per `skills/deft-directive-review-cycle/SKILL.md` monitoring tiers). Default for story implementation dispatches is `drive-to: merge-ready`.
+- ! When dispatching an implementation worker, the dispatch envelope MUST declare the unit-of-work boundary explicitly: `stop-at: pr-open` (worker opens PR and exits) OR `drive-to: merge-ready` (worker owns PR + Greptile review cycle + fix batches through merge-ready as ONE unit of work, following `skills/deft-directive-review-cycle/SKILL.md` monitoring tiers). On hosts whose leaves cannot nest a review-monitor (Cursor #2797, Claude Code #3134, Grok Build #4130), merge-ready means blocking `pr:watch` in **this** process -- not spawning a child poller. Default for story implementation dispatches is `drive-to: merge-ready`.
 - ! **Envelope selection SLA (#3153):** Choose the boundary before spawn using the swarm decision tree (`skills/deft-directive-swarm/references/core-phase-0.md` — capacity stall, conf-only residual, wall-clock budget, large multi-gate, host nest limits). Happy-path default remains `drive-to: merge-ready`. A **deliberate** `stop-at: pr-open` is valid only with an immediate partner merge-path owner per `skills/deft-directive-review-cycle/SKILL.md` § Partner merge-path (babysit / Approach 1 lease / parent-retained — not freestyle global babysit). Under human-merge policy, that owner (or an explicit handoff recipient) remains responsible through merge + `scope:complete` — do not stand down at CLEAN alone. Consumer pin: `templates/agents-entry.md` § Envelope selection SLA. Silent PR-open handback for a worker already scoped merge-ready remains **forbidden**.
 - ! **Cursor Task ownership split (#2797 / #2814):** A Cursor `Task` implementation leaf MUST NOT spawn another Cursor `Task` review-monitor: nested Task (leaf spawning leaf) is unsupported/unreliable. A Cursor `drive-to: merge-ready` leaf instead owns a blocking `task pr:watch -- <N>` in its own process. To use an Approach 1 monitor, scope the leaf `stop-at: pr-open`; the orchestrator that owns the Task primitive then launches the sibling monitor and runs `task review-monitor:register -- --pr <N> --monitor-agent-id <id> --platform-primitive cursor-task` (GitHub sticky `<!-- deft:review-owner -->` lease — not local JSON).
 - ⊗ Let a Cursor leaf background `task pr:watch` and claim review monitoring is active. The process dies with the leaf and has no GitHub review-owner lease; treat that claim as a regression/eval failure and let `task verify:review-monitor -- --pr <N>` fail closed.
+- ! **Grok Build ownership split (#4130 / #2797 analogue):** A `spawn_subagent` implementation leaf MUST NOT nested-spawn a review-monitor or any other `spawn_subagent`. Nested spawn does not report to the parent, and the parent cannot re-prompt a live child (`resume_from` requires terminal). A Grok Build `drive-to: merge-ready` leaf instead owns a blocking `deft pr:watch <N>` (or `task deft:pr:watch -- <N>`) in its own process, then `pr:merge-ready` / merge in the same loop. To use an Approach 1 monitor, scope the leaf `stop-at: pr-open`; the orchestrator that owns `spawn_subagent` then launches the sibling monitor and registers `--platform-primitive spawn_subagent`. If the leaf needs another agent, it stops and reports `BLOCKED`.
+- ⊗ Tell a grok-build leaf to spawn its own review poller, or let it nested-spawn `spawn_subagent` and claim monitoring is active.
 - ! **Post-merge scope lifecycle (#2321 / Gap C / #3429 / #3476):** Workers scoped `stop-at: pr-open` MUST NOT run `task scope:complete` before exit — their activation checkpoint rides into master on merge. The **orchestrator** (or Phase 6 `task swarm:finalize-cohort` / `task swarm:complete-cohort` on the headless path) MUST run `task scope:complete` or `task scope:cancel` for each shipped story xBRIEF after its PR merges. Workers scoped `drive-to: merge-ready` (or `drive-to: merge`) MUST include `task scope:complete` on their active xBRIEF as part of the same unit of work (after merge when appropriate). After merge (or observing merge) of issue `#N`, run `task verify:orphan-active -- --issue N`. Exit `0` is required before `DONE`. Exit `1` shipped → run the printed `task scope:complete -- <path>`. Exit `1` unresolved lookup → retry / emit `BLOCKED`; ⊗ complete unfinished scope. After `scope:complete`, `task verify:completed-tracked -- --issue N` MUST be exit `0` against `origin/<deliveryBranch>` (not feature-worktree HEAD) before `DONE` (#3476). Exit `1` missing tracked artifact → not DONE; remediate with `task swarm:finalize-cohort` or a lifecycle PR. `scope:complete` stays filesystem-only — ⊗ teach every leaf to commit on master.
 - ! Workers scoped `drive-to: merge-ready` MUST drive to merge-ready in their own tool loop — pre-PR, push, PR open, review-cycle poll/fix loop, and the #1259 Step 6 fail-closed exit — without handing back at PR-open for the orchestrator to re-dispatch separate leaf agents for review or fixes.
 - ⊗ Re-dispatch a separate review-monitor or fix agent after an implementation worker exits at PR-open when the original envelope scoped `drive-to: merge-ready` — that split recreates cross-agent state-handoff hazards and terminal lifecycle gaps (#1878 / Gap C).

package/templates/agents-entry.md

@@ -17,11 +17,11 @@ Deft is installed in .deft/core/. Full guidelines: .deft/core/main.md
 
 ## Session routing (#2176)
 
-! **Read-only default** until mutation intent: load AGENTS.md / main.md / USER.md / `xbrief/PROJECT-DEFINITION.xbrief.json`; resolve USER.md via `deft session:start` (`USER.md resolved …`; win32 `%APPDATA%\deft\USER.md`; unix `~/.config/deft/USER.md`; ⊗ invent `~/.config/deft` on Windows #2544); confirm Deft alignment + addressing-name; ⊗ no mutable `deft session:start` / triage welcome / sync / branch-policy unless asked or implementation-ready (#2176) — `.deft/core/commands.md` § Session routing. Bootstrap: cold-start → README § Cold-start (#2273) ⊗ never `.deft/core/`; pre-cutover → setup Pre-Cutover (#2068); missing USER.md / PROJECT-DEFINITION → setup Phase 1/2 (#1813) ⊗ before answering; else main → USER → PROJECT-DEFINITION; ~ sync. Mutation → `deft session:start` then `deft verify:session-ritual -- --tier=gated` (#1149). Occupancy (#3433/#3611/#3755): bearer-id, not auth/lineage; `occupancy:grant` → `commands.md`. ? `deft session:start -- --read-only` (#2176).
+! **Read-only default** until mutation intent: load AGENTS.md / main.md / USER.md / `xbrief/PROJECT-DEFINITION.xbrief.json`; resolve USER.md via `deft session:start` (`USER.md resolved …`; win32 `%APPDATA%\deft\USER.md`; unix `~/.config/deft/USER.md`; ⊗ invent `~/.config/deft` on Windows #2544); confirm Deft alignment + addressing-name; ⊗ no mutable `deft session:start` / triage welcome / sync / branch-policy unless asked or implementation-ready (#2176) — `.deft/core/commands.md` § Session routing. Bootstrap: cold-start → README § Cold-start (#2273) ⊗ never `.deft/core/`; pre-cutover → setup Pre-Cutover (#2068); missing USER.md / PROJECT-DEFINITION → setup Phase 1/2 (#1813) ⊗ before answering; else main → USER → PROJECT-DEFINITION; ~ sync. Mutation → `deft session:start` then `deft verify:session-ritual -- --tier=gated` (#1149). Occupancy (#3433/#3611/#3755/#3926): bearer-id, not auth/lineage; `occupancy:grant` → `commands.md`. ? `deft session:start -- --read-only` (#2176).
 
 ## Session-start ritual (#1149)
 
-! On **mutation** session start, run `deft session:start`; before code-writing or `start_agent` dispatch run `deft verify:session-ritual -- --tier=gated` (stale after `plan.policy.sessionRitualStalenessHours`; records `deft verify:tools` / `deft doctor` / `deft verify:cache-fresh` / `deft agents:refresh` / `npm i -g @deftai/directive@latest`; #1149 / #1348) — `.deft/core/commands.md` § Session-start ritual. Recovery: `deft session:ready` (one-shot: start + gated ritual + cache recovery; #2993). ! SCM mirror tip (#3124): restate existence + get-the-most user-visible when tip fires (depth `commands.md`). ⊗ Absorb tip without restating.
+! On **mutation** session start, run `deft session:start`; before code-writing or `start_agent` dispatch run `deft verify:session-ritual -- --tier=gated` (stale after `plan.policy.sessionRitualStalenessHours`; records `deft verify:tools` / `deft doctor` / `deft verify:cache-fresh` / `deft agents:refresh` / `npm i -g @deftai/directive@latest`; #1149 / #1348) — `.deft/core/commands.md` § Session-start ritual. Recovery: `deft session:ready` (one-shot: start + gated ritual + cache recovery; #2993). The #3124 SCM mirror tip does not fire (`triage:classify --mirror` withdrawn, #4070).
 
 ## WIP cap
 
@@ -29,9 +29,9 @@ Deft is installed in .deft/core/. Full guidelines: .deft/core/main.md
 
 ## xBRIEF layout (#2034 / #2110)
 
-Legacy `vbrief/`; `deft migrate:xbrief` (v0.6→v0.8). New writes `"version": "0.8"`. Depth: `main.md` (#3600).
-! Completed xBRIEFs are record of *what is*, zero authority over *what to build next* (#3383). Current contract = active xBRIEF + human operator live instruction. Depth: `main.md` Persistence; build skill declare-the-contract / halt-and-ask.
-⊗ Treat a completed xBRIEF as the next-build contract.
+! Writes: `./xbrief/` (`PROJECT-DEFINITION.xbrief.json`, `plan.xbrief.json`, `specification.xbrief.json`) as `"xBRIEFInfo"` `"version": "0.8"`. Legacy `vbrief/`; `deft migrate:xbrief`.
+! Completed xBRIEFs are record of *what is*, zero authority over *what to build next* (#3383). Current contract = active xBRIEF + human operator live instruction.
+⊗ Treat a completed xBRIEF as the next-build contract. ⊗ Emit `"version": "0.6"` on new writes.
 
 ## Unmanaged project header (#2065)
 
@@ -39,7 +39,7 @@ Legacy `vbrief/`; `deft migrate:xbrief` (v0.6→v0.8). New writes `"version": "0
 
 ## Cache-as-authoritative work selection (#1149)
 
-! "what next?" → two work-selection modes (#2402): **ordered plan** (`deft plan-sequence:*`) or **ranked queue** (`deft triage:queue`) — `commands.md` § Backlog Triage → Two paths. ordered-plan first; else `deft-directive-triage` + `deft triage:queue --limit=10` (D11). Empty cache auto-populates from GitHub (#2575).
+! "what next?" → two work-selection modes (#2402 / #1149): **ordered-plan first** (`deft plan-sequence:current`), then a read-only `deft triage:queue --limit=10` listing (D11) — `commands.md` § Backlog Triage → Two paths. `deft-directive-triage` classify withdrawn (#4070 / #4071). Empty cache auto-populates from GitHub (#2575).
 
 ⊗ Recommend work without queue/plan consult; ⊗ widen past an exhausted plan; ⊗ conclude "nothing to do" from `xbrief/{pending,active}` folder scans or GitHub-only reads without `deft triage:queue` (#2576).
 
@@ -92,7 +92,7 @@ Legacy `vbrief/`; `deft migrate:xbrief` (v0.6→v0.8). New writes `"version": "0
 
 ## Envelope selection SLA (#3153)
 
-! Default story / through-merge unit of work is `drive-to: merge-ready`. Deliberate `stop-at: pr-open` is allowed only when a **partner merge-path owner** is planned (review-cycle babysit / Approach 1 lease / parent-retained) for Greptile + CI + post-merge `scope:complete` — triggers: capacity stall, wall-clock budget, large multi-gate, host nest limits (swarm Phase 0 decision tree). Depth: `deft-directive-swarm` + `deft-directive-review-cycle` partner merge-path.
+! Default story / through-merge unit of work is `drive-to: merge-ready`. Deliberate `stop-at: pr-open` is allowed only when a **partner merge-path owner** is planned (review-cycle babysit / Approach 1 lease / parent-retained) for Greptile + CI + post-merge `scope:complete` — triggers: capacity stall, wall-clock budget, large multi-gate, host nest limits (Cursor / Claude Code / Grok Build #4130; swarm Phase 0 decision tree). Depth: `deft-directive-swarm` + `deft-directive-review-cycle` partner merge-path.
 ! Under human-merge policy, a **durable** owner (parent/monitor sticky lease or Phase 6 closer) MUST remain for post-merge `scope:complete` — CLEAN alone is not lifecycle complete; ⊗ stand down at CLEAN with no reachable owner.
 ⊗ 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).

package/templates/design-critique-brief.md

@@ -12,8 +12,11 @@ Dispatch envelope skeleton for one critic or synthesis pass. Fill the fields. Re
 - Critic role (fresh | resume):
 - Id ceiling (GitHub comment id, inclusive):
 - SHA at dispatch:
+- Run posture (`arc-mode: direct` | `arc-mode: checkout`):
 - Target (work issue or umbrella):
 - Audit targets (marker ids, comma-separated, or `none`; ids only, no parent rationale):
+- Seat families (N≥3: three claimed families before spawn):
+- Launcher (spawn_subagent | grok | claude | codex | paste-ready):
 
 ## Forbidden inputs
 
@@ -36,10 +39,12 @@ Read, do not restate:
 |---|---|
 | Gate (ADR-005) | Stop 1 — Gate |
 | Stop 1 `refutation-target:` | Stop 1 — Gate |
+| Run posture `arc-mode:` | Stop 1 — Gate |
 | Variant selection | Stop 2 — Variant selection |
 | Parent-facing dispatch rules | Parent-facing dispatch rules |
 | Critic method | Critic method |
 | Envelope and ceiling | Envelope and ceiling |
+| Seat families / Grok Build launcher | Envelope and ceiling |
 | Comment lead (model then role) | Stop 3 — Critic envelope |
 | Fresh reiteration | Stop 4 — Residual reiteration |
 | Operator-gated loop | Operator-gated loop |