duaer-spec 0.24.1 → 0.25.0

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

@@ -45,6 +45,8 @@ 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`)
+- **FDE desk:** only `http://127.0.0.1:8787` (`com.duaer.live8787`). Never start
+  `duaer-live` on another port; do not open Cursor Browser just to check the desk
 - 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

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

@@ -48,6 +48,8 @@ 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`)
+- **FDE desk:** only `http://127.0.0.1:8787` (`com.duaer.live8787`). Never start
+  `duaer-live` on another port; do not open Cursor Browser just to check the desk
 - 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

package/.cursor/rules/fde-8787-only.mdc

@@ -0,0 +1,31 @@
+---
+description: FDE live desk is only http://127.0.0.1:8787 — never alternate ports
+alwaysApply: true
+---
+
+# FDE desk port (8787 only)
+
+The Duaer-spec FDE desk has **one** URL:
+
+`http://127.0.0.1:8787`
+
+Managed by LaunchAgent `com.duaer.live8787`.
+
+## Do
+
+- Check / restart with `launchctl kickstart -k "gui/$(id -u)/com.duaer.live8787"`
+- Verify with `curl -s -o /dev/null -w '%{http_code}\n' http://127.0.0.1:8787/`
+- After merge handoff, restart that LaunchAgent only (see `.duaer/handoff.json`)
+- Open architecture / 派工图 via desk `POST /api/open-external` (OS browser on :8787)
+
+## Do not
+
+- Start `node bin/duaer-live.mjs` on any port other than **8787**
+- Start a second desk when 8787 is already listening
+- Use Cursor Browser / Simple Browser / browser MCP to open the desk or
+  architecture present pages — Cursor proxies those as random high ports
+  (`:62489`, `:64074`, …). That is **not** a second FDE server.
+- Treat product preview ports (3000, 8081, …) as the FDE desk
+
+Interactive `duaer live` may still open the OS browser once; LaunchAgent sets
+`DUAER_LIVE_NO_BROWSER=1` so kickstart does not spam tabs.

package/.duaer/active-job.json

@@ -1 +1,5 @@
-{"feature":"218-release-0241","updatedAt":"2026-09-19T14:11:06.000Z"}
+{
+  "feature": "250-release-025",
+  "specPath": ".duaer/specs/250-release-025/spec.md",
+  "source": "chat"
+}

package/.duaer/handoff.json

@@ -4,8 +4,8 @@
     "stop": "Stop any process whose working directory is under the request worktree (dev servers, file watchers, local APIs). Also stop the FDE desk if it was started from a worktree copy of duaer-live.",
     "restartFromPrimary": true,
     "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)"
+      "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; DUAER_LIVE_NO_BROWSER=1 node bin/duaer-live.mjs --port 8787)"
     ]
   },
-  "notes": "After merge to develop: remove worktree, then restart Duaer-spec FDE (LaunchAgent com.duaer.live8787) so /api/projects and other new routes load from primary checkout."
+  "notes": "FDE desk is ONLY http://127.0.0.1:8787 (com.duaer.live8787). Never start duaer-live on another port. LaunchAgent sets DUAER_LIVE_NO_BROWSER=1 so kickstart does not open new browser tabs. After merge: remove worktree, then kickstart so routes load from primary checkout on develop."
 }

package/.duaer/memory/testing.md

@@ -92,6 +92,23 @@ local **`develop`**:
 A waiver must state: which level, why it cannot run now, and the follow-up.
 “Too slow” alone is not enough if a subset command exists.
 
+## Machine accept gate (live desk)
+
+Product repos that ship through Duaer-spec FDE keep a short contract at
+`.duaer/memory/verify.json`:
+
+```json
+{ "commands": ["npm test"], "timeoutSec": 600 }
+```
+
+When tasks are complete, or an employee writes `delivery.json` `accepted`, the
+desk runs those commands in the worktree. A non-zero exit, or a missing /
+invalid file, sets status back to `open` and stores the command, exit code, and
+output tail on `delivery.verification`. Docs-only work with no commands uses
+`{ "waiver": "docs-only" }`. The first command list is frozen for that dispatch
+so a later waiver cannot replace it. `npx duaer-spec update` does not overwrite
+an existing `verify.json`.
+
 ## Adopter profiles
 
 Thick product examples (e.g. `examples/dianwu-flow/testing.md`) may add L5+

package/.duaer/memory/verify.json

@@ -0,0 +1,4 @@
+{
+  "commands": ["npm test"],
+  "timeoutSec": 600
+}

package/.duaer/specs/218-release-0241/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T14:12:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": ["npm test (177 pass)", "gh release v0.24.1", "npm view duaer-spec version → 0.24.1"],
+    "result": "pass"
+  },
+  "summary": "Released 0.24.1 (Functional regression employee docs) to GitHub and npm."
+}

package/.duaer/specs/218-release-0241/tasks.md

@@ -1,4 +1,4 @@
 # Tasks — 218
 
 - [x] T001 Bump to 0.24.1 and move CHANGELOG
-- [ ] T002 Promote develop → main, tag, GitHub Release, npm
+- [x] T002 Promote develop → main, tag, GitHub Release, npm

package/.duaer/specs/219-verify-gate/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-19T23:10:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["node --check bin/duaer-live.mjs", "npm test (185 pass)"],
+    "result": "pass"
+  },
+  "summary": "Desk runs verify.json before a delivery stamp can stick. Failed or missing contracts reopen accepted."
+}

package/.duaer/specs/219-verify-gate/spec.md

@@ -0,0 +1,26 @@
+# 219 — Machine verify gate
+
+## Goal
+
+The live desk, not the digital employee, decides whether `delivery.json` may stay `accepted`.
+
+## In scope
+
+- Read the product worktree `.duaer/memory/verify.json`.
+- When every task is checked, or the employee writes `accepted`, run `commands` in the worktree.
+- Non-zero exit: set status back to `open`, store command / exit / tail on `delivery.verification`, enqueue the log on the regression lane (last lane when N≥2). Do not nudge “stamp accept”.
+- Exit 0: allow `accepted` and keep the same evidence.
+- Missing or invalid contract: do not accept. Status tells the operator the contract is missing or unreadable.
+- `{ "waiver": "docs-only" }` with no commands passes without a shell. If a command list was already seen, later edits cannot replace it with a waiver.
+- `init` / `update` must not overwrite an existing product `verify.json`.
+
+## Out of scope
+
+- Screen recordings, a second judge model, a new employee role, post-deploy browser checks.
+- Parsing commands out of `testing.md` prose.
+
+## Acceptance
+
+1. A failing command cannot leave the job or deliverables page in the accepted state.
+2. A passing command records the command and exit code on `delivery.json`.
+3. The all-tasks-done “stamp accept” nudge is gone.

package/.duaer/specs/219-verify-gate/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 219
+
+- [x] T001 Desk reopens `accepted` when verify commands fail or the contract is missing
+- [x] T002 Passing commands are stored on `delivery.verification`; stamp nudge is removed
+- [x] T003 Docs, E2E row, and init keep an existing `verify.json`

package/.duaer/specs/220-project-activate-click/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T01:20:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["npm test (185 pass)"],
+    "result": "pass"
+  },
+  "summary": "Project activate click shows drawer errors and the drawer scrolls."
+}

package/.duaer/specs/220-project-activate-click/spec.md

@@ -0,0 +1,15 @@
+# 220 — Project activate click shows feedback
+
+## Goal
+
+Clicking「选为当前项目」always shows a result in the open project drawer.
+
+## Why
+
+Validation only posted a chat bubble behind the drawer, so a missing name or description looked like a dead click. The drawer also clips overflow, so the button can sit below the fold.
+
+## Acceptance
+
+1. Missing path, name, or description shows the message in the drawer (`#historyErr`), not only in chat.
+2. While activate is in flight, the button is disabled.
+3. The project drawer scrolls so the button stays reachable.

package/.duaer/specs/220-project-activate-click/tasks.md

@@ -0,0 +1,4 @@
+# Tasks — 220
+
+- [x] T001 Drawer shows activate errors; button disables while the request runs
+- [x] T002 Project drawer scrolls; E2E row updated

