duaer-spec 0.12.0 → 0.13.0

package/.claude/rules/agents-workflow.md

@@ -45,8 +45,10 @@ cd .worktree/feat-login
 - Merge into **`develop`** when done (hotfix: **`main`**, then back-merge **`develop`**)
 - **Handoff (mandatory):** stop worktree-bound processes → remove `.worktree/<id>` →
   restart from primary checkout on `develop` (`duaer handoff [--run]`, `.duaer/handoff.json`)
-- Push only when the user explicitly asks
+- Push only when the user explicitly asks (a deploy/hosting ask authorizes
+  the `gh` + push needed for that publish — see `docs/agent/deploy-github.md`)
 - Promote **`develop` → `main`** only when the user asks to go online
+- English docs: no Chinese (CJK); Chinese docs may include English terms
 
 ## GitHub issue / PR intake
 

package/.cursor/rules/agents-workflow.mdc

@@ -48,8 +48,10 @@ cd .worktree/feat-login
 - Merge into **`develop`** when done (hotfix: **`main`**, then back-merge **`develop`**)
 - **Handoff (mandatory):** stop worktree-bound processes → remove `.worktree/<id>` →
   restart from primary checkout on `develop` (`duaer handoff [--run]`, `.duaer/handoff.json`)
-- Push only when the user explicitly asks
+- Push only when the user explicitly asks (a deploy/hosting ask authorizes
+  the `gh` + push needed for that publish — see `docs/agent/deploy-github.md`)
 - Promote **`develop` → `main`** only when the user asks to go online
+- English docs: no Chinese (CJK); Chinese docs may include English terms
 
 ## GitHub issue / PR intake
 

package/.duaer/active-job.json

@@ -1 +1,5 @@
-{"specDir":".duaer/specs/022-live-preview-link","branch":"feat/live-preview-link","startedAt":"2026-09-16T02:00:00.000Z"}
+{
+  "specDir": ".duaer/specs/032-revise-ux",
+  "branch": "fix/revise-ux",
+  "startedAt": "2026-09-16T03:40:00.000Z"
+}

package/.duaer/specs/023-gh-deploy-docs-lang/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T02:20:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "rg -n '[\\p{Han}]' README.md CHANGELOG.md AGENTS.md docs/agent docs/npm-trusted-publishing.md docs/adr (expect empty)"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/023-gh-deploy-docs-lang/spec.md

@@ -0,0 +1,47 @@
+# Feature Specification: GitHub CLI deploy + English docs language
+
+**Feature Branch**: `feat/gh-deploy`
+
+**Created**: 2026-09-16
+
+**Status**: Accepted
+
+## Goal
+
+When a product job needs hosting/deploy, digital employees use **GitHub CLI
+(`gh`) + GitHub Actions** as the default automation path (not third-party
+host CLIs). English documentation must not contain Chinese characters;
+Chinese docs may include English terms.
+
+## In scope
+
+- Live dispatch: detect deploy need from Brief text; add tasks + agent prompt
+  rules for `gh` / Actions / Pages
+- Template workflow adopters/agents can copy
+- Agent-ops + README (EN/ZH) document the policy
+- Scrub Chinese from English tracked docs (`README.md`, `CHANGELOG.md`,
+  `docs/agent/*`, etc.)
+
+## Out of scope
+
+- Rewriting Chinese Live Dev UI copy to English
+- Non-GitHub cloud vendors as first-class defaults
+- Auto-push without an explicit deploy/ship ask in the job
+
+## Acceptance
+
+1. Deploy-needed live jobs get an extra task and prompt block pointing to
+   `gh` + Actions (Pages template available under `.duaer/templates/`)
+2. `docs/agent/deploy-github.md` exists (English only) and is linked from
+   branching/README
+3. English docs contain no CJK characters
+4. Chinese README documents the same deploy preference (may use English
+   tool names)
+5. E2E catalog lists the deploy policy scenario
+
+## Assumptions
+
+- “Needs deploy” includes 部署 / host / publish / Pages / go online for a
+  user-facing site or app artifact
+- User asking for a deployable site authorizes `gh` setup and the push
+  required to publish that deployment

package/.duaer/specs/023-gh-deploy-docs-lang/tasks.md

