duaer-spec 0.21.0 → 0.23.0

package/.claude/rules/duaer-spec.md

@@ -28,9 +28,12 @@ For new behavior, fixes, refactors that change product behavior, or architecture
 3. Do **not** wait for `/duaer-do` or any other skill invocation.
 4. Do **not** say “please run `/duaer-specify`” — you do it.
 5. Do **not** dump a methodology tutorial unless they ask how Duaer works.
-6. Merge to **`develop`** when done (hotfix: **`main`**, then back-merge
+6. **Break down to atomic, monitorable tasks:** each `tasks.md` item is one
+   independently verifiable atom with a `- [ ]` / `- [x]` checkbox; mark done
+   as you go so progress is visible. Do not leave only coarse mega-tasks.
+7. Merge to **`develop`** when done (hotfix: **`main`**, then back-merge
    **`develop`**). Promote to **`main`** only if the user asks to go online.
-7. **Handoff (mandatory):** stop processes bound to `.worktree/<id>/`, remove
+8. **Handoff (mandatory):** stop processes bound to `.worktree/<id>/`, remove
    the worktree, then restart services from the primary checkout on `develop`
    using `.duaer/handoff.json` / `duaer handoff [--run]`. Never leave the user
    on a dead worktree server.

package/.cursor/rules/duaer-spec.mdc

@@ -32,9 +32,12 @@ For new behavior, fixes, refactors that change product behavior, or architecture
 3. Do **not** wait for `/duaer-do` or any other skill invocation.
 4. Do **not** say “please run `/duaer-specify`” — you do it.
 5. Do **not** dump a methodology tutorial unless they ask how Duaer works.
-6. Merge to **`develop`** when done (hotfix: **`main`**, then back-merge
+6. **Break down to atomic, monitorable tasks:** each `tasks.md` item is one
+   independently verifiable atom with a `- [ ]` / `- [x]` checkbox; mark done
+   as you go so progress is visible. Do not leave only coarse mega-tasks.
+7. Merge to **`develop`** when done (hotfix: **`main`**, then back-merge
    **`develop`**). Promote to **`main`** only if the user asks to go online.
-7. **Handoff (mandatory):** stop processes bound to `.worktree/<id>/`, remove
+8. **Handoff (mandatory):** stop processes bound to `.worktree/<id>/`, remove
    the worktree, then restart services from the primary checkout on `develop`
    using `.duaer/handoff.json` / `duaer handoff [--run]`. Never leave the user
    on a dead worktree server.

package/.cursor/skills/duaer-do/SKILL.md

@@ -54,7 +54,13 @@ Do **not** lecture about methodology. Do **not** ask them to run commands.
    - Deep ambiguity after a full Spec still uses `duaer-clarify` (up to 5
      questions). Understand is the **lightweight front door** on every ask.
 
-3. **Break down** — If `tasks.md` missing, write a short checklist from the Spec.
+3. **Break down** — If `tasks.md` missing, write a checklist from the Spec.
+   **Atomic + monitorable (mandatory):**
+   - Split until each item is **one** independently verifiable acceptance /
+     deliverable atom (not a mega-phase).
+   - Every item is a markdown checkbox (`- [ ]` / `- [x]`) so progress can be
+     polled; check off immediately when that atom is done.
+   - Prefer one checkbox per Acceptance line; no artificial upper count.
    Skip a heavy plan unless architecture or contracts change.
 
 4. **Work** — Implement open tasks; mark `[x]` as you go. No scope beyond Spec.

package/.cursor/skills/duaer-tasks/SKILL.md

@@ -139,6 +139,14 @@ The tasks.md should be immediately executable - each task must be specific enoug
 
 **CRITICAL**: Tasks MUST be organized by user story to enable independent implementation and testing.
 
+**Atomic + monitorable (NON-NEGOTIABLE)**:
+- Every task is **one** independently verifiable atom (one acceptance point,
+  one file-scoped change, or one verification slice) — not a bundled mega-task.
+- Every task is a markdown checkbox (`- [ ]` / `- [x]`) so progress is
+  monitorable; agents mark `[x]` as each atom completes.
+- Prefer one task per Acceptance / independent-test criterion. No artificial
+  upper count; refine if still too coarse.
+
 **Verification is DEFAULT**: For each user story, generate verification tasks
 from `.duaer/memory/testing.md` (L0–L3 as the risk table requires). Do **not**
 omit tests just because the Spec did not say “TDD”. Only skip a level when the

package/.duaer/active-job.json

@@ -1,5 +1,4 @@
 {
-  "featureDir": ".duaer/specs/202-release-021",
-  "slug": "202-release-021",
-  "branch": "chore/release-021"
+  "feature": "210-release-023",
+  "specDir": ".duaer/specs/210-release-023"
 }

package/.duaer/memory/constitution.md

@@ -41,3 +41,16 @@ cannot cover the path.
 **Job handoff (not a git lock):** the agent reports accept/open itself.
 Default policy `coach` — do not claim "done" while the active job is unfinished.
 Do not send the human to run `duaer status` for routine work.
+
+### V. Atomic verifiable tasks; progress must be monitorable (NON-NEGOTIABLE)
+
+When breaking down work (`tasks.md`, kickoff task pool, or mid-job re-split):
+
+1. **Atomic + verifiable:** each task covers **one** independently checkable
+   acceptance point or deliverable slice. Do not bundle unrelated acceptance
+   into a mega-task.
+2. **Monitorable progress:** every task is a markdown checkbox
+   (`- [ ]` / `- [x]`). Mark `[x]` as soon as that atom is done so FDE / humans
+   can see progress. Do not replace checkboxes with prose-only status.
+3. Prefer splitting Acceptance lines (and Goal slices) over inventing coarse
+   phases. There is **no** artificial upper count; refine if still too coarse.

package/.duaer/specs/202-release-021/delivery.json

@@ -0,0 +1,18 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T04:20:00.000Z",
+  "summary": "0.21.0 shipped: develop+main pushed, tag v0.21.0, GitHub Release, npm publish success.",
+  "verification": {
+    "commands": [
+      "git push origin develop main v0.21.0",
+      "gh release create v0.21.0",
+      "gh run watch 35420973848 → success",
+      "npm view duaer-spec version → 0.21.0"
+    ]
+  },
+  "preview": {
+    "url": "https://www.npmjs.com/package/duaer-spec/v/0.21.0",
+    "label": "npm 0.21.0"
+  },
+  "release": "https://github.com/fujiezee/duaer-spec/releases/tag/v0.21.0"
+}

package/.duaer/specs/202-release-021/tasks.md

@@ -1,5 +1,5 @@
 # Tasks — 202-release-021
 
 - [x] Brief
-- [ ] Bump 0.21.0 + CHANGELOG
-- [ ] Promote / push / release / npm
+- [x] Bump 0.21.0 + CHANGELOG
+- [x] Promote / push / release / npm

package/.duaer/specs/203-atomic-monitorable-tasks/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T04:50:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": [
+      "node --check bin/live-modules.mjs bin/live-progress.mjs web/live-dev/task-graph.mjs web/live-dev/acceptance-lines.mjs",
+      "npm test (165 pass; atomic pool + preview split covered)"
+    ],
+    "result": "pass"
+  },
+  "summary": "Atomic verifiable tasks with checkbox-monitorable progress: constitution, skills, kickoff pool + preview graph split acceptance lines."
+}

package/.duaer/specs/203-atomic-monitorable-tasks/spec.md

@@ -0,0 +1,44 @@
+# Feature Specification: Atomic verifiable tasks with monitorable progress
+
+**Feature Branch**: `feat/atomic-tasks`
+
+## Goal
+
+When decomposing work (Break down / kickoff task pool / `tasks.md`), every
+task MUST be an **atomic, independently verifiable** unit, and every task's
+progress MUST be **monitorable** via a markdown checkbox that the FDE desk
+(and agents) can poll.
+
+## Why
+
+Coarse mega-tasks hide progress and block wave orchestration. Acceptance
+bundled into one line cannot be checked off piecemeal.
+
+## In scope
+
+- Constitution + duaer-do / duaer-tasks / template wording for the rule
+- Kickoff `buildTaskPoolFromModules` splits module acceptance into one
+  checkbox task per acceptance line (plus impl / verify / shared steps)
+- Preview task graph uses the same atomic split so path matches pool
+- `tasks.md` footer / dispatch prompt reinforce: checkbox = progress signal
+- Tests + E2E catalog row
+
+## Out of scope
+
+- Changing orchestration wave algorithm beyond richer ready sets
+- Dedicated cloud / npm release
+
+## Acceptance
+
+1. Constitution (or equivalent always-on rule) states: decompose to atomic
+   verifiable tasks; each task progress monitorable via `- [ ]` / `- [x]`
+2. Module with multi-line acceptance yields one task per acceptance line in
+   the task pool / `tasks.md`
+3. Preview pool for the same modules has matching atomic acceptance tasks
+4. Unit tests cover the split; E2E catalog mentions the rule
+5. Agents following duaer-do Break down must not leave only coarse mega-tasks
+
+## Assumptions
+
+- Prefer splitting on acceptance lines / `;` / `；` (existing
+  `splitAcceptanceLines`) rather than LLM rephrasing at kickoff