package/.duaer/specs/221-wave-exit-preempt/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T01:25:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check bin/duaer-live.mjs",
+      "node --check bin/live-orchestrate.mjs",
+      "npm test (188 pass)"
+    ],
+    "result": "pass"
+  },
+  "summary": "A finished wave that still holds the Terminal is preempted once the next job is queued."
+}

package/.duaer/specs/221-wave-exit-preempt/spec.md

@@ -0,0 +1,25 @@
+# 221 — Preempt a finished wave so the next job starts
+
+## Goal
+
+After a wave's tasks are checked, the next queued `--continue` starts even if the CLI did not exit.
+
+## Why
+
+The employee prints「本波完成，退出等编排器」and stays in the session. The desk already enqueued the next wave, then refuses to release that fingerprint again. The runner cannot dequeue until the leftover process dies, so the job looks stuck after the first wave.
+
+## In scope
+
+- On status poll, if `running.cmd`'s wave ids are all `[x]` and `queueDepth > 0`, preempt that session.
+- Do not preempt a session whose own wave is still open.
+
+## Out of scope
+
+- Changing task assignment, verify.json, or the personal-intro product job.
+- Killing the Terminal runner itself.
+
+## Acceptance
+
+1. A busy lane whose running script wave is fully checked, with a queued job, is preempted.
+2. A busy lane whose running script wave is still open is not preempted, even if an earlier wave is done and the queue is non-empty.
+3. The decision is covered by unit tests; live-desk docs and the E2E catalog record the behavior.

package/.duaer/specs/221-wave-exit-preempt/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] Preempt a finished wave when the next job is queued
+- [x] Do not preempt a session whose own wave is still open
+- [x] Record the behavior in live-desk docs and the E2E catalog

package/.duaer/specs/222-wave-exit-cat/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T01:32:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["node --check bin/live-orchestrate.mjs", "npm test (188 pass)"],
+    "result": "pass"
+  },
+  "summary": "A queued continue preempts a leftover CLI even when running.cmd only cats the prompt file."
+}

package/.duaer/specs/222-wave-exit-cat/spec.md

@@ -0,0 +1,14 @@
+# 222 — Preempt when the Terminal script does not name its wave
+
+## Goal
+
+A queued continue starts even when `running.cmd` only `cat`s the prompt file.
+
+## Why
+
+The first preempt only fired when `running.cmd` contained `- T00N:` lines. Live jobs store the wave in a prompt file that the next enqueue overwrites, so the desk saw no wave ids and left the leftover CLI in place.
+
+## Acceptance
+
+1. Busy lane, `queueDepth > 0`, and no wave ids in the running script → preempt.
+2. Busy lane whose named wave is still open → do not preempt.

package/.duaer/specs/222-wave-exit-cat/tasks.md

@@ -0,0 +1,4 @@
+# Tasks
+
+- [x] Preempt a waiting queue when the running script has no wave ids
+- [x] Keep the named-open-wave exception

package/.duaer/specs/223-dispatch-center/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T01:45:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["node --check web/live-dev/app.js", "npm test (188 pass)"],
+    "result": "pass"
+  },
+  "summary": "Dispatch center lists projects in a 100px rail and shows the selected project's dispatch graph."
+}

package/.duaer/specs/223-dispatch-center/spec.md

@@ -0,0 +1,16 @@
+# 223 — Dispatch center
+
+## Goal
+
+Open a project's dispatch graph from a top control, not from hidden hint text.
+
+## Why
+
+The line「与系统架构图同一排版…点击图可新页面全屏查看」is not visible on the desk. The graph needs a button and a place that stays on screen.
+
+## Acceptance
+
+1. The top bar has「调度中心」. Opening it hides the three-column desk and shows a two-pane view.
+2. The left pane is 100px wide and lists current projects. Selecting one shows that project's dispatch graph on the right.
+3. The dispatch card no longer shows that hint. A「查看派工图」button opens the center on the current project.
+4. A project with no confirmed tasks shows a short empty line, not the graph.

package/.duaer/specs/223-dispatch-center/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] Top Dispatch center opens a two-pane view
+- [x] Left rail is 100px and lists projects; the right pane shows that project's dispatch graph
+- [x] Dispatch card hint is a button that opens the center on the current project
+- [x] Empty projects show a short empty line

package/.duaer/specs/224-dispatch-center-page/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T02:05:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["node --check web/live-dev/app.js", "node --check web/live-dev/dispatch-center.js", "npm test (188 pass)"],
+    "result": "pass"
+  },
+  "summary": "Dispatch center is a separate page with a 100px project rail and the selected project's graph."
+}

package/.duaer/specs/224-dispatch-center-page/spec.md

@@ -0,0 +1,15 @@
+# 224 — Dispatch center is its own page
+
+## Goal
+
+Dispatch center opens a separate page, not a panel over the desk.
+
+## Why
+
+The first version hid the three-column desk in place. It needs its own page.
+
+## Acceptance
+
+1. The top Dispatch center button and the dispatch-card button each open `/dispatch-center.html` in a new page.
+2. That page has a title, a 100px project rail, and the selected project's dispatch graph.
+3. The desk itself no longer hides behind an in-page overlay.

package/.duaer/specs/224-dispatch-center-page/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] Dispatch center is a standalone page
+- [x] Top button and card button open that page
+- [x] Left rail is 100px; the right pane shows the selected project's graph
+- [x] The desk no longer uses an in-page overlay

package/.duaer/specs/225-wave-retry/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T02:20:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["node --check bin/duaer-live.mjs", "npm test (190 pass)"],
+    "result": "pass"
+  },
+  "summary": "An unchecked released wave is enqueued again when the Terminal lane is idle."
+}

package/.duaer/specs/225-wave-retry/spec.md

@@ -0,0 +1,15 @@
+# 225 — Requeue a lost wave
+
+## Goal
+
+If a released wave is still unchecked and the Terminal lane is idle, enqueue it again.
+
+## Why
+
+T007 was marked released, then the runner died and the queue emptied. The desk refused to release that fingerprint again, so the job looked in progress with nothing queued.
+
+## Acceptance
+
+1. An unchecked task-wave fingerprint is dropped when the lane is not busy and the queue is empty.
+2. A checked wave, and a non-task fingerprint, stay released.
+3. The drop happens before the next wave release, with a cooldown so a just-enqueued job is not duplicated.

package/.duaer/specs/225-wave-retry/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] Drop an unchecked released wave when the lane is idle
+- [x] Keep checked waves and non-task fingerprints
+- [x] Re-release only after a cooldown

package/.duaer/specs/226-progress-pollute/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T02:35:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": ["node --check web/live-dev/app.js", "npm test (190 pass)"],
+    "result": "pass"
+  },
+  "summary": "Status poll ignores stale job responses so a new project does not keep the previous 派工进度."
+}

package/.duaer/specs/226-progress-pollute/spec.md

@@ -0,0 +1,15 @@
+# 226 — Status poll must not paint another project's progress
+
+## Goal
+
+Switching or creating a project must not keep showing the previous project's 派工进度.
+
+## Why
+
+`clearDeskWorkspace` clears the timeline, but an in-flight `/api/status` from the old `jobId` can finish afterward and call `renderProgress`, so the new desk looks polluted until refresh.
+
+## Acceptance
+
+1. After a status poll returns, if `state.jobId` is no longer the job that was requested, do not apply progress, preview, or accepted chat bubbles.
+2. Creating or switching to an empty project still clears the progress column; a stale poll cannot refill it.
+3. Covered by a source marker test; E2E catalog updated.

package/.duaer/specs/226-progress-pollute/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+- [x] Ignore stale status-poll responses when jobId changed
+- [x] Keep empty-project progress clear after switch
+- [x] Update E2E catalog and tests

package/.duaer/specs/227-desk-sqlite/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T02:30:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": [
+      "node --check bin/live-desk-db.mjs",
+      "node --test test/live-desk-db.test.mjs test/live-project-chat.test.mjs (14 pass)",
+      "npm test (195 pass)"
+    ],
+    "result": "pass"
+  },
+  "summary": "Project desk sessions use ~/.duaer/live/desk.sqlite with automatic legacy JSON import and versioned schema migrations on open."
+}

