@momentiq/dark-factory-cli 3.0.1 → 3.0.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@momentiq/dark-factory-cli",
-  "version": "3.0.1",
+  "version": "3.0.2",
   "description": "Dark Factory OSS CLI — multi-vendor adversarial critic orchestration (Cursor, Codex, Gemini, Grok) with min-complete-quorum aggregation and trusted-surface rebind",
   "license": "Apache-2.0",
   "homepage": "https://momentiq.ai/dark-factory",

package/skills/designer-handoff/SKILL.md.tmpl

@@ -27,18 +27,30 @@ unassigned; it prints the Issue URL. Link the relevant PR or issue with
 
 ```bash
 df handoff --link pr:<PR#> <<'EOF'
-<the composed, scrubbed note — see structure below>
+<the composed, scrubbed note from "Dual-register" below —
+ INCLUDING its <!-- agent-context:v1 --> … <!-- /agent-context:v1 --> markers>
 EOF
 ```
 
+The note **must** be wrapped in the `<!-- agent-context:v1 -->` …
+`<!-- /agent-context:v1 -->` markers (they anchor the Issue-body upsert);
+`df handoff` refuses a note that is missing them.
+
 ## Dual-register: two audiences, one artifact
 
 Write the note for the **engineer**, and speak a separate plain sentence to the
 **operator**.
 
-Engineer-facing note (structured, precise):
+Engineer-facing note (structured, precise). Keep the `agent-context:v1` markers
+around the whole note — copy this verbatim into the heredoc above:
 
 ```markdown
+<!-- agent-context:v1 -->
+> 🤖 **Handoff context** — transient working memory, not a source of truth.
+> _Updated: <YYYY-MM-DD> by <your session>_
+
+**Work-stream:** `<the ask, in one line>` · the handoff Issue's title.
+
 ## Intent
 What the operator asked for, in their words.
 
@@ -48,6 +60,7 @@ What is already built and where (branch or PR), and what is verified visually.
 ## Blocked — why
 The specific boundary: which scope, protected path, dependency, or gate — and
 what an engineer needs to decide or do next.
+<!-- /agent-context:v1 -->
 ```
 
 Operator-facing sentence (plain, framed as progress):

package/skills/designer-ship/SKILL.md.tmpl

@@ -18,12 +18,14 @@ The brief's **Done-when checkboxes are the acceptance criteria.** Before
 shipping, confirm each is satisfied and backed by the before/after screenshots
 from `/designer-build` — a Done-when item with no visible proof is not done.
 
-Make "done" proof-bound, not free text. Where the change has a
-`.darkfactory/objectives.yaml`, verify it and read the closeout proof with
-`df prove` (per-objective proven/pending/failed); see the `/objectives` skill
-for authoring and binding mechanics. (Automated derivation of objectives
-directly from a brief is a later Designer-Mode phase; today, treat the Done-when
-list as the contract and verify each item visually.)
+Make "done" proof-bound, not free text. Derive an objectives contract straight
+from the brief with **`df objectives derive --brief <brief-path> --apply`** — it
+writes one objective per `## Done-when` checkbox to `.darkfactory/objectives.yaml`,
+each text-hash-bound to its source line (id form `brief-<slug>#ac<k>`). Verify the
+bindings and read the closeout proof with `df prove` (per-objective
+proven/pending/failed); see the `/objectives` skill for authoring and binding
+mechanics. Still confirm each Done-when item **visually** — the before/after
+screenshots are the evidence behind the proof.
 
 ## 2. Run the gates locally first
 
@@ -42,14 +44,15 @@ Mode: designer
 Closes #<N>
 ```
 
-The `Mode: designer` trailer tags the PR as designer-driven. Today, scope is
-enforced live by the PreToolUse guard during the session, and the change still
-faces the full multi-vendor critic quorum + merge queue like any other PR. The
-deterministic mode-scope critic — which reads this trailer to validate the diff
-against the catalog's writeScopes / protectedPaths / diffBudget and block an
-out-of-scope diff at merge time, even from a jailbroken local session — lands in
-a later Designer-Mode phase; the trailer is the label it will key on.
-`Closes #<N>` links the tracking issue.
+The `Mode: designer` trailer is what the **deterministic mode-scope critic**
+keys on: it reads the trailer, loads the catalog, and validates the diff against
+the mode's `writeScopes` / `protectedPaths` / `diffBudget` / `dependencyPolicy`,
+blocking an out-of-scope diff at merge time — even from a jailbroken local
+session, because CI re-derives scope from the *committed* trailer + catalog
+independently of whatever happened locally. Scope is *also* enforced live
+in-session by the PreToolUse guard, and the change still faces the full
+multi-vendor critic quorum + merge queue like any other PR. `Closes #<N>` links
+the tracking issue.
 
 Open the PR and embed the **before/after screenshots** in the body so the change
 is visible to reviewers and the operator: