@xenonbyte/da-vinci-workflow 0.1.11 → 0.1.13

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

@@ -8,40 +8,78 @@
 
 适合这种需求：
 
-- responsive 页面层级
-- marketing 与 product surface 的区分
+- responsive 层级
+- marketing surface 与 product surface 的区分
 - 明确处理 empty、loading、error、authenticated states
-- 把复杂流程拆成真实的设计 surface，而不是一个大页面
 
-推荐提示词：
+## 如何选择
+
+- `Simple redesign` 适合产品表面不大、主要页面不多、状态分支有限的项目。
+- `Complex redesign` 适合同时混合 marketing、auth、onboarding、app surface、dialogs、drawers 和大量状态的项目。
+- `Design-only` 适合先把设计链路和绑定做完，但暂时不改代码。
+- `Continue` 适合已经有 `.da-vinci/` 工件，需要继续推进的项目。
+
+## Simple Redesign
 
 ```text
 $da-vinci use redesign-from-code to redesign this existing web product.
 
 Existing code is the behavior source of truth, not the layout truth.
 Preserve current business logic, routes, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
-Inventory responsive surfaces, authenticated areas, settings pages, dialogs, drawers, overlays, and important states before broad Pencil work.
-Separate marketing-style surfaces from product-workflow surfaces when they require different visual treatment.
-Decompose complex pages into subpages, overlays, materially different states, and implementation surfaces.
+Inventory the current product surfaces and important states before Pencil work.
 Use the Visual Assist preferences declared in DA-VINCI.md.
 Do not pass design checkpoint if the result is a generic SaaS card grid or a recolor of the old interface.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
-什么时候先走 `intake`：
+## Complex Redesign
 
-- 同时混合 marketing、auth、onboarding 和 app surfaces
-- 第一条提示词很难一次说清
-- 存在外部设计参考，但它们必须服从现有行为真相
+```text
+$da-vinci use redesign-from-code to redesign this existing web product.
 
-`intake` 版本：
+Existing code is the behavior source of truth, not the layout truth.
+Preserve current business logic, routes, permissions, integrations, validations, and state transitions unless explicitly required otherwise.
+Inventory responsive product surfaces, marketing surfaces, authenticated areas, settings pages, dialogs, drawers, overlays, and materially different states before broad Pencil work.
+Separate marketing-style surfaces from product-workflow surfaces when they require different visual treatment.
+Decompose complex pages into subpages, overlays, materially different states, and implementation surfaces.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+Treat the resolved primary visual adapter as the first-pass design lead.
+Use Pencil guides only as responsive layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+Do not pass design checkpoint if the result is a generic SaaS card grid, repeated placeholder scaffolds, or a recolor of the old interface.
+Persist project-local Pencil files under .da-vinci/designs/.
+```
+
+## Design-Only
 
 ```text
-$da-vinci use intake for this existing web product.
+$da-vinci use redesign-from-code to redesign this existing web product.
 
-I need to redesign the UI while preserving current behavior.
 Existing code is the behavior source of truth, not the layout truth.
+Preserve current behavior, routes, permissions, integrations, and state transitions.
 Inventory product surfaces, marketing surfaces, overlays, and important states.
-Decompose complex pages before Pencil work.
-Generate the best executable Da Vinci workflow prompt for the next step.
+Decompose complex pages into real design surfaces before Pencil work.
+Use the Visual Assist preferences declared in DA-VINCI.md.
+If the product is complex, design 1-3 anchor surfaces first, review screenshots, then expand.
+Stop after DA-VINCI.md, design-registry.md, page-map.md, proposal.md, specs, design.md, pencil-design.md, pencil-bindings.md, and tasks.md.
+Do not start code changes yet.
 ```
+
+## Continue
+
+```text
+$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.
+Keep the registered project-local Pencil source under .da-vinci/designs/ as the design source of truth.
+If the redesign is complex, continue from the approved anchor surfaces instead of restarting broad scaffolding.
+Continue into the next unfinished stage and do not stop at tasks.md when the active intent is full-delivery.
+```
+
+## 什么时候先走 Intake
+
+- 产品混合了很多 surface 类型和真相源
+- 外部参考让第一条工作流请求变复杂
+- 第一条提示词仍然很难一次说对

package/docs/zh-CN/visual-adapters.md

@@ -118,6 +118,7 @@ visual adapter 是可选的 presentation 质量增强层。
   - 你希望 Da Vinci 优先尝试的本地 skill 列表
   - 顺序有意义
   - 即使多个 skill 都可用，最终也应该收敛出一个 primary adapter
+  - 不要把不同平台上的近名 adapter（例如 `frontend-skill` 和 `frontend-design`）默认当成同一个能力源，应该按当前环境里真实已安装、真实命名的 adapter 来解析
 - `Scope`
   - adapter 被允许影响的范围
   - 应该限制在构图、层级、spacing、Pencil refinement 这类 presentation 质量问题
@@ -180,9 +181,12 @@ adapter 的解析顺序建议固定为：
 ```md
 ## Visual Adapter Resolution
 - Requested adapters: frontend-skill, ui-ux-pro-max
