@devflow-core/dsh-devflow 0.7.0 → 0.9.0

package/assets/presets/devflow-2/agent.cordis.yml

@@ -88,7 +88,12 @@
 # restores THIS text after promotion. The DevFlow paragraph guarantees
 # activation even when the model would otherwise skip reading AGENTS.md; the
 # route table and hard boundaries stay in the devflow-core skill and AGENTS.md
-# (single source, no duplication).
+# (single source, no duplication). The two trailing paragraphs carry the
+# AGENTS.md rules no lifecycle skill owns — Independent Judgment and the
+# fallback output contracts — because `instructionHint: true` (tool-bootstrap
+# above) replaces the workspace AGENTS.md digest with a reference hint once the
+# session is promoted.
+# devflow: ceiling: clause-level restatement checked by scripts/validate-devflow.js, not full semantic alignment; revisit when either AGENTS.md section is reworded.
 - id: persona
   name: '@deepseek-ai/dsh-persona'
   config:
@@ -97,6 +102,10 @@
 
       You run DevFlow. Before any development work — creating features, building components, adding functionality, modifying behavior, or defining an unapproved problem-directed change — load the `devflow-core` skill with the skill tool and read its `core-methods.md` reference, then load only the selected lifecycle owner skill. The route table and hard boundaries live in that skill and in AGENTS.md; do not invent lifecycle details. Pure Q&A, lookup, verification, and investigation-only reports need no lifecycle.
 
+      Independent judgment: before answering or acting, check for false premises, logical leaps, and material missing information; never agree merely to accommodate the user — when disagreeing, state the evidence, risks, and plausible alternative explanations; separate verified facts, inferences, and opinions, and state the evidence boundary when verification is unavailable; name overlooked variables, costs, constraints, and likely biases.
+
+      Fallback output contracts: design as Goal / Smallest useful plan / Not doing / Impact / Verification; completion as Command / Result / Adversarial review / Judgment (PASS, FAIL, or BLOCKED).
+
 - id: agent-instructions
   name: '@deepseek-ai/dsh-agent-instructions'
   config:

package/assets/skills/devflow-build/references/build-methods.md

@@ -42,3 +42,5 @@ A function may contain several steps when they form one coherent business narrat
 ## Build Comments
 
 The approved Spec/Plan and local project convention define required code comments. Add a comment when it records a protected contract, failure condition, business rule, compatibility boundary, or other non-obvious reason; inline comments explain reasons, not syntax. Markdown runtime contracts use headings and fixed output shapes rather than narrative comments.
+
+When a comment describes behavior, write it from the accepted final state. Regenerate it from the final behavior instead of editing rejected wording; comments never narrate rejected alternatives, session corrections, intermediate attempts, or why-not-X reasoning, and keep only the non-obvious reasons a future maintainer needs.

package/assets/skills/devflow-core/SKILL.md

@@ -22,6 +22,14 @@ Status: [DevFlow: <node> -> <next> | awaiting approval / in progress]
 
 While a DevFlow lifecycle node is active, end each user-facing message with one status line: `[DevFlow: <node> -> <next> | awaiting approval / in progress]`. It reflects the current node without reloading the owner skill. Keep progress visible in the persistent UI: maintain a `todo_write` list with one item per active work unit (lifecycle node, background job, or subagent), marking it `completed` the moment it settles, and use `create_goal` for the session's long-running objective.
 
+## Delivery Surfaces
+
+Final artifacts and their wrappers — titles, filenames, body text, comments, tags, commits, PR text, documents, and handoffs — describe the accepted final state, assuming the reader did not see this session; rejected session-only alternatives, intermediate attempts, and wording corrections stay control data.
+
+For each surface, decide whether a session-less reader needs the information: keep an exclusion only when omission would make the artifact inaccurate, unsafe, misleading, or incompatible, or when this surface must explain a real change from the committed or user-approved baseline. Regenerate high-salience names, titles, and openings from the positive target instead of editing rejected wording, and never write an absent option as a labeled absence. Keep real baseline changes, executed external actions, required technical names, diagnostics, tests, and pre-existing user changes.
+
+Before completion, reread every user-visible surface and wrapper, including filenames, metadata, and hook rewrites, and recheck after any content change. Keep unrelated changes out of this task's commit, PR, or handoff; keep comparisons, quotations, audits, or migration notes only when the user asked or the surface requires them, and do not add cleanup or no-residue claims.
+
 ## Context Map
 
 Read `skills/devflow-core/references/core-methods.md` before route selection. It supplies Method 0, shared route rules, and the owner map. Do not load all lifecycle references by default.

package/assets/skills/devflow-docs-followup/SKILL.md

@@ -41,6 +41,8 @@ Rules:
 
 Before writing a selected document, read the current diff, implementation, tests, commands, and user-confirmed decisions. Use project documentation conventions and templates when they exist.
 
+Describe the accepted final state: session-only alternatives, intermediate attempts, and corrections stay out of created documents. Regenerate titles and openings from the positive target; keep API names, real removals, executed external actions, diagnostics, tests, and compatibility facts that accuracy requires, and keep unrelated changes out unless the document requires them.
+
 When the target project has no relevant convention, use these fallback locations:
 
 | Document type | Fallback path |

package/assets/skills/devflow-prove/references/proof-recovery-methods.md

@@ -17,6 +17,8 @@ Adversarial review: <acceptance, regressions, activation, proof coverage>
 Judgment: PASS / FAIL / BLOCKED
 ```
 
+Before the completion report, reread every final artifact and its wrapper — filenames, titles, comments, tags, documents, commit or PR text, metadata, hook rewrites, and the report itself — as a reader without access to this session, and describe only the accepted final state. Recheck after any content change; keep deliberate decision records, safety and compatibility facts, real baseline changes, executed external actions, and pre-existing user changes; keep unrelated changes out of this task's commit, PR, or handoff, and do not add cleanup or no-residue claims.
+
 `PASS` is Prove's terminal success after Learn review. Proof `FAIL`, `BLOCKED`, a real adversarial gap, unresolved Code Review Blocker/Warning, or incomplete PUA recovery evidence returns its facts to `devflow-core`; Core selects the repair, recovery, or re-clarification path. Prove never infers that next owner.
 
 ### Quality-Finding Recovery

package/assets/skills/devflow-spec/references/spec-plan-methods.md

@@ -8,6 +8,8 @@ Owner: `devflow-spec` and `devflow-plan`. Load this reference only after Core se
 
 `devflow-plan` consumes A/B `CUT_PASS` plus an approved design or confirmed Spec. It creates one implementation plan under `docs/plans/`, then waits for user review. An approved A/B Plan directly enters Build; scope-drift facts return to Core.
 
+Spec and Plan names, titles, and framing describe the accepted final state, regenerated from the positive target rather than edited from rejected wording. Keep Non-goals and Rejected as deliberate decision records; keep unrelated changes, comparisons, quotations, audits, or migration notes out unless the user asked or the document requires them.
+
 A Spec contains Goal, Context, Requirements, Non-goals, Approach, Impact, Acceptance, Verification, Code Documentation, and Open Questions. A Plan states Source, Spec coverage, Cut Decision, External Skills, exact files or anchors, interfaces, current and target behavior, mechanics, call impact, verification, comments, and exclusions.
 
 ## Plan Contract

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devflow-core/dsh-devflow",
-  "version": "0.7.0",
+  "version": "0.9.0",
   "description": "DevFlow for DeepSeek Harness: devflow-2 agent preset + skills + commands + verification scripts, synced into ~/.dsh on host startup.",
   "type": "module",
   "engines": {