duaer-spec 0.17.0 → 0.18.0

package/.claude/rules/ai-ui-copy.md

@@ -1,4 +1,4 @@
-<!-- Keep AI-generated page copy minimal (duaer-spec agent ops) -->
+<!-- Desk UI copy — minimal + Duaer brand (duaer-spec agent ops) -->
 
 # AI-generated page content
 
@@ -7,3 +7,13 @@ AI-generated pages must not contain redundant explanatory text.
 - No filler introductions, repeated summaries, or prose that only explains an obvious control
 - Prefer concise labels, headings, helper text, and empty states
 - Put rationale and implementation detail in docs or code comments, not in the UI, unless the user asks for explanatory content
+
+## Duaer brand (site-wide)
+
+Visible live-desk / FED copy that names the product surface must include the
+**Duaer** brand (or **Duaer-spec FED** where that full mark is already used).
+
+- Do not write anonymous「台面」/ “desk” alone when referring to this product’s
+  chat surface or model setup — prefer「Duaer 台面」/ “Duaer desk”
+- Keep helper text short; branding is a name signal, not a slogan paragraph
+- Applies to i18n strings, HTML fallbacks, empty states, and setup/settings copy

package/.cursor/rules/ai-ui-copy.mdc

@@ -1,5 +1,5 @@
 ---
-description: Keep AI-generated page copy minimal (duaer-spec agent ops)
+description: Desk UI copy — minimal + Duaer brand (duaer-spec agent ops)
 alwaysApply: true
 ---
 
@@ -10,3 +10,13 @@ AI-generated pages must not contain redundant explanatory text.
 - No filler introductions, repeated summaries, or prose that only explains an obvious control
 - Prefer concise labels, headings, helper text, and empty states
 - Put rationale and implementation detail in docs or code comments, not in the UI, unless the user asks for explanatory content
+
+## Duaer brand (site-wide)
+
+Visible live-desk / FED copy that names the product surface must include the
+**Duaer** brand (or **Duaer-spec FED** where that full mark is already used).
+
+- Do not write anonymous「台面」/ “desk” alone when referring to this product’s
+  chat surface or model setup — prefer「Duaer 台面」/ “Duaer desk”
+- Keep helper text short; branding is a name signal, not a slogan paragraph
+- Applies to i18n strings, HTML fallbacks, empty states, and setup/settings copy

package/.duaer/active-job.json

@@ -1,6 +1 @@
-{
-  "featureDir": ".duaer/specs/087-release-017",
-  "slug": "087-release-017",
-  "branch": "chore/release-017",
-  "worktree": ".worktree/chore-release-017"
-}
+{"slug":"148-release-018","spec":".duaer/specs/148-release-018/spec.md"}

package/.duaer/handoff.json

@@ -1,9 +1,11 @@
 {
   "schemaVersion": 1,
   "onWorktreeRemove": {
-    "stop": "Stop any process whose working directory is under the request worktree (dev servers, file watchers, local APIs).",
+    "stop": "Stop any process whose working directory is under the request worktree (dev servers, file watchers, local APIs). Also stop the FED desk if it was started from a worktree copy of duaer-live.",
     "restartFromPrimary": true,
-    "commands": []
+    "commands": [
+      "launchctl kickstart -k \"gui/$(id -u)/com.duaer.live8787\" 2>/dev/null || (lsof -t -iTCP:8787 -sTCP:LISTEN | xargs kill 2>/dev/null; sleep 1; node bin/duaer-live.mjs --port 8787)"
+    ]
   },
-  "notes": "After merging into develop (or hotfix main), stop worktree-bound processes, remove .worktree/<id>, then restart from the primary checkout. Add commands such as \"npm run dev\" when this project needs a local service after handoff. Empty commands = stop only; agent still reports handoff."
+  "notes": "After merge to develop: remove worktree, then restart Duaer-spec FED (LaunchAgent com.duaer.live8787) so /api/projects and other new routes load from primary checkout."
 }

