@deftai/directive-runtime 0.126.0-beta.1 → 0.126.0-beta.2

package/vendor/directive-content/docs/framework-gap-filing.md

@@ -0,0 +1,85 @@
+# Framework-gap filing (consumer → deftai/directive)
+
+Durable house style for consumer framework-gap issues filed against
+`deftai/directive`. Mirrors the shipped builders `buildFrameworkGapTitle` and
+`buildFrameworkGapBody` in the value-feedback engine. This document is
+**gate-free**: agents may read it while `plan.policy.valueFeedback.upstreamPrompt`
+is OFF.
+
+Primary command: `deft feedback:file` (optional Taskfile wrapper when
+go-task is installed). Skill: `deft-directive-feedback`.
+
+Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
+
+## Title
+
+- ! Prefix with `[framework-gap]` (the builder adds it when missing).
+- ! Consumer hard-stop classification uses the sole title token `BLOCKER`
+  (`--blocker`). Example: `[framework-gap] BLOCKER Missing decompose hint`.
+- ⊗ Invent other title classifications. Label-only classes stay labels.
+- ⊗ Treat absence of `BLOCKER` as "not a blocker" — absence means not classified.
+
+## Body sections
+
+The builder emits this shape (placeholders when a field is omitted):
+
+1. `## Summary` — one-line sanitized summary
+2. `## Context`
+3. `## Expected behavior`
+4. `## Actual behavior / gap`
+5. `## Session notes`
+6. When `--blocker`: `## Adoption impact` with affected flow/version,
+   documented alternatives, observed recovery cost, and a triage owner/date
+   placeholder for a privileged actor
+7. Footer separator + `_Filed via \`deft feedback:file\` … (Refs #1709 …)_`
+
+Free-text fields fence line-leading `#` and `---` (indent) so operator paste
+cannot break the markdown skeleton.
+
+## Labels at create
+
+- ! Pass an **empty** label list at issue create. Consumers generally lack
+  push access to set labels.
+- ! Maintainer triage applies labels afterward from the maintainer catalog
+  (`.github/ISSUE_LABELS.md`) and `content/scm/github.md`.
+- ~ `docs/consumer-issue-label-kit.md` is contrast only for consumer-kit
+  repos — not the privileged upstream `adoption-blocker` SoT.
+- ⊗ Cite the consumer label kit as authority for upstream
+  `adoption-blocker`.
+
+## Privileged `adoption-blocker`
+
+- ! `adoption-blocker` is a **privileged write** after the body-evidence test
+  in `content/scm/github.md` § Consumer hard-blocker.
+- ! The `BLOCKER` title token is an inbound flare only; it never writes the
+  ranking label.
+- ⊗ Auto-apply or request `adoption-blocker` from a consumer-authored title alone.
+
+## Dedup
+
+- ! Normalize titles by stripping `[framework-gap]` and optional `BLOCKER`
+  before comparison so marked/unmarked drafts collide.
+- ! When an open upstream issue matches, STOP and link it — do not file again.
+
+## Tracking footer
+
+- ! Use `Refs #1709` (value-feedback gap escalation) only.
+- ⊗ Use `Closes` / `Fixes` / `Resolves` in the upstream body.
+
+## Draft → confirm
+
+1. Draft / readout: `deft feedback:file --summary "…" …` (optional
+   `--dry-run` / `--json`). Gate-OFF still returns title+body for template
+   readout; filing stays blocked until consent.
+2. Enable upstream path when needed:
+   `deft policy:enable-value-feedback --confirm --upstream-prompt`
+   (audited setter; bare `--confirm` does not silently enable
+   `upstreamPrompt`). ⊗ Hand-edit PROJECT-DEFINITION as the primary setter.
+3. Confirm: re-run the **same report fields and target repo** with `--confirm`
+   added and without `--dry-run` or `--json`.
+
+## Related
+
+- Skill: `skills/deft-directive-feedback/SKILL.md`
+- SCM hard-stop rules: `scm/github.md` § Consumer hard-blocker
+- Maintainer label catalog: `.github/ISSUE_LABELS.md` (repo-only; not deposited)