@@ -0,0 +1,7 @@
+# Tasks
+
+- [x] T001 Spec + active-job
+- [x] T002 Live dispatch: needsDeploy → tasks + prompt; Pages workflow template
+- [x] T003 Docs: deploy-github.md, AGENTS/README EN+ZH, scrub CJK from English docs
+- [x] T004 E2E catalog + CHANGELOG Unreleased
+- [x] T005 Verify (docs + static checks) and accept

package/.duaer/specs/024-live-revise-feedback/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T02:30:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "rg revise README.md / api / UI"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/024-live-revise-feedback/spec.md

@@ -0,0 +1,43 @@
+# Feature Specification: Live revise after preview feedback
+
+**Feature Branch**: `feat/live-revise`
+
+**Created**: 2026-09-16
+
+**Status**: Accepted
+
+## Goal
+
+After the user opens the finished product and is not satisfied, they can give
+feedback on the live desk; the system understands the ask and relaunches the
+digital employee on the **same** product worktree to improve.
+
+## In scope
+
+- UI after `delivery.json` accepted: feedback box +「继续改进」
+- `POST /api/revise`: append revision to product Brief/tasks, reopen delivery,
+  relaunch CLI agent (same worktree)
+- Optional light restatement of feedback into the Brief
+- Resume progress polling after revise
+- Docs (EN no CJK) + E2E scenario
+
+## Out of scope
+
+- Creating a brand-new worktree for every revision
+- Changing the original confirm-card flow before first dispatch
+- Automatic satisfaction scoring
+
+## Acceptance
+
+1. When status is accepted and preview is shown (or missing), revise panel is
+   visible
+2. Submitting non-empty feedback calls `/api/revise`, updates product
+   `spec.md` / `tasks.md`, sets delivery back to open (not accepted)
+3. Agent Terminal relaunches with a revise prompt that cites the feedback
+4. Status poll resumes until the next accept
+5. English docs mention the revise loop without CJK
+
+## Assumptions
+
+- Same `dispatch.worktreePath` / Brief folder is reused
+- User feedback authorizes another agent run (not a remote push by itself)

package/.duaer/specs/024-live-revise-feedback/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Spec + active-job
+- [x] T002 `reviseDispatchedJob` + `POST /api/revise`
+- [x] T003 Live UI feedback panel + poll resume
+- [x] T004 Docs + E2E + CHANGELOG; verify; accept

package/.duaer/specs/025-revise-dialogue-continue/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T02:50:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "rg --continue bin/duaer-live.mjs"
+    ],
+    "result": "pass"
+  }
+}

package/.duaer/specs/025-revise-dialogue-continue/spec.md

@@ -0,0 +1,40 @@
+# Feature Specification: Revise via dialogue + agent --continue
+
+**Feature Branch**: `feat/revise-dialogue`
+
+**Created**: 2026-09-16
+
+**Status**: Accepted
+
+## Goal
+
+After preview, users start「继续改进」and clarify dissatisfaction in the **left
+chat** (why / what to change). Only after the revise card is confirmed does the
+desk dispatch. Revise launches reuse Cursor Agent / Claude **`--continue`** so
+the Terminal session keeps working on the same job.
+
+## In scope
+
+- Enter revise mode from a single button; freeform one-shot dispatch removed
+- `/api/chat` mode `revise` with multi-turn understand
+- Confirm card becomes revise card; confirm triggers `/api/revise`
+- `launchAgent({ continueSession: true })` → `agent --continue` / `claude --continue`
+- Docs EN/ZH (no CJK in EN)
+
+## Out of scope
+
+- Injecting keystrokes into an already-open Terminal TTY
+- Resuming a specific chatId UI picker
+
+## Acceptance
+
+1. After accept,「继续改进」opens left dialogue; no immediate dispatch
+2. Chat asks about reasons / desired change; revise card fills until ready
+3. Only「改进方案确认，再派一版」calls revise + Terminal relaunch
+4. Revise Terminal command includes `--continue` for Cursor Agent and Claude
+5. English docs mention continue-session revise without CJK
+
+## Assumptions
+
+- `--continue` uses the latest session for that worktree/cwd
+- If continue fails (no prior session), agent still runs with the new prompt

package/.duaer/specs/025-revise-dialogue-continue/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Spec + active-job
+- [x] T002 Chat mode revise + revise card confirm → /api/revise
+- [x] T003 launchAgent continueSession (--continue)
+- [x] T004 UI enter revise mode; docs; verify; accept

