@xenonbyte/da-vinci-workflow 0.1.17 → 0.1.18

package/docs/zh-CN/mode-use-cases.md

@@ -52,7 +52,12 @@ project/
    - 当前代码是行为真相
    - 目标是大范围或全局 UI 重设计
 
-4. `feature-change`
+4. `overhaul-from-code`
+   - 现有项目
+   - 当前代码仍然是迁移基线和参考证据
+   - 流程、逻辑、信息架构或 UI 都要被大范围重写
+
+5. `feature-change`
    - 现有项目
    - 目标是局部功能、页面或流程改动
 
@@ -177,7 +182,47 @@ Da Vinci 应该：
 - 截图 PNG 只是审查产物，不能替代登记好的 `.pen` 设计源
 - 如果当前 Pencil editor 仍然是 `new` 或其他未命名 live document，就不能宣布工作流完成
 
-## 4. `feature-change`
+## 4. `overhaul-from-code`
+
+适合：
+
+- 已有产品，但不是单纯换 UI
+- 旧系统里有一部分逻辑、流程或结构需要被整体重写
+- 现有代码仍然重要，但不再天然等于新系统最终行为真相
+
+Da Vinci 应该：
+
+1. 先做 `project-inventory.md`
+   - 盘点当前 routes、flows、integrations、permissions、legacy constraints
+2. 生成 `proposal.md`
+   - 定义新的目标产品方向、范围和非目标
+3. 生成 `migration-contract.md`
+   - 标记 `preserve`
+   - 标记 `revise`
+   - 标记 `retire`
+   - 标记 `unknown`
+4. 按 overhaul slice 写 `specs/<slice>/spec.md`
+   - 让新的 spec 成为目标行为真相
+5. 重建 `page-map.md`
+   - 描述目标产品页面集，而不是只复制旧 route tree
+6. 再进入：
+   - `DA-VINCI.md`
+   - `design-registry.md`
+   - `design-brief.md`
+   - `design.md`
+   - `pencil-design.md`
+   - `pencil-bindings.md`
+   - `tasks.md`
+   - `verification.md`
+
+它和 `redesign-from-code` 的区别：
+
+- `redesign-from-code` 默认保留旧代码行为真相
+- `overhaul-from-code` 默认把旧代码当成参考基线和迁移上下文
+- `redesign-from-code` 更偏向广泛 UI 重设计
+- `overhaul-from-code` 更偏向存量系统上的产品级重构
+
+## 5. `feature-change`
 
 适合：
 

package/docs/zh-CN/pencil-rendering-workflow.md

