@deftai/directive-content 0.91.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/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/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.91.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",