package/.duaer/specs/026-auto-fix-accept/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:00:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0"],
+    "commands": ["node --check bin/duaer-live.mjs"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/026-auto-fix-accept/spec.md

@@ -0,0 +1,27 @@
+# Feature Specification: Auto-fix button on accept failure
+
+**Feature Branch**: `feat/auto-fix-accept`
+
+**Created**: 2026-09-16
+
+**Status**: Active
+
+## Goal
+
+When confirm auto-accept fails (`自动验收未通过`), show an **自动修正** button
+on that bot message. Clicking it asks the model to fix the confirm card from
+the listed issues, then re-runs accept (and on success continues to dispatch
+as usual).
+
+## Acceptance
+
+1. Failed `/api/confirm` bubble includes an 自动修正 action button
+2. Click calls `/api/confirm/fix` with card + issues
+3. Fixed fields apply to the card; if accept passes, same success path as
+   normal confirm (Brief + dispatch panel)
+4. If still failing, show issues again with another 自动修正 button
+
+## Out of scope
+
+- Revise-card flow
+- Silent fix without a button

package/.duaer/specs/026-auto-fix-accept/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Spec
+- [x] T002 `/api/confirm/fix` + FIX prompt
+- [x] T003 UI action button on accept failure
+- [x] T004 Docs/CHANGELOG; accept; merge

package/.duaer/specs/027-duaer-prefix/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:10:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0"],
+    "commands": ["node --check bin/duaer-live.mjs", "rg Duaer web/live-dev bin/duaer-live.mjs"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/027-duaer-prefix/spec.md

@@ -0,0 +1,21 @@
+# Feature Specification: Start command prefix Duaer
+
+**Feature Branch**: `feat/duaer-prefix`
+
+**Created**: 2026-09-16
+
+**Status**: Active
+
+## Goal
+
+Live desk start-command / agent-prompt prefix is **`Duaer`**, not `Agent`.
+
+## Acceptance
+
+1. UI label/placeholder and default start command use `Duaer`
+2. Server dispatch/revise enforce `/^Duaer\b/`; legacy `Agent` prefix is rewritten to `Duaer`
+3. README EN/ZH and CHANGELOG mention `Duaer` prefix (EN docs no CJK)
+
+## Out of scope
+
+- Renaming Cursor Agent product labels

package/.duaer/specs/027-duaer-prefix/tasks.md

@@ -0,0 +1,4 @@
+# Tasks
+
+- [x] T001 Change prefix Agent → Duaer (UI + server + docs)
+- [x] T002 Accept + merge

package/.duaer/specs/028-fix-revise-stuck/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:20:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0"],
+    "commands": ["node --check bin/duaer-live.mjs"],
+    "result": "pass"
+  }
+}

package/.duaer/specs/028-fix-revise-stuck/spec.md

@@ -0,0 +1,20 @@
+# Feature Specification: Fix stuck revise UI
+
+**Feature Branch**: `fix/revise-stuck`
+
+**Created**: 2026-09-16
+
+**Status**: Accepted
+
+## Goal
+
+Revise mode must show clear motion: auto-start left-chat questions, no stuck
+「正在左侧对话改进…」label, and a visible **再派一版** button in the revise
+panel (not only the far confirm card).
+
+## Acceptance
+
+1. Entering revise kicks off an assistant question immediately
+2. Revise panel shows status + **再派一版** when card ready; no fake loading label
+3. Re-clicking enter revise does not wipe an in-progress revise chat
+4. Confirm-card and revise-panel CTAs both dispatch revise

package/.duaer/specs/028-fix-revise-stuck/tasks.md

@@ -0,0 +1,4 @@
+# Tasks
+
+- [x] T001 Auto kickoff + revise panel CTA + no stuck label
+- [x] T002 Accept + merge + restart live

package/.duaer/specs/029-self-update/delivery.json

@@ -0,0 +1,19 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:10:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0", "L1-smoke", "L3-catalog"],
+    "commands": [
+      "node --check bin/update-check.mjs",
+      "node --check bin/duaer.mjs",
+      "node --check bin/duaer-live.mjs",
+      "DUAER_NO_UPDATE_CHECK=1 node bin/duaer.mjs version",
+      "cmpSemver / formatUpdateHint unit smoke",
+      "curl /api/health → update.outdated + versions",
+      "rg CJK scrub on EN docs (CHANGELOG fixed)"
+    ],
+    "result": "pass",
+    "e2e": ["E2E-030"]
+  },
+  "notes": "Prompt-only update check; self-update is explicit. Product repos still use npx duaer-spec update."
+}