package/.duaer/specs/203-atomic-monitorable-tasks/tasks.md

@@ -0,0 +1,8 @@
+# Tasks
+
+- [x] T001 Add constitution + duaer-do / duaer-tasks / template rule
+- [x] T002 Split acceptance into atomic tasks in live-modules pool
+- [x] T003 Mirror atomic split in task-graph preview pool
+- [x] T004 Strengthen tasks.md footer + dispatch prompt wording
+- [x] T005 Unit tests + E2E catalog
+- [x] T006 Stamp delivery accepted

package/.duaer/specs/204-live-i18n-ja/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T07:40:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/i18n.js web/live-dev/i18n-ja.js web/live-dev/app.js bin/live-deliverables.mjs",
+      "npm test (168 pass incl. live-i18n-ja)",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  },
+  "summary": "Added Japanese (ja) live desk locale with full catalog parity, language select, and deliverables lang=ja."
+}

package/.duaer/specs/204-live-i18n-ja/spec.md

@@ -0,0 +1,34 @@
+# Feature Specification: Live desk Japanese locale (ja)
+
+**Feature Branch**: `feat/live-i18n-ja`
+
+## Goal
+
+Add **Japanese (`ja`)** as a third FDE live-desk language beside zh-CN and en.
+Users can switch to 日本語; reload keeps the choice; desk copy updates.
+
+## In scope
+
+- `LOCALES` includes `ja`; full catalog for all i18n keys
+- Language `<select>` option; `detectLocale` for `ja*` navigator
+- Deliverables `lang=ja` + date/`html lang` handling
+- app.js list join / toLocaleString for ja
+- task-graph Archify locale passthrough
+- E2E catalog + unit/smoke markers; CHANGELOG
+
+## Out of scope
+
+- Translating README / intro site / worker-models.md into Japanese
+- Other locales beyond `ja`
+
+## Acceptance
+
+1. Language select shows 日本語 (`ja`); switching updates visible desk copy
+2. Reload keeps `ja` via localStorage
+3. Every key present in `en` exists in `ja` (no missing-key gaps in catalog parity test)
+4. Deliverables HTML accepts `lang=ja`
+5. `npm test` / required live smoke still pass
+
+## Assumptions
+
+- Default remains zh-CN when unset; `ja` browser language can auto-detect to ja

