duaer-spec 0.15.0 → 0.17.0

package/.duaer/active-job.json

@@ -1,6 +1,6 @@
 {
-  "featureDir": ".duaer/specs/055-release-015",
-  "branch": "feat/release-015",
-  "worktree": ".worktree/feat-release-015",
-  "status": "active"
+  "featureDir": ".duaer/specs/087-release-017",
+  "slug": "087-release-017",
+  "branch": "chore/release-017",
+  "worktree": ".worktree/chore-release-017"
 }

package/.duaer/memory/testing.md

@@ -41,8 +41,13 @@ Covers without a paid LLM:
 3. `/api/validate` pass and `/api/validate/fix` via an in-process mock
    OpenAI-compatible server
 
-Does **not** cover: real model quality, Terminal CLI launch, or full revise
-dispatch. Those stay manual E2E catalog rows or future suites.
+Also run `npm test` (includes revise-reliability contract tests: Brief
+snapshot/rollback helpers + source markers for `PREEMPT_FAILED` / longer
+client timeout).
+
+Does **not** cover: real model quality, live Terminal CLI launch against a
+real Cursor/Claude session. Those stay manual E2E catalog rows (E2E-055) or
+future suites.
 
 ## Opt-in (still need an explicit ask or Spec note)
 

package/.duaer/specs/056-revise-reliability/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "summary": "Revise dispatch: honest preempt, Brief rollback on launch fail, structured retryable errors, terminal status line, longer client wait.",
+  "verification": {
+    "levels": ["L0", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "npm run test:live",
+      "node --test test/revise-reliability.test.mjs"
+    ],
+    "notes": "E2E-055 manual for live Terminal preempt path."
+  }
+}

package/.duaer/specs/056-revise-reliability/spec.md

@@ -0,0 +1,44 @@
+# Feature Specification: Revise round reliability
+
+**Feature Branch**: `feat/revise-reliability`
+
+**Created**: 2026-09-17
+
+**Status**: Active
+
+## Goal
+
+Revise dispatch is **observable**, **retryable**, and failures are **readable**:
+confirm → Terminal enqueue must not report success when preempt failed; Brief
+mutations must not stick after a failed launch; client timeout matches server
+budgets; status exposes Terminal busy/queue; UI keeps dispatch unlocked when
+retryable.
+
+## In scope
+
+- Honest preempt outcome (no false preempted / false HTTP 200)
+- Rollback Brief writes if launch/enqueue fails
+- Structured revise errors (`code`, `retryable`) + UI copy
+- Align client `/api/revise` abort with recreate/init budgets (~3 min)
+- `/api/status` includes `terminal: { busy, queueDepth, runnerHealthy }`
+- Minimal status/hint line; extend L3 smoke for error shape / rollback unit
+
+## Out of scope
+
+- Desk layout / column redesign
+- Full Playwright Terminal automation
+- Paid live LLM quality
+
+## Acceptance
+
+1. When preempt cannot clear leftover agents, `/api/revise` fails with
+   `PREEMPT_FAILED` and does **not** lock the revise card
+2. Failed launch does not leave a new Revision block in Brief (rollback)
+3. Client wait ≥ worst-case recreate path; timeout message mentions retry
+4. Status poll shows terminal busy/queue when revising
+5. `npm run test:live` still passes; new smoke/unit covers rollback or error codes
+
+## Assumptions
+
+- Worktree: `.worktree/feat-revise-reliability`
+- Brief: `.duaer/specs/056-revise-reliability/`

package/.duaer/specs/056-revise-reliability/tasks.md

@@ -0,0 +1,10 @@
+# Tasks: Revise round reliability
+
+**Brief**: `.duaer/specs/056-revise-reliability/`
+
+## Checklist
+
+- [x] Honest preempt + PREEMPT_FAILED; Brief rollback on launch fail
+- [x] Structured errors on `/api/revise`; status.terminal
+- [x] UI: longer timeout, retryable unlock, terminal line, i18n
+- [x] L3 / unit smoke; docs; accept; merge develop

package/.duaer/specs/057-progress-accepted/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "On delivery accepted, progress shows N/N and reconciles unchecked tasks.md boxes.",
+  "verification": {
+    "levels": ["L0", "L3"],
+    "commands": ["npm test"],
+    "notes": "E2E-056."
+  }
+}

package/.duaer/specs/057-progress-accepted/spec.md

@@ -0,0 +1,42 @@
+# Feature Specification: Progress sync when delivery accepted
+
+**Feature Branch**: `fix/progress-accepted`
+
+**Created**: 2026-09-17
+
+**Status**: Active
+
+## Goal
+
+Task progress must not show `0/N · delivery accepted · 工单完成`. When
+`delivery.json` is `accepted`, the desk treats tasks as complete (done ===
+total) and reconciles unchecked boxes in `tasks.md` when safe.
+
+## Problem
+
+`dispatchStatus` only rewrites `progress.current` on accept; `done` stays at
+the unchecked count. Agents often stamp `delivery.json` without flipping every
+`- [ ]` to `- [x]`, so 任务跟进 shows a contradictory `0/3 · …工单完成`.
+
+## In scope
+
+- Normalize progress when accepted: `done = total`, all task rows `done: true`
+- Reconcile `tasks.md` unchecked boxes to `[x]` once when accepted (idempotent)
+- Unit/smoke coverage; short README/CHANGELOG/E2E note
+
+## Out of scope
+
+- Changing how agents are prompted (except if a one-line reminder helps)
+- Progress column layout redesign
+
+## Acceptance
+
+1. Accepted delivery never surfaces `done < total` with an “工单完成 /
+   delivery accepted” current line
+2. Unchecked tasks in Brief are marked `[x]` after status observes accept
+3. `npm test` / `npm run test:live` pass
+
+## Assumptions
+
+- Worktree: `.worktree/fix-progress-accepted`
+- Brief: `.duaer/specs/057-progress-accepted/`

package/.duaer/specs/057-progress-accepted/tasks.md

@@ -0,0 +1,8 @@
+# Tasks: Progress sync when delivery accepted
+
+**Brief**: `.duaer/specs/057-progress-accepted/`
+
+## Checklist
+
+- [x] Normalize progress on accept; reconcile tasks.md
+- [x] Tests + docs; accept; merge develop

package/.duaer/specs/058-revise-progress-track/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-17T09:50:00.000Z",
+  "summary": "Revise-round progress scopes to Revision N / R{n}-* tasks; lagging accepted + busy Terminal no longer freezes on 工单完成.",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "npm test"
+    ],
+    "result": "pass (14 tests)"
+  }
+}

package/.duaer/specs/058-revise-progress-track/spec.md

@@ -0,0 +1,48 @@
+# Feature Specification: Track revise-round task progress
+
+**Feature Branch**: `fix/revise-progress-track`
+
+**Created**: 2026-09-17
+
+**Status**: Accepted
+
+## Goal
+
+After **Confirm revise and dispatch**, 任务跟进 shows **this revision’s**
+checklist and updates as work starts — not the prior dispatch’s completed
+`T001…` pile, and not a frozen “delivery accepted · 工单完成” while Terminal
+is already running the revise.
+
+## Problem
+
+Progress parses the whole `tasks.md`. After revise, old tasks stay `[x]` so
+the bar looks finished (or accepted-normalized to N/N) while the new `R{n}-*`
+round has started. Live `revisionCount` can lag; status may still say
+`accepted`, so the wrong run-block is updated and revise work looks untracked.
+
+## In scope
+
+- Scope progress to dispatch (pre-Revision section) vs active `Revision N`
+- Infer active revision from job / delivery / tasks.md headers and `R{n}` ids
+- While revising (or Terminal busy with open `R{n}` tasks), do not force
+  accept-complete progress
+- Persist inferred `revisionCount` onto the live job when missing
+- Tests + CHANGELOG / E2E note
+
+## Out of scope
+
+- Layout / column redesign
+- Changing revise launch / preempt behavior
+
+## Acceptance
+
+1. After Confirm revise, progress shows only this revision’s tasks (e.g. `0/3`
+   then rising), under the Revision N run block
+2. While revise is active, status is not stuck on `delivery accepted · 工单完成`
+3. When revise delivery accepts, that revision shows `N/N · …完成`
+4. `npm test` passes
+
+## Assumptions
+
+- Worktree: `.worktree/fix-revise-progress-track`
+- Brief: `.duaer/specs/058-revise-progress-track/`