@@ -0,0 +1,233 @@
+# Pencil 渲染工作流
+
+> 中文配套文档。若与英文原文存在差异，请以 `docs/pencil-rendering-workflow.md` 为准。
+
+这份文档专门描述 Da Vinci 里的 Pencil 渲染生命周期。
+
+适合在你需要理解下面这些内容时阅读：
+
+- 项目内 `.pen` 的 seed 和恢复
+- 通过 Pencil MCP 编辑
+- live 改动如何持久化
+- screenshot review
+- runtime gate 和 filesystem audit
+
+如果你想看 `design`、`tasks`、`build`、`verify` 这些 `dv:` 路由之间怎么衔接，以及 `verify` 出问题后退回哪一层，请看 [dv-command-reference.md](/Users/xubo/x-skills/da-vinci/docs/zh-CN/dv-command-reference.md)。
+
+## 渲染真相模型
+
+Da Vinci 把下面三类真相分开看：
+
+- live truth：当前 Pencil MCP editor
+- disk truth：登记好的项目内 `.pen`
+- review truth：`.da-vinci/changes/<change-id>/exports/` 下的截图导出
+
+PNG 只是审查产物，不是设计真相源。
+
+`.da-vinci/designs/` 只允许放 `.pen` 文件。
+
+## 会话模型
+
+Da Vinci 现在优先使用这组 session wrapper：
+
+- `da-vinci pencil-session begin`
+- `da-vinci pencil-session persist`
+- `da-vinci pencil-session end`
+
+这组 wrapper 的作用，是把下面三件事变成强制步骤：
+
+- seed 好的 `.pen` 所有权
+- 串行化的 Pencil MCP 写权限
+- 明确的 live-to-disk 持久化和同步校验
+
+## 首次运行路径
+
+如果项目里还没有登记好的 `.pen`：
+
+1. 先开始一个 Pencil session。
+2. seed 登记好的项目内 `.pen`。
+3. 拿到全局 Pencil 锁。
+4. 打开这个精确路径。
+5. 再开始 Pencil 编辑。
+
+工作流不应该从 `new` 开始做 anchor 渲染。
+
+## 继续迭代路径
+
+如果项目里已经有登记好的 `.pen`：
+
+1. 先对着已有路径开始 Pencil session。
+2. reopen 这个精确 `.pen`。
+3. 做 live MCP 编辑。
+4. 发生实质性改动后，把当前 MCP 快照重新覆盖写回同一路径。
+
+Da Vinci 不会假设 live MCP 编辑已经被自动刷盘。
+
+## 持久化规则
+
+Da Vinci 不把 headless interactive `save()` 当作权威持久化真相。
+
+正式持久化步骤是：
+
+1. 读取 MCP 可读的 node snapshot
+2. 读取 MCP 可读的 variable snapshot
+3. 写项目内 `.pen`
+4. reopen 校验
+5. 比较 live snapshot hash 和 persisted snapshot hash
+
+相关命令：
+
+- `da-vinci write-pen`
+- `da-vinci check-pen-sync`
+
+`da-vinci snapshot-pen` 只用于 disk-to-disk，不是 live 编辑持久化路径。
+
+## 锁规则
+
+Pencil MCP 的写操作通过全局锁串行化。
+
+可用：
+
+- `da-vinci pencil-lock acquire`
+- `da-vinci pencil-lock release`
+
+或者直接优先用 session wrapper，让它自动管理锁。
+
+这套锁的目的，是防止多个项目抢同一个 active editor。
+
+## 批次纪律
+
+在发送非小型 `batch_design` 前：
+
+- 如果有 shell 能力，先跑 `da-vinci preflight-pencil --ops-file <path>`
+- anchor 批次尽量小
+- anchor surface 优先每批不超过 12 个操作
+- 同一个 anchor 连续两次回滚后，切成每批不超过 6 个操作的微批次
+
+反复 schema rollback 不能算正常前进。
+
+## 审查门禁
+
+### Screenshot Review
+
+每个被批准的 surface 都需要明确的截图审查结果：
+
+- `PASS`
+- `WARN`
+- `BLOCK`
+
+每条审查记录都必须包含：
+
+- 问题列表
+- 是否已回改
+
+像 “looks good” 这种自我肯定文本不算审查记录。
+
+### Layout Hygiene
+
+每个被审查的 surface 还必须满足当前 form factor 的 layout-hygiene 规则：
+
+- mobile
+- tablet
+- desktop
+- web
+
+这一层独立于 `Visual Assist`。
+
+### Design Checkpoint
+
+如果出现下面这些情况，渲染结果不能通过：
+
+- 只是旧 UI 换皮
+- 大量 placeholder scaffold
+- 忽略 screenshot review 里的问题
+- 仍然有明显 schema 不稳定
+
+## 设计源门禁
+
+active Pencil 工作一旦存在，就要跑 `design-source checkpoint`。
+
+它会验证：
+
+- `design-registry.md` 是否指向一个明确的 `.pen`
+- active editor 是否就是这个 `.pen`
+- shell 上是否真的存在这个 `.pen`
+- 登记的 `.pen` 是否还停留在“只有内存，没有磁盘”
+- `.da-vinci/designs/` 是否被 markdown 或 PNG 污染
+
+## MCP Runtime Gate
+
+如果启用了 Pencil MCP，Da Vinci 会把 runtime gate 结果记录到 `pencil-design.md`。
+
+它会验证：
+
+- active editor 不是 `new`
+- 注册 `.pen` 后没有继续用空 `filePath`
+- claimed anchor id 在 active editor 中真实存在
+- reviewed screenshot target 在 active editor 中真实存在
+- completion 阶段 live snapshot hash 和 persisted hash 一致
+
+## Filesystem 审计
+
+### Integrity Audit
+
+工作中期运行：
+
+```text
+da-vinci audit --mode integrity <project-path>
+```
+
+推荐时机：
+
+- 第一次成功写入 `.pen` 后立刻跑
+- 在 anchor surface 通过后、继续大范围扩展前再跑
+
+### Completion Audit
+
+任何终态完成声明前运行：
+
+```text
+da-vinci audit --mode completion --change <change-id> <project-path>
+```
+
+这个审计现在还会检查 `.da-vinci/state/pencil-session.json`，要求它记录的 hash 与最新持久化 `.pen` 一致。
+
+## 推荐命令链
+
+典型自治流程：
+
+1. `da-vinci pencil-session begin --project <project-path> --pen <path>`
+2. Pencil MCP 编辑
+3. `da-vinci pencil-session persist --project <project-path> --pen <path> --nodes-file <nodes.json> --variables-file <vars.json> --version <version>`
+4. screenshot review + layout hygiene
+5. `da-vinci pencil-session end --project <project-path> --pen <path> --nodes-file <nodes.json> --variables-file <vars.json> --version <version>`
+6. `da-vinci audit --mode completion --change <change-id> <project-path>`
+
+## 流程图
+
+```mermaid
+flowchart TD
+    A[开始 Pencil 设计] --> B{是否已有登记的 .pen?}
+    B -- 否 --> C[pencil-session begin 先 seed .pen 并拿全局锁]
+    B -- 是 --> D[pencil-session begin reopen 已有 .pen 并拿全局锁]
+    C --> E[对非小型 batch_design 做 preflight]
+    D --> E
+    E --> F[渲染或更新 anchor surface]
+    F --> G{同一 anchor 连续回滚两次?}
+    G -- 是 --> H[切换到 6 个操作以内的微批次]
+    G -- 否 --> I[截图并做审查]
+    H --> F
+    I --> J{Screenshot review 与 layout hygiene 通过?}
+    J -- 否 --> F
+    J -- 是 --> K[pencil-session persist 把 live MCP 快照写回 .pen]
+    K --> L[check-pen-sync 校验 live hash 与 persisted hash 一致]
+    L --> M{design-source checkpoint 和 runtime gate 通过?}
+    M -- 否 --> F
+    M -- 是 --> N{是否还要继续设计?}
+    N -- 是 --> E
+    N -- 否 --> O[pencil-session end 释放锁]
+    O --> P[completion audit]
+    P --> Q{completion audit 通过?}
+    Q -- 否 --> F
+    Q -- 是 --> R[design complete]
+```

