@xenonbyte/da-vinci-workflow 0.1.19 → 0.1.21

package/CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## v0.1.21 - 2026-03-29
+
+### Added
+- `scripts/test-mode-consistency.js` coverage for `build` completion-audit discipline and `continue` build-recommendation gate behavior
+- `scripts/test-pencil-session.js` coverage requiring live snapshot input for `pencil-session end` unless `--force` is used
+
+### Changed
+- `da-vinci pencil-session end` now requires `--nodes-file` (and optional variables/version payload) unless `--force` is explicitly provided
+- `build` prompts across Codex, Claude, and Gemini now treat compile success as non-terminal and require completion-audit pass before terminal completion claims
+- `continue` prompts across Codex, Claude, and Gemini now block build recommendation while unresolved design gates exist
+- command reference docs (English and Chinese) now reflect the stricter build/continue routing discipline and completion gate expectations
+
+## v0.1.20 - 2026-03-29
+
+### Added
+- `scripts/test-audit-context-delta.js` to cover context-delta expectation signals, status mismatch reporting, `supersedes` validation, and timestamp-normalized reference matching
+
+### Changed
+- continue prompt/docs behavior now consistently route from artifact and checkpoint truth first, with contextual deltas used only as auxiliary recovery context
+- context-delta audit expectation signals now trigger on `## Checkpoint Status` and `## MCP Runtime Gate` (or explicit `Context Delta Required` opt-in) instead of broad `## Outcome` matching
+- context-delta mismatch warnings now use neutral status-mismatch wording and include per-checkpoint status history
+- context-delta `supersedes` fields are now validated against earlier entries in the same artifact, including parseable timestamp normalization
+- README, Chinese README, workflow docs, prompt docs, and templates now document automatic context-delta checks plus optional explicit opt-in usage
+
 ## v0.1.19 - 2026-03-28
 
 ### Added

package/README.md

@@ -28,10 +28,17 @@ This workflow is intended for:
 
 Latest published npm package:
 
-- `@xenonbyte/da-vinci-workflow@0.1.19`
+- `@xenonbyte/da-vinci-workflow@0.1.21`
 
 Release highlights:
 
+- `da-vinci pencil-session end` now requires live snapshot input (`--nodes-file`) unless `--force` is used, preventing silent session close while live MCP and disk are out of sync
+- `build` route discipline now treats compile success as non-terminal and requires `da-vinci audit --mode completion --change <change-id> <project-path>` before reporting terminal completion
+- `continue` route guidance now blocks `build` recommendation whenever core design gates remain unresolved (missing project-local `.pen`, active session, runtime/design-source BLOCK, or required design-supervisor BLOCK)
+- added regression coverage for session-end sync guards and prompt-level build/continue gate discipline
+- continue-routing and recovery guidance now consistently prioritize artifact/checkpoint truth first, with contextual deltas treated as auxiliary notes only
+- context-delta audit now uses tighter expectation signals, status-mismatch wording, and `supersedes` validation with timestamp normalization
+- context-delta expectation checks are now automatic for checkpoint-bearing artifacts and allow explicit opt-in (`Context Delta Required`) only for edge cases
 - `design-supervisor review` is now a first-class final style-quality gate with explicit advisory versus required behavior controlled by `Require Supervisor Review`
 - `Visual Assist` docs now explain gate order, gate judging criteria, and branching across screenshot review, layout hygiene, design checkpoint, and design-supervisor review
 - `visual-assist-presets` for mobile, desktop, web, and tablet now ship three explicit variants: adapter-only, advisory reviewer, and required reviewer signoff in both English and Chinese
@@ -118,6 +125,9 @@ Route discipline:
 - `intake` and `continue` should usually generate a main `$da-vinci ...` or `/da-vinci ...` prompt
 - they should not default the user into `build`
 - `build` remains a direct expert route for workflows that are already implementation-ready