package/.duaer/specs/058-revise-progress-track/tasks.md

@@ -0,0 +1,9 @@
+# Tasks: Track revise-round task progress
+
+**Brief**: `.duaer/specs/058-revise-progress-track/`
+
+## Checklist
+
+- [x] Scope parseTasksProgress by revision; infer active revision
+- [x] Revising / busy Terminal skips accept-complete normalize
+- [x] Tests + docs; merge develop

package/.duaer/specs/059-revise-preempt-order/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-17T10:05:00.000Z",
+  "summary": "priorAccepted revise preempts leftovers before enqueue so Confirm revise no longer returns PREEMPT_FAILED while the revise Agent is already running.",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "npm test"
+    ],
+    "result": "pass (14 tests)"
+  }
+}

package/.duaer/specs/059-revise-preempt-order/spec.md

@@ -0,0 +1,47 @@
+# Feature Specification: Honest revise preempt (enqueue after clear)
+
+**Feature Branch**: `fix/revise-preempt-order`
+
+**Created**: 2026-09-17
+
+**Status**: Accepted
+
+## Goal
+
+After Confirm revise, either the revise Agent is launched and the desk
+reports success, or preempt truly failed and nothing was started — never
+“Could not preempt…” while Terminal is already running the revise job.
+
+## Problem
+
+`launchInTerminal` enqueues the revise job **before** preempt. Within the
+post-preempt wait, the runner starts the new Agent; status then sees
+`busy && agentsLeft > 0` and throws `PREEMPT_FAILED`. The API rolls back
+Brief while the queued revise Agent keeps working — UI error, work already
+underway; retries kill that Agent.
+
+## In scope
+
+- Preempt leftover agents **before** enqueueing the revise Terminal job
+- Fail `PREEMPT_FAILED` only when prior agents remain (nothing queued yet)
+- Do not treat the newly started revise Agent as a preempt failure
+- Tests + CHANGELOG / E2E note
+
+## Out of scope
+
+- Progress scoping (058)
+- Changing when priorAccepted revise preempts vs waits
+
+## Acceptance
+
+1. priorAccepted revise: preempt clears leftovers, then enqueue; HTTP 200
+2. If leftover agents cannot be cleared, `PREEMPT_FAILED` and **no** new
+   Terminal job for that attempt
+3. Desk does not show preempt failure while revise Agent is already running
+   from that same Confirm tap
+4. `npm test` passes
+
+## Assumptions
+
+- Worktree: `.worktree/fix-revise-preempt-order`
+- Brief: `.duaer/specs/059-revise-preempt-order/`

package/.duaer/specs/059-revise-preempt-order/tasks.md

@@ -0,0 +1,8 @@
+# Tasks: Honest revise preempt (enqueue after clear)
+
+**Brief**: `.duaer/specs/059-revise-preempt-order/`
+
+## Checklist
+
+- [x] Preempt before enqueue; fail only on leftover prior agents
+- [x] Tests + docs; merge develop

package/.duaer/specs/060-release-016/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T00:00:00.000Z",
+  "summary": "Release 0.16.0: honest revise preempt, revise progress scope, accept progress sync.",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test"],
+    "result": "pass (14 tests)"
+  }
+}

package/.duaer/specs/060-release-016/spec.md