package/vendor/directive-content/docs/product-signal.md

@@ -54,6 +54,6 @@ Agents: `deft-directive-product-signal` — triggers `product check-in`, `produc
 
 ## Related
 
-- Public gap escalation: `deft-directive-feedback` / `task feedback:file` (hard confirm)
+- Public gap escalation: `deft-directive-feedback` / `deft feedback:file` (hard confirm)
 - Skill telemetry emit: #829 (optional `skillsSummary` hook only; not required for pulse)
 - HTTP transport: #2697 (Phase 2)

package/vendor/directive-content/packs/skills/skills-pack-0.1.json

@@ -94,17 +94,20 @@
     },
     {
       "id": "deft-directive-feedback",
-      "description": "Batched session-end gap escalation for directive consumers. Collects friction/gap reports, drafts deduped framework-gap issues against deftai/directive, and files upstream only after explicit operator confirmation. Gated on plan.policy.valueFeedback upstreamPrompt.",
+      "description": "Mid-session and session-end framework-gap escalation for directive consumers. Collects friction/gap reports, drafts deduped framework-gap issues against deftai/directive, and files upstream only after explicit operator confirmation. Use when the operator says \"file a directive issue\", \"file this upstream\", or \"report a framework gap\".",
       "triggers": [
         "feedback",
         "framework gap",
         "file upstream",
+        "file this upstream",
+        "file a directive issue",
+        "report a framework gap",
         "gap escalation",
         "directive feedback"
       ],
       "path": "skills/deft-directive-feedback/SKILL.md",
       "version": "0.1",
-      "body": "# Deft Directive Feedback -- gap escalation to upstream\n\nConversational batched flow for filing framework gaps discovered during consumer sessions. Mirrors the confirmation gate from `deft-directive-article-review` -- the agent drafts and dedups; the operator approves before any upstream issue is created.\n\nLegend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.\n\n## When to Use\n\n- Session end when `friction:*` ledger signals or operator reports a directive shortfall\n- Operator says \"file this upstream\", \"report a framework gap\", or \"directive feedback\"\n- After enabling `plan.policy.valueFeedback.upstreamPrompt` during onboarding\n\n## Preconditions\n\n- ! Run only from a **consumer project** -- the filing path no-ops inside the directive maintainer repo\n- ! `plan.policy.valueFeedback.upstreamPrompt` MUST be ON (`task policy:show --field=valueFeedback`)\n- ⊗ File upstream issues without explicit operator confirmation\n- ⊗ Invoke when `valueFeedback.enabled` is OFF\n\n## Phase 1 -- Collect (batched)\n\n- ! Gather concrete gap reports from the session: what was expected, what happened, and minimal reproduction context\n- ! Batch multiple friction items into one upstream issue when they share a root cause; otherwise prepare separate drafts\n- ~ Prefer attributed phrasing (\"encoding gate blocked a valid file\") over vague quality claims\n\n## Phase 1.5 -- Adoption-blocker judgment\n\n- ! Ask whether the gap blocks adoption. A gap blocks adoption when the consumer cannot complete an intended Directive flow and has no reasonable workaround.\n- ! When the answer is yes, collect the body evidence a privileged actor needs before applying `adoption-blocker`: affected consumer flow and version; documented alternatives attempted, or why they are not a reasonable workaround; observed recovery cost. Pass `--blocker` (and `--flow`, `--alternatives`, `--recovery-cost` when known) so the title carries `BLOCKER` and the body carries those sections.\n- ! When the answer is no or unknown, omit `--blocker`. Absence of the token does not mean \"not a blocker\" -- it means not classified.\n- ⊗ Apply or request the `adoption-blocker` ranking label from a consumer-authored title. The label is a privileged write after the body-evidence test.\n\n## Phase 2 -- Draft + dedup\n\n- ! For each candidate report, run a dry draft:\n\n```bash\ntask feedback:file -- --summary \"<one-line summary>\" --context \"<session context>\" --expected \"<expected>\" --actual \"<actual>\" --notes \"<optional>\" [--blocker --flow \"<flow and version>\" --alternatives \"<alts>\" --recovery-cost \"<cost>\"]\n```\n\n- ! Read the printed draft title/body with the operator before proceeding\n- ! If the command reports a duplicate open issue, STOP and link the existing issue instead of filing again\n- ⊗ Proceed past a duplicate-detection block without operator override\n\n## Phase 3 -- Confirm + file\n\n- ! Present the final draft and ask for explicit yes/no confirmation\n- ! Only after approval, re-run with `--confirm`:\n\n```bash\ntask feedback:file -- --summary \"<one-line summary>\" --context \"<session context>\" --expected \"<expected>\" --actual \"<actual>\" --confirm [--blocker]\n```\n\n- ! Print the filed issue URL to the operator\n- ⊗ Use `Closes`/`Fixes`/`Resolves` in the upstream body -- use `Refs #1709` only\n\n## Phase 4 -- Handoff\n\n- ~ Record the upstream issue URL in the session handoff or continue checkpoint if the operator tracks follow-ups locally\n- ~ Return to the prior workflow; gap escalation does not block story completion\n\n## Anti-Patterns\n\n- ⊗ Filing from the maintainer framework repo (consumer-only guard)\n- ⊗ Skipping dedup review when the command reports an existing open issue\n- ⊗ Treating `--confirm` as implicit from broad session approval -- require an explicit filing confirmation step\n- ⊗ Infer \"not a blocker\" from an unmarked report -- absence of `BLOCKER` means not classified\n- ⊗ Auto-apply `adoption-blocker` from a consumer-authored title\n",
+      "body": "# Deft Directive Feedback -- gap escalation to upstream\n\nConversational batched flow for filing framework gaps discovered during consumer sessions. Mirrors the confirmation gate from `deft-directive-article-review` -- the agent drafts and dedups; the operator approves before any upstream issue is created. House style for title/body/labels/dedup lives in [`docs/framework-gap-filing.md`](../../docs/framework-gap-filing.md).\n\nLegend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.\n\n## When to Use\n\n- Mid-session when the operator says \"file a directive issue\", \"file this upstream\", \"report a framework gap\", or \"directive feedback\" -- even while `plan.policy.valueFeedback.upstreamPrompt` is OFF\n- Session end when `friction:*` ledger signals or the operator reports a directive shortfall\n- After the operator opts into upstream filing via the audited setter below\n\n## Preconditions\n\n- ! Run only from a **consumer project** -- the filing path no-ops inside the directive maintainer repo\n- ! Filing requires `plan.policy.valueFeedback.upstreamPrompt` ON. If OFF, draft with `deft feedback:file --dry-run` / `--json` (title+body still print), then ask the operator to enable via `deft policy:enable-value-feedback --confirm --upstream-prompt`. If declined, STOP safely -- do not hand-edit PROJECT-DEFINITION.\n- ! Inspect current state with `deft policy:show --field=valueFeedback`\n- ⊗ File upstream issues without explicit operator confirmation\n- ⊗ Treat handwritten typed-block / PROJECT-DEFINITION edits as the primary audited setter\n\n## Phase 1 -- Collect (batched)\n\n- ! Gather concrete gap reports from the session: what was expected, what happened, and minimal reproduction context\n- ! Batch multiple friction items into one upstream issue when they share a root cause; otherwise prepare separate drafts\n- ~ Prefer attributed phrasing (\"encoding gate blocked a valid file\") over vague quality claims\n- ! Follow [`docs/framework-gap-filing.md`](../../docs/framework-gap-filing.md) for title/BLOCKER, section shape, empty create labels, privileged `adoption-blocker`, dedup, and Refs\n\n## Phase 1.5 -- Adoption-blocker judgment\n\n- ! Ask whether the gap blocks adoption. A gap blocks adoption when the consumer cannot complete an intended Directive flow and has no reasonable workaround.\n- ! When the answer is yes, collect the body evidence a privileged actor needs before applying `adoption-blocker`: affected consumer flow and version; documented alternatives attempted, or why they are not a reasonable workaround; observed recovery cost. Pass `--blocker` (and `--flow`, `--alternatives`, `--recovery-cost` when known) so the title carries `BLOCKER` and the body carries those sections.\n- ! When the answer is no or unknown, omit `--blocker`. Absence of the token does not mean \"not a blocker\" -- it means not classified.\n- ⊗ Apply or request the `adoption-blocker` ranking label from a consumer-authored title. The label is a privileged write after the body-evidence test.\n\n## Phase 2 -- Draft + dedup\n\n- ! For each candidate report, run a dry draft (reuse the same report fields and target repo in Phase 3; confirmation adds `--confirm` and drops `--dry-run`/`--json`):\n\n```bash\ndeft feedback:file --summary \"<one-line summary>\" --context \"<session context>\" --expected \"<expected>\" --actual \"<actual>\" --notes \"<optional>\" [--blocker --flow \"<flow and version>\" --alternatives \"<alts>\" --recovery-cost \"<cost>\"] [--dry-run|--json]\n```\n\n- ! Read the printed draft title/body with the operator before proceeding\n- ! If the command reports a duplicate open issue, STOP and link the existing issue instead of filing again\n- ⊗ Proceed past a duplicate-detection block without operator override\n- ~ When go-task is installed, the Taskfile may wrap the same verb; prefer `deft feedback:file` as primary\n\n## Phase 3 -- Confirm + file\n\n- ! Present the final draft and ask for explicit yes/no confirmation\n- ! Only after approval, re-run the **same report fields and target repo** with `--confirm` added and without `--dry-run` or `--json`:\n\n```bash\ndeft feedback:file --summary \"<one-line summary>\" --context \"<session context>\" --expected \"<expected>\" --actual \"<actual>\" --confirm [--blocker]\n```\n\n- ! Print the filed issue URL to the operator\n- ⊗ Use `Closes`/`Fixes`/`Resolves` in the upstream body -- use `Refs #1709` only\n\n## Phase 4 -- Handoff\n\n- ~ Record the upstream issue URL in the session handoff or continue checkpoint if the operator tracks follow-ups locally\n- ~ Return to the prior workflow; gap escalation does not block story completion\n\n## Anti-Patterns\n\n- ⊗ Filing from the maintainer framework repo (consumer-only guard)\n- ⊗ Skipping dedup review when the command reports an existing open issue\n- ⊗ Treating `--confirm` as implicit from broad session approval -- require an explicit filing confirmation step\n- ⊗ Infer \"not a blocker\" from an unmarked report -- absence of `BLOCKER` means not classified\n- ⊗ Auto-apply `adoption-blocker` from a consumer-authored title\n- ⊗ Hand-editing PROJECT-DEFINITION to flip `upstreamPrompt` instead of the audited setter\n",
       "frontmatter_extra": null
     },
     {
@@ -233,7 +236,7 @@
       ],
       "path": "skills/deft-directive-product-signal/SKILL.md",
       "version": "0.1",