+- `continue` should determine route selection from artifact and checkpoint truth first
+- contextual checkpoint deltas are auxiliary recovery notes only and must not override routing
+- if contextual deltas conflict with current artifacts, ignore them for routing and record the conflict
 
 ## Visual Assist Quick Start
 
@@ -127,32 +137,14 @@ Recommended default:
 
 ```md
 ## Visual Assist
-- Preferred adapters:
-  - ui-ux-pro-max
-  - frontend-skill
-- Design-supervisor reviewers:
-  - frontend-skill
-  - ui-ux-pro-max
-- Design-supervisor review mode:
-  - screenshot-and-theme
-- Design-supervisor review inputs:
-  - screenshots
-  - pencil variables
-  - visual thesis
-  - content plan
-  - interaction thesis
-- Scope:
-  - visual contract refinement
-  - page composition
-  - hierarchy and spacing
-  - anchor-surface composition
-  - Pencil design refinement
-- Fallback:
-  - native-da-vinci
-- Require Adapter:
-  - false
-- Require Supervisor Review:
-  - false
+- Preferred adapters: ui-ux-pro-max, frontend-skill
+- Design-supervisor reviewers: frontend-skill, ui-ux-pro-max
+- Design-supervisor review mode: screenshot-and-theme
+- Design-supervisor review inputs: screenshots, pencil variables, visual thesis, content plan, interaction thesis
+- Scope: visual contract refinement, page composition, hierarchy and spacing, anchor-surface composition, Pencil design refinement
+- Fallback: native-da-vinci
+- Require Adapter: false
+- Require Supervisor Review: false
 ```
 
 Use this when:
@@ -165,33 +157,14 @@ Quality-first redesign configuration:
 
 ```md
 ## Visual Assist
-- Preferred adapters:
-  - frontend-skill
-  - ui-ux-pro-max
-- Design-supervisor reviewers:
-  - frontend-skill
-  - ui-ux-pro-max
-- Design-supervisor review mode:
-  - screenshot-and-theme
-- Design-supervisor review inputs:
-  - screenshots
-  - pencil variables
-  - visual thesis
-  - content plan
-  - interaction thesis
-- Scope:
-  - visual contract refinement
-  - page composition
-  - hierarchy and spacing
-  - motion guidance
-  - anchor-surface composition
-  - Pencil design refinement
-- Fallback:
-  - native-da-vinci
-- Require Adapter:
-  - true
-- Require Supervisor Review:
-  - true
+- Preferred adapters: frontend-skill, ui-ux-pro-max
+- Design-supervisor reviewers: frontend-skill, ui-ux-pro-max
+- Design-supervisor review mode: screenshot-and-theme
+- Design-supervisor review inputs: screenshots, pencil variables, visual thesis, content plan, interaction thesis
+- Scope: visual contract refinement, page composition, hierarchy and spacing, motion guidance, anchor-surface composition, Pencil design refinement
+- Fallback: native-da-vinci
+- Require Adapter: true
+- Require Supervisor Review: true
 ```
 
 Use this when:
@@ -340,6 +313,11 @@ Checkpoint outcomes:
 - `WARN`
 - `BLOCK`
 
+Context delta notes:
+
+- keep concise `Context Delta` entries inside existing change artifacts (`pencil-design.md`, `tasks.md`, `verification.md`)
+- treat contextual deltas as recovery aids, not as a second source of phase truth
+
 ## Execution Policy
 
 Da Vinci is `autonomous-by-default`.
@@ -355,6 +333,7 @@ Default behavior:
 - `PASS` -> continue
 - `WARN` -> record and continue
 - `BLOCK` -> stop only when the blocker cannot be resolved from existing artifacts or local context
+- missing or status-mismatched contextual deltas -> warn and continue
 
 Typical stop conditions:
 