package/.duaer/specs/204-live-i18n-ja/tasks.md

@@ -0,0 +1,7 @@
+# Tasks
+
+- [x] T001 Add ja catalog + LOCALES/detectLocale/setLocale wiring
+- [x] T002 Language select option in index.html
+- [x] T003 app.js / deliverables / task-graph ja handling
+- [x] T004 Tests + E2E + docs + CHANGELOG
+- [x] T005 Stamp delivery accepted

package/.duaer/specs/205-release-022/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T07:37:00.000Z",
+  "verification": {
+    "levels": ["L1"],
+    "commands": ["npm test (168 pass)", "gh release v0.22.0", "npm view duaer-spec version → 0.22.0"],
+    "result": "pass"
+  },
+  "summary": "Released 0.22.0 to GitHub and npm (ja locale + atomic tasks)."
+}

package/.duaer/specs/205-release-022/spec.md

@@ -0,0 +1,12 @@
+# 205 — Release 0.22.0
+
+## Goal
+
+Ship 0.22.0: bump version + CHANGELOG, promote develop → main, push,
+GitHub Release `v0.22.0`, trigger npm Trusted Publishing.
+
+## Acceptance
+
+1. `package.json` is `0.22.0`; CHANGELOG has `0.22.0` section (Unreleased cleared).
+2. `develop` and `main` pushed with release commits.
+3. GitHub Release `v0.22.0` published; npm shows `duaer-spec@0.22.0`.

package/.duaer/specs/205-release-022/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Bump package.json to 0.22.0 and move CHANGELOG Unreleased
+- [x] T002 Merge release branch to develop
+- [x] T003 Promote develop → main, push, tag, gh release, npm
+- [x] T004 Stamp delivery accepted

package/.duaer/specs/206-employee-directory/delivery.json

@@ -0,0 +1,13 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T12:45:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "npm test (173 pass)",
+      "npm run test:live"
+    ],
+    "result": "pass"
+  },
+  "summary": "Top employee directory with Implementer + Functional regression; task roles and verify-l3 lane assignment."
+}

package/.duaer/specs/206-employee-directory/spec.md

@@ -0,0 +1,32 @@
+# Feature Specification: Digital employee directory + role specialization
+
+**Feature Branch**: `feat/employee-directory`
+
+## Goal
+
+Add a top-bar **数字员工** directory listing specialized employees. Seed at
+least: **Implementer** and **Functional regression** (Acceptance → Playwright /
+testing.md L3). Kickoff tasks carry a `role`; multi-worker dispatch prefers
+verify-l3 tasks on a dedicated lane.
+
+## In scope
+
+- Top button + drawer (same pattern as Projects)
+- Catalog: implementer + regression (capabilities copy via i18n zh/en/ja)
+- Task pool `role: implement | verify-l3`; markdown shows role
+- When workerCount ≥ 2, assign verify-l3 tasks to the last worker lane
+- Kickoff prompts include role blurb for owned roles
+- Docs / E2E / tests
+
+## Out of scope
+
+- New CLI runtimes (still Cursor / Claude)
+- jev-ultrafast / browser-use agent
+- User-editable custom employees
+
+## Acceptance
+
+1. Top bar has 数字员工; drawer lists implementer + regression with capability text
+2. Kickoff task-pool.json tasks include `role`
+3. workerCount≥2 puts verify-l3 tasks on last worker
+4. Unit tests + E2E catalog row; live smoke markers if needed

package/.duaer/specs/206-employee-directory/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Employee catalog module + task role on pool
+- [x] T002 Top directory drawer UI + i18n
+- [x] T003 Assign verify-l3 to last lane; kickoff role prompts
+- [x] T004 Docs tests CHANGELOG stamp

package/.duaer/specs/207-fix-projects-root-pick/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T12:55:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": ["node --check bin/duaer-live.mjs", "npm test (173 pass)"],
+    "result": "pass"
+  },
+  "summary": "Parent folder picker activates Finder (frontmost) and path field click opens pick; async so HTTP stays responsive."
+}

