@deftai/directive-content 0.90.0 → 0.92.0

package/QUICK-START.md

@@ -155,7 +155,7 @@ Read and follow `../AGENTS.md`. This starts the normal first-session flow (user
 
 **Writing pointer:** For docs, issues, and PR prose that maintainers or agents author, follow [docs/writing-ste100.md](./docs/writing-ste100.md) (short controlled English; #2927).
 
-**Opt-out pointer:** Projects that must not use Directive should commit root [`.no-deft-directive`](./docs/no-deft-directive.md) so session/doctor/init/setup skip install and ritual (#2926).
+**Opt-out pointer:** Projects that must not use Directive should commit root [`.no-deft-directive`](./docs/no-deft-directive.md) so session/doctor/init/setup skip install and ritual (#2926). Temporary local kill-switch (deposit OK): [`.deft-directive-disable`](./docs/deft-directive-disable.md) (#3039).
 
 **Contributor pointer (non-blocking):** Working on Deft itself (a `deftai/directive` source checkout)? See [CONTRIBUTING.md](../CONTRIBUTING.md) and use the maintainer install path (`deft-install --yes --upgrade --maintainer --repo-root . --json`). The repo's root `AGENTS.md` has contributor instructions — you do not need the consumer first-session flow above.
 

package/coding/coding.md

@@ -4,6 +4,7 @@
 <!-- Regenerate with: task packs:render -->
 <!-- Edit the source, not this file. Slice instead of loading every coding doc: task packs:slice rules by-tier --tier <TIER> (or by-domain, list) -->
 
+
 # Coding Guidelines
 
 Software development specific guidelines for AI agents.
@@ -83,6 +84,13 @@ See [../scm/git.md](../scm/git.md) for:
 - ! Comments explain **why**, code shows **what**
 - ⊗ Clever code over clear code
 
+**State & Data Modeling (#1695):**
+- ! A field MUST encode exactly one fact. Do NOT overload a field's value — or its presence/absence — to also signal a second orthogonal concern. Smuggling decision-, config-, lifecycle-, or control-state through a data field is *in-band signaling*; give that signal its own out-of-band field.
+- ! "Absence is not a decision." Distinguish "unset / never considered" from "deliberately set to the default." If a workflow must know a human made a choice, record the choice explicitly — never infer it from whether a value-field is present.
+- ~ Orthogonality test: if two facts can vary independently (e.g. value==default while decided ∈ {true,false}), they MUST live in separate slots. If one fact strictly implies the other (true Optional<T>, tombstones), sharing a slot is fine.
+- ⊗ Infer decision / onboarding / configuration state from the presence of a value field. Use an explicit out-of-band marker — cf. the resolver `source` provenance pattern (typed | default | default-on-error) directive already uses for *value*-provenance.
+- See [../patterns/in-band-signaling.md](../patterns/in-band-signaling.md) for the full model, orthogonality procedure, and the wipCap worked example (#1694).
+
 ## Quality Standards
 
 **General:**

package/commands.md

@@ -90,6 +90,7 @@ Scope xBRIEFs live under `xbrief/{proposed,pending,active,completed,cancelled}/`
 Common commands:
 
 - `task scope:promote -- xbrief/proposed/<file>.xbrief.json` -- move proposed work to `pending/` and set status to `pending`.
+- `task scope:promote -- --batch` -- batch-promote **all** `xbrief/proposed/` scopes to `pending/` in one command (#3011 / epic #3009). Optional: `--batch <path>…` for an explicit list; `--force` overrides WIP cap (logged). Does **not** activate; implement remains one `scope:activate` at a time.
 - `task scope:activate -- xbrief/pending/<file>.xbrief.json` -- move accepted work to `active/` and set status to `running`.
 - `task scope:complete -- xbrief/active/<file>.xbrief.json` -- move running work to `completed/` and set status to `completed`.
 - `task scope:fail -- xbrief/active/<file>.xbrief.json` -- mark running work failed when the scope cannot complete.
@@ -109,7 +110,9 @@ deft xbrief:preflight -- xbrief/active/<file>.xbrief.json
 
 Gate 0 `task verify:story-ready` machine-checks working-tree cleanliness (or `--allow-dirty`), the target xBRIEF in `xbrief/active/` with `plan.status == "running"`, and the dispatch envelope's `## Allocation context` consent token (#1378). A `swarm-cohort` section is ready only when `allocation_plan_id` AND `batching_rationale` are non-null. Complete stories with `task scope:complete -- <active-story-path>`.
 
-**Story Start Gate (#1378):** Before starting any new implementation story or switching stories, run `git status --short --branch`. If the working tree is dirty, stop and summarize the current branch, modified/untracked files, and whether the changes appear related to the next story — ask the operator to choose: commit existing work, stash existing work, include existing work in the current story, or stop. ⊗ Do not begin a new story while unrelated dirty work is present without explicit operator approval. When invoked as part of a swarm cohort dispatch, the approved Phase 5 allocation plan satisfies batching consent (#954); between stories checkpoint-commit it and proceed — do not pause to ask the operator mid-cohort. Promote/activate via `task scope:promote -- <path>` / `task scope:activate -- <path>`; preflight with `deft xbrief:preflight -- <active-story-path>`.
+**Story Start Gate (#1378):** Before starting any new implementation story or switching stories, run `git status --short --branch`. If the working tree is dirty, stop and summarize the current branch, modified/untracked files, and whether the changes appear related to the next story — ask the operator to choose: commit existing work, stash existing work, include existing work in the current story, or stop. ⊗ Do not begin a new story while unrelated dirty work is present without explicit operator approval. When invoked as part of a swarm cohort dispatch, the approved Phase 5 allocation plan satisfies batching consent (#954); between stories checkpoint-commit it and proceed — do not pause to ask the operator mid-cohort. Promote/activate via `task scope:promote -- <path>` (or `task scope:promote -- --batch` for multi-scope pins, #3011) / `task scope:activate -- <path>`; preflight with `deft xbrief:preflight -- <active-story-path>`.
+
+**Multi-scope turn/cache budget (#3009):** After offline seed (init + pin scopes + session ritual), implement agents ⊗ re-run `directive init`, cold `session:start`, migrate, or re-copy scopes — recover with `session:ready` / re-arm only (#3010). Batch-promote the pin; activate+implement one scope at a time (#3011). Run full `task check` once at end of the multi-scope batch unless the last check failed (#3012). Init seeds a minimal render-ready `PROJECT-DEFINITION`; treat `project:render` as a one-shot lifecycle refresh, not identity research (#3013).
 
 The implementation gate succeeds only for active scope xBRIEFs with `plan.status == "running"`. Do not infer implementation intent from lifecycle vocabulary — require explicit action-verb directives (`build`, `implement`, `ship`, `swarm`, `run agents`, `start agent`) per #810.
 
@@ -140,9 +143,11 @@ flowchart TD
 
 Edit the xBRIEF source, then render the markdown view.
 
-- `task spec:render` -- render `xbrief/specification.xbrief.json` to `SPECIFICATION.md`.
+- `task spec:render` -- render `xbrief/specification.xbrief.json` to a **compact** `SPECIFICATION.md` by default (#1566). Defaults: no lifecycle Scope outlook, no `LegacyArtifacts`. Opt in with engine flags passed after `--`:
+  - `--include-scopes=off` (default) / `current` (pending+active) / `all` (include completed archive)
+  - `--include-legacy-artifacts=on|off` (default off)
 - `task prd:render` -- render a stakeholder PRD view from the specification xBRIEF.
-- `task roadmap:render` -- render `ROADMAP.md` from lifecycle scope xBRIEFs.
+- `task roadmap:render` -- render `ROADMAP.md` from lifecycle scope xBRIEFs (`pending/` + `proposed/` + `active/` forward; `completed/` capped).
 - `task project:render` -- refresh the `PROJECT-DEFINITION.xbrief.json` items registry from lifecycle folders.
 - `deft xbrief:validate` -- validate xBRIEF schema, filenames, folders, statuses, and cross-file consistency.
 - `deft migrate:xbrief` (or `task migrate:xbrief`) -- convert a legacy `vbrief/` project tree to `xbrief/` (v0.6→v0.8 semantic transforms; requires clean working tree unless `--force`). Legacy `vbrief/` and `x-vbrief/` tokens remain read-accepted until this runs.
@@ -279,6 +284,17 @@ Full always-on contract for the interactive session-start ritual and its gated v
 
 Agents use this signal to prefer portable syntax and quote zsh-sensitive data such as globs, tildes, `~N`, `!`, and `#`. When a command requires Bash, zsh, PowerShell, or another shell's behavior, invoke that explicit shell rather than relying on implicit execution semantics.
 
+### SCM readiness orientation (#2275)
+
+`session:start` also reports whether GitHub SCM tooling is usable **in this execution env** (not the install host). Human output includes `[deft scm]` lines; `--json` includes a `scm` object (`ready`, `binary`, `auth_state`, `github_auth_mode`, `runtime_mode`, `injected_token_present`, `skipped_gates`, `detail`, ...). Cold mutation records a `scm_readiness` step in `steps[]`.
+
+- Shallow probe (default hot path): PATH ladder `ghx` > `gh`, injected-token env presence, short `gh auth status`.
+- Deep probe when `--with-network` / `DEFT_SESSION_START_NETWORK=1`: full `github-auth-modes` validation (API + optional repo).
+- Session-start never hard-blocks on SCM absence (framework-local gates still run). When not ready it lists skipped SCM-dependent gates (`triage:queue`, `issue:ingest`, `pr:*`, `reconcile:issues`, `cache:fetch-all`, `scm:*`, ...).
+- Explicit probe: `deft scm:status` (alias `scm:readiness`) -- exit `0` ready / `1` not ready / `2` config; flags `--json`, `--deep` / `--shallow`.
+- Credential bridging: host-gh (`gh auth login` in the execution env) or injected-token (`GH_TOKEN` / `GITHUB_TOKEN` / `GH_ENTERPRISE_TOKEN`). Never put token values in prompts or transcripts.
+- Contract: `content/contracts/scm-readiness.md`; operator docs: `content/scm/github.md` § Mismatched/headless SCM readiness.
+
 **Pre-`start_agent` gate stack (#1149/#1348):** (0) `deft verify:session-ritual -- --tier=gated` → (1) `deft verify:story-ready` → (2) `deft xbrief:preflight` → (3) `deft verify:cache-fresh` → (4) `deft verify:branch` + hooks → (5) `start_agent`.
 
 ```mermaid
@@ -302,7 +318,7 @@ Local ceremony cost signal for WWYSYDH / weekly process rollups. Emits to `.deft
 | Session start (cold) | `session:start` | Mutation `session:start` cold path finishes | `ceremony_tier=cold`, `duration_ms`, `exit_code`, `steps[]` |
 | Session re-arm | `session:start` | `session:start --rearm` finishes | `ceremony_tier=rearm`, `duration_ms`, `exit_code`, `steps[]` |
 | PreToolUse ritual deny | `session:ritual-blocked` | Hook blocks write/spawn because gated ritual is not ready | `tool_name`, `code=ritual-not-ready`, `recovery_tier` (`cold`\|`rearm`) |
-| Per-step wall-clock | (field on `session:start`) | Same emit as session start | `steps[].name` + `steps[].duration_ms` (`alignment`, `branch_policy`, `verify_tools`, `triage_welcome`, `release_probe`, `ritual_write`) |
+| Per-step wall-clock | (field on `session:start`) | Same emit as session start | `steps[].name` + `steps[].duration_ms` (`alignment`, `scm_readiness`, `branch_policy`, `verify_tools`, `triage_welcome`, `release_probe`, `ritual_write`) |
 
 CLI mirror (no JSONL required): `deft session:start --json` already exposes the same `steps` / `duration_ms` / `ceremony_tier` fields for one-shot inspection.
 
@@ -414,6 +430,7 @@ flowchart TD
 
 - `task packs:*` -- render and verify content packs.
 - `task pr:*` -- protected issue checks, closing-keyword checks, merge readiness, and merge helpers.
+  - `task pr:check-closing-keywords` -- Layer 0 FP lint (#737) **plus intent mode** (#3015 class D). Default `--mode both`: fails on negation/quote/example/code-block hits **and** on any real `Closes|Fixes|Resolves #N` unless allowlisted via `--allow-close N,M` (CLI only; body trailers are not an authorization path). Offline: `--body-file` / `--commits-file`. Prefer `Tracking: #N` / `Refs #N` until full issue DoD.
 - `task release:*` -- release, publish, rollback, and e2e release rehearsal.
   - Step 3 (`Pre-flight vBRIEF lifecycle sync`) fetches GitHub issue states via REST. On HTTP 403 rate-limit exhaustion it sleeps once (capped at 120s) and retries before failing.
   - When Step 3 still fails with rate-limit exhaustion, stderr includes a `gh api rate_limit` probe (`core.remaining`, reset time) and recovery guidance. After local `task vbrief:validate` (or `task xbrief:validate`) exits 0, operators may pass `--allow-vbrief-drift` to skip Step 3 for that cut — reserved for transient SCM bucket stalls, not unreviewed lifecycle drift.

package/contracts/scm-readiness.md

@@ -0,0 +1,78 @@
+# Contract: SCM readiness in mismatched / headless envs (#2275)
+
+Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
+
+**Parent:** issue #2275 (follow-up to #2203 Decision 7). Sibling of USER.md
+resolution (#2271).
+
+## Problem
+
+In agentic sandboxes, execution-env often differs from install-env: `gh` /
+`ghx` may be absent or unauthenticated even when the host desktop is fully
+set up. SCM-dependent gates then fail opaquely (spawn errors, hung auth
+prompts) while framework-local gates still work.
+
+## Gate classes
+
+### Framework-local (no SCM required)
+
+`session:start`, `session:ready`, `verify:session-ritual`, `verify:tools`
+(orientation), `verify:branch`, `xbrief:preflight`, `doctor` (offline),
+`scope:*`, local cache-fresh / ritual state.
+
+These ! run regardless of SCM readiness.
+
+### SCM-dependent (require binary + auth)
+
+At minimum: `triage:queue`, `triage:welcome` network hydrate, `issue:ingest`,
+`reconcile:issues`, `pr:*`, `cache:fetch-all`, `scm:*` issue ops,
+`umbrella:current-shape` live fetch, deep `github-auth-modes`.
+
+These ! either run when ready or fail loud with a named reason. They ⊗ hang
+on interactive auth prompts in headless envs without a clear diagnostic.
+
+## Probe surface
+
+| Surface | Depth | Blocks session? |
+| --- | --- | --- |
+| `session:start` default | shallow (PATH + token + `gh auth status`) | no |
+| `session:start --with-network` | deep (API + optional repo) | no |
+| `deft scm:status` | shallow default; `--deep` opt-in | n/a (exit 0/1/2) |
+| `deft github-auth-modes` | mode validation (#1557) | n/a |
+
+JSON field shape (`session:start --json` → `scm`, or `scm:status --json`):
+
+- `ready` (bool)
+- `binary` (`ghx` \| `gh` \| null)
+- `binary_path`
+- `auth_state` (`authenticated` \| `unauthenticated` \| `missing-token` \|
+  `binary-absent` \| `unknown`)
+- `github_auth_mode` (`host-gh` \| `injected-token`)
+- `runtime_mode`
+- `injected_token_present` (bool; never the value)
+- `depth` (`shallow` \| `deep`)
+- `detail` (one-line human diagnostic)
+- `remediation` (string \| null)
+- `skipped_gates` (string[])
+- `login` (string \| null; deep only)
+- `failure_kind` (string \| null)
+
+## Remediation contract
+
+When not ready, agents ! prefer one of:
+
+1. Install + auth in the **execution** env (`gh` / `ghx`, then
+   `gh auth login` for host-gh).
+2. Inject `GH_TOKEN` / `GITHUB_TOKEN` / `GH_ENTERPRISE_TOKEN` for
+   injected-token / cloud-headless mode.
+3. Run SCM-dependent gates from a matched authenticated environment.
+
+⊗ Put token values into prompts, dispatch envelopes, or logs.
+
+## Implementation anchors
+
+- Probe: `packages/core/src/scm/readiness.ts`
+- CLI: `packages/core/src/scm/readiness-cli.ts` (`scm:status`)
+- Session orientation: `packages/core/src/session/session-start.ts`
+- Auth modes: `packages/core/src/intake/github-auth-modes.ts` (#1557)
+- Operator docs: `content/scm/github.md` § Mismatched/headless SCM readiness

package/docs/deft-directive-disable.md

@@ -0,0 +1,96 @@
+# Temporary kill-switch: `.deft-directive-disable`
+
+Use a **root file flag** to turn Directive **enforcement** off for local testing (A/B, DevHammer, ceremony vs loop) **without** permanent project opt-out and **without** deleting the deposit.
+
+Tracker: [#3039](https://github.com/deftai/directive/issues/3039).
+
+**Not** permanent opt-out — that is [`.no-deft-directive`](./no-deft-directive.md) (#2926).
+
+## Filename and location
+
+```text
+.deft-directive-disable
+```
+
+- **Exact name:** lowercase `.deft-directive-disable`
+- **Location:** project / workspace **root only**
+- **Content:** empty file or a short `#` comment. Presence is the flag. No schema.
+- **Git:** **Must be gitignored** (deposit baseline includes this entry). Committed / tracked flag is a misconfig: doctor **warns**, and enforcement is **not** disabled (repo-controlled content must not turn off hooks for clones).
+
+## Distinct from permanent opt-out
+
+| File | Intent |
+|------|--------|
+| [`.no-deft-directive`](./no-deft-directive.md) | Permanent: project does not use Directive. Flag + deposit is **inconsistent**. |
+| `.deft-directive-disable` | Temporary: testing kill-switch. **Deposit OK**. |
+
+## Behavior
+
+| Surface | When flag present |
+|---------|-------------------|
+| **Doctor** | Status **disabled (test kill-switch)**; **not** the #2926 flag+deposit dirty path; prints full recovery (file gone + new session). |
+| **Agent** | Always-on AGENTS contract: stop further Directive process load; echo recovery. |
+| **CLI** (`session:start`, ritual paths) | Disabled + recovery; no ritual write / no half-DD automation. |
+| **Host hooks** | SessionStart / PreToolUse / compact skip ritual and enforcement. |
+
+Deposit (`.deft/core`) **may remain**. Init/update are not blocked by this flag alone (unlike permanent opt-out).
+
+## Recovery (hysteresis)
+
+Directive is **fully operational** only when:
+
+1. **`.deft-directive-disable` is absent**, and
+2. A **new agent session** has been started after the file was removed
+
+Canonical recovery message:
+
+```text
+Directive is DISABLED for this project via root `.deft-directive-disable` (test/local kill-switch).
+Deposit may still be present; enforcement (hooks, session ritual, automation) will not run.
+
+To fully re-enable Directive:
+  1. Delete the file:  rm .deft-directive-disable   (or equivalent)
+  2. Start a NEW agent session (reload AGENTS / host skills / hooks)
+Until both are done, Directive is not fully operational.
+```
+
+## Precedence
+
+1. `.deft-directive-disable` → test kill-switch (deposit OK; recovery = delete + new session)
+2. `.no-deft-directive` → permanent opt-out (#2926)
+3. Else normal Directive
+
+If **both** flags are present: one combined message; permanent install semantics still apply for init/update.
+
+## Consumer note (A/B / DevHammer)
+
+Typical arm for “without Directive enforcement”:
+
+```bash
+# Ensure ignore entry exists (init/update baseline)
+# Then:
+touch .deft-directive-disable
+# Start a new agent session — enforcement off; deposit may stay.
+```
+
+Re-enable:
+
+```bash
+rm .deft-directive-disable
+# Start a NEW agent session
+```
+
+## Non-goals (v1)
+
+- ⊗ Auto-delete `.deft/` or uninstall deposit
+- ⊗ Replace or weaken `.no-deft-directive`
+- ⊗ Rewrite AGENTS to a stub on disable
+- ⊗ Org-remote kill switch
+- ⊗ Nested monorepo package roots
+- ⊗ `DEFT_DISABLED=1` env (optional later)
+
+## Related
+
+- [no-deft-directive.md](./no-deft-directive.md) — permanent opt-out
+- [getting-started.md](./getting-started.md) — install and first project
+- `session:start`, `doctor`, host hooks (SessionStart / PreToolUse / compact)

package/docs/directive-lifecycle.md

@@ -65,6 +65,22 @@ framework:
 | **Ship** | PR merge and release — `task pr:*` and [`deft-directive-release`](../skills/deft-directive-release/SKILL.md). |
 | **Issues / Features** | GitHub issues and feature requests mirrored into `.deft-cache/` and surfaced as triage candidates. |
 
+## Delivery integrity vs deploy / UAT (#3041)
+
+`scope:complete` and swarm cohort completion mark **lifecycle bookkeeping**, not environment
+green. For **code-bearing** scopes, delivered completion requires durable proof that the
+implementation reached the configured **delivery branch** (`plan.policy.deliveryBranch`,
+defaulting to the repo default branch) — typically: PR `base.ref` equals that branch, and the
+merge commit is an ancestor of the refreshed remote delivery ref. A merge into an intermediate
+feature/integration branch is **not** delivery.
+
+Handoff states that Git can assert are distinct: `implemented` → `pr_open` →
+`merged_to_integration` → `delivered`. **Deployed** and **UAT verified** are separate evidence
+axes and are never inferred from Git alone. Explicit non-delivery dispositions
+(`accepted_not_delivered`, `superseded`, `experiment_archived`, `cancelled`) complete the
+lifecycle without claiming the work shipped. Legacy completed records without completion
+provenance surface as `unknown` / `unverified`, not retroactively `delivered`.
+
 ## Why it loops
 
 The central claim of the picture is that Directive is **reiterative**. Strategy analysis is

package/docs/getting-started.md

@@ -145,3 +145,5 @@ Full command reference for every triage and cache verb lives in [`commands.md`
 **Writing:** For docs, issues, and PR prose, follow [writing-ste100.md](./writing-ste100.md) (short controlled English; #2927).
 
 **Opt out:** To mark a repo as not using Directive, add root [`.no-deft-directive`](./no-deft-directive.md) (#2926). Tools skip install and session ritual when that file is present.
+
+**Temporary test kill-switch:** For local A/B or DevHammer without permanent opt-out, use root [`.deft-directive-disable`](./deft-directive-disable.md) (#3039). Deposit may stay; re-enable by deleting the file and starting a new agent session.

package/docs/no-deft-directive.md

@@ -82,6 +82,7 @@ When `deft-directive-setup` runs:
 
 ## Related
 
+- [deft-directive-disable.md](./deft-directive-disable.md) — **temporary** test/local kill-switch (deposit OK; not this flag)
 - [getting-started.md](./getting-started.md) — install and first project
 - [product-signal.md](./product-signal.md) — optional partner signal (defaults off; flag still wins locally)
 - `session:start`, `doctor`, `directive init`, `directive update`

package/docs/openclaw-agent-host.md

@@ -142,9 +142,9 @@ When OpenClaw signals are present (`OPENCLAW` / `DEFT_PROBE_OPENCLAW` / `DEFT_AG
 deft doctor --fix
 ```
 
-Doctor links (preferred) or copies the four pin directories from the installed content package (`@deftai/directive-content` / `content/skills/…`) into the main OpenClaw skills root. It does **not** delete other user skills (e.g. a local `vbrief` skill stays). Divergent same-named directories are left alone unless you pass `--force` or confirm on a TTY.
+Doctor **copies** the four pin directories from the installed content package (`@deftai/directive-content` / `content/skills/…`) into the main OpenClaw skills root as **real directories** (#3008). It does **not** symlink into the npm tree — OpenClaw 2026.7.x skips workspace skills that resolve outside the skills root (`reason=symlink-escape`), which made pre-#3008 symlink installs look healthy in doctor while `openclaw skills list` never loaded the pins. It does **not** delete other user skills (e.g. a local `vbrief` skill stays). Divergent same-named directories **and escaping symlinks** are left alone unless you pass `--force` or confirm on a TTY (then replaced with a real copy).
 
-After a successful wire: **restart the OpenClaw gateway or start a new session** so host `available_skills` refreshes.
+After a successful wire: **restart the OpenClaw gateway or start a new session** so host `available_skills` refreshes. Confirm with `openclaw skills list` that the four always-pins are **ready**, not skipped.
 
 ### Multi-seat / crew workspaces
 

package/docs/skill-pin-policy.md

@@ -69,9 +69,16 @@ The managed AGENTS.md section `## Skill pin policy (#2508)` carries the framewor
 
 Skills-pack entries (`content/packs/skills/skills-pack-0.1.json`) MAY record `"alwaysPin": true` on metadata-only rows so slice tooling and future gates can list pins without parsing AGENTS.md. The authoritative runtime list for agents remains the AGENTS.md pin section; the catalog field is advisory for tooling (#1535).
 
+## Through-merge is false-negative sensitive (#3032)
+
+Operator phrases such as **through merge**, **drive to merge**, **land/ship issue**, or explicit **drive-to: merge-ready** often start implementation **without** a clear `swarm` keyword. That is the same false-negative class this policy targets: the parent may code instead of loading `deft-directive-swarm` and dispatching a worker.
+
+! AGENTS.md carries short always-on `!` / `⊗` bullets under **Through-merge worker dispatch (#3032)** (agents-entry + maintainer multi-agent doctrine). N=1 still uses the swarm/solo launch path; parent MUST NOT implement when background subagent/worktree dispatch is available. See also swarm Phase 0 `references/core-phase-0.md` and #1880 Gap C.
+
 ## Related
 
 - Skills Index: `REFERENCES.md` § Skills Index
 - Progressive disclosure: #2484
 - Trigger coverage evals: #1586
 - Review-surface precedence: #2308 / `deft-directive-review-cycle`
+- Through-merge parent-must-dispatch: #3032 / AGENTS.md `## Through-merge worker dispatch (#3032)`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deftai/directive-content",
-  "version": "0.90.0",
+  "version": "0.92.0",
   "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",
   "type": "module",