@@ -476,6 +455,13 @@ da-vinci uninstall --platform codex,claude,gemini
 - `--mode integrity`: a mid-workflow filesystem-truth check for missing baseline artifacts, misplaced exports, polluted `.da-vinci/designs/`, and missing persisted `.pen` sources
 - `--mode completion`: a strict pre-completion gate for one change scope; use `--change <change-id>` and treat any failure as blocking
 
+Context-delta integration in audit:
+
+- missing, incomplete, or status-mismatched contextual delta entries are warning-level signals
+- these warnings improve resume quality but do not introduce new completion failure gates by themselves
+- expectation checks are automatic when an artifact includes `## Checkpoint Status` or `## MCP Runtime Gate`; no manual toggle is needed in normal workflows
+- only add `Context Delta Required: true` (also accepts `yes` / `on` / `1`) for artifacts that intentionally opt in without those headings
+
 Both modes check the most common workflow-integrity failures in a project:
 
 - missing standard Da Vinci artifacts

package/README.zh-CN.md

@@ -30,10 +30,17 @@ Da Vinci 是一个把产品需求一路推进到结构化规格、Pencil 设计
 
 最新已发布 npm 包：
 
-- `@xenonbyte/da-vinci-workflow@0.1.19`
+- `@xenonbyte/da-vinci-workflow@0.1.21`
 
 已发布版本重点：
 
+- `da-vinci pencil-session end` 现在默认要求提供 live 快照输入（`--nodes-file`）；只有显式 `--force` 才允许跳过，避免 live MCP 与磁盘未同步时被静默关闭
+- `build` 路由现在明确：编译成功不等于流程完成；对外宣布终态前必须通过 `da-vinci audit --mode completion --change <change-id> <project-path>`
+- `continue` 的推荐规则现在会拦截未过设计门禁时的 `build` 选路（缺少项目内 `.pen`、session 未关闭、runtime/design-source BLOCK、required design-supervisor BLOCK）
+- 新增回归测试覆盖：session 结束同步防护，以及 build/continue 提示词级门禁约束
+- `continue` 的选路与恢复规则现已统一：先看工件/checkpoint 真相，再把 Context Delta 当作辅助信息
+- Context Delta 审计规则已强化：触发信号更精确、告警改为状态不一致语义，并补充 `supersedes` 校验与时间归一化
+- checkpoint 相关工件默认自动启用 Context Delta 期望检查；只有少数无 checkpoint 标题的工件才需要显式 `Context Delta Required`
 - `design-supervisor review` 现在成为正式的最终风格质量 gate，并通过 `Require Supervisor Review` 明确区分“建议性”与“硬门槛”
 - `Visual Assist` 文档现在补全了 gate 顺序、每层 gate 怎么审，以及 screenshot review、layout hygiene、design checkpoint、design-supervisor review 之间的分叉规则
 - 移动端、桌面端、Web、平板四套 `visual-assist-presets` 现在都提供三种明确变体：只有 adapter、reviewer 建议性审查、reviewer 硬签字，中英文一致
@@ -123,6 +130,9 @@ Da Vinci 当前支持五种模式：
 - `intake` 和 `continue` 通常应该回到主工作流入口，即 `$da-vinci ...` 或 `/da-vinci ...`
 - 它们不应该默认把用户直接导向 `build`
 - `build` 仍然保留，但它是给已经实现就绪的高级直接入口
+- `continue` 的选路应先看工件和 checkpoint 真相，再看上下文补充信息
+- Context Delta 只用于恢复上下文，不是阶段判定真相源
+- 如果 Context Delta 与当前工件冲突，应该忽略冲突条目并按工件真相继续
 
 ## Visual Assist 快速上手
 