package/.duaer/specs/029-self-update/spec.md

@@ -0,0 +1,28 @@
+# Feature Specification: CLI update check + self-update
+
+**Feature Branch**: `feat/self-update`
+
+**Created**: 2026-09-16
+
+**Status**: Active
+
+## Goal
+
+When a newer `duaer-spec` is on npm, the CLI (and live desk) **notifies** the
+user. `duaer self-update` upgrades the global CLI. Default is prompt-only —
+no silent global install.
+
+## In scope
+
+- Shared update-check (npm registry, 24h cache under `~/.duaer/`)
+- Print hint on `duaer live` / common commands; `DUAER_NO_UPDATE_CHECK=1` skips
+- `duaer self-update` → `npm i -g duaer-spec@latest`
+- Live `/api/health` + small UI notice when outdated
+- Docs EN/ZH (EN no CJK)
+
+## Acceptance
+
+1. Outdated install prints a one-line upgrade hint (cached ≤24h)
+2. `duaer self-update` runs global npm install of latest
+3. Live health exposes `update.outdated` / versions; UI shows a short notice
+4. Env `DUAER_NO_UPDATE_CHECK=1` disables the check

package/.duaer/specs/029-self-update/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Shared update-check module
+- [x] T002 `duaer self-update` + startup hints
+- [x] T003 Live health + UI notice
+- [x] T004 Docs; accept; merge

package/.duaer/specs/030-revise-card-ui/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:20:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0", "L3-catalog"],
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "rg no stale 正在对话或续派 / exitReviseMode"
+    ],
+    "result": "pass",
+    "e2e": ["E2E-031"]
+  }
+}

package/.duaer/specs/030-revise-card-ui/spec.md

@@ -0,0 +1,40 @@
+# Feature Specification: Revise card stays visible after dispatch
+
+**Feature Branch**: `fix/revise-card-ui`
+
+**Created**: 2026-09-16
+
+**Status**: Active
+
+## Goal
+
+After the user confirms a revision and dispatch succeeds, the right-hand card
+keeps showing that revision (like the confirm card after first accept). Chat
+busy must not look like "续派中".
+
+## Problem
+
+1. UI stuck on「正在对话或续派，请稍候…」/「续派中…」even after dispatch
+2. After dispatch, chrome falls back to confirm/specify ("继续收集需求") so the
+   confirmed revision is no longer visible as an improve card
+3. Users need the right panel to show this round's confirmed improve fields
+
+## In scope
+
+- Separate chat busy vs revise-dispatch busy for button/hint copy
+- After successful `/api/revise`: keep right card as locked 改进卡 with the
+  confirmed fields; CTA "已续派";「继续改进」starts a new round
+- Do not reset to specify confirm-card chrome on revise success
+- E2E catalog note
+
+## Out of scope
+
+- Changing Terminal `--continue` launch
+- Redesigning dispatch progress polling
+
+## Acceptance
+
+1. During left-chat only: hints say dialogue in progress, not「续派中」
+2. During revise POST: show「续派中…」; after success clear it
+3. After success, right card remains 改进卡 with locked confirmed values
+4.「继续改进（左侧对话）」available for another round; entering clears for new card

package/.duaer/specs/030-revise-card-ui/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] T001 Split chat/dispatch busy; fix revise hints
+- [x] T002 Keep locked 改进卡 after revise success
+- [x] T003 Docs E2E + accept + merge + restart live

package/.duaer/specs/031-dispatch-init/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:35:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0", "L1-smoke", "L3-catalog"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "duaer-live.mjs repo add <empty-dir> → git init + AGENTS.md/.duaer (SMOKE_OK)"
+    ],
+    "result": "pass",
+    "e2e": ["E2E-032"]
+  }
+}

package/.duaer/specs/031-dispatch-init/spec.md