+- Available requested adapters: frontend-skill
+- Unavailable requested adapters: none
 - Resolved primary adapter: frontend-skill
 - Secondary helpers: none
 - Status: active
+- Runtime declaration: explicitly stated before first anchor pass
 - Scope: DA-VINCI.md, design.md, pencil-design.md
 - Fallback reason if native Da Vinci rules were used: none
 ```
@@ -204,9 +208,23 @@ adapter 的解析顺序建议固定为：
 当 visual adapter 生效时：
 
 - 在 Pencil 设计前或设计过程中，用它来增强构图和层级判断
+- 解析出来的主 adapter 应该成为首轮设计的 art direction 主导，而不是只登记在 `design-registry.md` 里
+- 在第一个 anchor screen 设计前，必须在运行日志里明确写出解析结果
+- 在第一个 anchor screen 之前，先在这个 adapter 的主导下写出 visual thesis、content plan 和 interaction thesis
 - 页面命名和状态覆盖仍然要服从 `page-map.md`
 - 最终 presentation 真相仍然落在 Pencil `.pen` 数据里，而不是 adapter 的文字建议里
 
+面对复杂重设计时，还要额外遵守：
+
+- 不要一开始就批量搭很多空 screen
+- 先做 1 到 3 个 anchor surface
+- 每个 anchor surface 都要先做成完整构图，再扩展更多页面
+- 对每个 anchor surface，都要简短说明“新的构图与当前布局结构相比，具体改了什么”
+- 每做完一个 anchor surface 都先截图审查，再决定是否 clone 变体或继续扩展
+- 不要把截图分析结果自动当作通过；只要它指出 hierarchy、spacing、clarity、inconsistency 或 unresolved placeholder 问题，就应该先修再继续
+- 在扩展更多页面前，先从已通过的 anchor surface 中抽出一组 shared primitives
+- 如果结果仍然大量是占位块或重复模板，直接把 `design checkpoint` 判成 `BLOCK`，不要在坏底稿上继续叠更多页面
+
 把结果记录到 `pencil-design.md`。
 
 推荐字段：
@@ -236,6 +254,15 @@ If it is unavailable, fall back to native Da Vinci design rules and continue.
 Persist project-local Pencil files under .da-vinci/designs/.
 ```
 
+如果是复杂 Android 或多 surface 项目，建议再额外加上：
+
+```text
+Use frontend-skill explicitly as the primary visual reasoning source.
+Use Pencil guides only as layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+```
+
 ## adapter 选择建议
 
 - `frontend-skill`

package/docs/zh-CN/visual-assist-presets/README.md

@@ -19,6 +19,7 @@
 - 把 `frontend-skill` 提到第一位
 - 视情况把 `Require Adapter` 改成 `true`
 - 在大规模 Pencil 设计前先把 design checkpoint 门槛抬高
+- 改成 anchor-first：先做 1 到 3 个 anchor surface，截图审查通过后再扩展
 
 可用模板：
 
@@ -33,3 +34,4 @@
 2. 把其中的 `## Visual Assist` 片段复制到 `DA-VINCI.md`
 3. 只有在项目真的有不同视觉偏向时才调整 adapter 顺序
 4. 除非确实“没有某个本地 skill 就不能继续”，否则保持 `Require Adapter: false`