@@ -132,32 +142,14 @@ Da Vinci 当前支持五种模式：
 
 ```md
 ## Visual Assist
-- Preferred adapters:
-  - ui-ux-pro-max
-  - frontend-skill
-- Design-supervisor reviewers:
-  - frontend-skill
-  - ui-ux-pro-max
-- Design-supervisor review mode:
-  - screenshot-and-theme
-- Design-supervisor review inputs:
-  - screenshots
-  - pencil variables
-  - visual thesis
-  - content plan
-  - interaction thesis
-- Scope:
-  - visual contract refinement
-  - page composition
-  - hierarchy and spacing
-  - anchor-surface composition
-  - Pencil design refinement
-- Fallback:
-  - native-da-vinci
-- Require Adapter:
-  - false
-- Require Supervisor Review:
-  - false
+- Preferred adapters: ui-ux-pro-max, frontend-skill
+- Design-supervisor reviewers: frontend-skill, ui-ux-pro-max
+- Design-supervisor review mode: screenshot-and-theme
+- Design-supervisor review inputs: screenshots, pencil variables, visual thesis, content plan, interaction thesis
+- Scope: visual contract refinement, page composition, hierarchy and spacing, anchor-surface composition, Pencil design refinement
+- Fallback: native-da-vinci
+- Require Adapter: false
+- Require Supervisor Review: false
 ```
 
 适用场景：
@@ -170,33 +162,14 @@ Da Vinci 当前支持五种模式：
 
 ```md
 ## Visual Assist
-- Preferred adapters:
-  - frontend-skill
-  - ui-ux-pro-max
-- Design-supervisor reviewers:
-  - frontend-skill
-  - ui-ux-pro-max
-- Design-supervisor review mode:
-  - screenshot-and-theme
-- Design-supervisor review inputs:
-  - screenshots
-  - pencil variables
-  - visual thesis
-  - content plan
-  - interaction thesis
-- Scope:
-  - visual contract refinement
-  - page composition
-  - hierarchy and spacing
-  - motion guidance
-  - anchor-surface composition
-  - Pencil design refinement
-- Fallback:
-  - native-da-vinci
-- Require Adapter:
-  - true
-- Require Supervisor Review:
-  - true
+- Preferred adapters: frontend-skill, ui-ux-pro-max
+- Design-supervisor reviewers: frontend-skill, ui-ux-pro-max
+- Design-supervisor review mode: screenshot-and-theme
+- Design-supervisor review inputs: screenshots, pencil variables, visual thesis, content plan, interaction thesis
+- Scope: visual contract refinement, page composition, hierarchy and spacing, motion guidance, anchor-surface composition, Pencil design refinement
+- Fallback: native-da-vinci
+- Require Adapter: true
+- Require Supervisor Review: true
 ```
 
 适用场景：
@@ -403,6 +376,13 @@ da-vinci uninstall --platform codex,claude,gemini
 - `--mode integrity`：适合在工作进行中检查文件系统真相，比如基础工件缺失、导出路径错误、`.da-vinci/designs/` 被污染、项目内 `.pen` 没落盘
 - `--mode completion`：适合在宣称完成前做严格检查；配合 `--change <change-id>` 使用，任何失败都应视为阻断
 
+Context Delta 与 audit 的关系：
+
+- Context Delta 缺失、字段不完整或与最新 checkpoint 不一致时，属于告警（`WARN`）
+- 这些告警用于提升续跑质量，不应单独变成新的 completion 失败门槛
+- 当工件包含 `## Checkpoint Status` 或 `## MCP Runtime Gate` 时，期望检查会自动启用，正常流程不需要手动开关
+- 只有在不包含这些标题但仍想启用检查时，才需要写 `Context Delta Required: true`（也支持 `yes` / `on` / `1`）
+
 两种模式都会检查项目里最常见的工作流完整性问题：
 
 - 标准 Da Vinci 工件缺失

package/SKILL.md

@@ -136,8 +136,11 @@ Use these helper actions when the user needs help entering or resuming the workf
      - detected workflow state
      - gaps or blockers
      - one executable continuation prompt
+     - contextual recovery notes from recent checkpoint deltas when consistent with current artifacts
    - do not restart discovery if the artifacts already provide enough truth
    - do not default to `build` unless the project is clearly implementation-ready