package/.duaer/specs/227-desk-sqlite/spec.md

@@ -0,0 +1,17 @@
+# 227 — Desk project sessions in SQLite
+
+## Goal
+
+Store FDE project desk sessions in SQLite under `~/.duaer/live/desk.sqlite`, with automatic import of legacy JSON and a versioned schema for upgrades.
+
+## Why
+
+Whole-file JSON rewrites for every persist are slow. Users who already have `project-chats/*.json` must keep their data when they install or upgrade duaer-spec.
+
+## Acceptance
+
+1. `readProjectChat` / `writeProjectChat` use SQLite; public API paths stay the same.
+2. On first open of a live root, existing `project-chats/*.json` sessions are imported; re-open does not duplicate.
+3. The database stores `schema_version`; opening a newer duaer-spec runs migrations in order.
+4. `engines.node` requires a Node that ships `node:sqlite`.
+5. Unit tests cover round-trip, JSON import, and schema version.

package/.duaer/specs/227-desk-sqlite/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] Add desk SQLite open + schema_version migrations
+- [x] Import legacy project-chats JSON on first open
+- [x] Route read/writeProjectChat through SQLite
+- [x] ADR + engines bump + tests + docs

package/.duaer/specs/228-desk-sqlite-all/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T02:50:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1"],
+    "commands": [
+      "node --check bin/live-desk-db.mjs bin/duaer-live.mjs",
+      "node --test test/live-desk-db.test.mjs (7 pass)",
+      "npm test (197 pass)"
+    ],
+    "result": "pass"
+  },
+  "summary": "Config, repos, and live jobs join project sessions in desk.sqlite with legacy import; live root remains per-machine and never packaged."
+}

package/.duaer/specs/228-desk-sqlite-all/spec.md

@@ -0,0 +1,30 @@
+# 228 — Desk durable state fully in SQLite
+
+## Goal
+
+Keep all durable FDE live data in `~/.duaer/live/desk.sqlite` (config, repos, jobs, sessions). Architecture HTML stays a regenerable disk cache. Per-machine `~/.duaer/live` is never packaged or published with duaer-spec.
+
+## Why
+
+Sessions alone left config / repos / jobs on JSON and directories. Operators expect one database; install/upgrade must import legacy files automatically. Local desk data must not ship to other users.
+
+## In scope
+
+1. Schema migration v2: `desk_kv` (config, repos) + `jobs` (id + files map).
+2. On open: import legacy `config.json`, `repos.json`, and `jobs/*/…` when missing from the DB; do not delete legacy files.
+3. Runtime read/write for config, repos, and live jobs use SQLite as source of truth; job directories are materialized so existing Brief paths keep working.
+4. Docs/ADR/CHANGELOG/E2E note; unit tests for import + round-trip.
+
+## Out of scope
+
+- Publishing or bundling any user's `~/.duaer/live`
+- Moving `architecture/` HTML into SQLite (regenerable cache)
+- Moving product-repo worktree Briefs (those stay in the product repo)
+
+## Acceptance
+
+1. Config and repos load/save via SQLite; legacy files import once.
+2. Live jobs import and round-trip (job.json / spec.md / tasks.md and other text files under the job dir).
+3. Opening a newer desk runs migration to `DESK_SCHEMA_VERSION` ≥ 2.
+4. Docs state that live data is local-only and never part of the npm package.
+5. Targeted unit tests pass; `npm test` passes.

package/.duaer/specs/228-desk-sqlite-all/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] Schema v2: desk_kv + jobs + legacy import for config/repos/jobs
+- [x] Route config/repos/jobs IO through SQLite (materialize job dirs)
+- [x] Update ADR 002, live-desk docs, CHANGELOG, E2E-172/173
+- [x] Unit tests + npm test; stamp delivery accepted

package/.duaer/specs/229-task-decompose-graph/delivery.json

