dflow-sdd-ddd 0.13.0 → 0.14.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dflow-sdd-ddd",
-  "version": "0.13.0",
+  "version": "0.14.0",
   "description": "Spec-first SDD/DDD workflow kit for AI-assisted development",
   "type": "commonjs",
   "bin": {
@@ -39,7 +39,7 @@
   },
   "homepage": "https://github.com/weilung/dflow-sdd-ddd#readme",
   "scripts": {
-    "test": "node test/smoke.mjs && node test/skill-default.mjs && node test/registry-parity.mjs && node test/agent-inject.mjs && node test/bundle-guards.mjs && node test/render.mjs"
+    "test": "node test/smoke.mjs && node test/skill-default.mjs && node test/registry-parity.mjs && node test/agent-inject.mjs && node test/upgrade-drift.mjs && node test/bundle-guards.mjs && node test/render.mjs"
   },
   "license": "AGPL-3.0-or-later",
   "publishConfig": {

package/templates/brownfield/references/init-project-flow.md

@@ -104,7 +104,9 @@ Used to substitute `{Framework}` / `{Framework version}` / `{Language}` /
 If yes → `_overview.md` "Target Architecture Strategy" section is emphasised and
 `migration/tech-debt.md` is prioritised. If no → the scaffolding still
 mentions the principles (Migration Awareness / Domain Extraction /
-Dual-Track Parallel / Pragmatic First) but framed as forward-option.
+Dual-Track Parallel / Pragmatic First) but framed as forward-option. Either
+way the answer is recorded in the `Migration / legacy context` row of the AI
+agent guide's `## Project Context` table.
 
 ### Q4. Project prose language
 

package/templates/brownfield/scaffolding/AI-AGENT-GUIDE.md

@@ -13,6 +13,11 @@ This project uses Dflow for spec-first AI-assisted development.
 | Migration / legacy context | {migration-context} |
 | Prose language | {prose-language} |
 
+<!-- dflow-generated: guide-canonical START -->
+<!-- Everything between these markers is Dflow-managed canonical guide content.
+     `dflow configure-agents` refreshes it in place on upgrade. Put project-specific
+     notes in "## Project Context" above (or outside the markers), not in here. -->
+
 ## Why This Matters
 
 This project has business logic embedded in delivery/entrypoint code
@@ -300,7 +305,7 @@ needed). The criteria below apply when `/dflow:modify-existing` or
 | Tier | Scenario | Output | Command / Trigger |
 |---|---|---|---|
 | **T1 Heavy** | New feature, new phase, architectural change, new BR | Independent `phase-spec-YYYY-MM-DD-{slug}.md` placed in the feature directory + `_index.md` Phase Specs row + refresh BR Snapshot | `/dflow:new-feature` / `/dflow:new-phase` |
-| **T2 Light** | Bug fix, UI input validation tweak, flow branch change — has BR Delta | Independent `lightweight-{YYYY-MM-DD}-{slug}.md` (or `BUG-{NUMBER}-{slug}.md`) inside the feature directory + `_index.md` Lightweight Changes row (outbound link) + refresh BR Snapshot | `/dflow:bug-fix` or `/dflow:modify-existing` (lightweight branch) |
+| **T2 Light** | Bug fix, UI input validation tweak, flow branch change — has BR Delta | Independent `lightweight-YYYY-MM-DD-{slug}.md` (or `BUG-{NUMBER}-{slug}.md`) inside the feature directory + `_index.md` Lightweight Changes row (outbound link) + refresh BR Snapshot | `/dflow:bug-fix` or `/dflow:modify-existing` (lightweight branch) |
 | **T3 Trivial** | Button colour, copy/text fix, typo, formatting, pure comments — **no BR change, no Domain concept change, no data structure change** | **Inline row in `_index.md` Lightweight Changes only** (no independent spec file) | `/dflow:modify-existing` (`_index-only` branch) |
 
 **T3 criteria** (the AI must satisfy **all four** before classifying T3):