+   - determine route selection from artifact and checkpoint truth first; contextual deltas are auxiliary and must not override routing
+   - if contextual deltas conflict with current artifacts, ignore them for routing and record the conflict
 
 ## V2 Mode Selection
 
@@ -731,6 +734,7 @@ Checkpoint handling:
 - `PASS`: continue automatically
 - `WARN`: record the issue and continue automatically
 - `BLOCK`: stop, report the blocker, and ask only if the blocker cannot be resolved from existing artifacts
+- contextual-delta issues: warn and continue; do not treat missing/stale contextual notes as standalone blockers
 
 ## Drift Policy
 

package/commands/claude/dv/build.md

@@ -15,3 +15,9 @@ Focus on:
 During implementation:
 - run `execution checkpoint` after each top-level task group
 - update source artifacts before continuing if drift is found
+
+Completion discipline:
+- treat `BUILD SUCCESSFUL` as compile-only evidence, not workflow completion
+- do not report `design complete` or `workflow complete` while in-scope task groups remain unfinished
+- before any terminal completion claim, require `da-vinci audit --mode completion --change <change-id> <project-path>` to pass
+- if completion audit fails, continue from the minimal unfinished stage instead of exiting

package/commands/claude/dv/continue.md

@@ -15,12 +15,17 @@ Focus on:
 Output should include:
 - detected workflow state
 - missing or weak artifacts
+- contextual recovery notes from recent checkpoint deltas when they are consistent with current artifacts
 - one primary `/da-vinci continue ...` prompt
 - one more conservative continuation prompt when useful
 
 Route discipline:
 - do not restart discovery if the current artifacts already contain enough truth
+- determine route selection from artifact and checkpoint truth before reading contextual deltas
+- use contextual deltas as auxiliary recovery context only; they must not override route selection
+- if contextual deltas conflict with current artifacts, ignore them for routing and call out the conflict
 - do not default the user into `/dv:build` unless the project is clearly implementation-ready
 - if design artifacts exist but `tasks.md` does not, prefer a continuation prompt that moves into `/dv:tasks`
 - only prefer `/dv:build` once task generation and implementation readiness are already clear
+- do not route into `/dv:build` when any design gate is unresolved: missing shell-visible project-local `.pen`, active/unclosed Pencil session, runtime/design-source checkpoint still BLOCK, or required design-supervisor review still BLOCK/unaccepted
 - continuation prompts should usually target the main workflow entry so Da Vinci can resume the full state machine

package/commands/codex/prompts/dv-build.md

@@ -11,3 +11,7 @@ Implementation rules:
 - requirements decide behavior
 - Pencil decides presentation
 - run `execution checkpoint` after each top-level task group
+- treat `BUILD SUCCESSFUL` as compile-only evidence, not workflow completion
+- do not report `design complete` or `workflow complete` while in-scope task groups remain unfinished
+- before any terminal completion claim, require `da-vinci audit --mode completion --change <change-id> <project-path>` to pass
+- if completion audit fails, continue from the minimal unfinished stage instead of exiting

package/commands/codex/prompts/dv-continue.md

@@ -15,12 +15,17 @@ Goal:
 Output should include:
 - detected workflow state
 - missing or weak artifacts
+- contextual recovery notes from recent checkpoint deltas when they are consistent with current artifacts
 - one primary `$da-vinci continue ...` prompt
 - one more conservative continuation prompt when useful
 
 Route discipline:
 - do not restart discovery if the current artifacts already contain enough truth
+- determine route selection from artifact and checkpoint truth before reading contextual deltas
+- use contextual deltas as auxiliary recovery context only; they must not override route selection
+- if contextual deltas conflict with current artifacts, ignore them for routing and call out the conflict
 - do not default the user into `/prompts:dv-build` unless the project is clearly implementation-ready
 - if design artifacts exist but `tasks.md` does not, prefer a continuation prompt that moves into `/prompts:dv-tasks`
 - only prefer `/prompts:dv-build` once task generation and implementation readiness are already clear