package/.duaer/specs/207-fix-projects-root-pick/spec.md

@@ -0,0 +1,20 @@
+# Fix: projects parent folder picker unusable
+
+## Symptom
+
+Clicking 产品父目录 / 选择… does not yield a usable folder choice (dialog
+behind other windows, or readonly field ignores clicks).
+
+## Cause
+
+`pickFolderNative` uses `osascript choose folder` without activating a UI
+app, so the dialog often stays behind the browser. The path field is
+readonly with no click handler.
+
+## Acceptance
+
+1. Clicking **选择…** or the readonly parent path opens a frontmost macOS
+   folder dialog (Finder-activated).
+2. Pick is async (HTTP event loop not blocked by spawnSync).
+3. Cancel leaves previous `projectsRoot` unchanged.
+4. Unit markers + L0 check.

package/.duaer/specs/207-fix-projects-root-pick/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] T001 Async Finder-activated pickFolderNative
+- [x] T002 Path field click opens pick; tests/docs
+- [x] T003 Stamp accepted

package/.duaer/specs/208-arch-click-fullscreen/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T13:10:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": ["node --test test/arch-fullscreen.test.mjs test/live-archify.test.mjs", "npm test"],
+    "result": "pass"
+  },
+  "summary": "Architecture mount click opens present fullscreen only; embed node zoom disabled."
+}

package/.duaer/specs/208-arch-click-fullscreen/spec.md

@@ -0,0 +1,24 @@
+# Spec: Architecture click opens fullscreen only
+
+## Goal
+
+On the live desk system-architecture (and same-style) mounts, a click opens the
+fullscreen present view. Node zoom / enlarge-on-click in the embed is removed.
+
+## In scope
+
+- Host click (capture) opens `present=1` fullscreen and stops Archify node zoom
+- Disable desk embed `installDesktopReveal` zoom path
+- Update E2E catalog lines that still require embed node zoom
+
+## Out of scope
+
+- Changing fullscreen present page itself
+- Removing the explicit「全屏查看」button
+
+## Acceptance
+
+- [ ] Clicking the architecture diagram opens fullscreen present (new tab)
+- [ ] Clicking a node does not zoom / enlarge that node in the desk embed
+- [ ] Task-path / revise mounts keep the same click → fullscreen behavior
+- [ ] Tests and E2E catalog match the new behavior

package/.duaer/specs/208-arch-click-fullscreen/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] T001 Capture-phase click opens present; stop Archify node handlers
+- [x] T002 Disable embed node zoom in architecture-mount
+- [x] T003 Update E2E / CHANGELOG / unit tests
+- [x] T004 Verify and stamp accepted

package/.duaer/specs/209-orch-wave-deadlock/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T13:20:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": ["npm test (173 pass)"],
+    "result": "pass"
+  },
+  "summary": "Wave continue enqueues while lane busy; agents exit after wave instead of silent hang deadlock."
+}

package/.duaer/specs/209-orch-wave-deadlock/spec.md

@@ -0,0 +1,27 @@
+# Spec: Fix orchestration wave deadlock after silent wait
+
+## Goal
+
+After a wave finishes and `tasks.md` is checked, the orchestrator must release
+the next ready wave. Agents must not sit in a live Terminal session waiting —
+that keeps `lane_busy` and blocks continue forever.
+
+## In scope
+
+- Prompt: after a wave, exit the CLI session so the runner becomes idle /
+  can drain a queued `--continue`
+- `pendingWaveReleases`: enqueue next wave even when the lane is busy
+  (FIFO serialize); do not stall on `lane_busy`
+- Accept-nudge: same enqueue-when-busy behavior
+- Docs / tests / E2E note
+
+## Out of scope
+
+- Changing dependsOn / atomic task splitting
+- Fixing polluted startCommand content from other projects (separate)
+
+## Acceptance
+
+- [ ] Status with T001 done + next wave ready enqueues/releases while lane busy
+- [ ] Prompts no longer tell the agent to 静默停等 with the session held open
+- [ ] Unit tests updated; npm test passes