@@ -0,0 +1,24 @@
+# Feature Specification: Release 0.16.0
+
+**Feature Branch**: `feat/release-016`
+
+**Created**: 2026-09-18
+
+**Status**: Accepted
+
+## Goal
+
+Ship **0.16.0** to `main` + npm: revise reliability (honest preempt order),
+revise-round progress tracking, and accept progress sync.
+
+## Acceptance
+
+1. `package.json` version `0.16.0`; CHANGELOG dated section; Unreleased cleared
+2. `main` tagged `v0.16.0`; GitHub Release; npm `latest` is `0.16.0`
+3. `npm test` passes before promote
+
+## Assumptions
+
+- Worktree: `.worktree/feat-release-016`
+- Brief: `.duaer/specs/060-release-016/`
+- User ask「发版」authorizes push + promote `develop` → `main`

package/.duaer/specs/060-release-016/tasks.md

@@ -0,0 +1,4 @@
+# Tasks: Release 0.16.0
+
+- [x] Bump 0.16.0 + CHANGELOG + light README notes
+- [x] Verify `npm test`; merge develop; promote main; tag + npm

package/.duaer/specs/061-satisfactory-delivery/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T01:00:00.000Z",
+  "summary": "Position norms → satisfactory delivery; stricter checkable acceptance gate for confirm/revise; docs and live hints updated.",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test"],
+    "result": "pass (18 tests)"
+  }
+}

package/.duaer/specs/061-satisfactory-delivery/spec.md

@@ -0,0 +1,39 @@
+# Feature Specification: Spec AI for satisfactory delivery
+
+**Feature Branch**: `feat/satisfactory-delivery`
+
+**Created**: 2026-09-18
+
+**Status**: Accepted
+
+## Goal
+
+Position Duaer as **规范 AI → 满意交付**: acceptance must be objectively
+checkable before confirm/revise dispatch, and public docs lead with that
+promise—not phase/skill names.
+
+## In scope
+
+- Stricter local + LLM validate gate for confirm and revise cards
+- Positioning copy: README EN/ZH, package description, DUADER, live desk tag/hints
+- Dispatch/revise agent prompts emphasize meeting Acceptance + openable preview
+- Tests + CHANGELOG / E2E note
+
+## Out of scope
+
+- npm release / promote to main (ship when asked)
+- Layout redesign
+- New columns or cloud hosting
+
+## Acceptance
+
+1. Vague acceptance (e.g.「更好用」/ “looks better”) fails `/api/validate` locally
+2. Checkable acceptance (open X / see Y / command passes) can still pass the gate
+3. README EN/ZH lead with 规范 → 满意交付 (English: norms → satisfactory delivery)
+4. `npm test` passes
+
+## Assumptions
+
+- Worktree: `.worktree/feat-satisfactory-delivery`
+- Brief: `.duaer/specs/061-satisfactory-delivery/`
+- User confirmed evolution direction; no further intent wait

package/.duaer/specs/061-satisfactory-delivery/tasks.md

@@ -0,0 +1,5 @@
+# Tasks: Spec AI for satisfactory delivery
+
+- [x] Stricter acceptance gate (local heuristics + ACCEPT_PROMPT)
+- [x] Positioning docs + live i18n hints
+- [x] Agent prompts; tests; merge develop

package/.duaer/specs/062-deepseek-cli/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T01:20:00.000Z",
+  "summary": "Live desk launches DeepSeek TUI (deepseek) as a third CLI digital employee with PATH discovery for npm/nvm/cargo.",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test"],
+    "result": "pass (19 tests)"
+  }
+}

package/.duaer/specs/062-deepseek-cli/spec.md