+- do not route into `/prompts:dv-build` when any design gate is unresolved: missing shell-visible project-local `.pen`, active/unclosed Pencil session, runtime/design-source checkpoint still BLOCK, or required design-supervisor review still BLOCK/unaccepted
 - continuation prompts should usually target the main workflow entry so Da Vinci can resume the full state machine

package/commands/gemini/dv/build.toml

@@ -10,4 +10,8 @@ Implementation rules:
 - requirements decide behavior
 - Pencil decides presentation
 - run `execution checkpoint` after each top-level task group
+- treat `BUILD SUCCESSFUL` as compile-only evidence, not workflow completion
+- do not report `design complete` or `workflow complete` while in-scope task groups remain unfinished
+- before any terminal completion claim, require `da-vinci audit --mode completion --change <change-id> <project-path>` to pass
+- if completion audit fails, continue from the minimal unfinished stage instead of exiting
 """

package/commands/gemini/dv/continue.toml

@@ -14,13 +14,18 @@ Focus on:
 Output should include:
 - detected workflow state
 - missing or weak artifacts
+- contextual recovery notes from recent checkpoint deltas when they are consistent with current artifacts
 - one primary `/da-vinci continue ...` prompt
 - one more conservative continuation prompt when useful
 
 Route discipline:
 - do not restart discovery if the current artifacts already contain enough truth
+- determine route selection from artifact and checkpoint truth before reading contextual deltas
+- use contextual deltas as auxiliary recovery context only; they must not override route selection
+- if contextual deltas conflict with current artifacts, ignore them for routing and call out the conflict
 - do not default the user into `/dv:build` unless the project is clearly implementation-ready
 - if design artifacts exist but `tasks.md` does not, prefer a continuation prompt that moves into `/dv:tasks`
 - only prefer `/dv:build` once task generation and implementation readiness are already clear
+- do not route into `/dv:build` when any design gate is unresolved: missing shell-visible project-local `.pen`, active/unclosed Pencil session, runtime/design-source checkpoint still BLOCK, or required design-supervisor review still BLOCK/unaccepted
 - continuation prompts should usually target the main workflow entry so Da Vinci can resume the full state machine
 """

package/docs/codex-natural-language-usage.md

@@ -53,6 +53,7 @@ Use this when:
 - `DA-VINCI.md` already exists
 - `.da-vinci/` artifacts already exist
 - the workflow paused and needs to resume
+- route selection should come from artifact/checkpoint truth first, then contextual deltas
 
 ### Run a mode directly
 
@@ -151,6 +152,8 @@ $da-vinci use continue for this existing redesign-from-code workflow.
 
 Use the existing Da Vinci artifacts in this project.
 Existing code remains the behavior source of truth.
+Determine route progression from current artifacts and checkpoints first.
+Use contextual checkpoint deltas only as auxiliary recovery notes.
 Do not restart discovery unless an artifact is missing or clearly wrong.
 Do not stop at tasks.md.
 Continue into implementation and verification.

package/docs/dv-command-reference.md

@@ -73,6 +73,7 @@ Outputs:
 
 - detected workflow state
 - missing or weak artifacts
+- contextual recovery notes from recent checkpoint deltas when consistent with current artifacts
 - one primary continuation prompt
 - one conservative continuation prompt when useful
 
@@ -80,6 +81,9 @@ Important continuation rule:
 
 - if design exists but `tasks.md` does not, continuation should usually point to `tasks`
 - it should not promote `build` as a co-equal next step yet
+- route selection should be derived from artifact and checkpoint truth before contextual deltas are consulted
+- if contextual deltas conflict with current artifacts, ignore those deltas for route selection and report the conflict
+- do not route into `build` while design gates are unresolved: missing shell-visible project-local `.pen`, active/unclosed Pencil session, runtime or design-source checkpoint still `BLOCK`, or required design-supervisor review still `BLOCK`/unaccepted
 
 ### `/dv:breakdown`
 