package/.duaer/specs/209-orch-wave-deadlock/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] T001 Enqueue next wave even when lane busy
+- [x] T002 Prompt: exit session after wave (no silent hang)
+- [x] T003 Tests, CHANGELOG, E2E; stamp accepted

package/.duaer/specs/210-release-023/spec.md

@@ -0,0 +1,12 @@
+# 210 — Release 0.23.0
+
+## Goal
+
+Ship 0.23.0: bump version + CHANGELOG, promote develop → main, push,
+GitHub Release `v0.23.0`, trigger npm Trusted Publishing.
+
+## Acceptance
+
+1. `package.json` is `0.23.0`; CHANGELOG has `0.23.0` section (Unreleased cleared).
+2. `develop` and `main` both contain the release; tag `v0.23.0` pushed.
+3. GitHub Release `v0.23.0` published; npm shows `duaer-spec@0.23.0`.

package/.duaer/specs/210-release-023/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [ ] T001 Bump package.json to 0.23.0 and move CHANGELOG Unreleased
+- [ ] T002 Merge release branch to develop
+- [ ] T003 Promote develop → main, push, tag, gh release, npm
+- [ ] T004 Stamp delivery accepted

package/.duaer/templates/tasks-template.md

@@ -15,6 +15,10 @@ TDD-style tests-before-code remain encouraged when useful.
 
 **Organization**: Tasks are grouped by user story to enable independent implementation and testing of each story.
 
+**Atomic + monitorable**: Each checkbox is one independently verifiable atom.
+Progress is only via `- [ ]` / `- [x]` — no prose-only status. Split Acceptance
+into one task per criterion; no artificial upper count.
+
 ## Format: `[ID] [P?] [Story] Description`
 
 - **[P]**: Can run in parallel (different files, no dependencies)

package/CHANGELOG.md

@@ -2,6 +2,44 @@
 
 ## Unreleased
 
+## 0.23.0 — 2026-09-19
+
+### Fix: orchestration wave release no longer deadlocks on silent wait
+
+- Next ready wave is FIFO-enqueued even when the Terminal lane is busy
+- After a wave, agents exit the CLI session (no hang waiting for continue)
+
+### Fix: architecture embed click opens fullscreen only
+
+- Desk diagram click (capture) opens present fullscreen and does not zoom nodes
+- Embed `reveal` zoom path disabled; focus-chip hidden on the mount
+
+### Fix: projects parent folder picker frontmost + clickable path
+
+- macOS folder dialog activates Finder so it is not buried behind the browser
+- Pick is async (no spawnSync on the HTTP thread)
+- Clicking the readonly parent path also opens the picker
+
+### Feat: digital employee directory + role specialization
+
+- Top bar **数字员工** drawer lists Implementer and Functional regression
+- Kickoff tasks carry `role: implement | verify-l3`; multi-worker puts
+  verify-l3 on the last lane; prompts include role blurbs
+
+## 0.22.0 — 2026-09-19
+
+### Feat: Japanese (ja) live desk locale
+
+- Language select adds 日本語; catalog covers all en keys
+- Deliverables API accepts `lang=ja`; dates / HTML `lang` use ja-JP
+
+### Feat: atomic verifiable tasks with monitorable progress
+
+- Constitution + duaer-do / duaer-tasks: decompose to one independently
+  verifiable atom per checkbox; progress only via `- [ ]` / `- [x]`
+- Kickoff task pool and preview graph split multi-line acceptance into
+  one task per criterion so FDE can monitor and release waves
+
 ## 0.21.0 — 2026-09-19
 
 ### Feat: click architecture diagram for fullscreen present view