package/docs/zh-CN/prompt-entrypoints.md

@@ -75,6 +75,11 @@
 
 `build` 仍然有效，但它更适合已经明确进入实现阶段的高级直接调用。
 
+状态规则：
+
+- 如果设计已经完成，但 `tasks.md` 还不存在，下一步主推荐通常应该是 `tasks`，而不是 `build`
+- 只有任务和实现就绪度都已经明确时，才把 `build` 作为主推荐下一步
+
 ## 平台语法
 
 如果你只想直接复制不同场景的起始提示词，也可以看：
@@ -122,6 +127,24 @@ HTML references are in /abs/path/to/mockups.
 - 一条更保守的 planning-first 版本
 - 一条后续 continue 提示词
 
+## 示例：现有产品但流程和逻辑也要一起重做
+
+```text
+$da-vinci use intake for this existing product.
+
+This is a large overhaul, not only a UI refresh.
+Current codebase is important reference evidence and migration baseline, but it should not be treated as the final target behavior truth.
+We need to redefine flows, logic, and page structure while preserving selected integrations and constraints.
+Generate the best executable Da Vinci workflow prompt for the next step.
+```
+
+预期输出：
+
+- 推荐 mode：`overhaul-from-code`
+- 一条主执行提示词
+- 一条更保守的 planning-first 版本
+- 一条后续 continue 提示词
+
 ## 示例：盘点完成后继续
 
 ```text

package/docs/zh-CN/prompt-presets/README.md

@@ -2,6 +2,9 @@
 
 这些模板用于在不同产品形态下，快速拿到可直接执行的起始提示词。
 
+这些模板主要服务于 screen 设计阶段。
+如果是存量系统的大改版，且流程或逻辑也会一起变化，应该先用 `overhaul-from-code` 搭配 `intake` 或自定义提示词把 `proposal.md`、`migration-contract.md` 和目标 `specs/` 稳定下来，再复用对应的设计模板。
+
 它们建议和下面这组文档配合使用：
 
 - `docs/zh-CN/visual-assist-presets/`
@@ -37,3 +40,80 @@
 - `Complex redesign`
 - `Design-only`
 - `Continue`
+
+## `overhaul-from-code` 提示词模板
+
+这组模板不是按 surface 划分的 redesign 预设。
+
+它们用于：项目已经存在，但目标流程或逻辑要重写，旧代码只能作为参考证据和迁移上下文，不能再默认当成最终行为真相。
+
+### 1. 进入大改版的 intake 提示词
+
+适合：
+
+- 仓库已经存在
+- 用户明确知道要大改版
+- 但新的目标行为还没稳定
+
+```text
+$da-vinci use intake for this existing product.
+
+This is a broad overhaul, not only a UI refresh.
+Current codebase is important reference evidence and migration baseline, but it should not be treated as the final target behavior truth.
+We need to redefine flows, logic, page structure, and selected UI surfaces while preserving only the approved integrations, permissions, and constraints.
+Recommend the best Da Vinci mode and generate the best executable next-step prompt.
+```
+
+### 2. `overhaul-from-code` 的需求拆解 / 规格稳定提示词
+
+适合：
+
+- mode 已经明确
+- 需要先盘点旧系统并划清迁移边界，再进入设计
+
+```text
+$da-vinci use overhaul-from-code to inventory the current product, define preserve/revise/retire/unknown boundaries, and stabilize the new target requirements before broad design.
+
+Current codebase is reference evidence and migration baseline, not the final target behavior truth.
+Create or update:
+- .da-vinci/project-inventory.md
+- .da-vinci/changes/<change-id>/proposal.md
+- .da-vinci/changes/<change-id>/migration-contract.md
+- .da-vinci/changes/<change-id>/specs/
+- .da-vinci/page-map.md
+
+Do not start broad Pencil work until the new proposal, migration contract, target specs, and page map are stable enough to drive design.
+```
+
+### 3. Overhaul 规格稳定后的设计交接提示词
+
+适合：
+
+- `proposal.md`、`migration-contract.md`、目标 `specs/`、`page-map.md` 已存在
+- 现在准备开始做 Pencil-backed 的大改版设计
+
+```text
+$da-vinci use overhaul-from-code to design the new target product surfaces from the approved overhaul artifacts.
+
+Use the existing .da-vinci/project-inventory.md, proposal.md, migration-contract.md, target specs, page-map.md, DA-VINCI.md, and design-registry.md.
+Treat the new proposal and specs as the target behavior truth.
+Treat the old codebase only as reference evidence and migration context.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Persist project-local Pencil files under .da-vinci/designs/.
+Run the normal Pencil runtime gate and completion audit before terminal completion claims.
+```
+
+### 4. 已有 `overhaul-from-code` 工件后的继续提示词
+
+适合：
+
+- 仓库里已经有 overhaul 工件
+- 需要从当前真相状态继续推进
+
+```text
+$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.
+Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
+```

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

@@ -2,6 +2,9 @@
 
 适用于桌面优先的工具型或工作台型产品。
 
+这些提示词变体主要服务于设计驱动的 `redesign-from-code` 场景，前提是 workflow mode 已经明确。
+如果当前 mode 是 `overhaul-from-code`，应该先把 `proposal.md`、`migration-contract.md` 和目标 `specs/` 稳定下来，再按需要改写这个模板，而不是直接原样套用。
+
 建议搭配：
 
 - `docs/zh-CN/visual-assist-presets/desktop-app.md`
@@ -19,6 +22,61 @@
 - `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
 - `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
 
+## Overhaul From Code
+
+当桌面产品已经存在，但 workspace 模型、流程逻辑、导航方式或信息架构也要一起重写，而不是只做视觉翻新时，用这组模板。
+
+### Overhaul Intake
+
+```text
+$da-vinci use intake for this existing desktop product.
+
+This is a broad overhaul, not only a UI refresh.
+Current desktop codebase is important reference evidence and migration baseline, but it should not be treated as the final target behavior truth.
+We need to redefine flows, workspace structure, interaction model, and selected UI surfaces while preserving only approved integrations, permissions, and constraints.
+Recommend the best Da Vinci mode and generate the best executable next-step prompt.
+```
+
+### Overhaul Breakdown
+
+```text
+$da-vinci use overhaul-from-code to inventory the current desktop product, define preserve/revise/retire/unknown boundaries, and stabilize the new target requirements before broad design.
+
+Current desktop codebase is reference evidence and migration baseline, not the final target behavior truth.
+Create or update:
+- .da-vinci/project-inventory.md
+- .da-vinci/changes/<change-id>/proposal.md
+- .da-vinci/changes/<change-id>/migration-contract.md
+- .da-vinci/changes/<change-id>/specs/
+- .da-vinci/page-map.md
+
+Inventory workspaces, side panels, inspectors, dialogs, overlays, and materially different states before broad Pencil work.
+Do not start broad Pencil work until the new proposal, migration contract, target specs, and page map are stable enough to drive design.
+```
+
+### Overhaul Design
+
+```text
+$da-vinci use overhaul-from-code to design the new target desktop surfaces from the approved overhaul artifacts.
+
+Use the existing .da-vinci/project-inventory.md, proposal.md, migration-contract.md, target specs, page-map.md, DA-VINCI.md, and design-registry.md.
+Treat the new proposal and specs as the target behavior truth.
+Treat the old desktop codebase only as reference evidence and migration context.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Persist project-local Pencil files under .da-vinci/designs/.
+Run the normal Pencil runtime gate and completion audit before terminal completion claims.
+```
+
+### Overhaul Continue
+
+```text
+$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.
+Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
+```
+
 ## Simple Redesign
 
 ```text

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

