@deftai/directive-content 0.115.0 → 0.117.0

package/strategies/interview.md

@@ -31,10 +31,12 @@ or switch to a different spec-generating strategy. This gate is the single
 orchestration point for strategy composition.
 
 ! The chaining gate MUST always be shown — even when the interview strategy is
-invoked directly with no prior strategy.
+invoked directly with no prior strategy — except the identity-only Starting-new
+skip below (#4390).
 ! The chaining gate is a **blocking question**. The AI MUST present the options
 and wait for the user to choose before proceeding.
-⊗ Skip the chaining gate or proceed to the sizing gate without presenting it.
+⊗ Skip the chaining gate or proceed to the sizing gate without presenting it,
+except the identity-only Starting-new / Proceed invocation named below.
 
 ### When It Appears
 
@@ -44,17 +46,31 @@ and wait for the user to choose before proceeding.
 
 ### Brownfield Detector
 
-Before rendering menu options, classify the repo (align with setup Phase 3):
+Before rendering menu options, classify the repo (same rule as setup Phase 3; #4390 recut of the #2925 identity-OR-scopes probe):
 
-- **Brownfield** when **either**:
-  - `PROJECT-DEFINITION` exists under `./xbrief/` or legacy `./vbrief/` (`PROJECT-DEFINITION.xbrief.json` or `PROJECT-DEFINITION.vbrief.json`), **or**
-  - any lifecycle folder (`proposed/`, `pending/`, `active/`, `completed/`, `cancelled/` under `xbrief/` or legacy `vbrief/`) has scope records
-- **Greenfield** otherwise
+- **Identity-only** when BOTH:
+  - live PROJECT-DEFINITION `plan.items` is empty (`[]` or absent), AND
+  - no convention-valid `*.xbrief.json` / `*.vbrief.json` in lifecycle folders (`proposed/`, `pending/`, `active/`, `completed/`, `cancelled/` under `./xbrief/` or legacy `./vbrief/`). Exclude `.gitkeep` and `*.premigrate.*`. PROJECT-DEFINITION itself is identity, not a scope record.
+- **Scoped (brownfield)** when `plan.items` is non-empty OR at least one convention-valid scope file exists
+- **Greenfield** otherwise (no PROJECT-DEFINITION and no convention-valid scope file)
 
 ! The detector MUST run on every Chaining Gate presentation.
+! Identity-only and greenfield share the Proceed / Starting-new default. Scoped/brownfield defaults to Add-scope.
+⊗ Treat PROJECT-DEFINITION existence alone as brownfield.
+⊗ Use session-age ("this setup turn just wrote identity") as the probe.
+⊗ Invent a "finished Phase 3" marker.
 ⊗ Offer only the greenfield-framed **Proceed to specification** default on a brownfield repo.
 ⊗ Treat brownfield as a full create path without an explicit Replace/scrap confirm.
 
+### Starting-new / Proceed skip (#4390)
+
+! Starting-new (setup Phase 3) and Proceed (this gate) MUST ask what to build before writing a scope.
+
+? When setup Phase 3 already selected **Starting a new project specification** on identity-only, this Chaining Gate MAY be skipped for that invocation and the agent may continue to the Sizing Gate. Written reason: identity-only default is already Proceed; the prior identity-OR-scopes detector re-defaulted to Add-scope one step later and skipped the product interview.
+
+⊗ Skip this gate on scoped/brownfield repos.
+⊗ Skip this gate when the operator chose Add-scope, Update, or Replace.
+
 ### Options
 
 ! Numbered Chaining Gate menus (greenfield and brownfield examples below) MUST end with `Discuss` and `Back` as the final two options per [deterministic-questions.md](../contracts/deterministic-questions.md).
@@ -63,16 +79,22 @@ Present groups sourced from the `Type` column in
 [strategies/README.md](./README.md#strategy-types). The **default path** depends
 on the brownfield detector:
 
-**Default path (greenfield):**
-1. **Proceed to specification** (default) — continue to the [Sizing Gate](#sizing-gate) for a full create path
+**Default path (greenfield or identity-only):**
+1. **Proceed to specification** (default) — ask what to build; continue to the [Sizing Gate](#sizing-gate) for a full create path
+
+**Identity-only also keeps Add-scope / Update / Replace / Process-only on the menu** (same vocabulary as setup Phase 3). They are not the default.
 
 **Default path (brownfield) — create-vs-update menu:**
-1. **Add scope to this project** (default) — load existing project identity + preparatory artifacts; **skip** the greenfield "what are we building?" interview; gather only the new scope; emit **one** proposed scope record; apply the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light) on write
+1. **Add scope to this project** (default) — load existing project identity + preparatory artifacts; **skip** the greenfield "what are we building?" interview only after capturing an explicit product or slice description; gather only the new scope; emit **one** proposed scope record; apply the [Preparatory Guard](./artifact-guards.md#preparatory-guard-light) on write
+   - ! On identity-only Add-scope: capture a product or slice description, or do not emit a proposed xBRIEF. ⊗ Synthesize the first scope from Overview / directory name / init seed. Swarm's `xbrief/proposed/` scan is in scope for that skip.
 2. **Update project definition** — run a **delta** interview against existing identity; apply the [Spec-Generating Guard](./artifact-guards.md#spec-generating-guard-full); **merge** narratives (prefer enrich/merge when the user declines replace)
 3. **Replace specification (scrap)** — full recreate equivalent to greenfield Proceed; **only** after explicit affirmative (`yes` / `confirmed`); vague replies (`proceed`, `ok`, `go ahead`) are **not** acceptance
    - ! On confirmed scrap, continue to the [Sizing Gate](#sizing-gate) as a full create path
    - ⊗ Auto-delete PROJECT-DEFINITION without scrap confirm
    - ⊗ Rename Proceed to "Update" without changing behavior
+4. **Process-only (keep Phase 2 identity)** — leave strategy; no new scope; no spec write. Do not emit a proposed scope. Do not merge or scrap PROJECT-DEFINITION narratives. Then-path: session ritual / deft check / later Add scope. Skip Sizing Gate, export, Acceptance Gate, and build. GitHub issues stay cache/queue inputs. Docs stay described content.
+   - ⊗ Use Back or Other as this option
+   - ⊗ Bind docs or issues as the next-build plan
 
 **Preparatory strategies** (type: `preparatory` — loops back to this gate on completion):
 - Research — investigate the domain, find libraries, identify pitfalls
@@ -144,7 +166,32 @@ Ready to generate the specification. Before we proceed, would you like to:
 10. Back
 ```
 
-**Brownfield:**
+**Identity-only** (PROJECT-DEFINITION exists; empty `plan.items`; no convention-valid scopes) — same options as setup Phase 3; Proceed is the default:
+
+```
+This repo has project identity but no scopes yet. Before we proceed:
+
+1. Proceed to specification (default) — ask what to build; full create path
+2. Add scope to this project — keep identity; requires an explicit product or slice description
+3. Update project definition — delta interview; merge narratives (Spec-Generating Guard)
+4. Replace specification (scrap) — requires explicit yes/confirmed; full recreate
+5. Process-only (keep Phase 2 identity) — leave strategy; no new scope; no spec write
+
+--- Preparatory (loops back) ---
+6. Run a research phase — investigate the domain, find libraries, identify pitfalls
+7. Run a discuss phase — lock key decisions using Feynman technique
+8. Run a probe phase — adversarially stress-test the plan; surface assumptions, edge cases, and risks
+9. Run a map phase — analyze existing codebase conventions
+
+--- Switch strategy ---
+10. Switch to yolo — auto-pilot picks all answers
+11. Switch to speckit — formal spec process with story readiness before implementation
+12. Other (specify)
+13. Discuss
+14. Back
+```
+
+**Brownfield** (scoped):
 
 ```
 This repo already has a project definition and/or scopes. Before we proceed:
@@ -152,19 +199,20 @@ This repo already has a project definition and/or scopes. Before we proceed:
 1. Add scope to this project (default) — keep identity; add one new proposed scope
 2. Update project definition — delta interview; merge narratives (Spec-Generating Guard)
 3. Replace specification (scrap) — requires explicit yes/confirmed; full recreate
+4. Process-only (keep Phase 2 identity) — leave strategy; no new scope; no spec write
 
 --- Preparatory (loops back) ---
-4. Run a research phase — investigate the domain, find libraries, identify pitfalls
-5. Run a discuss phase — lock key decisions using Feynman technique
-6. Run a probe phase — adversarially stress-test the plan; surface assumptions, edge cases, and risks
-7. Run a map phase — analyze existing codebase conventions
+5. Run a research phase — investigate the domain, find libraries, identify pitfalls
+6. Run a discuss phase — lock key decisions using Feynman technique
+7. Run a probe phase — adversarially stress-test the plan; surface assumptions, edge cases, and risks
+8. Run a map phase — analyze existing codebase conventions
 
 --- Switch strategy ---
-8. Switch to yolo — auto-pilot picks all answers
-9. Switch to speckit — formal spec process with story readiness before implementation
-10. Other (specify)
-11. Discuss
-12. Back
+9. Switch to yolo — auto-pilot picks all answers
+10. Switch to speckit — formal spec process with story readiness before implementation
+11. Other (specify)
+12. Discuss
+13. Back
 ```
 
 ---

package/tasks/verify.yml

@@ -113,7 +113,9 @@ tasks:
       - task: :engine:_ts-build
     dir: '{{.USER_WORKING_DIR}}'
     cmds:
-      - node "{{.DEFT_ROOT}}/packages/core/dist/docs/docs-impact.js" --project-root "{{.USER_WORKING_DIR}}" {{.CLI_ARGS}}
+      - task: :engine:invoke
+        vars:
+          ENGINE_CMD: 'docs-impact --project-root "{{.USER_WORKING_DIR}}" {{.CLI_ARGS}}'
 
   license-sync:
     desc: "Drift guard for root LICENSE ↔ content/LICENSE.md and published package.json license fields (#2902). Three-state exit (0 clean / 1 drift / 2 config). Framework-source only."

package/templates/agent-prompt-preamble.md

@@ -96,7 +96,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.
+- ! `leaf-implementation` workers implement scoped xBRIEF work in their assigned worktree only -- gates (prefer `deft check`; else tree-correct `task deft:check` on include-only consumers or `task check` in framework source; file-scope audit; Greptile review cycle) are model-agnostic and MUST still pass. These are one gate, not two sequential runs. Do not add a fourth probe (#2893 / #4379).
 - ! **Spawned mutating workers take their own worktree (#4066 / #4295).** Implement-class spawn must dest-place before occupancy claim. Grok `spawn_subagent` dest is `cwd` only (cannot rewrite PreToolUse input). Claude/Codex keep `isolation=worktree` or a linked path. Cursor Task has no local dest field — dest-placing is a dest-rooted window (nursery inherit) or `@cursor/sdk` `Agent.create({ local: { cwd } })`; do not advertise Task dest keys. 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.
 - ! `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.

package/templates/agents-entry.md

@@ -71,10 +71,12 @@ Deft is installed in .deft/core/. Full guidelines: .deft/core/main.md
 
 ! Process-critical skills with false-negative risk MUST be named in AGENTS.md (always-pin tier) — tier definitions: `.deft/core/docs/skill-pin-policy.md` (#2508).
 ! **Default always-pins:** `deft-directive-build`, `deft-directive-pre-pr`, `deft-directive-review-cycle`, `deft-directive-swarm` — read each `SKILL.md` when that work type starts.
+! Policy-anchored review-response (#3452): HEAD policy before out-of-model. Depth: review-cycle SKILL.
 ⊗ Pin entire language packs, deployment docs, or framework bulk into AGENTS.md — pins are for false-negative-sensitive process gates only (#2508).
 ! **Dual stop (#2442):** multi-iteration work MUST have success + failure/budget stop (max iters / no-progress / budget); single-turn exempt; halt with operator-visible report; ⊗ thrash. Defaults: build, swarm, review-cycle skills. See main.md Dual Stop Rule. Ledger #3143 (`packages/core/src/delivery-attempt/`).
 ## Rule Authority [AXIOM]
 ! Prefer `task deft:*` over AGENTS.md prose. See main.md.
+! Merge chokepoint (#4379 / #2893): prefer `deft check`; else `task deft:check` on include-only consumers. One gate, not two runs.
 ## Thin Fail-Closed Design (#3265)
 ! One fail-closed `task deft:*` check + one remediation. See main.md.
 ## Writing bar (#3368)

package/tools/package-manager-network.md

@@ -15,7 +15,7 @@ Directive runs against arbitrary repositories, including private monorepos with
 
 - ! Read-only, session-start, and session-ritual flows (`deft session:start`, `deft verify:session-ritual`, `deft verify:tools`) MUST perform no npm/pnpm registry access. Tool-presence probes MUST use PATH lookups (`which`/`accessSync`) or `--version` checks, never a subcommand that can resolve dependencies or query a registry.
 - ! `npm config get @deftai:registry` and `npm config get registry` are offline configuration reads, not registry access. `deft doctor` MAY use them in its default tier to identify effective routing, but MUST NOT print the raw values because registry URLs can contain internal hostnames or credentials.
-- ! `deft doctor` MUST default to an OFFLINE tier: no check in the default run may contact an npm/pnpm registry. The one check that can (`payload-staleness`, which uses `git ls-remote` to verify the installed pin and `npm view <package> version --registry=https://registry.npmjs.org/ --ignore-scripts` to compare a release-tag install with the latest stable package) is gated behind the explicit `--network` flag and is skipped by default with a pointer to that flag.
+- ! `deft doctor` MUST default to an OFFLINE tier: no check in the default run may contact an npm/pnpm registry. The one check that can (`payload-staleness`, which uses `git ls-remote` to verify the installed pin and `npm view <package> version --ignore-scripts` from a temp cwd whose project `.npmrc` sets `@deftai:registry=https://registry.npmjs.org/`) is gated behind the explicit `--network` flag and is skipped by default with a pointer to that flag. `--registry` does not beat `@scope:registry`; `--userconfig` does not beat a project `@scope:registry`. Directive-owned `npm view` MUST unset or override the scoped key (cwd change with a project `.npmrc`, or durable `@deftai:registry`) rather than pin `--registry` from the consumer cwd.
 - ! Before a network-gated check runs, `deft doctor --network` MUST print a disclosure line naming the tool and registry class it may contact (for example, "may contact your git remote and the npm registry") BEFORE any network call is attempted.
 - ! Any future doctor check, session step, or read-only command that needs to invoke `npm`/`pnpm` in a way that can reach a registry MUST follow the same pattern: explicit flag or subcommand, disclosed registry class before the call, and offline by default.
 - ~ Where a package-manager operation is unavoidable in an explicitly-invoked flow (e.g. a release or install workflow that legitimately needs to fetch packages), prefer offline/frozen modes (`--offline`, `--prefer-offline`, `--frozen-lockfile`) when the operation only needs to validate local state rather than resolve fresh metadata.
@@ -28,4 +28,4 @@ This does not ban dependency installation or registry verification from explicit
 
 ## Reference implementation
 
-`packages/core/src/doctor/npm-registry.ts` performs only the two offline `npm config get` reads above and redacts their values from findings. `packages/core/src/doctor/payload-staleness.ts` owns the network-capable doctor probes (`git ls-remote` and `npm view`); `packages/core/src/doctor/main.ts` gates them behind `--network` and prints the disclosure line first. The npm release lookup pins `--registry=https://registry.npmjs.org/` and `--ignore-scripts`, so a configured mirror cannot silently report an old latest release. `packages/core/src/session/session-start.ts` and `packages/core/src/verify-env/verify-tools.ts` perform no package-manager network access at all -- tool presence is resolved via PATH probing only.
+`packages/core/src/doctor/npm-registry.ts` performs only the two offline `npm config get` reads above and redacts their values from findings. `packages/core/src/doctor/payload-staleness.ts` owns the network-capable doctor probes (`git ls-remote` and `npm view`); `packages/core/src/doctor/main.ts` gates them behind `--network` and prints the disclosure line first. The npm release lookup isolates from project/user `@deftai:registry` with a temp cwd whose project `.npmrc` sets `@deftai:registry=https://registry.npmjs.org/`, and `--ignore-scripts`. User npmrc still supplies proxy/cafile. `--registry` does not beat `@scope:registry` (npm/cli#7659). `--userconfig` does not beat a project scoped registry. Default doctor and gated session-ritual MUST NOT add a fail-closed `npm view`. `packages/core/src/session/session-start.ts` and `packages/core/src/verify-env/verify-tools.ts` perform no package-manager network access at all -- tool presence is resolved via PATH probing only. Do not parse per-package `.npmrc` keys.

package/vbrief/schemas/vbrief-core.schema.json

@@ -612,7 +612,7 @@
         "sessionRitualStalenessHours": {
           "type": "integer",
           "minimum": 1,
-          "description": "Maximum age, in hours, for .deft/ritual-state.json before the fail-closed session ritual verifier requires task session:start to run again. Default: 4."
+          "description": "Maximum age, in hours, for .deft/ritual-state.json before the fail-closed session ritual verifier requires task session:start to run again. Default: 8."
         },
         "forgeOutageRetryMinutes": {
           "type": ["integer", "null"],