+5. 如果是复杂重设计，不要只复制 preset 就开画；还要配合 anchor-first 的 Pencil 生成策略

package/docs/zh-CN/workflow-examples.md

@@ -64,10 +64,11 @@ $da-vinci use greenfield-brainstorm to turn product brainstorming into a page ma
 4. 写入 `specs/<capability>/spec.md`
 5. 定义 `page-map.md`
 6. 解析请求的 visual adapter，并把结果记到 `design-registry.md`
-7. 建立或登记 Pencil 设计源
-8. 完成页面绑定
-9. 生成任务
-10. 实现并验证
+7. 建立或登记项目内 Pencil 设计源
+8. 先做 1 到 3 个 anchor surface，并完成截图审查，再扩展更多页面
+9. 完成页面绑定
+10. 生成任务
+11. 实现并验证
 
 ## 3. `redesign-from-code`
 
@@ -90,11 +91,13 @@ $da-vinci use redesign-from-code to inventory the current app, identify current
 4. 在 `proposal.md` 中定义重设计范围
 5. 当范围过大时，把工作拆成多个 `specs/<slice>/spec.md`
 6. 重建或细化 `page-map.md`，把 subpage、overlay、重要 state 一起拆出来
-7. 创建新的或更新后的 Pencil 页面，基于重新构图而不是旧 UI 换皮，并优先持久化到 `.da-vinci/designs/`
-8. 运行 `design-source checkpoint`，确认登记的项目内 `.pen` 路径、当前 Pencil 设计源和 shell 可见文件是一致的
-9. 绑定路由和 Pencil 页面
-10. 生成和 redesign slice 对齐的任务
-11. 实现并验证
+7. 先写出 anchor surface 的 visual thesis、content plan、interaction thesis 和 structural-delta 说明
+8. 创建新的或更新后的 Pencil 页面，基于重新构图而不是旧 UI 换皮，并优先持久化到 `.da-vinci/designs/`
+9. 在第一次成功写入 Pencil 后，立即验证登记的项目内 `.pen` 路径已经成为 shell 可见文件
+10. 运行 `design-source checkpoint`，确认登记的项目内 `.pen` 路径、当前 Pencil 设计源和 shell 可见文件是一致的
+11. 绑定路由和 Pencil 页面
+12. 生成和 redesign slice 对齐的任务
+13. 实现并验证
 
 ### 复杂 Android 页面示例
 
@@ -104,6 +107,17 @@ $da-vinci use redesign-from-code to redesign this existing Android app.
 Existing code is the behavior source of truth, not the layout truth.
 Inventory activities, fragments, tabs, dialogs, bottom sheets, nested flows, and important states.
 Decompose complex screens into separate design surfaces before Pencil work.