@@ -151,6 +155,12 @@ Creates or updates:
 
 This is the execution stage.
 
+Completion discipline:
+
+- treat `BUILD SUCCESSFUL` as compile-only evidence
+- do not claim `design complete` or `workflow complete` while in-scope task groups remain
+- run `da-vinci audit --mode completion --change <change-id> <project-path>` before any terminal completion claim
+
 ### `/dv:verify`
 
 Use when:

package/docs/mode-use-cases.md

@@ -82,6 +82,8 @@ Common rule:
 
 - `intake` and `continue` should normally lead back to the main workflow entry
 - they should not default the user into `build` unless the project is already implementation-ready
+- `continue` should determine route selection from artifact/checkpoint truth first, then use contextual deltas as auxiliary recovery notes
+- if contextual deltas conflict with current artifacts, ignore those deltas for routing and record the conflict
 
 ---
 

package/docs/pencil-rendering-workflow.md

@@ -63,6 +63,14 @@ When the project already has a registered `.pen`:
 
 Da Vinci does not assume live MCP edits were flushed automatically.
 
+## Continuation Recovery Rule
+
+When resuming from existing artifacts:
+
+- choose routing from current artifact and checkpoint truth first
+- use checkpoint-adjacent `Context Delta` notes only as auxiliary recovery context
+- if a contextual delta conflicts with current artifact/checkpoint truth, ignore that conflicting entry and record the conflict before continuing
+
 ## Persistence Rule
 
 Da Vinci does not treat headless interactive `save()` as authoritative persistence truth.
@@ -227,6 +235,14 @@ da-vinci audit --mode completion --change <change-id> <project-path>
 
 This audit now also expects `.da-vinci/state/pencil-session.json` to reflect the latest persisted `.pen` hash.
 
+Context-delta audit expectations are warning-only:
+
+- missing concrete context deltas for checkpoint-bearing artifacts -> `WARN`
+- incomplete context-delta entries -> `WARN`
+- context-delta status mismatch with current checkpoints -> `WARN`
+- a mismatch can indicate stale checkpoint status or stale context-delta notes
+- these warnings improve resume quality but do not create standalone completion blockers
+
 ## Preferred Command Chain
 
 Typical autonomous chain:

package/docs/prompt-entrypoints.md

@@ -58,9 +58,16 @@ What it should output:
 
 - detected workflow state
 - missing or weak artifacts
+- contextual recovery notes from recent checkpoint deltas when available
 - one primary continuation prompt
 - one more conservative continuation prompt when useful
 
+Continuation precedence:
+
+- determine routing from artifact and checkpoint truth first
+- use contextual checkpoint deltas only as auxiliary recovery context
+- if contextual deltas conflict with current artifacts, ignore them for routing and note the conflict
+
 ## Default Flow
 
 Use this default sequence:

package/docs/prompt-presets/README.md

@@ -116,5 +116,7 @@ $da-vinci use continue for this existing overhaul-from-code workflow.
 
 Use the existing Da Vinci artifacts.
 Detect whether the workflow should return to breakdown, continue with design, generate tasks, continue implementation, or verify drift.
+Determine routing from artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
 ```

package/docs/prompt-presets/desktop-app.md

@@ -75,6 +75,8 @@ $da-vinci use continue for this existing overhaul-from-code desktop workflow.
 
 Use the existing Da Vinci artifacts.
 Detect whether the workflow should return to breakdown, continue with design, generate tasks, continue implementation, or verify drift.
+Determine routing from artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
 ```
 
@@ -187,6 +189,8 @@ $da-vinci use continue for this existing desktop-product redesign workflow.
 
 Use the existing Da Vinci artifacts in this project.
 Do not restart discovery unless an artifact is missing or clearly wrong.
