@deftai/directive-content 0.109.1 → 0.111.0

package/conventions/machine-generated-banner.md

@@ -10,7 +10,7 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 ## Why
 
 Before this contract, deft had four machine-managed file writers
-(`task migrate:vbrief` deprecation redirects, `task spec:render`,
+(frozen `task migrate:vbrief` deprecation redirects (v0.59.0; historical), `task spec:render`,
 `task prd:render`, `task roadmap:render`) and each used a different
 (or no) banner convention. Downstream heuristics that distinguish
 "is this file user-customized" from "is this machine-managed" were
@@ -34,7 +34,7 @@ of the file:
 - `{purpose}` — one of the enumerated per-writer purposes below; fixed
   string values so downstream detectors can match on a stable token.
 - `{source}` — the source-of-truth path the writer consumed
-  (typically `vbrief/specification.vbrief.json`), or `n/a` when the
+  (typically `xbrief/specification.xbrief.json`), or `n/a` when the
   writer has no single source-of-truth file (e.g. the migrator
   deprecation redirect, which is driven by the migration flow).
 - `{command}` — the canonical `task *` invocation that regenerates
@@ -49,10 +49,10 @@ of the file:
 The `Purpose:` value is a small fixed enum so detectors can match on a
 stable token. Writers MUST use exactly one of these values:
 
-- `rendered specification` -- `scripts/spec_render.py` -> `SPECIFICATION.md`
-- `rendered PRD` -- `scripts/prd_render.py` -> `PRD.md`
-- `rendered roadmap` -- `scripts/roadmap_render.py` -> `ROADMAP.md`
-- `deprecation redirect` -- `scripts/migrate_vbrief.py::_deprecation_redirect()`
+- `rendered specification` -- `task spec:render` -> `SPECIFICATION.md`
+- `rendered PRD` -- `task prd:render` -> `PRD.md`
+- `rendered roadmap` -- `task roadmap:render` -> `ROADMAP.md`
+- `deprecation redirect` -- frozen `task migrate:vbrief` (v0.59.0; historical)
   -> replaced `SPECIFICATION.md` / `PROJECT.md`
 
 ? Future render tasks added under `tasks/` MUST extend this list before
@@ -61,7 +61,7 @@ contract violation.
 
 ## Detection heuristic (for user-customization guards)
 
-! `scripts/migrate_vbrief.py::_is_user_customized()` consults the
+! Frozen `task migrate:vbrief` (v0.59.0) `_is_user_customized()` consults the
 `_SPEC_AUTO_MARKERS` and `_PROJECT_AUTO_MARKERS` tuples. Both MUST
 include `"AUTO-GENERATED by"` and the FULL HTML-comment prefix
 `"<!-- Purpose:"` so any file carrying this banner is recognised as
@@ -83,13 +83,13 @@ incorrectly re-flagged as pre-cutover on rc.3.
 ```
 <!-- AUTO-GENERATED by task spec:render -- DO NOT EDIT MANUALLY -->
 <!-- Purpose: rendered specification -->
-<!-- Source of truth: vbrief/specification.vbrief.json -->
+<!-- Source of truth: xbrief/specification.xbrief.json -->
 <!-- Regenerate with: task spec:render -->
 # My Project
 ...
 ```
 
-## Example (migrator deprecation redirect)
+## Example (frozen migrator deprecation redirect, v0.59.0; historical)
 
 ```
 <!-- AUTO-GENERATED by task migrate:vbrief -- DO NOT EDIT MANUALLY -->

package/conventions/rule-ownership.json

@@ -252,11 +252,11 @@
     },
     {
       "id": "main-vbrief-persistence",
-      "text": "All vBRIEF files MUST be stored in `./vbrief/` or its lifecycle subfolders",
+      "text": "All xBRIEF files MUST be stored in `./xbrief/` or its lifecycle subfolders",
       "owner_file": "main.md",
-      "owner_section": "## vBRIEF Persistence",
+      "owner_section": "## xBRIEF Persistence",
       "authority": "MUST",
-      "last_verified": "2026-04-28"
+      "last_verified": "2026-09-02"
     },
     {
       "id": "agents-deft-alignment-confirmation",

package/docs/consumer-issue-label-kit.md

@@ -109,10 +109,9 @@ https://github.com/deftai/directive/blob/master/content/docs/consumer-issue-labe
 - epic (rare multi-ship product root)
 - status:tracker, status:child
 
-## Mirror (if using triage:classify -- --mirror)
-- triaged
-- optional action chips: triage:deferred, triage:archived
-  (only if plan.policy.triageLabelMirror.actionLabels maps them)
+## Mirror (withdrawn #4070)
+- `triage:classify -- --mirror` is withdrawn. Do not stamp `triaged` / `triage:*` from classify.
+- Replacement sieve is #4071. Leave these names unused until the replacement recuts the catalog.
 
 ## Optional project routing (only if used)
 - security (advisory security review routing; not a merge gate)
@@ -126,16 +125,7 @@ Do not invent labels outside this file. Prefer existing names over twins.
 
 ## Optional: label mirror appendix
 
-After SCM label mirror Waves 1–2 (#1423 / #3125):
-
-| Topic | Guidance |
-|-------|----------|
-| Defaults | Mirror is available; on match it stamps **`triaged`** (idempotency). Action chips only when configured. |
-| Dry-run | `deft triage:classify -- --mirror` (open-only default). Review the digest before `--apply`. |
-| Apply | `deft triage:classify -- --mirror --apply` writes labels in batches; re-run is a no-op for already-`triaged` issues. |
-| More matches | Add rules under `plan.policy.triageAutoClassify` in `xbrief/PROJECT-DEFINITION.xbrief.json`. |
-| Richer chips | Set `plan.policy.triageLabelMirror.actionLabels` **and** create those GitHub labels first. |
-| Accept path | ⊗ Never auto-`triage:accept` / never auto-write `proposed/` from mirror. Accept stays an operator decision. |
+After #4070, SCM label mirror Waves 1–2 (#1423 / #3125) are unusable. `deft triage:classify -- --mirror` (dry-run and `--apply`) fail closed. Strip leftover chips with `deft triage:strip-withdrawn-chips`. Replacement sieve is #4071. #2611 stays open. Accept stays an operator decision (`triage:accept` / ingest unchanged).
 
 Minimal policy sketch (clone and edit; broader triage field examples live in the framework repo at [`docs/example-project-definition.md`](https://github.com/deftai/directive/blob/master/docs/example-project-definition.md) — not deposited under `.deft/core/`):
 
@@ -166,13 +156,10 @@ Minimal policy sketch (clone and edit; broader triage field examples live in the
 }
 ```
 
-If you only want the default `triaged` stamp, you can omit `actionLabels` entirely.
-
-Validate with:
+`triage:classify -- --mirror` is withdrawn (#4070). Do not add `triageLabelMirror` to stamp `triaged` / `triage:*`. Validate remaining classify rules with:
 
 ```bash
 deft triage:classify -- --validate
-deft triage:classify -- --mirror
 ```
 
 ---
@@ -221,5 +208,5 @@ Framework source / GitHub (browse when not in a deposit):
 ## Related reading
 
 - Maintainer taxonomy (do not import wholesale): [`.github/ISSUE_LABELS.md`](https://github.com/deftai/directive/blob/master/.github/ISSUE_LABELS.md) (#2609)
-- Label mirror behavior: deposit `.deft/core/commands.md` (or framework `content/commands.md`) / `deft triage:classify -- --mirror` (#1423, #3125)
+- Label mirror withdrawn: deposit `.deft/core/commands.md` (or framework `content/commands.md`) / #4070 (do not run `deft triage:classify -- --mirror`)
 - Example PROJECT-DEFINITION triage fields: [`docs/example-project-definition.md`](https://github.com/deftai/directive/blob/master/docs/example-project-definition.md) (#1186; framework repo only, not deposited)

package/docs/getting-started.md

@@ -79,7 +79,7 @@ checks tools without rewriting consumer-managed files.
 
 If you are adopting Deft on a project that already has an issue tracker (existing repo, brownfield migration, an upstream bug list that has been accumulating), you do not have to start from an empty `xbrief/proposed/`. The refinement skill's **Phase 0 triage workflow** lets you walk an existing backlog locally, decide what to keep, and let only the **accepted** items land in `xbrief/proposed/`. Trigger words: **"triage"**, **"work the cache"**, **"pre-ingest"**, **"action menu"**.
 
-**Labels first:** capacity and triage matchers only help when labels exist. For a bare or thin label set, adopt the [consumer issue-label kit](./consumer-issue-label-kit.md) (#2611) before you rely on ranking or `triage:classify -- --mirror`.
+**Labels first:** capacity and triage matchers only help when labels exist. For a bare or thin label set, adopt the [consumer issue-label kit](./consumer-issue-label-kit.md) (#2611) before you rely on ranking. `triage:classify -- --mirror` is withdrawn (#4070).
 
 ### Step 1 — Scoped first populate
 

package/docs/grok-build-subscription-setup.md

@@ -0,0 +1,146 @@
+# Grok Build subscription-only setup
+
+Agent-facing playbook for a new maintainer. Paste this file (or issue [#4035](https://github.com/deftai/directive/issues/4035)) and say: follow this playbook. The human completes browser logins when the agent stops.
+
+This is **host auth**, not Directive `session:start` and not product work in `deftai/directive`.
+
+Legend (RFC2119): `!`=MUST, `~`=SHOULD, `⊗`=MUST NOT.
+
+---
+
+## Goal
+
+Grok Build is the parent on SuperGrok (`grok login` / grok.com). Claude Code and Codex run only through their CLIs on subscriptions. Console API keys may still exist at User scope for other tools. Grok must not use those keys.
+
+## Target shape
+
+Verified 2026-08-31 on win32 (Grok 4.6 parent). Org names differ per maintainer. The auth *methods* must match.
+
+| Surface | Required auth | Must not use |
+|---|---|---|
+| Grok Build parent | grok.com / `auth.x.ai` OIDC session (`grok login`) | `XAI_API_KEY`, `GROK_CODE_XAI_API_KEY`, Console BYOK `[model.*]` |
+| Claude Code CLI | `claude.ai` team subscription (`claude auth login --claudeai`) | `ANTHROPIC_API_KEY` / `apiKeySource=ANTHROPIC_API_KEY` |
+| Codex CLI | ChatGPT (`codex login status` → ChatGPT) | `OPENAI_API_KEY` |
+
+Grok catalog (`grok models`) is only `grok-4.6` / `grok-4.5`. Default is `grok-4.6`.
+
+User-scope `ANTHROPIC_API_KEY` and `OPENAI_API_KEY` may remain for non-Grok tools. Leave them set.
+
+## Hard stops
+
+The agent MUST NOT:
+
+- implement product code while running this playbook
+- unset User-scope or Machine-scope `ANTHROPIC_API_KEY` / `OPENAI_API_KEY` / `XAI_API_KEY`
+- run `claude logout`, `codex logout`, or `grok logout`
+- add or restore BYOK `[model.*]` blocks in `~/.grok/config.toml` (opus / sonnet / fable / gpt-5.6 Console ids)
+- print secret values (print only `set=$true` / `set=$false`)
+- invent `~/.config/deft` on Windows (#2544)
+
+Config is read at Grok session start. After any `config.toml` edit, start a **new** Grok session. Mid-session children will not pick up `shell_environment_policy`.
+
+Close stdin on CLI spawns: Windows `cmd /c "… <nul"`; Unix `… </dev/null`.
+
+## Playbook
+
+### 1. Grok Build
+
+Install the Grok CLI. Put it on PATH.
+
+Human (browser): `grok login` (grok.com / SpaceXAI OAuth at `auth.x.ai`).
+
+Confirm: `grok models` prints `You are logged in with grok.com.` and lists only `grok-4.6` / `grok-4.5`.
+
+### 2. `~/.grok/config.toml`
+
+Path: `~/.grok/config.toml` (Windows: `%USERPROFILE%\.grok\config.toml`).
+
+Set:
+
+```toml
+[models]
+default = "grok-4.6"
+default_reasoning_effort = "high"
+web_search = "grok-4.6"
+
+# Grok Build must not meter Anthropic/OpenAI/xAI Console API.
+# Claude/Codex go through their CLIs (subscription).
+# User/Machine env keys stay for other tools; Grok shells do not inherit them.
+[shell_environment_policy]
+exclude = [
+  "ANTHROPIC_API_KEY",
+  "OPENAI_API_KEY",
+  "XAI_API_KEY",
+  "GROK_CODE_XAI_API_KEY",
+]
+```
+
+Remove every `[model.<id>]` table that points at Anthropic or OpenAI Console (typical leftovers: `opus-5-high-fast`, `sonnet-5`, `fable-5`, `gpt-5.6-*`). Do not add new ones.
+
+Do not copy unrelated `[ui]` personal settings from another maintainer.
+
+Then start a **new** Grok session before the probes.
+
+### 3. Claude Code CLI
+
+Install current Claude Code. On Windows a working layout is `~\.local\bin\claude.exe` plus shims (`~\.local\bin` and `%AppData%\npm` on PATH).
+
+Human (browser): `claude auth login --claudeai`. Use the team org the operator names.
+
+Confirm: `claude auth status` shows `loggedIn=true`, `authMethod=claude.ai`, `subscriptionType=team`, and **no** `apiKeySource=ANTHROPIC_API_KEY`.
+
+### 4. Codex CLI
+
+Install Codex. On Windows the hashed binary may live under `%LOCALAPPDATA%\OpenAI\Codex\bin\`; keep a `codex` shim on PATH.
+
+Human (browser): `codex login` (ChatGPT).
+
+Confirm: `codex login status` prints `Logged in using ChatGPT`.
+
+### 5. PATH
+
+User PATH includes `~/.local/bin` (Windows: `%USERPROFILE%\.local\bin`) so Grok children find `claude` and `codex` without extra env surgery.
+
+## Verification (report pass/fail with evidence)
+
+Run from a **Grok** `run_terminal_command` child after the new session. Close stdin. Never print key values.
+
+1. **Catalog.** `grok models` → only `grok-4.6` / `grok-4.5`. Fail if opus / sonnet / fable / gpt-5.6 appear in *this* catalog (Codex may still say `gpt-5.6-*` as *its* ChatGPT model; that is not Grok BYOK).
+
+2. **Env policy.** This process may still have User keys. Print only `set=$true/$false` for User / Machine / Process scope of `ANTHROPIC_API_KEY`, `OPENAI_API_KEY`, `XAI_API_KEY`, `GROK_CODE_XAI_API_KEY`. The Grok child Process-scope for `ANTHROPIC_API_KEY` and `OPENAI_API_KEY` MUST be `$false`. Fail if the child still has them — policy did not apply (old session, or config not loaded). Do not delete User keys.
+
+3. **Claude from Grok, no extra unset.** `claude auth status` as above. Then:
+
+   `claude -p "Do not use tools. Reply with the single word: pong" --output-format text`
+
+   Fail on an API-key warning or not-logged-in.
+
+4. **Codex from Grok.** `codex login status` → ChatGPT. Then:
+
+   `codex exec --ephemeral --skip-git-repo-check --sandbox read-only "Do not use tools. Reply with the single word: pong"`
+
+   Fail if it demands `OPENAI_API_KEY`.
+
+5. **Grok itself.** The session model is `grok-4.6` (or `grok-4.5`), not a Claude id. `XAI_API_KEY` unset. Auth is grok.com session (`grok models` / `~/.grok/auth.json` `auth_mode=oidc` at `auth.x.ai`). Do not dump tokens from `auth.json`.
+
+**Pass.** All five true. Grok Build is subscription-only: xAI login + Claude team + Codex ChatGPT. Keys may remain in User env for non-Grok tools.
+
+**Fail.** Child shells still inherit `ANTHROPIC_API_KEY` (old session / policy not loaded) or Claude reports `apiKeySource=ANTHROPIC_API_KEY`. Do not delete User keys. Report and stop.
+
+## Design-critique dispatch
+
+When a Grok Build parent runs an N≥3 design-critique panel, this playbook's CLIs are the other-family launchers. Probe `claude` / `codex` on PATH and CLI-spawn those seats. Paste-ready is the fallback when a CLI is absent, not the default recovery. Normative stop: [`contracts/design-critique.md`](../contracts/design-critique.md) Envelope and ceiling (#4067).
+
+## Out of scope
+
+- [#4027](https://github.com/deftai/directive/issues/4027) — N≥3 design-critique lean-timing. This playbook is host auth. Do not launch a 3-panel unless the operator asks.
+- [#2520](https://github.com/deftai/directive/issues/2520) — multi-engine least-privilege *pattern*. Related theme, different artifact.
+- Unsetting User keys that other tools still need.
+- Product code in `deftai/directive`.
+
+## Related Grok docs (local, after install)
+
+- `~/.grok/docs/user-guide/02-authentication.md` — grok.com session vs `XAI_API_KEY` fallback
+- `~/.grok/docs/user-guide/05-configuration.md` — `config.toml` precedence
+- `~/.grok/docs/user-guide/11-custom-models.md` — BYOK `[model.*]` (do not add these)
+- `~/.grok/docs/user-guide/18-sandbox.md` — `[shell_environment_policy]`

package/docs/scope-provenance.md

@@ -90,6 +90,8 @@ Flags:
 | `--xbrief-rel-path` | no | override path binding; default maps `pending/` → `active/` |
 | `--repo` | no | `owner/name` seed for preimage `approvedRepos` (same source as `issue:emit`) |
 
+Those two record kinds are **tracked provenance**, not local cache. Canonical `deft init` / `deft update` gitignore must not ignore the `.deft/approved-scope/` directory. Crash-journal, lock, and `.next` sidecars in that directory stay ignored. `git add` of the two record files must work without `-f`. Leftover directory ignore lines (both slash spellings) are healed off on update.
+
 Commit **both** `.deft/approved-scope/<plan-id>.json` and `<plan-id>.intent.json` on the **merge base** (or a prior PR) before the implementation PR activates or expands the scoped xBRIEF. Read the preimage before you commit — that file is the approved intent.
 
 ## Three layers (do not mix)
@@ -156,3 +158,29 @@ git add .deft/approved-scope/<plan-id>.json .deft/approved-scope/<plan-id>.inten
 ```
 
 Editing the xBRIEF alone does not authorize new implementation paths.
+
+
+## Cohort-created scope (operator mint at allocation) (#3874)
+
+If a swarm cohort brief should declare `file_scope`, the operator who approved
+the cohort mints the digest on a real TTY at allocation time and lands
+`.deft/approved-scope/<plan-id>.json` on the merge base before workers activate.
+
+- Allocation-context tokens (#1378) are **not** provenance.
+- Swarm briefs are **not** exempt from this gate.
+- `#3110` human-presence mint and merge-base layering are unchanged.
+
+If the operator does not mint, omit `file_scope` when authoring the cohort brief.
+Undeclared cohort briefs are then a deliberate outcome, not a post-failure
+workaround. Do not undeclare a declared `file_scope` to pass the gate.
+
+## Working-tree / untracked files
+
+`verify:scope-provenance` unions:
+
+1. `git diff --name-only <base>...HEAD`
+2. `git diff --name-only HEAD`
+3. `git ls-files --others --exclude-standard`
+
+and lists on-disk `xbrief/active/` files. Presence in the working tree is what
+matters. Committing or not committing the brief does not hide it from the gate.

package/docs/test-boundary.md

@@ -1,6 +1,8 @@
 # Test / source boundary (`verify:test-boundary`)
 
-Refs: #3145 · Related: #1310 forward-coverage, testing layout guidance
+Refs: #3145 · Related: #1310 / #4009 forward-coverage, testing layout guidance
+
+`verify:forward-coverage` reuses this policy for source-to-test correspondence. It does not add a second testRoots config.
 
 ## Problem
 

package/main.md

@@ -10,7 +10,7 @@ Foundational guidelines for AI agent behavior in the Deft framework.
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ Rule Precedence**: USER.md has two sections: `Personal` (always wins — name, custom rules) and `Defaults` (fallback — strategy, coverage, languages; PROJECT-DEFINITION.vbrief.json overrides these). (Override path via `DEFT_USER_PATH` env var; )
+**⚠️ Rule Precedence**: USER.md has two sections: `Personal` (always wins — name, custom rules) and `Defaults` (fallback — strategy, coverage, languages; PROJECT-DEFINITION.xbrief.json overrides these). (Override path via `DEFT_USER_PATH` env var; )
 
 **📋 Lazy Loading**: See `npx deft packs:slice skills list` (Skills Index; `REFERENCES.md` is maintainer-only and does not ship) for guidance on when to load which files.
 
@@ -26,7 +26,7 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 - `main.md` - General AI behavior (this document)
 - [coding/coding.md](./coding/coding.md) - Software development guidelines
 - `~/.config/deft/USER.md` - Personal preferences (highest precedence)
-- `./vbrief/PROJECT-DEFINITION.vbrief.json` - Project identity gestalt and scope registry
+- `./xbrief/PROJECT-DEFINITION.xbrief.json` - Project identity gestalt and scope registry
 
 **Coding-Specific:**
 - Languages: [languages/cpp.md](./languages/cpp.md), [languages/go.md](./languages/go.md), [languages/officejs.md](./languages/officejs.md), [languages/python.md](./languages/python.md), [languages/typescript.md](./languages/typescript.md), [languages/vba.md](./languages/vba.md)
@@ -191,21 +191,21 @@ Source material: AI Agent Traps paper (`docs/ssrn-6372438.pdf`, Franklin et al.,
 
 Propagation: the canonical orchestrator preamble at [templates/agent-prompt-preamble.md](./templates/agent-prompt-preamble.md) carries the same rule so dispatched workers inherit the behavior. This is the same class as the approval-fatigue defense above (`## Agent Trap Defenses`) applied to a different surface -- "you cancelled" is a buried mis-attribution that the rule corrects with the same fail-loud / surface-the-anomaly discipline.
 
-## vBRIEF Persistence
+## xBRIEF Persistence
 
-- ! All vBRIEF files MUST be stored in `./vbrief/` or its lifecycle subfolders — never in workspace root
-- ! Use `PROJECT-DEFINITION.vbrief.json` (singular) as the project identity gestalt — narratives for identity, items as scope registry
-- ! Use `plan.vbrief.json` (singular) for session-level tactical plans and progress tracking
-- ! Use `continue.vbrief.json` (singular) for interruption recovery checkpoints
-- ! Specifications are written as `specification.vbrief.json`, then rendered to `.md`
-- ! Scope vBRIEFs live in lifecycle folders: `proposed/`, `pending/`, `active/`, `completed/`, `cancelled/`
-- ! Scope vBRIEF filenames MUST follow: `YYYY-MM-DD-descriptive-slug.vbrief.json` (slug rules: [`conventions/vbrief-filenames.md`](./conventions/vbrief-filenames.md))
-- ! Playbooks use `playbook-{name}.vbrief.json` (named, not ULID-suffixed)
+- ! All xBRIEF files MUST be stored in `./xbrief/` or its lifecycle subfolders — never in workspace root
+- ! Use `PROJECT-DEFINITION.xbrief.json` (singular) as the project identity gestalt — narratives for identity, items as scope registry
+- ! Use `plan.xbrief.json` (singular) for session-level tactical plans and progress tracking
+- ! Use `continue.xbrief.json` (singular) for interruption recovery checkpoints
+- ! Specifications are written as `specification.xbrief.json`, then rendered to `.md`
+- ! Scope xBRIEFs live in lifecycle folders: `proposed/`, `pending/`, `active/`, `completed/`, `cancelled/`
+- ! Scope xBRIEF filenames MUST follow: `YYYY-MM-DD-descriptive-slug.xbrief.json` (slug rules: [`conventions/vbrief-filenames.md`](./conventions/vbrief-filenames.md))
+- ! Playbooks use `playbook-{name}.xbrief.json` (named, not ULID-suffixed)
 - ! Completed xBRIEFs are evidence of what was built — full standing as a record of *what is*, zero authority over *what to build next* (#3383). The current contract is the active xBRIEF plus the human operator's live instruction. Both halves are required.
 - ⊗ Use ULID-suffixed filenames for plan, todo, or continue files
-- ⊗ Place vBRIEF files at workspace root
-- ⊗ Write `SPECIFICATION.md` directly — it MUST be generated from `specification.vbrief.json`
-- ⊗ Move scope vBRIEFs between lifecycle folders without updating `plan.status`
+- ⊗ Place xBRIEF files at workspace root
+- ⊗ Write `SPECIFICATION.md` directly — it MUST be generated from `specification.xbrief.json`
+- ⊗ Move scope xBRIEFs between lifecycle folders without updating `plan.status`
 - ⊗ Treat a completed xBRIEF as the next-build contract, or let it override the active story or the live human instruction
 
 ### Schema version: v0.8 (canonical write)
@@ -230,10 +230,10 @@ Projects that pre-date v0.20 (pre-vBRIEF-centric model) must migrate on a **pinn
 
 A consumer project is **pre-cutover** if ANY of these hold:
 
-- `SPECIFICATION.md` exists at the project root and is neither a deprecation redirect nor a current generated spec export. A current generated spec export contains `<!-- Purpose: rendered specification -->` and `<!-- Source of truth: vbrief/specification.vbrief.json -->`, and `vbrief/specification.vbrief.json` plus all five lifecycle folders exist.
+- `SPECIFICATION.md` exists at the project root and is neither a deprecation redirect nor a current generated spec export. A current generated spec export contains `<!-- Purpose: rendered specification -->` and a layout-resolved `<!-- Source of truth: ... -->` line for the specification artifact (`xbrief/specification.xbrief.json` on a migrated tree), and that artifact plus all five lifecycle folders exist.
 - `PROJECT.md` exists at the project root and is not a deprecation redirect (`<!-- deft:deprecated-redirect -->` or `<!-- Purpose: deprecation redirect -->`)
-- `vbrief/` exists but one or more of the five lifecycle subfolders (`proposed/`, `pending/`, `active/`, `completed/`, `cancelled/`) is missing
-- `vbrief/PROJECT-DEFINITION.vbrief.json` is absent on a project that otherwise looks set up
+- `xbrief/` exists but one or more of the five lifecycle subfolders (`proposed/`, `pending/`, `active/`, `completed/`, `cancelled/`) is missing
+- `xbrief/PROJECT-DEFINITION.xbrief.json` is absent on a project that otherwise looks set up
 
 The executable detection helper is `task migrate:preflight`. The full agent-facing flow lives in [QUICK-START.md](./QUICK-START.md) Step 2 and in [skills/deft-directive-setup/SKILL.md](./skills/deft-directive-setup/SKILL.md) (Pre-Cutover Detection Guard).
 
@@ -275,7 +275,7 @@ After migration completes, upgrade to current npm per [UPGRADING.md](./UPGRADING
 
 ### What migration produces
 
-The migrator replaces `SPECIFICATION.md` and `PROJECT.md` with deprecation-redirect stubs (both carry the `<!-- deft:deprecated-redirect -->` sentinel) and writes:
+**Legacy (frozen v0.59.0 `task migrate:vbrief` only — not a current write path; do not reverse #2907).** The migrator replaces `SPECIFICATION.md` and `PROJECT.md` with deprecation-redirect stubs (both carry the `<!-- deft:deprecated-redirect -->` sentinel) and writes:
 
 - `vbrief/PROJECT-DEFINITION.vbrief.json` — project identity gestalt (narratives + items registry)
 - `vbrief/specification.vbrief.json` — design narratives and requirements
@@ -366,18 +366,18 @@ See [commands.md](./commands.md) for full workflow details.
 ### Session
 
 - `/deft:continue` — Resume from continue checkpoint ([resilience/continue-here.md](./resilience/continue-here.md))
-- `/deft:checkpoint` — Save session state to `./vbrief/continue.vbrief.json`
+- `/deft:checkpoint` — Save session state to `./xbrief/continue.xbrief.json`
 
 ## Context Awareness
 
 **Project Context:**
-- ! Check `./vbrief/PROJECT-DEFINITION.vbrief.json` (in your consumer project) for project-specific rules and scope registry
+- ! Check `./xbrief/PROJECT-DEFINITION.xbrief.json` (in your consumer project) for project-specific rules and scope registry
 - ! Follow project-specific patterns and conventions
 - ~ Note which rules/patterns are being applied
 
 **User Context:**
 - ! Respect `~/.config/deft/USER.md` Personal section (highest precedence)
-- ! For project-scoped settings, PROJECT-DEFINITION.vbrief.json overrides USER.md Defaults
+- ! For project-scoped settings, PROJECT-DEFINITION.xbrief.json overrides USER.md Defaults
 - ! Remember user's maintained projects and their purposes
 - ~ Adapt communication style to user's expertise level
 
@@ -389,4 +389,4 @@ See [commands.md](./commands.md) for full workflow details.
 
 **Context Engineering:**
 - ~ See [context/context.md](./context/context.md) for strategies on managing context budget
-- ~ Use vBRIEF ([vbrief.org](https://vbrief.org)) for structured task plans, scratchpads, and checkpoints
+- ~ Use xBRIEF for structured task plans, scratchpads, and checkpoints

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deftai/directive-content",
-  "version": "0.109.1",
+  "version": "0.111.0",
   "deftConsumerDeposit": true,
   "description": "Shippable Directive framework content in the consumer .deft/core/ layout (C1 flatten), plus the engine surfaces (.githooks/, Taskfile.yml, tasks/) the deposit wires. Python-free per #2022 Phase 3. Refs #11, #1669, #1967.",
   "license": "MIT",

package/packs/rules/rules-pack-0.1.json

@@ -3839,7 +3839,7 @@
       "id": "agents-029",
       "tier": "MUST",
       "domain": "agents",
-      "text": "**Worker-owns-lifecycle (Gap C):** When dispatching an implementation worker, the envelope MUST declare `stop-at: pr-open` OR `drive-to: merge-ready` (default for story work). Workers scoped `drive-to: merge-ready` own PR + review cycle + fix batches through merge-ready as ONE unit of work \u2014 they spawn their own review poller per review-cycle monitoring tiers; the orchestrator MUST NOT hand back at PR-open and re-dispatch separate leaf agents for review/fixes.",
+      "text": "**Worker-owns-lifecycle (Gap C):** When dispatching an implementation worker, the envelope MUST declare `stop-at: pr-open` OR `drive-to: merge-ready` (default for story work). Workers scoped `drive-to: merge-ready` own PR + review cycle + fix batches through merge-ready as ONE unit of work \u2014 following review-cycle monitoring tiers (Grok Build / Cursor / Claude Code leaves that cannot nest block on `pr:watch` in-process and MUST NOT spawn a child poller) (#4130); the orchestrator MUST NOT hand back at PR-open and re-dispatch separate leaf agents for review/fixes.",
       "path": "AGENTS.md",
       "body": null
     },