@@ -0,0 +1,37 @@
+# Feature Specification: DeepSeek CLI digital employee
+
+**Feature Branch**: `feat/deepseek-cli`
+
+**Created**: 2026-09-18
+
+**Status**: Accepted
+
+## Goal
+
+Live desk can launch **DeepSeek TUI** (`deepseek` / `deepseek-tui`) as a third
+CLI digital employee alongside Cursor Agent and Claude Code.
+
+## In scope
+
+- Detect `deepseek` on PATH (incl. npm global / nvm / cargo bins under launchd)
+- Dispatch + revise Terminal launch with workspace, YOLO tools, optional `--continue`
+- Preempt matching for deepseek processes; install hint `npm install -g deepseek-tui`
+- README / i18n / tests
+
+## Out of scope
+
+- Embedding DeepSeek API chat (already used for desk validate) as the worker
+- Shipping npm release unless asked
+
+## Acceptance
+
+1. With `deepseek` installed, desk lists **DeepSeek** as available CLI
+2. Dispatch/revise enqueue a Terminal command using `deepseek -w <worktree> …`
+3. Without `deepseek`, missing list shows install command
+4. `npm test` passes
+
+## Assumptions
+
+- Target CLI: DeepSeek-TUI entrypoint `deepseek` (`npm i -g deepseek-tui`)
+- Worktree: `.worktree/feat-deepseek-cli`
+- Brief: `.duaer/specs/062-deepseek-cli/`

package/.duaer/specs/062-deepseek-cli/tasks.md

@@ -0,0 +1,4 @@
+# Tasks: DeepSeek CLI digital employee
+
+- [x] Catalog + detect + PATH dirs; launch + preempt
+- [x] Docs/i18n/tests; merge develop

package/.duaer/specs/063-queued-count/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T01:50:00.000Z",
+  "summary": "Define queuedCount on fresh Terminal open path to stop ReferenceError.",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": ["npm test"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/063-queued-count/spec.md

@@ -0,0 +1,12 @@
+# Feature Specification: Fix queuedCount ReferenceError
+
+**Feature Branch**: `fix/queued-count`  
+**Brief**: `.duaer/specs/063-queued-count/`  
+**Status**: Active
+
+## Goal
+Fresh Terminal open path must not throw `queuedCount is not defined`.
+
+## Acceptance
+1. Unhealthy-runner launch return uses a defined queue depth
+2. `npm test` passes

package/.duaer/specs/063-queued-count/tasks.md

@@ -0,0 +1,3 @@
+# Tasks
+- [x] Define queuedCount on fresh Terminal open path
+- [x] Test + merge develop

package/.duaer/specs/064-cli-install-show/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T02:00:00.000Z",
+  "summary": "Missing CLI chips show install commands; install panel + redetect for PATH refresh.",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test"],
+    "result": "pass (19 tests)"
+  }
+}

package/.duaer/specs/064-cli-install-show/spec.md

@@ -0,0 +1,17 @@
+# Feature Specification: Show CLI install commands when missing
+
+**Feature Branch**: `feat/cli-install-show`  
+**Brief**: `.duaer/specs/064-cli-install-show/`  
+**Status**: Accepted
+
+## Goal
+
+「用哪个 CLI 数字员工启动」must detect install status; if not installed,
+show the install command clearly (on the chip + install panel), with redetect.
+
+## Acceptance
+
+1. Missing CLIs render as distinct chips with install command text visible
+2. Install panel lists the selected missing CLI’s command + copy button
+3. Redetect button refreshes `/api/agents`
+4. `npm test` passes

package/.duaer/specs/064-cli-install-show/tasks.md

@@ -0,0 +1,3 @@
+# Tasks
+- [x] Missing chips show install cmd; panel + redetect
+- [x] i18n/CSS/tests; merge develop

package/.duaer/specs/065-detailed-progress/delivery.json

@@ -0,0 +1,18 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T00:00:00.000Z",
+  "featureDir": ".duaer/specs/065-detailed-progress",
+  "branch": "feat/detailed-progress",
+  "worktree": ".worktree/feat-detailed-progress",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "node --check bin/live-progress.mjs",
+      "node --check web/live-dev/app.js",
+      "npm test",
+      "npm run test:live"
+    ],
+    "notes": "Richer default tasks.md, status.activity, progress-activity UI"
+  }
+}

package/.duaer/specs/065-detailed-progress/spec.md