+Use frontend-skill explicitly as the primary visual reasoning source.
+State the resolved primary visual adapter explicitly in the log before the first anchor surface.
+Write a visual thesis, content plan, and interaction thesis before the first anchor surface.
+Use Pencil guides only as layout constraints, not as the design direction.
+Do not start with broad multi-screen scaffolding.
+Design 1-3 anchor surfaces first, review screenshots, then expand.
+For each anchor surface, explain how the new composition differs structurally from the current layout.
+Do not treat screenshot analysis as an automatic pass if it reports hierarchy, spacing, clarity, or inconsistency issues.
+Use only Pencil-supported properties; do not use web-only props like flex or margin.
+Verify the registered project-local `.pen` file exists as a shell-visible file after the first Pencil write.
+Keep `.da-vinci/designs/` reserved for `.pen` files only.
 Do not pass design checkpoint if the result is just a skin-swap of the old UI.
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xenonbyte/da-vinci-workflow",
-  "version": "0.1.11",
+  "version": "0.1.13",
   "description": "Requirement-to-design-to-code workflow skill for Codex, Claude, and Gemini",
   "bin": {
     "da-vinci": "bin/da-vinci.js"

package/references/artifact-templates.md

@@ -11,6 +11,7 @@ Write artifacts into the target project using this rule:
 - keep `DA-VINCI.md` at the project root
 - keep project-level workflow files in `.da-vinci/`
 - keep project-local Pencil `.pen` files in `.da-vinci/designs/`
+- keep workflow markdown out of `.da-vinci/designs/`; that directory is reserved for `.pen` sources only
 - keep change-level workflow files in `.da-vinci/changes/<change-id>/`
 
 Recommended placement:
@@ -86,6 +87,10 @@ Use this structure:
 - Route
 - Page purpose
 
+## Implementation Surfaces
+- Activity / fragment / tab / dialog / sheet / overlay
+- Materially different states
+
 ## UI Regions
 - Shared layout regions
 - Repeated page patterns
@@ -241,9 +246,12 @@ Use this structure:
 
 ## Visual Adapter Resolution
 - Requested adapters
+- Available requested adapters
+- Unavailable requested adapters
 - Resolved primary adapter
 - Secondary helpers
 - Status: active / fallback / unavailable
+- Whether runtime execution explicitly declared the resolved primary adapter
 - Scope
 - Fallback reason if native Da Vinci rules were used
 
@@ -255,6 +263,7 @@ Use this structure:
 - Why a source is active
 - Whether a source is safe to iterate
 - Whether shell-visible filesystem persistence exists
+- Whether shell-visible persistence was verified immediately after the first Pencil write
 - Whether the file had to be reconstructed from MCP-readable document data
 ```
 
@@ -399,9 +408,23 @@ Use this structure:
 ```md
 # Design
 
+## Visual Thesis
+- One-sentence art-direction statement
+
+## Content Plan
+- Primary anchor
+- Supporting rail
+- Action lane
+
+## Interaction Thesis
+- Motion or presence ideas that affect hierarchy or affordance
+
 ## Page Map
 - Pages and sections
 
+## Structural Delta From Current Layout
+- For each anchor surface, how the new composition differs from the current XML or layout grouping
+
 ## Interaction Model
 - Primary actions
 - Secondary actions
@@ -415,6 +438,12 @@ Use this structure:
 - Reusable blocks
 - Page-specific blocks
 
+## Shared Primitive Plan
+- Top bar
+- Segmented tabs
+- Metric rails
+- Tiles, rows, trays, overlays
+
 ## Content Notes
 - Key text
 - Priority order
@@ -442,10 +471,26 @@ Use this structure:
 
 ## Visual Adapter Use
 - Resolved primary adapter
+- Available requested adapters
+- Unavailable requested adapters
 - Secondary helpers
+- Whether runtime execution explicitly declared the resolved primary adapter
+- Whether the primary adapter actively led the first-pass composition
 - How it affected composition, hierarchy, or motion guidance
 - Whether native Da Vinci fallback was used
 
+## Anchor Surfaces
+- Which 1-3 anchor screens were designed first
+- Structural-delta summary for each anchor surface
+- Screenshot review status for each anchor
+- Whether screenshot review found hierarchy, spacing, clarity, or inconsistency issues
+- Whether each anchor was revised after screenshot review
+- Whether broad multi-screen expansion is approved yet
+
+## Shared Primitives
+- Reusable UI family extracted from the approved anchors
+- Whether broad page expansion happened before or after the primitive family was defined
+
 ## Page Mapping
 - Requirement -> Pencil page
 
@@ -464,6 +509,7 @@ Use this structure:
 ## Implementation Notes
 - Important layout or styling constraints to preserve in code
 - Persistence notes if the project-local `.pen` file had to be reconstructed from MCP-readable document data
+- Confirmation that `.da-vinci/designs/` was used only for `.pen` files
 ```
 
 Recommended path:

package/references/checkpoints.md

@@ -37,6 +37,7 @@ Use the design checkpoint to confirm:
 - the current Pencil pages follow the same visual baseline
 - later pages are not re-inventing the product style from scratch
 - `redesign-from-code` is not treating the old UI layout as the new design baseline
+- non-design workflow markdown is not being written into `.da-vinci/designs/`, which should stay reserved for project-local `.pen` sources
 
 ## `discovery checkpoint`
 
@@ -49,6 +50,7 @@ Check:
 - product form factor and visual direction are known, inferred, or explicitly deferred
 - candidate pages or current pages are clear enough to move into `page-map.md`
 - open questions are explicitly tracked
+- workflow artifacts are being written to standard locations, especially keeping `.da-vinci/designs/` for `.pen` files rather than markdown notes
 
 Result meanings:
 
@@ -94,9 +96,16 @@ Check:
 - major layout strategy matches the design artifact
 - Pencil names and artifact names are aligned enough to implement from
 - Pencil pages follow the current `DA-VINCI.md` visual contract
+- runtime logs or artifacts explicitly name the requested adapters, which were available, which were unavailable, and which adapter was resolved as primary
+- if visual adapters were requested, the resolved primary adapter clearly shaped the first design pass instead of being recorded only as metadata
+- when a primary adapter is active, the workflow wrote a visual thesis, content plan, and interaction thesis before broad anchor-surface generation
+- complex redesigns have 1-3 fully composed anchor surfaces reviewed before broad multi-screen expansion
+- each anchor surface includes a short explanation of how its composition differs structurally from the current layout truth
 - each page has a clear visual anchor or primary working surface
 - section hierarchy is readable without relying on decorative chrome
 - the design does not collapse into generic card-grid or border-heavy filler UI
+- the design is not placeholder-heavy or built from repeated empty templates masquerading as finished screens
+- shared primitives or a reusable component family are identified before the workflow expands a multi-surface redesign from the anchor pages
 - motion ideas, if present, improve hierarchy or affordance instead of adding noise
 - complex pages with multiple fragments, subpages, overlays, or materially different states are decomposed clearly enough to design and implement from
 - `redesign-from-code` output is a fresh composition driven by page responsibility and state, not a skin-swap of the old UI
@@ -107,6 +116,14 @@ Result meanings:
 - `WARN`: minor design gaps exist, but the visual direction is still coherent
 - `BLOCK`: design is not ready to drive implementation, or the result is generic, cluttered, or materially below the intended visual bar
 
+Automatic failures:
+
+- if broad Pencil generation starts before anchor surfaces are compositionally stable, treat the design checkpoint as `BLOCK`
+- if more than roughly 20% of a screen's primary content area is unresolved placeholder scaffolding, treat the design checkpoint as `BLOCK`
+- if multiple screens are effectively the same scaffold with title changes, treat the design checkpoint as `BLOCK`
+- if screenshot review or image analysis calls out hierarchy, spacing, clarity, inconsistency, or unresolved-placeholder issues and the workflow marks the screen as passed without revision, treat the design checkpoint as `BLOCK`
+- if a redesign screen materially mirrors the current XML grouping with only recolor, spacing tweaks, or minor rearrangement, treat the design checkpoint as `BLOCK`
+
 ## `design-source checkpoint`
 
 Run after `design-registry.md` resolves the preferred project-local `.pen` path and after active Pencil work exists, but before mapping is treated as safe.
@@ -116,8 +133,9 @@ Check:
 - `design-registry.md` records one specific preferred project-local `.pen` path
 - the preferred `.pen` path is workflow-owned state, not a hand-wavy placeholder
 - the active Pencil editor path matches the preferred project-local `.pen` path, or the mismatch has been reconciled explicitly
-- if the workflow created or edited Pencil work, the preferred project-local `.pen` file exists as a shell-visible file
+- if the workflow created or edited Pencil work, the preferred project-local `.pen` file exists as a shell-visible file immediately after the first successful Pencil write, not just at workflow close
 - if Pencil MCP only exposed a live document, the workflow reconstructed and wrote the registered project-local `.pen` file from MCP-readable document data before continuing
+- `.da-vinci/designs/` is being used cleanly for project-local `.pen` files rather than mixed with workflow markdown
 - `design-registry.md`, `pencil-design.md`, and `pencil-bindings.md` describe the same active project-local `.pen` source clearly enough to map and implement from
 
 Result meanings:

package/references/design-inputs.md

@@ -9,6 +9,7 @@ Check for `DA-VINCI.md` first, then check whether the project already has persis
 - if it exists, treat it as the project visual contract
 - if `DA-VINCI.md` declares preferred visual adapters, treat them as optional design-assist preferences
 - if `.da-vinci/designs/*.pen` exists, treat those files as project-local design inputs and record the exact preferred path in `design-registry.md`
+- treat non-`.pen` files inside `.da-vinci/designs/` as artifact-placement drift that must be corrected instead of as valid design inputs
 - if it does not exist, generate it from the best stable inputs before broad Pencil page generation
 - avoid re-deriving the visual language page by page
 
@@ -107,6 +108,16 @@ If Pencil creates or updates a baseline during the workflow:
 If the project requests a visual adapter:
 
 - try to resolve it from locally available skills
+- do not assume that near-name adapters on different platforms are equivalent; resolve only adapters that are explicitly named and installed in the current environment unless the project intentionally maps them
 - choose one primary adapter when multiple helpers are available
-- record the requested adapters, resolved primary adapter, any secondary helpers, and fallback result in `design-registry.md`
+- record the requested adapters, which were available, which were unavailable, the resolved primary adapter, any secondary helpers, and fallback result in `design-registry.md`
+- treat the resolved primary adapter as the design lead for the first Pencil pass, especially for anchor screens and other quality-critical surfaces
+- if the resolved primary adapter is active, state that resolution explicitly in the runtime log before the first anchor-screen pass and let it shape the visual thesis, content plan, and interaction thesis
+- use Pencil guides or style helpers only as platform and buildability constraints, not as the art-direction source
+- if `Require Adapter: true` and the requested adapter is unavailable, block instead of silently downgrading the visual bar
 - if no adapter is available, continue with native Da Vinci design rules unless the user explicitly required a specific adapter
+
+For `redesign-from-code` on complex products:
+
+- write a short structural-delta note for each anchor surface explaining how the new composition differs from the current layout grouping
+- keep those notes in `design.md` or `pencil-design.md` before broad multi-screen generation begins

package/references/pencil-design-to-code.md

@@ -38,10 +38,30 @@ If the current active Pencil editor does not match the preferred path in `design
 
 If the project resolved a visual adapter:
 
-- use it to refine composition, hierarchy, spacing discipline, and motion suggestions before or during Pencil design work
+- use it to lead early composition, hierarchy, spacing discipline, and motion suggestions before or during Pencil design work
+- on complex redesigns, apply it first to 1-3 anchor surfaces before expanding the rest of the screen set
+- if it is active, make that resolution explicit in the runtime log and let it shape the visual thesis, content plan, and interaction thesis before the first anchor screen
+- do not let Pencil guides, generic style packs, or repeated scaffolding override the resolved primary adapter's role in the first-pass art direction
 - do not let it override behavior, route truth, or page-state truth
 - treat it as a presentation-quality assistant, not as a replacement for Pencil or requirements
 
+For `redesign-from-code`:
+
+- preserve behavior from the current codebase, not the current layout grouping
+- write a short structural-delta note for each anchor surface explaining how the new composition differs from the current XML or screen grouping
+- if the result still mirrors the old layout with only recolor or spacing tweaks, treat it as a failed redesign pass
+
+## Pencil Operation Discipline
+
+When generating or editing Pencil data:
+
+- use only Pencil-supported properties and layout concepts
+- do not emit web- or CSS-only properties such as `flex` or `margin`
+- prefer smaller, schema-safe batches on anchor screens so errors do not roll back large composition chunks
+- verify the registered project-local `.pen` path becomes shell-visible immediately after the first successful Pencil write
+- keep workflow markdown out of `.da-vinci/designs/`; reserve that directory for `.pen` files only
+- after the first approved anchor surfaces, extract a shared primitive family before broad page expansion
+
 ## Map Pencil To Frontend
 
 Use these default mappings:
@@ -76,4 +96,5 @@ Before treating the code as complete:
 - compare major sections against Pencil
 - compare headline and CTA hierarchy against Pencil
 - compare panel grouping against Pencil
+- compare the implemented structure against the approved structural-delta notes for anchor surfaces
 - note any intentional deviations

package/references/platform-adapters.md

@@ -93,3 +93,9 @@ Keep these stable:
 - prompt helper semantics
 
 Platform adapters may differ in command syntax, but not in workflow semantics.
+
+Visual-adapter names may differ across platforms.
+
+- do not assume that near-name adapters such as `frontend-skill` and `frontend-design` are equivalent
+- resolve the actual installed adapter names for the current environment
+- record the requested adapters, available adapters, unavailable adapters, and resolved primary adapter explicitly in runtime artifacts