@@ -426,3 +431,5 @@ should stay thin and point back here.
 If a tool does not support Dflow slash commands, treat the command names as
 plain workflow names and follow the matching flow file from the workflow bundle
 at `dflow/specs/shared/dflow-workflows/`.
+
+<!-- dflow-generated: guide-canonical END -->

package/templates/greenfield/references/init-project-flow.md

@@ -110,12 +110,12 @@ Used to substitute `{Framework version}` / `{ORM version}` /
 
 > "Was this project ported / migrated from a prior stack (e.g. legacy
 > presentation framework, monolith), or is it new-build on the chosen
-> framework? If migrated, is there any legacy concern you'd like the
-> overview to flag?"
+> framework? If migrated, is there any legacy concern you'd like noted?"
 
-If migrated → `_overview.md` can carry a short migration-context note.
-Otherwise skip. In the Greenfield track, migration is not the first-class
-concern, but noting origin is still useful.
+If migrated → the answer is recorded in the `Migration / legacy context` row
+of the AI agent guide's `## Project Context` table. If not migrated, skip —
+the row records `none`. In the Greenfield track, migration is not the
+first-class concern, but noting origin is still useful.
 
 ### Q4. Project prose language
 

package/templates/greenfield/scaffolding/AI-AGENT-GUIDE.md

@@ -13,6 +13,11 @@ This project uses Dflow for spec-first AI-assisted development.
 | Migration / legacy context | {migration-context} |
 | Prose language | {prose-language} |
 
+<!-- dflow-generated: guide-canonical START -->
+<!-- Everything between these markers is Dflow-managed canonical guide content.
+     `dflow configure-agents` refreshes it in place on upgrade. Put project-specific
+     notes in "## Project Context" above (or outside the markers), not in here. -->
+
 ## Before Editing Code
 
 Do not jump from a request directly to code. First identify the matching
@@ -258,7 +263,7 @@ judgement needed). The criteria below apply when `/dflow:modify-existing` or
 | Tier | Scenario | Output | Command / Trigger |
 |---|---|---|---|
 | **T1 Heavy** | New feature, new phase, new Aggregate / BC, architectural change, new BR | Independent `phase-spec-YYYY-MM-DD-{slug}.md` placed in the feature directory + `_index.md` Phase Specs row + refresh BR Snapshot. For a new Aggregate / BC also create an `aggregate-design.md` from `templates/aggregate-design.md` **in the feature directory** (working worksheet; the durable summary stays in `models.md`) + update `context-map.md` + `events.md`. | `/dflow:new-feature` / `/dflow:new-phase` |
-| **T2 Light** | Bug fix (logic error), UI input validation tweak, flow branch change — has BR Delta | Independent `lightweight-{YYYY-MM-DD}-{slug}.md` (or `BUG-{NUMBER}-{slug}.md`) inside the feature directory + `_index.md` Lightweight Changes row (outbound link) + refresh BR Snapshot. Confirm the fix lands in the correct architectural layer. | `/dflow:bug-fix` or `/dflow:modify-existing` (lightweight branch) |
+| **T2 Light** | Bug fix (logic error), UI input validation tweak, flow branch change — has BR Delta | Independent `lightweight-YYYY-MM-DD-{slug}.md` (or `BUG-{NUMBER}-{slug}.md`) inside the feature directory + `_index.md` Lightweight Changes row (outbound link) + refresh BR Snapshot. Confirm the fix lands in the correct architectural layer. | `/dflow:bug-fix` or `/dflow:modify-existing` (lightweight branch) |
 | **T3 Trivial** | Button colour, copy/text fix, typo, formatting, pure comments — **no BR change, no Domain concept change, no data structure change** | **Inline row in `_index.md` Lightweight Changes only** (no independent spec file) | `/dflow:modify-existing` (`_index-only` branch) |
 
 **T3 criteria** (the AI must satisfy **all four** before classifying T3):
@@ -389,3 +394,5 @@ should stay thin and point back here.
 If a tool does not support Dflow slash commands, treat the command names as
 plain workflow names and follow the matching flow file from the workflow bundle
 at `dflow/specs/shared/dflow-workflows/`.
+
+<!-- dflow-generated: guide-canonical END -->