@@ -0,0 +1,19 @@
+# Feature Specification: Detailed coding progress
+
+**Feature Branch**: `feat/detailed-progress`  
+**Brief**: `.duaer/specs/065-detailed-progress/`  
+**Status**: Active
+
+## Goal
+
+Live desk progress shows more than 3 coarse tasks: a finer `tasks.md`
+checklist on dispatch, stronger agent check-off rules, and live worktree
+file activity while the CLI runs.
+
+## Acceptance
+
+1. New dispatch writes ≥6 checkbox tasks (not only T001–T003)
+2. `/api/status` includes `activity` (recent changed files / git porcelain)
+3. Progress column shows activity under the task list while work is running
+4. Agent launch prompt requires expanding/checking detailed tasks
+5. `npm test` passes

package/.duaer/specs/065-detailed-progress/tasks.md

@@ -0,0 +1,4 @@
+# Tasks
+- [x] Richer default tasks.md + agent prompt
+- [x] worktree activity on status + UI
+- [x] Tests/docs; merge develop

package/.duaer/specs/066-duaer-fed/delivery.json

@@ -0,0 +1,16 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T00:00:00.000Z",
+  "featureDir": ".duaer/specs/066-duaer-fed",
+  "branch": "feat/duaer-fed",
+  "worktree": ".worktree/feat-duaer-fed",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "node --check web/live-dev/i18n.js",
+      "npm test",
+      "npm run test:live"
+    ]
+  }
+}

package/.duaer/specs/066-duaer-fed/spec.md

@@ -0,0 +1,18 @@
+# Feature Specification: Brand live desk as Duaer FED
+
+**Feature Branch**: `feat/duaer-fed`  
+**Brief**: `.duaer/specs/066-duaer-fed/`  
+**Status**: Active
+
+## Goal
+
+User-facing name for the web confirm desk is **Duaer FED** (Field
+Engineering Desk). Chinese keeps「现场开发」as the secondary mark.
+
+## Acceptance
+
+1. Desk header brand + document title show `Duaer FED`
+2. zh mark is「现场开发」; en mark is `Field Engineering Desk`
+3. README EN/ZH section titles use Duaer FED; CLI help / start banner say FED
+4. Agent/system prompts refer to Duaer FED (not only「现场开发」)
+5. `duaer live` command path unchanged; `npm test` + `npm run test:live` pass

package/.duaer/specs/066-duaer-fed/tasks.md

@@ -0,0 +1,4 @@
+# Tasks
+- [x] UI i18n + index title/brand
+- [x] CLI banner, README, agent prompts
+- [x] Tests/docs; merge develop

package/.duaer/specs/067-duaer-spec-fed/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-18T00:00:00.000Z",
+  "featureDir": ".duaer/specs/067-duaer-spec-fed",
+  "branch": "feat/duaer-spec-fed",
+  "worktree": ".worktree/feat-duaer-spec-fed",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test", "npm run test:live"]
+  }
+}

package/.duaer/specs/067-duaer-spec-fed/spec.md

@@ -0,0 +1,16 @@
+# Feature Specification: Brand as Duaer-spec FED
+
+**Feature Branch**: `feat/duaer-spec-fed`  
+**Brief**: `.duaer/specs/067-duaer-spec-fed/`  
+**Status**: Active
+
+## Goal
+
+Correct the live desk product name from `Duaer FED` to **Duaer-spec FED**
+(tied to the duaer-spec product).
+
+## Acceptance
+
+1. Header, title, CLI banner/help, README, and agent prompts say `Duaer-spec FED`
+2. Secondary marks unchanged (zh on-site desk / en Field Engineering Desk)
+3. Brand tests updated; `npm test` + `npm run test:live` pass

package/.duaer/specs/067-duaer-spec-fed/tasks.md

@@ -0,0 +1,3 @@
+# Tasks
+- [x] Rename Duaer FED → Duaer-spec FED across UI/docs/CLI
+- [x] Update brand test; verify; merge develop