duaer-spec 0.20.0 → 0.22.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.
@@ -67,10 +73,22 @@ Do **not** lecture about methodology. Do **not** ask them to run commands.
 
 6. **Handoff** — One line to the human:
    - `✅ Job accepted — ready for your review.`
-   - `⏳ Job not accepted yet — <one sentence>.`
+   - `⏳ Job not accepted yet — <one sentence>.` (**not** for FDE / live-dispatch
+     — see below)
    - During Understand wait: `⏳ Confirming intent — <one sentence restatement>.`
    Never claim done unless accepted + tasks clear. Git is not locked by this.
 
+### FDE live-dispatch (mandatory finish)
+
+When `.duaer/active-job.json` has `"source": "live-dispatch"` (Duaer-spec FDE
+kicked you off), **every** assigned task must be completed and
+`delivery.json` stamped `accepted` before you stop.
+
+- **Do not** end with `⏳ Job not accepted yet` — that freezes the desk mid-coding.
+- Mid-wave pause for the orchestrator is fine **only** as a quiet stop (no
+  unaccepted handoff line).
+- Final line after stamp: `✅ Job accepted — ready for your review.`
+
 ## Hotfix
 
 Still a short Spec (symptom / cause / acceptance). Restate once; if repro is

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,5 @@
 {
-  "feature": "192-release-020",
-  "spec": ".duaer/specs/192-release-020/spec.md",
-  "updatedAt": "2026-09-19T02:50:00.000Z"
+  "featureDir": ".duaer/specs/205-release-022",
+  "slug": "205-release-022",
+  "updatedAt": "2026-09-19T07:35:00.000Z"
 }

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/192-release-020/delivery.json

@@ -0,0 +1,19 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T02:48:00.000Z",
+  "summary": "0.20.0 shipped: develop+main pushed, tag v0.20.0, GitHub Release, npm publish success.",
+  "verification": {
+    "commands": [
+      "git push origin develop main v0.20.0",
+      "gh release create v0.20.0",
+      "gh run view 35416594850 (Publish npm package success)",
+      "npm view duaer-spec version → 0.20.0"
+    ],
+    "result": "pass"
+  },
+  "npm": {
+    "url": "https://www.npmjs.com/package/duaer-spec/v/0.20.0",
+    "label": "npm 0.20.0"
+  },
+  "release": "https://github.com/fujiezee/duaer-spec/releases/tag/v0.20.0"
+}

package/.duaer/specs/192-release-020/tasks.md

@@ -1,6 +1,6 @@
 # Tasks — 192-release-020
 
 - [x] Brief
-- [ ] Bump 0.20.0 + CHANGELOG
-- [ ] Merge to develop; promote main; push; tag; gh release
-- [ ] Watch npm publish / stamp delivery
+- [x] Bump 0.20.0 + CHANGELOG
+- [x] Merge to develop; promote main; push; tag; gh release
+- [x] Watch npm publish / stamp delivery

package/.duaer/specs/193-dispatch-must-accept/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:10:00.000Z",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs",
+    "L1": "node --test test/dispatch-must-accept.test.mjs test/live-orchestrate.test.mjs",
+    "L3": "npm run test:live",
+    "result": "pass"
+  },
+  "summary": "FDE dispatch must finish every task; forbid Job not accepted yet; accept nudge when checklist done."
+}

package/.duaer/specs/193-dispatch-must-accept/spec.md

@@ -0,0 +1,17 @@
+# 193 — Dispatch must finish every task (no early “not accepted”)
+
+## Goal
+
+FDE-dispatched digital employees must complete **every** assigned task and
+stamp `delivery.json` `accepted`. They must not stop with
+`⏳ Job not accepted yet` mid-job (that freezes product coding).
+
+## Acceptance
+
+1. Kickoff / wave / continue / revise prompts forbid “Job not accepted yet”
+   as a final handoff; require ✅ accepted only after all tasks + stamp.
+2. When all `tasks.md` boxes are checked but delivery is not accepted, status
+   poll nudges an idle lane to stamp accepted (once).
+3. `duaer-do` skill: for `source: live-dispatch` (and FDE worktrees), never end
+   unaccepted.
+4. L0 + unit/smoke markers; merge to develop.

package/.duaer/specs/193-dispatch-must-accept/tasks.md

@@ -0,0 +1,6 @@
+# Tasks — 193-dispatch-must-accept
+
+- [x] Brief
+- [ ] Prompt harden + accept nudge in advanceOrchestration
+- [ ] duaer-do skill + docs/E2E/tests
+- [ ] Merge develop + handoff

package/.duaer/specs/194-chat-preview-link/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:25:00.000Z",
+  "verification": {
+    "L0": "node --check web/live-dev/chat-markdown.mjs; node --check web/live-dev/app.js",
+    "L1": "node --test test/chat-markdown.test.mjs",
+    "L3": "npm run test:live",
+    "result": "pass"
+  },
+  "summary": "Accepted chat bubble preview URL is clickable (markdown + bare URL auto-link)."
+}