+Determine continuation routing from current artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth. If the resumed session will perform Pencil edits, require `da-vinci pencil-session begin --project <project-path> --pen <path>`, then use `da-vinci pencil-session persist --project <project-path> --pen <path> ...` after material live edits; fall back to the lower-level `write-pen + check-pen-sync` path only when the session wrapper cannot be used.
 If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
 If Pencil MCP is active and this session performs new Pencil writes, rerun the MCP runtime gate and record the refreshed result in `pencil-design.md`.

package/docs/prompt-presets/mobile-app.md

@@ -75,6 +75,8 @@ $da-vinci use continue for this existing overhaul-from-code mobile workflow.
 
 Use the existing Da Vinci artifacts.
 Detect whether the workflow should return to breakdown, continue with design, generate tasks, continue implementation, or verify drift.
+Determine routing from artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
 ```
 
@@ -195,6 +197,8 @@ $da-vinci use continue for this existing mobile-app redesign workflow.
 
 Use the existing Da Vinci artifacts in this project.
 Do not restart discovery unless an artifact is missing or clearly wrong.
+Determine continuation routing from current artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth. If the resumed session will perform Pencil edits, require `da-vinci pencil-session begin --project <project-path> --pen <path>`, then use `da-vinci pencil-session persist --project <project-path> --pen <path> ...` after material live edits; fall back to the lower-level `write-pen + check-pen-sync` path only when the session wrapper cannot be used.
 If the redesign is complex, keep the anchor-first flow until the design checkpoint passes.
 If Pencil MCP is active and this session performs new Pencil writes, rerun the MCP runtime gate and record the refreshed result in `pencil-design.md`.

package/docs/prompt-presets/tablet-app.md

@@ -75,6 +75,8 @@ $da-vinci use continue for this existing overhaul-from-code tablet workflow.
 
 Use the existing Da Vinci artifacts.
 Detect whether the workflow should return to breakdown, continue with design, generate tasks, continue implementation, or verify drift.
+Determine routing from artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
 ```
 
@@ -187,6 +189,8 @@ $da-vinci use continue for this existing tablet-product redesign workflow.
 
 Use the existing Da Vinci artifacts in this project.
 Do not restart discovery unless an artifact is missing or clearly wrong.
+Determine continuation routing from current artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth. If the resumed session will perform Pencil edits, require `da-vinci pencil-session begin --project <project-path> --pen <path>`, then use `da-vinci pencil-session persist --project <project-path> --pen <path> ...` after material live edits; fall back to the lower-level `write-pen + check-pen-sync` path only when the session wrapper cannot be used.
 If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
 If Pencil MCP is active and this session performs new Pencil writes, rerun the MCP runtime gate and record the refreshed result in `pencil-design.md`.

package/docs/prompt-presets/web-app.md

@@ -75,6 +75,8 @@ $da-vinci use continue for this existing overhaul-from-code web workflow.
 
 Use the existing Da Vinci artifacts.
 Detect whether the workflow should return to breakdown, continue with design, generate tasks, continue implementation, or verify drift.
+Determine routing from artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
 ```
 
@@ -188,6 +190,8 @@ $da-vinci use continue for this existing web-product redesign workflow.
 
 Use the existing Da Vinci artifacts in this project.
 Do not restart discovery unless an artifact is missing or clearly wrong.
+Determine continuation routing from current artifact and checkpoint truth first, then use contextual checkpoint deltas only as auxiliary recovery notes.
+If a contextual delta conflicts with current artifacts, ignore that delta and record the conflict before continuing.
 Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth. If the resumed session will perform Pencil edits, require `da-vinci pencil-session begin --project <project-path> --pen <path>`, then use `da-vinci pencil-session persist --project <project-path> --pen <path> ...` after material live edits; fall back to the lower-level `write-pen + check-pen-sync` path only when the session wrapper cannot be used.
 If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
 If Pencil MCP is active and this session performs new Pencil writes, rerun the MCP runtime gate and record the refreshed result in `pencil-design.md`.