@deftai/directive-content 0.108.0 → 0.109.0

package/contracts/path-write-fence.md

@@ -30,6 +30,13 @@ schema with its own matcher.
 When a fence is active, PreToolUse direct writes (Write / Edit / StrReplace / …) **fail closed**
 for out-of-fence paths after ritual / scope / read-only / human-origin authz gates.
 
+ApplyPatch is a direct write. Every path `hookMutationTargetPaths` returns — the declared
+path plus every `*** Add/Update/Delete/Move/Rename File:` header and every `*** Move to:`
+destination — must pass the same fence as Write (#3614). A mixed patch is denied if any
+target is denied. An ApplyPatch body that names no classifiable mutation target fails closed
+while the fence is active. ⊗ Authorize only the declared path when the patch body names
+other targets.
+
 Deny reasons are stable and name the fence source:
 
 - `write fence project allowPaths (source: project)` or `project+story`
@@ -101,10 +108,24 @@ output of running a program, so gating them by parsing the command string means
 a program will do without running it. Recognition of *destructive spellings* is decidable;
 prediction of *mutation* is not.
 
-What that means concretely — all of these are **fail-open today**:
+Tree-wide destructive git is **recognized and fail-closed**, always-on, independent of
+`shellDestForms` (#3917). The forms are `git reset --hard`, `git clean -f` (including
+combined `-fd` / `-fdx`), `git checkout -f` / `git switch --force` / `-B`, and
+`git stash drop` / `git stash clear`. A simple command whose relocators (`-C`,
+`--git-dir`, `--work-tree`, `GIT_DIR=`, `GIT_WORK_TREE=`) are all absolute paths
+outside the project root is allowed as a throwaway fixture. Relative, in-project,
+opaque (`GIT_CONFIG*`, `-c core.workTree`), and compound forms stay denied.
+
+That close is a **guard**, not a root-cause claim. Every recognized form, deny or
+fixture-allow, appends one JSONL line under the platform user-config dir
+(`%APPDATA%\deft\logs\git-destructive.jsonl` / `~/.config/deft/logs/git-destructive.jsonl`,
+overridable with `DEFT_GIT_DESTRUCTIVE_LOG`) so a later occurrence names host, actor,
+command, project root, and disposition even if reflogs are gone.
 
-- Unrecognized mutators: `git reset --hard`, `git clean -fd`, `git stash drop`, `git checkout`
-  without `--`, `mv`, `cp`, `sed -i`, `truncate`, `find -delete`, and `>` / `>>` redirection
+What remains **fail-open today**:
+
+- Unrecognized mutators: `git checkout` without `--` or `-f` (branch switch / ambiguous
+  path checkout), `mv`, `cp`, `sed -i`, `truncate`, `find -delete`, and `>` / `>>` redirection
 - Interpreters: `bash -c 'rm x'`, `python -c`, `node -e`, `cmd /c`
 - Non-literal verbs: `\rm x`, `rm${IFS}x` — the tokenizer cannot see the verb, so even the
   fail-closed branch does not fire
@@ -113,10 +134,49 @@ What that means concretely — all of these are **fail-open today**:
   cannot tell which shell will run the command (#3624)
 - Mutations by allowed programs: `npm run build`, `node scripts/clean.js`, `make` — inherent
   to any string recognizer, since writing files is what those commands are *for*
-- **Nothing on the allow path is audited**, so a bypass currently leaves no trace
-
-Do not describe this gate as closing the Bash bypass. It raises the floor on the four
-recognized verbs in simple commands. The bypass class remains open.
+- **Nothing on the dest-form allow path is audited** except the tree-wide destructive-git
+  log above. A dest-form bypass still leaves no dest-form trace.
+
+### Shell file-write reissue (#3983 / #3987)
+
+This gate is a **cooperative guardrail**. It raises the cost of an accidental or
+careless reissue -- a Write that occupancy, ritual, or scope already denied,
+sent again through the host shell. It is **not** a boundary against a determined
+caller. An agent that wants out of the fence has unbounded exits, and parsing
+the command string cannot close them.
+
+Grok Build shell is `run_terminal_command`. That name is in `SHELL_TOOL_NAMES`,
+so PreToolUse fires. Recognized in-repo dests (`Set-Content`, `Out-File`,
+`Add-Content`, python pathlib `write_text`/`write_bytes`, IO.File WriteAllText /
+WriteAllBytes) are injected as Write targets and authorized through
+`inspectMutationGates` -- occupancy, ritual, scope, and the path fence -- the
+same way ApplyPatch authorizes every mutation target (#3614). Always-on,
+independent of `shellDestForms`. Named PowerShell parameters are honoured in
+any order: `-Value` before `-Path` is not taken as the dest.
+
+OS-temp dests and commands with no recognized dest (`git status`,
+`occupancy:release`, `git commit -F` of a temp body) stay fail-open.
+
+**Measured limits** (bound #3997 arc: synthesis 5472062522, table 5472059705):
+
+- Recogniser recall is about **47%**: 2,843 of 5,372 real file-writing commands
+  were invisible to the classifier, and 17 of 29 probed in-repo write shapes
+  yielded zero targets. Recall work stays on #3987.
+- Destinations that are shell **variables** are not recovered. That is most
+  logged shell: 1,089 of 1,131 calls were dynamic, compound, or emitted no
+  target.
+- A **directory junction** created without elevation defeats `provablyExternal`:
+  the path is lexically outside the root and its realpath is inside. That is
+  **re-entry** polarity. `#3186` `assertProjectionContained` is **escape**
+  polarity (in-tree dest whose realpath leaves the tree) and does not close it.
+
+Fail-open at this predicate is the bound posture (#3997). Inverting it to
+fail-closed on dests the parser cannot prove external is that issue's refuted
+proposal, not this gate's next patch.
+
+Do not cite this merge as "the shell write path is gated." It narrows the
+cooperative reissue hole. The residual class is every command whose dest is
+not statically recoverable.
 
 ### Dest-form target recognition (#3438)
 

package/conventions/content-manifest.json

@@ -363,7 +363,7 @@
     {
       "path": "REFERENCES.md",
       "bucket": "repo-dev",
-      "note": "Repo-level references index for maintainers (harness-entry-adjacent; stays at root)."
+      "note": "Maintainer-only Skills Index and lazy-load guide. Audience boundary (bucket repo-dev). Consumers use npx deft packs:slice skills list (#3601 / #3899). Do not reclassify as content."
     },
     {
       "path": "ROADMAP.md",

package/conventions/references.md

@@ -1,10 +1,11 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/conventions/references.md" -->
 # vBRIEF References — `x-vbrief/*` Type Registry
 
 Canonical reference for the shape and type registry of `plan.references` entries in vBRIEF files.
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**See also**: [../vbrief/vbrief.md](../vbrief/vbrief.md) | [../vbrief/schemas/vbrief-core.schema.json](../vbrief/schemas/vbrief-core.schema.json) | [../main.md](../../main.md)
+**See also**: [../vbrief/vbrief.md](../vbrief/vbrief.md) | [../vbrief/schemas/vbrief-core.schema.json](../vbrief/schemas/vbrief-core.schema.json) | [../main.md](../main.md)
 
 ---
 
@@ -63,7 +64,7 @@ Consumer projects ? MAY extend the registry with additional `x-vbrief/*` values.
 ## Origin Provenance (D11)
 
 Scope vBRIEFs in `vbrief/pending/` and `vbrief/active/` SHOULD carry at least
-one reference whose `type` matches `^x-vbrief/`. `scripts/vbrief_validate.py`
+one reference whose `type` matches `^x-vbrief/`. `task xbrief:validate`
 treats any `x-vbrief/*`-typed reference as an origin for the D11 check by
 default (schema-trusting behavior).
 
@@ -78,7 +79,7 @@ enforce the allow-list in CI can opt in via the same flag.
 
 For scope vBRIEFs ingested from a GitHub issue, the canonical provenance
 signal is the `plan.narratives.Origin` text emitted by
-`scripts/issue_ingest.py::_build_issue_vbrief`:
+`task issue:ingest::_build_issue_vbrief`:
 
 - ! `Origin` MUST take one of these two forms:
   - `Ingested from https://github.com/{owner}/{repo}/issues/{N}` (browser URL resolves)
@@ -104,12 +105,13 @@ from *informational* references using this narrative:
 - ⊗ Mutate a `completed/` vBRIEF to remove a companion / sibling reference solely because `task issue:ingest` false-positives on it (rewriting completed history is an anti-pattern per `skills/deft-directive-refinement/SKILL.md`)
 - ~ When adding a companion / sibling / related-plan reference to an ingested vBRIEF, keep `Origin` pointing at the original ingest source so the dedup pass continues to recognise the vBRIEF as the canonical owner of that issue
 
-## Schema Version: v0.6 (Canonical, Strict)
+## Schema Version: v0.8 (canonical write)
 
-- ! All vBRIEFs MUST emit `"vBRIEFInfo": { "version": "0.6" }`
-- ! `scripts/vbrief_validate.py` accepts ONLY `"0.6"`; any other version (including legacy `"0.5"`) is a hard validation error
-- ! The vendored schema at `../vbrief/schemas/vbrief-core.schema.json` is the canonical v0.6 copy from [`deftai/vBRIEF`](https://github.com/deftai/vBRIEF/blob/master/schemas/vbrief-core-0.6.schema.json) and pins `vBRIEFInfo.version` to `const: "0.6"`
-- ! `scripts/migrate_vbrief.py` emits `"0.6"`; pre-existing v0.5 vBRIEFs are swept to `"0.6"` as part of the migrator flip PR
+- ! All new xBRIEFs MUST emit `"xBRIEFInfo": { "version": "0.8" }`
+- ! `task vbrief:validate` / `task xbrief:validate` accepts `"0.8"` (current write) and `"0.6"` (legacy read)
+- ! The current write schema at `../vbrief/schemas/xbrief-core-0.8.schema.json` pins `xBRIEFInfo.version` to `const: "0.8"`. The vendored v0.6 copy at `../vbrief/schemas/vbrief-core.schema.json` remains for read/migration.
+- ! `deft migrate:xbrief` rewrites 0.6 envelopes to `xBRIEFInfo@0.8`
+- ⊗ Emit `"version": "0.6"` on any new write path -- 0.6 is migration/read compatibility only
 
 ## Anti-Patterns
 

package/conventions/task-caching.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/conventions/task-caching.md" -->
 # Task Caching Convention
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**See also**: [main.md](../../main.md) | [tasks/prd.yml](../../tasks/prd.yml) | [tasks/scope.yml](../../tasks/scope.yml) | [tests/content/test_taskfile_caching.py](../../tests/content/test_taskfile_caching.py)
+**See also**: [main.md](../main.md) | [tasks/prd.yml](../tasks/prd.yml) | [tasks/scope.yml](../tasks/scope.yml) | [tests/content/test_taskfile_caching.py](../../tests/content/test_taskfile_caching.py)
 
 ## Invariant
 

package/conventions/vbrief-filenames.md

@@ -1,10 +1,11 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/conventions/vbrief-filenames.md" -->
 # vBRIEF Filename Conventions
 
 Canonical rules for scope vBRIEF filenames and slug normalization.
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**See also**: [../vbrief/vbrief.md](../vbrief/vbrief.md) | [./references.md](./references.md) | [../main.md](../../main.md)
+**See also**: [../vbrief/vbrief.md](../vbrief/vbrief.md) | [./references.md](./references.md) | [../main.md](../main.md)
 
 ---
 
@@ -19,13 +20,13 @@ YYYY-MM-DD-<slug>.vbrief.json
 - ! The leading date is the **creation date** in `YYYY-MM-DD` form. It is immutable — it MUST NOT change as the scope moves through the lifecycle.
 - ! The `<slug>` is a lowercase hyphen-separated descriptor derived from the scope title (or origin issue title for ingested vBRIEFs).
 - ! The filename MUST end in `.vbrief.json`.
-- ! The filename MUST match `scripts/vbrief_validate.py`'s `FILENAME_PATTERN`: `^\d{4}-\d{2}-\d{2}-[a-z0-9]+(?:-[a-z0-9]+)*\.vbrief\.json$`.
+- ! The filename MUST match `task xbrief:validate`'s `FILENAME_PATTERN`: `^\d{4}-\d{2}-\d{2}-[a-z0-9]+(?:-[a-z0-9]+)*\.vbrief\.json$`.
 
 speckit Phase 4 scope vBRIEFs use the extended pattern `YYYY-MM-DD-ip<NNN>-<slug>.vbrief.json` where `<NNN>` is the implementation-phase index zero-padded to exactly three digits (e.g. `ip001`, `ip042`, `ip128`). See [`../vbrief/vbrief.md`](../vbrief/vbrief.md#speckit-phase-4-scope-vbriefs) for detail.
 
 ## Slug Normalization Rules
 
-`scripts/slug_normalize.py` exposes the canonical `normalize_slug(title, issue_number=None)` function. Every tool or skill that coins a scope vBRIEF filename MUST either call that function or apply the same rules documented below so that two different producers always agree on the slug for the same title.
+`conventions/vbrief-filenames.md` exposes the canonical `normalize_slug(title, issue_number=None)` function. Every tool or skill that coins a scope vBRIEF filename MUST either call that function or apply the same rules documented below so that two different producers always agree on the slug for the same title.
 
 The rules, applied in order:
 
@@ -67,4 +68,4 @@ Scope vBRIEF filenames are part of the file's identity. Renames MUST preserve th
 - ⊗ Use uppercase letters, underscores, or camelCase in the slug
 - ⊗ Put the origin issue number in the date segment (`2026-04-22-#541-...`) — the issue number belongs in the suffix (`...-issue-541`) or in `references`
 - ⊗ Change the date prefix when a scope moves between lifecycle folders — the date is the creation date, not the current-status date
-- ⊗ Coin slugs by hand inside skills; call `scripts/slug_normalize.py` (`normalize_slug`) instead
+- ⊗ Coin slugs by hand inside skills; call `conventions/vbrief-filenames.md` (`normalize_slug`) instead

package/docs/consumer-check-contract.md

@@ -39,6 +39,41 @@ A **partial local** root check aggregate still fails closed — the include must
 
 Root cause of red `greenfield-python-free-smoke` after #3145: the gate only inspected the root Taskfile, treated include-only greenfield as “no check composition,” and hard-failed (`exit 201` via #3188). That was a **gate false positive** for the intentional deposit shape, not a missing deposit wiring bug.
 
+## Merge-chokepoint gate scoping (#3893)
+
+Some gates are repo-wide by default and must be **narrowed** when composed on a
+merge chokepoint. `verify:orphan-active` is the first: composed unscoped it
+fails a candidate for lifecycle residue another merge stranded, and N stranded
+briefs make N single-brief lifecycle PRs mutually unmergeable.
+
+The contract therefore records a required argument per gate
+(`MERGE_CHOKEPOINT_SCOPED_GATE_ARGS`) and reports a check aggregate that lists
+the gate without it:
+
+```yaml
+  check:consumer:
+    deps:
+      - task: verify:orphan-active
+        vars:
+          CLI_ARGS: "--changed-only"
+```
+
+The check reads the dependency's effective `CLI_ARGS` value, not the raw entry
+text, so the flag appearing in a comment, a sibling variable, or a descriptive
+value does not satisfy it.
+
+- **`--framework-source`: fail closed.** This repo owns its own composition, so
+  a regression to the unscoped form is a hard failure here.
+- **Consumer deposits: warn.** `deft update` re-deposits the Taskfile; the
+  warning names the exact one-line repair in the meantime.
+- **Aggregates that do not list the gate are silent.** Include-only greenfield
+  roots and orchestrator-body `check` tasks are unaffected.
+
+This is a strengthening, not a relaxation: nothing about the detector, the
+required-gate set, or any exit code is weakened. Repo-wide residue truth still
+runs on the bare verb, at the delivery tip, and on the after-merge
+`verify:orphan-active -- --issue N` DONE gate (#3429).
+
 ## Repair path
 
 1. Restore deposit Taskfiles: `deft update` (includes `tasks/verify.yml` under `.deft/core/`)

package/docs/delivery-attempt.md

@@ -34,6 +34,8 @@ MUST evaluate this gate before automatic retry or re-dispatch.
 | `BLOCK_ELAPSED_BUDGET` | Wall-clock budget exhausted |
 | `BLOCK_TOOL_OR_TOKEN_BUDGET` | Tool-call (or host-token when telemetried) budget exhausted |
 
+evaluateInFlight(ledger, input) applies the same elapsed budget to a run that is already queued or running. Pre-dispatch never sees that case: an active attempt is DENY_DUPLICATE_ACTIVE. In-flight elapsed is totalElapsedSeconds plus wall-clock since startedAt. Under budget returns ALLOW_RESUME. Exhausted returns BLOCK_ELAPSED_BUDGET. No second budget store.
+
 Once a **block** decision is emitted, automatic re-dispatch MUST stop until a
 declared resume condition is satisfied or an audited operator override is
 recorded. Persist the terminal handoff (`buildTerminalHandoff` /

package/docs/gate-integrity.md

@@ -1,3 +1,4 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/docs/gate-integrity.md" -->
 # Gate integrity — a failing gate must not be fixed by editing the gate (#3156)
 
 General product and process rule for Directive fix loops, refine loops, and quality-gate repair: **when a gate is red, clear red by fixing the work under test — not by mutating the gate.**
@@ -80,7 +81,7 @@ Field notes and parent framing: issue [#3156](https://github.com/deftai/directiv
 ## Discoverability
 
 - Pre-PR Diff phase checklist: [deft-directive-pre-pr](../skills/deft-directive-pre-pr/SKILL.md) (gate-integrity bullet).
-- Stance / propose-not-apply: [main.md § Self-Improving, Not Self-Editing (#3164)](../../main.md#self-improving-not-self-editing-3164), [philosophy.md](../meta/philosophy.md).
+- Stance / propose-not-apply: [main.md § Self-Improving, Not Self-Editing (#3164)](../main.md#self-improving-not-self-editing-3164), [philosophy.md](../meta/philosophy.md).
 - Verification outcomes: [verification.md](../verification/verification.md).
 - Goal/gate rigidity: [goal-gate-determinism.md](../patterns/goal-gate-determinism.md) (#852).
 - Scope self-auth instance: [scope-provenance.md](./scope-provenance.md) (#3145).
@@ -94,13 +95,27 @@ Full CI automation that blocks “diff touches a gate that just failed” withou
 | Topic | Where |
 |-------|--------|
 | Parent epic | [#3179](https://github.com/deftai/directive/issues/3179) |
-| Stance (propose-not-apply) | [#3164](https://github.com/deftai/directive/issues/3164), [main.md](../../main.md#self-improving-not-self-editing-3164) |
+| Stance (propose-not-apply) | [#3164](https://github.com/deftai/directive/issues/3164), [main.md](../main.md#self-improving-not-self-editing-3164) |
 | Refine-internal SkillOpt | [#2436](https://github.com/deftai/directive/issues/2436) |
 | Fixed evaluator / agent-loop | [#782](https://github.com/deftai/directive/issues/782) |
 | Verification independence | [#1499](https://github.com/deftai/directive/issues/1499) |
 | Scope self-authorization | [#3145](https://github.com/deftai/directive/issues/3145), [scope-provenance.md](./scope-provenance.md) |
 | Host self-mutate honesty | [#3162](https://github.com/deftai/directive/issues/3162), [host-surface-assumptions.md](./host-surface-assumptions.md) |
 | Safety via formal gates | [#1200](https://github.com/deftai/directive/issues/1200) |
+| Poisoned product-oracle history from a safety refusal | [#3615](https://github.com/deftai/directive/issues/3615), this page § Product-oracle history poisoned by a safety refusal |
+
+---
+
+## Product-oracle history poisoned by a safety refusal (#3615)
+
+A safety-refused acceptance command is not a product measurement. `verify:ac` keeps the acceptance gate red, and it does not write `verification.outcome=fail` for an all-refused walk. A mixed walk that still has a refusal does not write a product-oracle pass.
+
+Records already written still pair on `session_id` + `check_id`. A correct classifier going forward does not unwrite a `fail` already on disk. Recovery is an operator workaround, not independent re-derivation:
+
+1. Start a new Deft session (new `DEFT_SESSION_ID`) so the integrity layer does not pair against the poisoned fail, or
+2. Truncate or delete the run-summary JSONL (default `.deft-run-summary.json`, typically gitignored).
+
+⊗ Set `independent_rederivation=true` to clear this class. That flag asserts both sides were rebuilt from scratch. The refused side never executed.
 
 ---
 

package/docs/host-surface-assumptions.md

@@ -1,3 +1,4 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/docs/host-surface-assumptions.md" -->
 # Host-surface assumptions: file gates vs REPL / self-mutating hosts (#3162)
 
 Directive control surfaces assume two host behaviors that **some** modern agent hosts break by design.
@@ -131,7 +132,7 @@ Named hook home for managed-path deny: **Tier-1 host hooks** (`packages/core/src
 
 | Topic | Where |
 |-------|--------|
-| Self-improving, not self-editing stance | [main.md § Self-Improving, Not Self-Editing (#3164)](../../main.md#self-improving-not-self-editing-3164), [philosophy.md](../meta/philosophy.md) |
+| Self-improving, not self-editing stance | [main.md § Self-Improving, Not Self-Editing (#3164)](../main.md#self-improving-not-self-editing-3164), [philosophy.md](../meta/philosophy.md) |
 | Gate integrity (do not clear red by editing the gate) | [gate-integrity.md](./gate-integrity.md) (#3156); refine-internal #2436 separate |
 | Skill pin tiers (process pins, not full #830) | [skill-pin-policy.md](./skill-pin-policy.md) |
 | Host lifecycle duty list | [host-lifecycle-duties.md](../contracts/host-lifecycle-duties.md) |

package/docs/orphan-active-verdict-basis.md

@@ -35,6 +35,37 @@ aggregate unknown would break `--skip-gh`, offline runs, and fresh clones.
 
 ---
 
+## What each run is allowed to look at (#3893)
+
+Mode decides *how* a verdict is reached. Scope decides *which briefs* are in
+the question at all.
+
+| | Bare / `--issue N` | `--changed-only` |
+|---|---|---|
+| Caller | doctor, manual runs, swarm finalize, after-merge DONE proof | `check:framework-source` / `check:consumer` merge chokepoint |
+| Briefs evaluated | every running brief under `active/` | only briefs in the candidate's own diff against `origin/<deliveryBranch>` |
+| On the delivery line | n/a | falls back to the full sweep -- this run *is* the delivery-tip check |
+| Unresolvable git or base ref | n/a | falls back to the full sweep, never to a narrower scan |
+
+The merge chokepoint was unscoped until #3893. Measured 2026-08-28: four
+unrelated PRs failed the same two lanes on one stranded brief, one of them
+passed an unchanged re-run once the strandings landed, and two single-brief
+lifecycle PRs could not pass alone because each left the other orphan.
+
+The pre-merge run was never preventive for its own candidate either: the gate
+reads REST `merged_at`, and the candidate's linked PR still reads null while
+that candidate's gate runs. The pre-merge signal for closeout residue is
+`verify:pr-closeout-attestable` (#3781), which keys on the PR's structured
+closing references rather than the branch diff.
+
+The detector is unchanged. The linked-PR/open-issue signature still fails a
+candidate whose own diff carries it.
+
+⊗ Do not read a `--changed-only` pass as repo-wide truth. Every run prints its
+scope; `EvaluateResult.scope` carries the same thing structurally.
+
+---
+
 ## The freshness choice
 
 **Age bound plus re-validation, applied per mode.** Both options offered by
@@ -164,3 +195,5 @@ mode for callers.
 - [#3476](https://github.com/deftai/directive/issues/3476) — `verify:completed-tracked`
 - [#3752](https://github.com/deftai/directive/issues/3752) — the open-inventory mechanism reused here
 - [#3156](https://github.com/deftai/directive/issues/3156) — gate integrity; this was a deliberate gate-definition change
+- [#3893](https://github.com/deftai/directive/issues/3893) — merge-chokepoint scoping; the named check-composition change
+- [#3781](https://github.com/deftai/directive/issues/3781) — `verify:pr-closeout-attestable`, the pre-merge closeout signal

package/docs/skill-pin-policy.md

@@ -13,7 +13,7 @@ Pins are for **false-negative-sensitive process gates**, not for copying entire
 | Tier | Meaning | How the agent discovers it |
 |---|---|---|
 | **always-pin** | Named in AGENTS.md (managed or consumer unmanaged header) as a required `SKILL.md` load when a matching work type starts | Always-loaded AGENTS.md |
-| **on-demand** | Routed via Skills Index triggers in `REFERENCES.md` — scan Level-0, read Level-1 on match | Skills Index → `SKILL.md` |
+| **on-demand** | Routed via Skills Index triggers (consumer: `npx deft packs:slice skills list`; maintainer: `REFERENCES.md`) — scan Level-0, read Level-1 on match | Skills Index → `SKILL.md` |
 | **reference-only** | External, rare, or maintainer-only corpora; no standing trigger routing | Explicit doc pointer only |
 
 ### Criteria for always-pin

package/events/README.md

@@ -27,11 +27,11 @@ data-file-convention check ([#710](https://github.com/deftai/directive/issues/71
 
 - **`detection-bound`** — detectable from filesystem state alone (e.g. dirty
   tree, vBRIEF schema invalidity, version drift). Emitted via
-  `scripts/_event_detect.py`. Detector lives at the call site documented in
+  `task lifecycle:event`. Detector lives at the call site documented in
   the entry's `trigger` field.
 - **`behavioral`** — requires runtime instrumentation (paired
   `session:interrupted` / `session:resumed`, `plan:approved`,
-  `legacy:detected`). Emitted via `scripts/_events.py`, which manages 1:1
+  `legacy:detected`). Emitted via `task lifecycle:event`, which manages 1:1
   session-pair invariants and a JSONL append-only log at
   `<project_root>/.deft-cache/events.jsonl`.
 
@@ -48,29 +48,28 @@ conforming to `event-record.schema.json`:
 }
 ```
 
-`scripts/_event_detect.py::emit(name, payload)` validates against the full
+`task lifecycle:event -- emit <name> ...` validates against the full
 registry (any registered name is accepted) and is silent by default; when the
 `DEFT_EVENT_LOG` environment variable points to a writable path, each
 emission is appended as a single JSON line.
 
-`scripts/_events.py::emit(name, payload)` validates against the
-`category="behavioral"` subset of the registry, generates a sortable event id
-for pairing semantics, enforces required-payload contracts, and persists to
-`<project_root>/.deft-cache/events.jsonl` (or a path injected via `log_path` /
+Behavioral emits validate against the `category="behavioral"` subset of the
+registry, generate a sortable event id for pairing semantics, enforce
+required-payload contracts, and persist to
+`<project_root>/.deft-cache/events.jsonl` (or a path injected via `--log` /
 `DEFT_EVENT_LOG`). The log lives under the already-gitignored `.deft-cache/`
 rather than `.deft/`, because `.deft/` is not blanket-gitignored on hybrid
 installs (`.deft/core/` is gitignored and reconstituted by `directive init`,
-per #1942 / #1465). Use this helper when emitting behavioral events from
-skills (`python -m scripts._events emit ...`).
+per #1942 / #1465). Skills emit behavioral events with
+`task lifecycle:event -- emit <name> ...`.
 
 ## Adding an event
 
 1. Append the entry to `registry.json` with the appropriate `category`,
    payload contract, trigger pointer, and consumer pointers (validate via
-   `tests/cli/test_events.py` and `tests/cli/test_behavioral_events.py`).
-2. Add the detection / emission call site in `scripts/` or the relevant
-   surface (use `scripts/_event_detect.py` for detection-bound,
-   `scripts/_events.py` for behavioral).
+   `packages/core/src/lifecycle/events.ts` tests).
+2. Add the detection / emission call site in the TypeScript lifecycle surface
+   (use `task lifecycle:event` for both detection-bound and behavioral events).
 3. Reference the event by name from at least one consumer (skill, task,
    script) so the surface stays usable -- the schema requires `consumers`
    to be a non-empty array.

package/glossary.md

@@ -1,3 +1,4 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/glossary.md" -->
 # Glossary
 
 The authoritative vocabulary for the Deft framework.
@@ -120,7 +121,7 @@ Canonical vocabulary for the xBRIEF lifecycle. **xBRIEF** / `xbrief/` is the sol
 
 - **Cross-scope dependency** -- Dependency between two scope xBRIEFs at `plan.metadata.dependencies` (array of dependency IDs). See [vbrief/vbrief.md](./vbrief/vbrief.md).
 
-- **Exit Commands** -- The seven deterministic `task scope:*` commands that transition a scope xBRIEF between lifecycle folders: `scope:promote`, `scope:activate`, `scope:complete`, `scope:cancel`, `scope:restore`, `scope:block`, `scope:unblock` (see [tasks/scope.yml](../tasks/scope.yml)).
+- **Exit Commands** -- The seven deterministic `task scope:*` commands that transition a scope xBRIEF between lifecycle folders: `scope:promote`, `scope:activate`, `scope:complete`, `scope:cancel`, `scope:restore`, `scope:block`, `scope:unblock` (see [tasks/scope.yml](tasks/scope.yml)).
 
 - **Origin provenance** -- A `references` entry linking a scope xBRIEF to its origin issue / ticket / user-request. Required for ingestion dedup. See [vbrief/vbrief.md](./vbrief/vbrief.md).
 

package/incidents/README.md

@@ -1,3 +1,4 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/incidents/README.md" -->
 # Incidents Library
 
 This directory captures real-world incidents that motivated specific Deft
@@ -53,7 +54,7 @@ Examples:
 - `2026-04-15-some-other-incident.md`
 
 Filenames use hyphens, not underscores -- this mirrors the project-wide
-filename convention in [`main.md`](../../main.md).
+filename convention in [`main.md`](../main.md).
 
 ## When to add an entry
 

package/interfaces/cli.md

@@ -1,3 +1,4 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/interfaces/cli.md" -->
 # CLI Best Practices
 
 Opinionated patterns for command-line interfaces with AI agents.
@@ -110,4 +111,4 @@ else:
 
 ---
 
-**See also**: [python.md](../languages/python.md) | [typescript.md](../languages/typescript.md) | [tui.md](../interfaces/tui.md)
+**See also**: [python.md](../languages/python.md) | [typescript.md](../languages/typescript.md) | [tui.md](tui.md)

package/languages/6502-DASM.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/6502-DASM.md" -->
 # 6502 + DASM Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md)
 
 ## Scope
 - This guide covers:

package/languages/c.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/c.md" -->
 # C Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 **Stack**: C17/C23, CMake 3.25+, clang/GCC; Testing: Unity/cmocka; Analysis: clang-tidy, cppcheck, AddressSanitizer
 

package/languages/cpp.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/cpp.md" -->
 # C++ Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 **Stack**: C++20/23, CMake 3.25+, Catch2/GoogleTest, GSL (Guidelines Support Library); CLI: CLI11; TUI: FTXUI; Async: Asio/libcoro
 

package/languages/csharp.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/csharp.md" -->
 # C# Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 **Stack**: C# 12+/.NET 8+ (LTS), SDK-style projects; Web: ASP.NET Core/Minimal APIs; Testing: xUnit + NSubstitute + FluentAssertions; Analysis: Roslyn Analyzers, StyleCop.Analyzers
 

package/languages/dart.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/dart.md" -->
 # Dart Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md)
 
 **Stack**: Dart 3.x+; Framework: Flutter (mobile/web) or standalone; Testing: `package:test` / `flutter_test`; Lint: `analysis_options.yaml` + custom_lint; Format: `dart format`; Docs: dartdoc
 

package/languages/delphi.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/delphi.md" -->
 # Delphi / Object Pascal Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 **Stack**: Delphi 12+/Object Pascal, RAD Studio; GUI: VCL (Windows), FMX (cross-platform); DB: FireDAC; Testing: DUnitX
 

package/languages/elixir.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/elixir.md" -->
 # Elixir Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md)
 
 **Stack**: Elixir 1.16+ / OTP 26+; Build: Mix; Testing: ExUnit; Lint: Credo; Format: `mix format`; Docs: ExDoc; Types: Dialyxir
 

package/languages/go.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/go.md" -->
 # Go Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 ## Standards
 

package/languages/java.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/java.md" -->
 # Java Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 **Stack**: Java 21+ (LTS), Maven/Gradle; Web: Spring Boot 3+; Testing: JUnit 5 + Mockito + AssertJ; Analysis: Checkstyle, SpotBugs, Error Prone
 

package/languages/javascript.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/javascript.md" -->
 # JavaScript Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md) | [telemetry.md](../tools/telemetry.md)
 
 **Stack**: ES2022+, Node 20+; Build: Vite/esbuild; Testing: Vitest/Jest; Lint: ESLint + Prettier; Web: React/Next.js
 

package/languages/julia.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/julia.md" -->
 # Julia Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md)
 
 **Stack**: Julia 1.10+; Packages: Pkg.jl; Testing: `Test` stdlib + Aqua.jl; Docs: Documenter.jl; Format: JuliaFormatter.jl; Lint: JET.jl / Aqua.jl
 

package/languages/kotlin.md

@@ -1,8 +1,9 @@
+<!-- deft:deposit-link-rewrite v=1 source="content/languages/kotlin.md" -->
 # Kotlin Standards
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
-**⚠️ See also**: [main.md](../../main.md) | [PROJECT.md](../../PROJECT.md)
+**⚠️ See also**: [main.md](../main.md) | [PROJECT.md](../../PROJECT.md)
 
 **Stack**: Kotlin 2.0+; Build: Gradle (Kotlin DSL); Testing: JUnit 5 + kotest; Lint: detekt; Format: ktfmt/ktlint; Docs: KDoc