package/.duaer/specs/194-chat-preview-link/spec.md

@@ -0,0 +1,14 @@
+# 194 — Clickable preview URL in chat
+
+## Goal
+
+When the desk posts「数字员工已做好…打开看看」with a preview URL, that URL
+must be a real clickable link in the chat bubble (not plain text).
+
+## Acceptance
+
+1. Accepted bot bubble shows an `<a href>` for http(s) and `/api/…` preview URLs.
+2. Clicking opens in a new tab (noopener).
+3. Relative page paths still offer an open action via「打开看看」chip when not
+   directly linkable.
+4. L0 + chat-markdown / smoke tests; merge develop.

package/.duaer/specs/194-chat-preview-link/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 194-chat-preview-link
+
+- [x] Brief
+- [ ] chat-markdown auto-link + accepted bubble href
+- [ ] Tests / E2E / merge

package/.duaer/specs/195-chat-link-garble/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:35:00.000Z",
+  "verification": {
+    "L1": "node --test test/chat-markdown.test.mjs",
+    "L3": "npm run test:live",
+    "result": "pass"
+  },
+  "summary": "Fix nested /api/result auto-link garble in chat preview URLs."
+}

package/.duaer/specs/195-chat-link-garble/spec.md

@@ -0,0 +1,17 @@
+# 195 — Fix garbled chat preview links
+
+## Goal
+
+Accepted-bubble preview links must not show broken HTML (e.g. raw
+`target="_blank"` text) when the URL is `http://…/api/result/…`.
+
+## Cause
+
+Bare `/api/result/…` auto-link matched inside an existing `http://host/api/result/…`
+href and nested/broke the `<a>` tag.
+
+## Acceptance
+
+1. `http://127.0.0.1:8787/api/result/…` renders as one clean clickable link.
+2. Bare `/api/result/…` and `/api/artifact/…` still auto-link when standalone.
+3. Unit tests cover the nested-path regression; merge develop.

package/.duaer/specs/195-chat-link-garble/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 195-chat-link-garble
+
+- [x] Brief
+- [ ] Fix chat-markdown bare /api/ nesting; simplify accepted link
+- [ ] Tests + merge

package/.duaer/specs/196-task-exec-graph/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:50:00.000Z",
+  "verification": {
+    "L0": "node --check web/live-dev/app.js; node --check web/live-dev/task-graph.mjs",
+    "L1": "node --test test/task-graph.test.mjs",
+    "L3": "npm run test:live",
+    "result": "pass"
+  },
+  "summary": "Worker count chips + SVG task dependency execution graph on kickoff."
+}

package/.duaer/specs/196-task-exec-graph/spec.md

@@ -0,0 +1,15 @@
+# 196 — Worker chips + task dependency execution graph
+
+## Goal
+
+Improve the digital-employee count control (chips instead of a bare select),
+and show a **task path dependency graph** (architecture-panel look) driven by
+module/task `dependsOn` and the selected worker count.
+
+## Acceptance
+
+1. Worker count is a chip radiogroup (1–4); selected state matches deploy chips.
+2. When the task pool is visible, an SVG dependency graph shows tasks, edges,
+   and worker lane coloring for the current count.
+3. Changing worker count re-assigns and re-renders the graph.
+4. Unit tests for layout/render; L3 smoke; merge develop.

package/.duaer/specs/196-task-exec-graph/tasks.md

@@ -0,0 +1,6 @@
+# Tasks — 196-task-exec-graph
+
+- [x] Brief
+- [ ] Worker count chips + CSS
+- [ ] task-graph.mjs layout/SVG + wire preview
+- [ ] Tests / docs / merge

package/.duaer/specs/197-task-graph-archify/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:20:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3-archify-smoke"],
+    "commands": [
+      "node --test test/task-graph.test.mjs",
+      "renderArchitectureHtml smoke (workers 1–3)"
+    ],
+    "notes": "Task path IR uses Archify deliver; transitive reduction + ranked/lane positions for clean-flow validation."
+  }
+}

package/.duaer/specs/197-task-graph-archify/spec.md

@@ -0,0 +1,14 @@
+# 197 — Task graph via Archify (same as architecture)
+
+## Goal
+
+Task execution path uses the **same Archify renderer and left-to-right layered
+layout** as the system architecture diagram — not a custom SVG.
+
+## Acceptance
+
+1. Kickoff task graph is produced via `/api/architecture/render` +
+   `mountArchitectureDiagram`.
+2. IR maps tasks → components, `dependsOn` → connections; layout matches Archify.
+3. Changing worker count re-renders the Archify graph.
+4. Unit tests for IR mapping; L3 smoke; merge develop.

package/.duaer/specs/197-task-graph-archify/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 197-task-graph-archify
+
+- [x] Brief
+- [x] taskPoolToArchitectureIr + mount via Archify
+- [x] Tests / docs / merge