-      "body": "# Deft Directive Product Signal — consented check-in (#2693)\n\nAgent-driven qualitative product-improvement signal for partner/trial installs. Lightweight interview, minimized local summaries (value/health/helped), optional skillsSummary hook — submits to private `deftai/product-signal` when enable + consent gates pass.\n\nLegend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.\n\n## When to Use\n\n- Operator says `product check-in`, `product pulse`, `partner feedback`, or `product signal`\n- Partner onboarding after ops enables `plan.policy.productSignal`\n- ⊗ Do NOT invoke from session:start or ambient rituals when disabled (#2693 D3)\n\n## Preconditions\n\n- ! `plan.policy.productSignal.enabled` MUST be true (`task policy:show --field=productSignal`)\n- ! Install-level consent MUST be recorded before outbound submit (`task product-signal:status`)\n- ! Consent schema v2 binds to the configured sinkRepo; legacy v1 consent authorizes only `deftai/product-signal` (#2767)\n- ! Re-consent after changing `plan.policy.productSignal.sinkRepo`; mismatch soft-skips as sink-unconsented\n- ⊗ Prompt or submit when `enabled` is false\n- ⊗ Block story work on sink errors — fail open (#2693 D16/D18)\n\n## Phase 1 — Gate\n\n```bash\ntask product-signal:status\ntask policy:show -- --field=productSignal\n```\n\n- ! If disabled: soft-skip with one line; exit skill\n- ! If headless/CI: fail open — no consent/interview prompts (#2693 D16)\n\n## Phase 2 — First-time consent (interactive only, D17)\n\nWhen enabled, interactive, and consent missing/revoked, ask:\n\n> May we collect usage metrics and related session signal from this install to improve Directive? This can include a short check-in plus minimized local summaries (value/health and related ledgers). Nothing is sent while this path is off or without your consent.\n>\n> If you are unsure, please check with your company before saying no — they are a Directive partner and may already expect this signal to be shared.\n>\n> Reply **yes** to consent, or **no** to decline.\n\n- **yes** → `task product-signal:consent -- --grant` (pass `--project-root` when using a custom sinkRepo); continue\n- **no** → soft-skip; do not badger every turn\n\n## Phase 3 — Interview (≤3 answers + optional NPS)\n\n- ! Ask at most three short questions plus optional NPS (0–10)\n- ~ Target ≤30s human time beyond first-time consent\n- ⊗ Paste secrets, paths, raw logs, or full USER.md into answers\n\n## Phase 4 — Assemble + validate + submit\n\n```bash\ntask product-signal:submit -- --surface pulse --dry-run\ntask product-signal:submit -- --surface pulse --nps 9\n```\n\n- ! On validation failure: show reason; no partial write\n- ! On sink ACL/network errors: soft-skip with hint; do not fail caller (#2693 D18)\n- ! Report issue URL on success\n\n## Private gaps (D19)\n\n- ! Record bugs/gaps as `Gap:` comments on the standing **pulse** thread (enable+consent sufficient)\n- ! Public promote to `deftai/directive` remains hard-confirm via `deft-directive-feedback` / `task feedback:file`\n\n## Revoke\n\n```bash\ntask product-signal:consent -- --revoke\n# and/or disable: set plan.policy.productSignal.enabled false\n```\n\n## Anti-Patterns\n\n- ⊗ Ambient consent nag when disabled\n- ⊗ Fail-closed headless behavior\n- ⊗ Sticky forever-fail when sink is down\n- ⊗ Auto-file public framework-gap issues from pulses\n\n## Exit\n\ndeft-directive-product-signal complete — exiting skill.\n",
+      "body": "# Deft Directive Product Signal — consented check-in (#2693)\n\nAgent-driven qualitative product-improvement signal for partner/trial installs. Lightweight interview, minimized local summaries (value/health/helped), optional skillsSummary hook — submits to private `deftai/product-signal` when enable + consent gates pass.\n\nLegend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.\n\n## When to Use\n\n- Operator says `product check-in`, `product pulse`, `partner feedback`, or `product signal`\n- Partner onboarding after ops enables `plan.policy.productSignal`\n- ⊗ Do NOT invoke from session:start or ambient rituals when disabled (#2693 D3)\n\n## Preconditions\n\n- ! `plan.policy.productSignal.enabled` MUST be true (`task policy:show --field=productSignal`)\n- ! Install-level consent MUST be recorded before outbound submit (`task product-signal:status`)\n- ! Consent schema v2 binds to the configured sinkRepo; legacy v1 consent authorizes only `deftai/product-signal` (#2767)\n- ! Re-consent after changing `plan.policy.productSignal.sinkRepo`; mismatch soft-skips as sink-unconsented\n- ⊗ Prompt or submit when `enabled` is false\n- ⊗ Block story work on sink errors — fail open (#2693 D16/D18)\n\n## Phase 1 — Gate\n\n```bash\ntask product-signal:status\ntask policy:show -- --field=productSignal\n```\n\n- ! If disabled: soft-skip with one line; exit skill\n- ! If headless/CI: fail open — no consent/interview prompts (#2693 D16)\n\n## Phase 2 — First-time consent (interactive only, D17)\n\nWhen enabled, interactive, and consent missing/revoked, ask:\n\n> May we collect usage metrics and related session signal from this install to improve Directive? This can include a short check-in plus minimized local summaries (value/health and related ledgers). Nothing is sent while this path is off or without your consent.\n>\n> If you are unsure, please check with your company before saying no — they are a Directive partner and may already expect this signal to be shared.\n>\n> Reply **yes** to consent, or **no** to decline.\n\n- **yes** → `task product-signal:consent -- --grant` (pass `--project-root` when using a custom sinkRepo); continue\n- **no** → soft-skip; do not badger every turn\n\n## Phase 3 — Interview (≤3 answers + optional NPS)\n\n- ! Ask at most three short questions plus optional NPS (0–10)\n- ~ Target ≤30s human time beyond first-time consent\n- ⊗ Paste secrets, paths, raw logs, or full USER.md into answers\n\n## Phase 4 — Assemble + validate + submit\n\n```bash\ntask product-signal:submit -- --surface pulse --dry-run\ntask product-signal:submit -- --surface pulse --nps 9\n```\n\n- ! On validation failure: show reason; no partial write\n- ! On sink ACL/network errors: soft-skip with hint; do not fail caller (#2693 D18)\n- ! Report issue URL on success\n\n## Private gaps (D19)\n\n- ! Record bugs/gaps as `Gap:` comments on the standing **pulse** thread (enable+consent sufficient)\n- ! Public promote to `deftai/directive` remains hard-confirm via `deft-directive-feedback` / `deft feedback:file`\n\n## Revoke\n\n```bash\ntask product-signal:consent -- --revoke\n# and/or disable: set plan.policy.productSignal.enabled false\n```\n\n## Anti-Patterns\n\n- ⊗ Ambient consent nag when disabled\n- ⊗ Fail-closed headless behavior\n- ⊗ Sticky forever-fail when sink is down\n- ⊗ Auto-file public framework-gap issues from pulses\n\n## Exit\n\ndeft-directive-product-signal complete — exiting skill.\n",
       "frontmatter_extra": null
     },
     {

package/vendor/directive-content/scm/github.md

@@ -531,7 +531,7 @@ Agent `edit_files` operations can fail when structured file sections contain Uni
 
 This is the canonical ranking label for **a Directive consumer cannot complete an intended flow and has no reasonable workaround**. The range is install, first session, update, `task check`, and ship -- not onboarding alone. Do not invent a second ranking label for that class.
 
-**Title classification (the one sanctioned exception, #3713):** `BLOCKER` in the title is permitted for this class, and is the **only** classification allowed in an issue title. Every other classification stays label-only. Reason: the filing population cannot apply labels -- GitHub requires push access to set them at issue creation. The token is an inbound flare; it never writes `adoption-blocker`. A privileged actor applies the label after the body-evidence test below. Absence of the token does not mean "not a blocker." `task feedback:file --blocker` is the consumer filing path that carries the token and this evidence.
+**Title classification (the one sanctioned exception, #3713):** `BLOCKER` in the title is permitted for this class, and is the **only** classification allowed in an issue title. Every other classification stays label-only. Reason: the filing population cannot apply labels -- GitHub requires push access to set them at issue creation. The token is an inbound flare; it never writes `adoption-blocker`. A privileged actor applies the label after the body-evidence test below. Absence of the token does not mean "not a blocker." `deft feedback:file --blocker` is the consumer filing path that carries the token and this evidence. See also [`docs/framework-gap-filing.md`](../docs/framework-gap-filing.md).
 
 **Release census (#3969 / #4917):** `task verify:consumer-hard-stops` blocks a cut only for open `blocks-release-tag`. `adoption-blocker` is the punch list and does not block a tag. The BLOCKER title flare does not by itself block a cut. Issue bodies are not read into the verdict.
 

package/vendor/directive-content/skills/deft-directive-feedback/SKILL.md

@@ -1,10 +1,11 @@
 ---
 name: deft-directive-feedback
 description: >-
-  Batched session-end gap escalation for directive consumers. Collects
-  friction/gap reports, drafts deduped framework-gap issues against
-  deftai/directive, and files upstream only after explicit operator
-  confirmation. Gated on plan.policy.valueFeedback upstreamPrompt.
+  Mid-session and session-end framework-gap escalation for directive
+  consumers. Collects friction/gap reports, drafts deduped framework-gap
+  issues against deftai/directive, and files upstream only after explicit
+  operator confirmation. Use when the operator says "file a directive issue",
+  "file this upstream", or "report a framework gap".
 ---
 <!-- AUTO-GENERATED by task packs:render -- DO NOT EDIT MANUALLY -->
 <!-- Purpose: rendered skill -->
@@ -14,28 +15,30 @@ description: >-
 
 # Deft Directive Feedback -- gap escalation to upstream
 
-Conversational batched flow for filing framework gaps discovered during consumer sessions. Mirrors the confirmation gate from `deft-directive-article-review` -- the agent drafts and dedups; the operator approves before any upstream issue is created.
+Conversational batched flow for filing framework gaps discovered during consumer sessions. Mirrors the confirmation gate from `deft-directive-article-review` -- the agent drafts and dedups; the operator approves before any upstream issue is created. House style for title/body/labels/dedup lives in [`docs/framework-gap-filing.md`](../../docs/framework-gap-filing.md).
 
 Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
 ## When to Use
 
-- Session end when `friction:*` ledger signals or operator reports a directive shortfall
-- Operator says "file this upstream", "report a framework gap", or "directive feedback"
-- After enabling `plan.policy.valueFeedback.upstreamPrompt` during onboarding
+- Mid-session when the operator says "file a directive issue", "file this upstream", "report a framework gap", or "directive feedback" -- even while `plan.policy.valueFeedback.upstreamPrompt` is OFF
+- Session end when `friction:*` ledger signals or the operator reports a directive shortfall
+- After the operator opts into upstream filing via the audited setter below
 
 ## Preconditions
 
 - ! Run only from a **consumer project** -- the filing path no-ops inside the directive maintainer repo
-- ! `plan.policy.valueFeedback.upstreamPrompt` MUST be ON (`task policy:show --field=valueFeedback`)
+- ! Filing requires `plan.policy.valueFeedback.upstreamPrompt` ON. If OFF, draft with `deft feedback:file --dry-run` / `--json` (title+body still print), then ask the operator to enable via `deft policy:enable-value-feedback --confirm --upstream-prompt`. If declined, STOP safely -- do not hand-edit PROJECT-DEFINITION.
+- ! Inspect current state with `deft policy:show --field=valueFeedback`
 - ⊗ File upstream issues without explicit operator confirmation
-- ⊗ Invoke when `valueFeedback.enabled` is OFF
+- ⊗ Treat handwritten typed-block / PROJECT-DEFINITION edits as the primary audited setter
 
 ## Phase 1 -- Collect (batched)
 
 - ! Gather concrete gap reports from the session: what was expected, what happened, and minimal reproduction context
 - ! Batch multiple friction items into one upstream issue when they share a root cause; otherwise prepare separate drafts
 - ~ Prefer attributed phrasing ("encoding gate blocked a valid file") over vague quality claims
+- ! Follow [`docs/framework-gap-filing.md`](../../docs/framework-gap-filing.md) for title/BLOCKER, section shape, empty create labels, privileged `adoption-blocker`, dedup, and Refs
 
 ## Phase 1.5 -- Adoption-blocker judgment
 
@@ -46,23 +49,24 @@ Legend (from RFC2119): !=MUST, ~=SHOULD, ≉=SHOULD NOT, ⊗=MUST NOT, ?=MAY.
 
 ## Phase 2 -- Draft + dedup
 
-- ! For each candidate report, run a dry draft:
+- ! For each candidate report, run a dry draft (reuse the same report fields and target repo in Phase 3; confirmation adds `--confirm` and drops `--dry-run`/`--json`):
 
 ```bash
-task feedback:file -- --summary "<one-line summary>" --context "<session context>" --expected "<expected>" --actual "<actual>" --notes "<optional>" [--blocker --flow "<flow and version>" --alternatives "<alts>" --recovery-cost "<cost>"]
+deft feedback:file --summary "<one-line summary>" --context "<session context>" --expected "<expected>" --actual "<actual>" --notes "<optional>" [--blocker --flow "<flow and version>" --alternatives "<alts>" --recovery-cost "<cost>"] [--dry-run|--json]
 ```
 
 - ! Read the printed draft title/body with the operator before proceeding
 - ! If the command reports a duplicate open issue, STOP and link the existing issue instead of filing again
 - ⊗ Proceed past a duplicate-detection block without operator override
+- ~ When go-task is installed, the Taskfile may wrap the same verb; prefer `deft feedback:file` as primary
 
 ## Phase 3 -- Confirm + file
 
 - ! Present the final draft and ask for explicit yes/no confirmation
-- ! Only after approval, re-run with `--confirm`:
+- ! Only after approval, re-run the **same report fields and target repo** with `--confirm` added and without `--dry-run` or `--json`:
 
 ```bash
-task feedback:file -- --summary "<one-line summary>" --context "<session context>" --expected "<expected>" --actual "<actual>" --confirm [--blocker]
+deft feedback:file --summary "<one-line summary>" --context "<session context>" --expected "<expected>" --actual "<actual>" --confirm [--blocker]
 ```
 
 - ! Print the filed issue URL to the operator
@@ -80,3 +84,4 @@ task feedback:file -- --summary "<one-line summary>" --context "<session context
 - ⊗ Treating `--confirm` as implicit from broad session approval -- require an explicit filing confirmation step
 - ⊗ Infer "not a blocker" from an unmarked report -- absence of `BLOCKER` means not classified
 - ⊗ Auto-apply `adoption-blocker` from a consumer-authored title
+- ⊗ Hand-editing PROJECT-DEFINITION to flip `upstreamPrompt` instead of the audited setter

package/vendor/directive-content/skills/deft-directive-product-signal/SKILL.md

@@ -75,7 +75,7 @@ task product-signal:submit -- --surface pulse --nps 9
 ## Private gaps (D19)
 
 - ! Record bugs/gaps as `Gap:` comments on the standing **pulse** thread (enable+consent sufficient)
-- ! Public promote to `deftai/directive` remains hard-confirm via `deft-directive-feedback` / `task feedback:file`
+- ! Public promote to `deftai/directive` remains hard-confirm via `deft-directive-feedback` / `deft feedback:file`
 
 ## Revoke