package/.duaer/specs/087-release-017/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T00:56:00.000Z",
+  "verification": {
+    "levels": [],
+    "commands": ["gh release create v0.17.0", "npm publish via Actions"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/088-result-versions/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T01:10:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "node --check web/live-dev/app.js",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/088-result-versions/spec.md

@@ -0,0 +1,37 @@
+# Feature Specification: Result versions follow progress
+
+**Feature Branch**: `feat/result-versions`
+**Brief**: `.duaer/specs/088-result-versions/`
+**Status**: Accepted
+
+## Goal
+
+Live desk「查看结果」tracks each accepted dispatch/revision as its own
+previewable version, with a unified version list. Drop dead links after
+worktree cleanup. Clear stuck「续派中」when the job is finished.
+
+## In scope
+
+1. Rename CTA / labels: 查看成品 → 查看结果 (EN: View result)
+2. On each delivery accept (初版 + each revision), record a result version
+3. Unified UI to open any still-previewable version
+4. Persist previewable snapshots under the live job so artifacts survive
+   worktree removal; prune entries that cannot be opened
+5. Fix status/UI stuck on revising /「续派中」after delivery accepted and
+   work finished (or worktree already cleaned)
+
+## Out of scope
+
+- Full site asset bundling beyond the preview entry file
+- Changing Terminal queue semantics beyond status inference
+
+## Acceptance
+
+1. i18n + HTML use「查看结果」/ View result
+2. `/api/status` returns `results[]` of previewable versions; grows with
+   each accept; non-previewable entries omitted after worktree gone
+3. Preview panel lists versions; latest opens via primary CTA
+4. When delivery accepted and worktree gone (or no open revise work),
+   status is `accepted` — not stuck `revising`; client clears
+   `reviseDispatching`
+5. L0 + L1 + `npm run test:live`; E2E catalog updated

package/.duaer/specs/088-result-versions/tasks.md

@@ -0,0 +1,8 @@
+# Tasks: 088-result-versions
+
+- [x] T001 Spec + active-job
+- [x] T002 Server: result versions + prune + activelyRevising fix
+- [x] T003 Client: 查看结果 + version list + clear 续派中
+- [x] T004 i18n / HTML / CSS
+- [x] T005 Tests + E2E catalog + CHANGELOG
+- [x] T006 Verify L0/L1/L3; stamp delivery

package/.duaer/specs/089-deploy-target-tasks/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T01:25:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/089-deploy-target-tasks/spec.md

@@ -0,0 +1,28 @@
+# Feature Specification: Deploy target choice + fine tasks + self-update bootstrap
+
+**Feature Branch**: `feat/deploy-target-tasks`
+**Brief**: `.duaer/specs/089-deploy-target-tasks/`
+**Status**: Accepted
+
+## Goal
+
+1. Global CLI users on old builds can upgrade: `self-update` works on current
+   package; banners tell people to run `npm i -g duaer-spec@latest` when the
+   installed CLI lacks the command.
+2. On live dispatch, choose planned hosting: Cloudflare / 阿里云 / AWS /
+   GitHub Pages / none. Code and agent prompts follow that platform’s rules
+   (Cloudflare: Workers/Pages constraints documented).
+3. Drop hard task-count caps (no max 12). Split into single-function,
+   independently acceptable tasks; do not couple acceptance into one mega-task.
+
+## Acceptance
+
+1. `duaer self-update` / `upgrade` run npm global install; unknown-command and
+   update hints show `npm i -g duaer-spec@latest` bootstrap
+2. Dispatch UI has deploy-target control; `/api/dispatch` persists target;
+   agent prompt + Spec notes reference the chosen platform doc
+3. Cloudflare choice adds Workers/Pages coding constraints in prompt +
+   `docs/agent/deploy-targets.md`
+4. `buildDetailedProductTasksMd` / revision builders do not slice acceptance
+   to 6/4; prompts say split finely with no upper count
+5. Tests + E2E + CHANGELOG; `npm test` + `npm run test:live` pass

package/.duaer/specs/089-deploy-target-tasks/tasks.md

@@ -0,0 +1,9 @@
+# Tasks: 089-deploy-target-tasks
+
+- [x] T001 Brief + active-job
+- [x] T002 self-update bootstrap + aliases + hint copy
+- [x] T003 deploy-targets module + docs (Cloudflare/阿里云/AWS/Pages)
+- [x] T004 live dispatch API + agent prompts
+- [x] T005 desk UI + i18n for deploy target
+- [x] T006 fine-grained tasks (remove caps) + prompts
+- [x] T007 tests / E2E / CHANGELOG / verify / stamp

package/.duaer/specs/090-project-first/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T01:50:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/090-project-first/spec.md

@@ -0,0 +1,41 @@
+# Feature Specification: Project-first desk (no SQLite)
+
+**Feature Branch**: `feat/project-first`  
+**Brief**: `.duaer/specs/090-project-first/`  
+**Status**: Accepted
+
+## Goal
+
+Duaer-spec FED is **project-first**: the human must select or create a product
+project before chatting. Conversations (former flat「历史」) hang under that
+project. Top bar label is「项目」. Storage stays file-based (`~/.duaer/live/`);
+no SQLite in this job.
+
+## In scope
+
+- Persist `activeProjectPath` (+ keep `projectsRoot`) in live config
+- Top bar「历史」→「项目」; drawer: create/select project, then conversations
+- Gate chat / composer until a project is active
+- Stamp project path on confirm; dispatch defaults to active project
+- Move「产品父目录」into the project create block (out of mid-dispatch clutter)
+- Group jobs by `repoPath` under each project
+- Tests, E2E catalog, CHANGELOG
+
+## Out of scope
+
+- SQLite / `desk.db`
+- Cloud sync; multi-user
+- Renaming CSS class names wholesale (`history-*` may remain as hooks)
+
+## Acceptance
+
+1. Without active project: Send disabled; bot/empty state tells user to open「项目」
+2. Create project (parent + name) or browse/select sets active project and unlocks chat
+3. Drawer lists projects; under active/selected project, jobs for that path; restore works
+4. Confirm/dispatch uses active project path (no need to re-pick unless changed)
+5. `npm test` + `npm run test:live` pass
+
+## Assumptions
+
+- Worktree: `.worktree/feat-project-first`
+- User confirmed: must select/create first; top bar「项目」; SQLite deferred

package/.duaer/specs/090-project-first/tasks.md

@@ -0,0 +1,7 @@
+# Tasks: 090-project-first
+
+- [x] T001 Brief + active-job
+- [x] T002 Config + API: activeProjectPath, GET/POST projects, confirm stamp
+- [x] T003 Desk UI: 项目 drawer, create block, chat gate, dispatch default
+- [x] T004 i18n EN/ZH + empty-state copy
+- [x] T005 Tests / E2E / CHANGELOG / verify / stamp

package/.duaer/specs/091-project-meta/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:05:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/091-project-meta/spec.md

@@ -0,0 +1,35 @@
+# Feature Specification: Project name + background
+
+**Feature Branch**: `feat/project-meta`  
+**Brief**: `.duaer/specs/091-project-meta/`  
+**Status**: Accepted
+
+## Goal
+
+When creating/opening a product project on the FED desk, the human must enter a
+**display name** and a short **background** description (not only a folder path).
+These persist with the project and show in the project list.
+
+## In scope
+
+- Persist `title` (display name) + `description` on remembered projects (`repos.json`)
+- Create form: folder path/name + 项目名称 + 背景描述
+- List / active line show title; description as secondary line
+- Activate API accepts and saves title/description
+- Tests + E2E note + CHANGELOG
+
+## Out of scope
+
+- SQLite; editing history of descriptions; LLM-generated backgrounds
+
+## Acceptance
+
+1. Create/activate requires a non-empty project title
+2. Background description is saved and shown on the project row (may be empty only if user left blank — prefer prompting a short line)
+3. Folder path still works as before (parent + short name or absolute path)
+4. `npm test` + `npm run test:live` pass
+
+## Assumptions
+
+- Require **title**; description optional but UI labels it clearly as「背景描述」
+- Worktree: `.worktree/feat-project-meta`

package/.duaer/specs/091-project-meta/tasks.md

@@ -0,0 +1,6 @@
+# Tasks: 091-project-meta
+
+- [x] T001 Brief + active-job
+- [x] T002 Persist title/description on repos + activate API
+- [x] T003 Desk form + list i18n
+- [x] T004 Tests / E2E / CHANGELOG / verify / stamp

package/.duaer/specs/092-project-chat-gate/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:15:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test", "npm run test:live"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/092-project-chat-gate/spec.md

@@ -0,0 +1,17 @@
+# Feature Specification: Harden project-before-chat gate
+
+**Feature Branch**: `fix/project-chat-gate`  
+**Brief**: `.duaer/specs/092-project-chat-gate/`  
+**Status**: Active
+
+## Goal
+
+Chat must stay locked until a current project is selected/created. Make the
+gate impossible to bypass and show the active project (or「未选项目」) in the UI.
+
+## Acceptance
+
+1. Composer starts disabled; Send / Enter / chips call sendChat which refuses without project
+2. Header shows current project title or「未选项目」
+3. `/api/chat` still returns NEED_PROJECT when config has no activeProjectPath
+4. `npm test` + `npm run test:live` pass

package/.duaer/specs/092-project-chat-gate/tasks.md

@@ -0,0 +1,4 @@
+# Tasks: 092-project-chat-gate
+
+- [x] T001 Harden sendChat + initial disabled + header badge
+- [x] T002 i18n / tests / stamp / merge

package/.duaer/specs/093-project-auto-chat/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:25:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test", "npm run test:live"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/093-project-auto-chat/spec.md

@@ -0,0 +1,16 @@
+# Feature Specification: Auto-start chat after project select
+
+**Feature Branch**: `feat/project-auto-chat`  
+**Brief**: `.duaer/specs/093-project-auto-chat/`  
+**Status**: Active
+
+## Goal
+
+After the human selects or creates the current project, the desk immediately
+starts the requirements dialogue (LLM chat kickoff) — no extra Send needed.
+
+## Acceptance
+
+1. Successful「选为当前项目」/ list select closes the drawer and calls chat with a kickoff that includes project name + background
+2. Composer is unlocked; conversation bubble appears
+3. `npm test` + `npm run test:live` pass

package/.duaer/specs/093-project-auto-chat/tasks.md

@@ -0,0 +1,4 @@
+# Tasks: 093-project-auto-chat
+
+- [x] T001 Kickoff sendChat after activate + i18n
+- [x] T002 Tests / CHANGELOG / stamp / merge

package/.duaer/specs/094-dispatch-project-simple/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:30:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test", "npm run test:live"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/094-dispatch-project-simple/spec.md

@@ -0,0 +1,17 @@
+# Feature Specification: Simplify dispatch when project already set
+
+**Feature Branch**: `feat/dispatch-project-simple`  
+**Brief**: `.duaer/specs/094-dispatch-project-simple/`  
+**Status**: Accepted
+
+## Goal
+
+After the current project is chosen (Projects drawer), the dispatch panel must
+not re-ask for a product repo. Show a short project summary only; keep deploy
+target + agent + launch.
+
+## Acceptance
+
+1. With active project: hide browse/scan/filter/list/path; show「当前项目：名称」+ path
+2. Title reads「启动数字员工」/ Launch digital employee (not「派工到当前项目」)
+3. `npm test` + `npm run test:live` pass

package/.duaer/specs/094-dispatch-project-simple/tasks.md

@@ -0,0 +1,4 @@
+# Tasks: 094-dispatch-project-simple
+
+- [x] T001 Hide repo pick when project set; summary line; i18n
+- [x] T002 Verify / stamp / merge

package/.duaer/specs/095-project-chat-persist/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:35:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test", "npm run test:live"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/095-project-chat-persist/spec.md

@@ -0,0 +1,17 @@
+# Feature Specification: Persist project chat across refresh
+
+**Feature Branch**: `feat/project-chat-persist`  
+**Brief**: `.duaer/specs/095-project-chat-persist/`  
+**Status**: Accepted
+
+## Goal
+
+Each project's desk conversation is saved under `~/.duaer/live/project-chats/`
+and restored when that project is active (including after page refresh).
+
+## Acceptance
+
+1. After chatting on a project, refresh restores the same messages
+2. Switching projects saves the previous chat and loads the other
+3. Empty project still auto-kickoffs; project with history restores (no re-kickoff)
+4. `npm test` + `npm run test:live` pass

package/.duaer/specs/095-project-chat-persist/tasks.md

@@ -0,0 +1,5 @@
+# Tasks: 095-project-chat-persist
+
+- [x] T001 Server read/write + API
+- [x] T002 Client persist/restore; kickoff only when empty
+- [x] T003 Tests / CHANGELOG / stamp / merge

package/.duaer/specs/096-project-card-persist/delivery.json

@@ -0,0 +1,15 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:45:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "node --check bin/live-project-chat.mjs",
+      "node --check web/live-dev/app.js",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/096-project-card-persist/spec.md

@@ -0,0 +1,25 @@
+# Feature Specification: Persist requirements card + job binding
+
+**Feature Branch**: `feat/project-card-persist`  
+**Brief**: `.duaer/specs/096-project-card-persist/`  
+**Status**: Accepted
+
+## Goal
+
+When a project is selected, the desk restores not only chat messages but also
+the **requirements card** (需求) and **task binding** (任务 / jobId + dispatch
+UI), so refresh does not lose mid-confirm or in-progress work.
+
+## Why
+
+Chat persistence (095) left the confirm/revise card and job progress empty
+after refresh. Users expect the full desk session to come back with the
+project.
+
+## Acceptance
+
+1. Editing confirm/revise fields is saved under the project session file
+2. After Confirm, refresh restores locked card + jobId and shows dispatch/progress
+3. After Dispatch / revise, refresh restores job binding and resumes status poll
+4. Switching projects saves the previous desk session and loads the other
+5. `npm test` + `npm run test:live` pass

package/.duaer/specs/096-project-card-persist/tasks.md

@@ -0,0 +1,9 @@
+# Tasks: 096-project-card-persist
+
+- [x] Extend `live-project-chat` schema: card, reviseCard, jobId, locked, mode
+- [x] PUT `/api/projects/chat` accepts full desk session fields
+- [x] Client persist on card input (debounced), confirm, dispatch, revise
+- [x] Client restore applies cards + starts status poll when jobId present
+- [x] Unit + source-wiring tests
+- [x] E2E catalog + CHANGELOG
+- [x] Verify L0/L1/L3 and accept

package/.duaer/specs/097-validate-persist/delivery.json

@@ -0,0 +1,15 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:50:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/live-project-chat.mjs",
+      "node --check bin/duaer-live.mjs",
+      "node --check web/live-dev/app.js",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/097-validate-persist/spec.md

@@ -0,0 +1,24 @@
+# Feature Specification: Persist validate gate with desk session
+
+**Feature Branch**: `fix/validate-persist`  
+**Brief**: `.duaer/specs/097-validate-persist/`  
+**Status**: Accepted
+
+## Goal
+
+After refresh, if the requirements card was already auto-validated
+(passed), the Confirm button stays enabled — do not force a silent
+idle gate that blocks Confirm.
+
+## Why
+
+096 restored card text and jobId, but `state.validate` reset to idle.
+Confirm requires `validationAllowsSend` (passed + matching fingerprint),
+so users see a filled card that “already passed” but cannot click Confirm.
+
+## Acceptance
+
+1. Passing auto-validate is saved in the project session file
+2. Refresh with unchanged card restores passed gate → Confirm clickable
+3. Editing the card after restore invalidates / re-validates as today
+4. `npm test` + `npm run test:live` pass

package/.duaer/specs/097-validate-persist/tasks.md

@@ -0,0 +1,7 @@
+# Tasks: 097-validate-persist
+
+- [x] Persist validate snapshot in project session
+- [x] Restore gate when fingerprint matches card; else re-validate
+- [x] Persist after validate result
+- [x] Tests / E2E / CHANGELOG
+- [x] Verify and accept

package/.duaer/specs/098-req-structured-edit/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:55:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --check web/live-dev/structured-html.mjs",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/098-req-structured-edit/spec.md

@@ -0,0 +1,18 @@
+# Feature Specification: Structured requirements edit
+
+**Feature Branch**: `feat/req-structured-edit`  
+**Brief**: `.duaer/specs/098-req-structured-edit/`  
+**Status**: Accepted
+
+## Goal
+
+Requirements fields keep the same structured look while editing — row/list
+items with add/remove — instead of collapsing into a raw textarea.
+
+## Acceptance
+
+1. Clicking a requirements field opens structured item rows (same chrome as view)
+2. Enter /「添加一条」adds a row; empty Backspace / × removes a row
+3. Blur commits text back to the card (bullet/numbered/para serialization)
+4. Confirm + revise cards both use this editor
+5. `npm test` + `npm run test:live` pass

package/.duaer/specs/098-req-structured-edit/tasks.md

@@ -0,0 +1,7 @@
+# Tasks: 098-req-structured-edit
+
+- [x] parse/serialize helpers for structured edit model
+- [x] Replace textarea edit mode with structured item editor
+- [x] CSS + i18n for add/remove
+- [x] Tests / E2E / CHANGELOG
+- [x] Verify and accept

package/.duaer/specs/099-setup-cli-guide/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T03:00:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --check bin/duaer-live.mjs",
+      "npm test",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/099-setup-cli-guide/spec.md

@@ -0,0 +1,19 @@
+# Feature Specification: Setup guide for CLI install + other models
+
+**Feature Branch**: `feat/setup-cli-guide`  
+**Brief**: `.duaer/specs/099-setup-cli-guide/`  
+**Status**: In progress
+
+## Goal
+
+The FED model setup **说明** explains how to install Cursor Agent / Claude Code
+and how to wire other desk / coding models.
+
+## Acceptance
+
+1. Setup page has a 说明/Guide block with Cursor + Claude install commands
+2. Guide covers Custom desk models and Claude→DeepSeek (etc.) for coding
+3. Header **模型** reopens setup (with 返回台面 when already ready)
+4. `worker-models(.zh-CN).md` and README match the install commands
+5. Missing Claude installCommand is the concrete npm install line
+6. `npm test` + `npm run test:live` pass