@@ -0,0 +1,14 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T03:20:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/app.js web/live-dev/task-graph.mjs",
+      "npm test (200 pass)",
+      "npm run test:live (1 pass)"
+    ],
+    "result": "pass"
+  },
+  "summary": "After architecture confirm, decompose atomic tasks with parallel marks, recommend 1–4 workers, and generate the dispatch graph only after count confirm (revise same gate)."
+}

package/.duaer/specs/229-task-decompose-graph/spec.md

@@ -0,0 +1,14 @@
+# 229 — Task decompose → recommend workers → dispatch graph
+
+## Goal
+
+After architecture confirm (and on revise re-confirm), decompose atomic tasks with parallel marks, recommend 1–4 digital employees, and generate the dispatch graph only after the operator confirms the count.
+
+## Acceptance
+
+1. Dispatch panel appears only after architecture is confirmed.
+2. Atomic task list is visible above Digital employees; parallelizable tasks are marked.
+3. System recommends worker count (1–4) from parallel width; user can change it.
+4. Confirm count generates the dispatch graph; graph is gated until then.
+5. Revise path uses the same gate after architecture re-confirm.
+6. Docs/E2E/i18n/tests updated; risk verification passes.

package/.duaer/specs/229-task-decompose-graph/tasks.md

@@ -0,0 +1,6 @@
+# Tasks
+
+- [x] Worktree + Brief 229
+- [x] Gate dispatch on arch confirm; decompose list + parallel chips
+- [x] Recommend workers; confirm generates 派工图; revise path
+- [x] i18n/docs/E2E/tests; stamp; merge develop; handoff

package/.duaer/specs/230-graph-confirm-busy/delivery.json

@@ -0,0 +1,15 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T03:20:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --test test/task-graph.test.mjs test/live-i18n-*.test.mjs (17 pass)",
+      "npm test",
+      "npm run test:live (1 pass)"
+    ],
+    "result": "pass"
+  },
+  "summary": "Confirm-workers button spins while Archify renders the dispatch graph; view enables only after success."
+}

package/.duaer/specs/230-graph-confirm-busy/spec.md

@@ -0,0 +1,13 @@
+# 230 — Confirm workers graph button busy state
+
+## Goal
+
+When the operator clicks「确认人数并生成派工图」, the button shows a spinning/busy state until the dispatch graph is rendered; only then can「查看派工图」be used.
+
+## Acceptance
+
+1. Click starts busy/spinning on the confirm button (disabled, busy label).
+2. Desk POSTs task IR to `/api/architecture/render` and waits for success.
+3. On success: busy ends, `dispatchGraphReady` is true, graph view is enabled.
+4. On failure: busy ends, error shown, graph stays gated.
+5. Tests/docs updated; verification passes.

package/.duaer/specs/230-graph-confirm-busy/tasks.md

@@ -0,0 +1,4 @@
+# Tasks
+
+- [x] Busy/spinning confirm button + async Archify render before graph ready
+- [x] i18n + CSS + source test; stamp; merge develop; handoff

package/.duaer/specs/231-graph-edge-spacing/delivery.json

@@ -0,0 +1,16 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-20T03:25:00.000Z",
+  "verification": {
+    "levels": ["L0", "L1", "L3"],
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --test test/task-graph.test.mjs (13 pass)",
+      "npm test (201 pass)",
+      "npm run test:live (1 pass)",
+      "POST /api/architecture/render with live 34-task pool → 200"
+    ],
+    "result": "pass"
+  },
+  "summary": "Task-pool IR spacing clears Archify 24px edge minimum; render failures show in chat."
+}

package/.duaer/specs/231-graph-edge-spacing/spec.md

@@ -0,0 +1,12 @@
+# 231 — Fix dispatch graph Archify spacing
+
+## Goal
+
+「确认人数并生成派工图」must actually produce a viewable graph. Archify was rejecting task IRs because edges were shorter than 24px after label-driven component growth.
+
+## Acceptance
+
+1. Task-pool IR uses spacing that keeps Archify edge length ≥ 24px for real multi-task pools.
+2. Render failures show in chat (not only a fleeting button flash).
+3. Confirm succeeds against the live mypro session task pool; graph view enables.
+4. Tests cover spacing / render success; merge to develop.