package/.duaer/specs/198-task-graph-labels/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:25:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --test test/task-graph.test.mjs",
+      "renderArchitectureHtml smoke (no depends/Workers)",
+      "npm run test:live"
+    ]
+  }
+}

package/.duaer/specs/198-task-graph-labels/spec.md

@@ -0,0 +1,12 @@
+# 198 — Task graph: no redundant Archify labels
+
+## Goal
+
+Kickoff task-path Archify diagram shows nodes and edges only — no
+redundant edge/legend/subtitle copy (e.g. repeated "depends").
+
+## Acceptance
+
+1. Connections have no `label`.
+2. No legend `cards`; no meta `subtitle`.
+3. Unit tests assert label-free IR; L0/L1/L3; merge develop.

package/.duaer/specs/198-task-graph-labels/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 198-task-graph-labels
+
+- [x] Brief
+- [x] Strip depends / cards / subtitle from task IR
+- [x] Tests / docs / merge

package/.duaer/specs/199-preview-open-url/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:30:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --test test/chat-markdown.test.mjs test/result-versions.test.mjs",
+      "npm run test:live"
+    ]
+  }
+}

package/.duaer/specs/199-preview-open-url/spec.md

@@ -0,0 +1,16 @@
+# 199 — 打开看看 opens the focused preview URL
+
+## Goal
+
+Result-bar「打开看看」(and the same open path) must open the **currently
+focused** preview URL (`state.lastPreviewUrl`), not always re-resolve the
+latest delivery preview (which can be a different revision or a docs path).
+
+## Acceptance
+
+1. `/api/artifact|result/…` and other same-origin paths open directly.
+2. Public https URLs open directly.
+3. Local `http://localhost:…` still goes through `/api/preview/ensure`, then
+   opens the focused URL when set.
+4. Chat「打开看看」href stays a same-origin `/api/…` path (not a baked host).
+5. L0/L1/L3; merge develop.

package/.duaer/specs/199-preview-open-url/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 199-preview-open-url
+
+- [x] Brief
+- [ ] Fix ensureAndOpenPreview + chatPreviewHref
+- [ ] Tests / docs / merge

package/.duaer/specs/200-preview-start-url/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:35:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --test test/live-preview.test.mjs",
+      "npm run test:live"
+    ]
+  }
+}

package/.duaer/specs/200-preview-start-url/spec.md

@@ -0,0 +1,15 @@
+# 200 — 打开看看 uses project start URL, not docs paths
+
+## Goal
+
+「打开看看」must open the **runnable product** (local service or HTML page),
+never a documentation artifact such as `docs/**/*.md` even when
+`delivery.preview.url` points there.
+
+## Acceptance
+
+1. Relative non-HTML preview paths are ignored for primary open URL.
+2. After an openable delivery path, prefer inferred local service over auto
+   HTML candidates when both exist.
+3. Status `preview` / accepted chat link use that openable URL (not `/api/result/…/*.md`).
+4. Unit + L3; merge develop.

package/.duaer/specs/200-preview-start-url/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 200-preview-start-url
+
+- [x] Brief
+- [x] resolvePreviewPayload + status previewOut prefer start/HTML
+- [x] Tests / docs / merge

package/.duaer/specs/201-arch-fullscreen/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T03:45:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --test test/arch-fullscreen.test.mjs test/task-graph.test.mjs",
+      "npm run test:live"
+    ]
+  }
+}

package/.duaer/specs/201-arch-fullscreen/spec.md

@@ -0,0 +1,15 @@
+# 201 — Architecture click opens fullscreen; keep user-facing hints
+
+## Goal
+
+1. Keep clear user-facing hints (e.g. task-path copy about layout / worker
+   colors) — written for humans, not jargon.
+2. Clicking the system architecture diagram (and task-path diagram) opens the
+   Archify HTML in a **new tab** with `present=1` for a fullscreen view.
+
+## Acceptance
+
+1. Task-graph hint text stays user-facing (HTML fallback matches i18n).
+2. Architecture panel hint mentions click-to-fullscreen when a diagram is shown.
+3. Click on architecture / task-graph mounts opens `/api/architecture/….html?present=1`.
+4. L0/L1/L3; merge develop.

package/.duaer/specs/201-arch-fullscreen/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 201-arch-fullscreen
+
+- [x] Brief
+- [ ] i18n + HTML hints; click → present=1 new tab
+- [ ] Tests / docs / merge

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/spec.md

@@ -0,0 +1,12 @@
+# 202 — Release 0.21.0
+
+## Goal
+
+Ship 0.21.0: bump version + CHANGELOG, promote develop → main, push,
+GitHub Release `v0.21.0`, trigger npm Trusted Publishing.
+
+## Acceptance
+
+1. `package.json` is `0.21.0`; CHANGELOG has `0.21.0` section (Unreleased cleared).
+2. `develop` and `main` pushed with release commits.
+3. GitHub Release `v0.21.0` published; npm publish workflow run succeeds or documented.

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

@@ -0,0 +1,5 @@
+# Tasks — 202-release-021
+
+- [x] Brief
+- [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