@@ -0,0 +1,38 @@
+# Feature Specification: Init Duaer in the chosen product directory
+
+**Feature Branch**: `fix/dispatch-init`
+
+**Created**: 2026-09-16
+
+**Status**: Active
+
+## Goal
+
+When the user picks a product directory for live dispatch, install/init Duaer
+**in that directory** (and the created worktree). Do not redirect to another
+repo or leave the agent to hunt for Duaer elsewhere.
+
+## Problem
+
+User selected a folder; it had no Duaer install; the flow “went looking”
+elsewhere (child git repo or agent search) instead of initializing in place.
+
+## In scope
+
+- Dispatch uses the chosen path (no silent single-child repo redirect)
+- Auto `git init` + `duaer init --here` in the chosen dir when needed
+- After worktree create: ensure Duaer is installed inside the worktree too
+- Agent prompt: work only here; Duaer already installed; do not search other trees
+- Browse/remember path: same ensure when registering a repo
+
+## Out of scope
+
+- Changing npm global self-update
+- Forcing commit of init files onto develop
+
+## Acceptance
+
+1. Dispatch to empty/non-duaer folder installs Duaer under that path
+2. Worktree contains AGENTS.md / `.duaer/` before agent launch
+3. Choosing a parent with one child git repo no longer silently switches; init stays on chosen path (or clear error)
+4. Docs/E2E note

package/.duaer/specs/031-dispatch-init/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] T001 exact-path probe + ensureDuaerInstalled
+- [x] T002 wire dispatch + repo remember; prompt text
+- [x] T003 verify smoke; docs; accept; merge; restart live

package/.duaer/specs/032-revise-ux/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-16T03:50:00.000Z",
+  "verification": {
+    "levels": ["docs", "L0", "L3-catalog"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "manual: Terminal reuse via .duaer/live-terminal queue"
+    ],
+    "result": "pass",
+    "e2e": ["E2E-033"]
+  }
+}

package/.duaer/specs/032-revise-ux/spec.md

@@ -0,0 +1,32 @@
+# Feature Specification: Revise UX — brief visible, preview, Terminal reuse
+
+**Feature Branch**: `fix/revise-ux`
+
+**Created**: 2026-09-16
+
+**Status**: Active
+
+## Goal
+
+1.「再改一版」must not bury the original requirements; keep original Brief visible
+2. After dispatch / revise, user can always open the (updated) product preview
+3. Reuse one Terminal window per worktree for follow-up tasks instead of opening many
+
+## In scope
+
+- Show compact「原始需求」when in revise / revise-locked chrome
+- Soften revise CTA: show only when delivery accepted; secondary style
+- Preview: keep serving last preview during revising (do not drop delivery.preview)
+- Terminal task queue under worktree `.duaer/live-terminal/`; enqueue revise into same runner
+
+## Out of scope
+
+- Cross-machine Terminal remoting
+- Changing agent CLI flags beyond queue wrapping
+
+## Acceptance
+
+1. Original goal/acceptance remain readable while「再改一版」is available
+2. Preview link stays usable after accept and during/after revise when artifact exists
+3. Second revise enqueue does not `open` a new Terminal if runner PID is alive
+4. E2E catalog updated

package/.duaer/specs/032-revise-ux/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] T001 Terminal queue reuse in launchInTerminal / launchAgent
+- [x] T002 Preview kept during revise; original brief UI + softer CTA
+- [x] T003 Docs accept merge restart

package/.duaer/templates/deploy-github-pages.yml

@@ -0,0 +1,43 @@
+# name: Deploy to GitHub Pages
+
+# Default product deploy path for static sites built with duaer-spec.
+# Agents: copy into the product repo as .github/workflows/deploy.yml
+# (or merge steps), then use `gh` to enable Pages and trigger the workflow.
+# See docs/agent/deploy-github.md
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: true
+
+jobs:
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Pages
+        uses: actions/configure-pages@v5
+
+      # Adjust if the site is not at repo root (e.g. copy dist/ → _site)
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: .
+
+      - name: Deploy
+        id: deployment
+        uses: actions/deploy-pages@v4

package/ADOPT.md

@@ -8,6 +8,17 @@ npx duaer-spec init --here
 
 ## Update
 
+**Global CLI:**
+
+```bash
+duaer self-update
+```
+
+Or: `npm i -g duaer-spec@latest`. The CLI prints a hint when npm has a newer
+release (≤24h cache; `DUAER_NO_UPDATE_CHECK=1` skips).
+
+**Product-repo adapters:**
+
 ```bash
 npx duaer-spec update
 ```