@@ -2,6 +2,9 @@
 
 适用于以手机为主的产品界面。
 
+这些提示词变体主要服务于设计驱动的 `redesign-from-code` 场景，前提是 workflow mode 已经明确。
+如果当前 mode 是 `overhaul-from-code`，应该先把 `proposal.md`、`migration-contract.md` 和目标 `specs/` 稳定下来，再按需要改写这个模板，而不是直接原样套用。
+
 建议搭配：
 
 - `docs/zh-CN/visual-assist-presets/mobile-app.md`
@@ -19,6 +22,61 @@
 - `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
 - `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
 
+## Overhaul From Code
+
+当产品已经存在，但移动端流程、逻辑和页面结构也要一起重写，而不是只做换皮时，用这组模板。
+
+### Overhaul Intake
+
+```text
+$da-vinci use intake for this existing mobile product.
+
+This is a broad overhaul, not only a UI refresh.
+Current Android or mobile code is important reference evidence and migration baseline, but it should not be treated as the final target behavior truth.
+We need to redefine mobile flows, states, navigation structure, and selected surfaces while preserving only approved integrations, permissions, and constraints.
+Recommend the best Da Vinci mode and generate the best executable next-step prompt.
+```
+
+### Overhaul Breakdown
+
+```text
+$da-vinci use overhaul-from-code to inventory the current mobile product, define preserve/revise/retire/unknown boundaries, and stabilize the new target requirements before broad design.
+
+Current mobile codebase is reference evidence and migration baseline, not the final target behavior truth.
+Create or update:
+- .da-vinci/project-inventory.md
+- .da-vinci/changes/<change-id>/proposal.md
+- .da-vinci/changes/<change-id>/migration-contract.md
+- .da-vinci/changes/<change-id>/specs/
+- .da-vinci/page-map.md
+
+Inventory activities, fragments, tabs, dialogs, sheets, overlays, and materially different states before broad Pencil work.
+Do not start broad Pencil work until the new proposal, migration contract, target specs, and page map are stable enough to drive design.
+```
+
+### Overhaul Design
+
+```text
+$da-vinci use overhaul-from-code to design the new target mobile surfaces from the approved overhaul artifacts.
+
+Use the existing .da-vinci/project-inventory.md, proposal.md, migration-contract.md, target specs, page-map.md, DA-VINCI.md, and design-registry.md.
+Treat the new proposal and specs as the target behavior truth.
+Treat the old mobile codebase only as reference evidence and migration context.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Persist project-local Pencil files under .da-vinci/designs/.
+Run the normal Pencil runtime gate and completion audit before terminal completion claims.
+```
+
+### Overhaul Continue
+
+```text
+$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.
+Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
+```
+
 ## Simple Redesign
 
 ```text

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

@@ -2,6 +2,9 @@
 
 适用于平板优先，或强依赖扩展触控区域的产品。
 
+这些提示词变体主要服务于设计驱动的 `redesign-from-code` 场景，前提是 workflow mode 已经明确。
+如果当前 mode 是 `overhaul-from-code`，应该先把 `proposal.md`、`migration-contract.md` 和目标 `specs/` 稳定下来，再按需要改写这个模板，而不是直接原样套用。
+
 建议搭配：
 
 - `docs/zh-CN/visual-assist-presets/tablet-app.md`
@@ -19,6 +22,61 @@
 - `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
 - `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
 
+## Overhaul From Code
+
+当平板产品已经存在，但 split-pane 行为、流程逻辑、方向感知结构或页面职责也要一起重写，而不是只做视觉翻新时，用这组模板。
+
+### Overhaul Intake
+
+```text
+$da-vinci use intake for this existing tablet product.
+
+This is a broad overhaul, not only a UI refresh.
+Current tablet codebase is important reference evidence and migration baseline, but it should not be treated as the final target behavior truth.
+We need to redefine flows, orientation-aware structure, page responsibilities, and selected surfaces while preserving only approved integrations, permissions, and constraints.
+Recommend the best Da Vinci mode and generate the best executable next-step prompt.
+```
+
+### Overhaul Breakdown
+
+```text
+$da-vinci use overhaul-from-code to inventory the current tablet product, define preserve/revise/retire/unknown boundaries, and stabilize the new target requirements before broad design.
+
+Current tablet codebase is reference evidence and migration baseline, not the final target behavior truth.
+Create or update:
+- .da-vinci/project-inventory.md
+- .da-vinci/changes/<change-id>/proposal.md
+- .da-vinci/changes/<change-id>/migration-contract.md
+- .da-vinci/changes/<change-id>/specs/
+- .da-vinci/page-map.md
+
+Inventory split-pane regions, sidebars, expanded canvases, dialogs, sheets, orientation-driven changes, and materially different states before broad Pencil work.
+Do not start broad Pencil work until the new proposal, migration contract, target specs, and page map are stable enough to drive design.
+```
+
+### Overhaul Design
+
+```text
+$da-vinci use overhaul-from-code to design the new target tablet surfaces from the approved overhaul artifacts.
+
+Use the existing .da-vinci/project-inventory.md, proposal.md, migration-contract.md, target specs, page-map.md, DA-VINCI.md, and design-registry.md.
+Treat the new proposal and specs as the target behavior truth.
+Treat the old tablet codebase only as reference evidence and migration context.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Persist project-local Pencil files under .da-vinci/designs/.
+Run the normal Pencil runtime gate and completion audit before terminal completion claims.
+```
+
+### Overhaul Continue
+
+```text
+$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.
+Prefer the artifact-backed next safe stage instead of restarting the overhaul from scratch.
+```
+
 ## Simple Redesign
 
 ```text