duaer-spec 0.27.1 → 0.27.3

package/.duaer/active-job.json

@@ -1,5 +1,5 @@
 {
-  "feature": "275-release-0271",
-  "branch": "feat/release-0271",
-  "worktree": ".worktree/feat-release-0271"
+  "feature": "291-release-0273",
+  "branch": "chore/release-0273",
+  "worktree": ".worktree/chore-release-0273"
 }

package/.duaer/specs/275-release-0271/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "0.27.1 is on main as v0.27.1, GitHub Release published, npm Trusted Publishing succeeded.",
+  "verification": {
+    "publish": "git push origin main develop v0.27.1 — fast-forward 1d6d164..26ede20",
+    "release": "https://github.com/Duaer/duaer-spec/releases/tag/v0.27.1",
+    "npm": "gh run 35558574069 success — + duaer-spec@0.27.1"
+  }
+}

package/.duaer/specs/275-release-0271/tasks.md

@@ -1,4 +1,4 @@
 # Tasks — 275-release-0271
 
 - [x] Bump 0.27.1 and move changelog notes
-- [ ] Tag v0.27.1 on main and publish the GitHub Release
+- [x] Tag v0.27.1 on main and publish the GitHub Release

package/.duaer/specs/276-fde08-perf-budget/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Feature confirm requires LCP, INP, bundle size, virtualized long lists, a weak-network check, and a large-data check, or a no-page-performance opt-out. A vague speed line fails. Kickoff schedules the budget before implement.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs bin/live-modules.mjs web/live-dev/app.js web/live-dev/perf-budget.mjs — pass",
+    "L1": "npm test — 254 pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/276-fde08-perf-budget/spec.md

@@ -0,0 +1,38 @@
+# Feature Specification: FDE-08 performance budget
+
+## Goal
+
+A feature confirm card cannot pass on a vague speed claim. It must record
+LCP, INP, bundle size, virtualized long lists, a weak-network check, and a
+large-data check. Kickoff schedules that budget before implementation.
+
+## In scope
+
+- Local validate on perfBudget
+- One FDE-08 task per confirmed module that declares page performance,
+  placed before implement and after the env probe, data precheck, and
+  external-dependency board when those exist
+- Hint, placeholder, and chat/accept prompts
+- Explicit opt-out: no page performance requirement
+
+## Out of scope
+
+- Bug desk
+- Running a customer performance lab from the desk
+
+## Assumptions
+
+- The desk records the budget; the digital employee runs the weak-network
+  and large-data checks.
+- 「本模块无页面性能要求」 / "no page performance" skips the six items
+  and the kickoff task.
+- "挺快的" and other vague speed lines fail.
+
+## Acceptance
+
+1. A vague speed line, or a line missing any of the six items, fails
+   local validate
+2. All six present, or the no-page-performance opt-out, passes
+3. Kickoff adds an FDE-08 task before implement when page performance is
+   declared, and skips it on the opt-out
+4. npm test and npm run test:live pass

package/.duaer/specs/276-fde08-perf-budget/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 276-fde08-perf-budget
+
+- [x] Validate the performance budget (LCP, INP, bundle, long list, weak network, large data, or opt-out)
+- [x] Inject an FDE-08 kickoff task before implement
+- [x] Update hints, prompts, docs, and tests

package/.duaer/specs/277-project-dir-reuse/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Create mode refuses when the target project directory already exists. Open from the list or browse still works. Existing folder contents are left untouched.",
+  "verification": {
+    "L0": "node --check bin/live-repo-path.mjs bin/duaer-live.mjs web/live-dev/app.js — pass",
+    "L1": "npm test — pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/277-project-dir-reuse/spec.md

@@ -0,0 +1,31 @@
+# Feature Specification: Refuse reusing an existing project directory on create
+
+## Goal
+
+Creating a new project must not reuse a directory that already exists.
+An existing folder can only be opened from the project list or by browse-open.
+
+## In scope
+
+- `/api/projects/activate` create mode refuses when the target path already exists
+- Create form sends create mode; list click opens without create
+- Clear Chinese error telling the user to rename or open the existing project
+- Unit / smoke coverage
+
+## Out of scope
+
+- Deleting or renaming old project folders
+- Changing how desk sessions are keyed
+
+## Assumptions
+
+- "选为当前项目" on the create form means create when the path is new
+- Clicking an item under 「已有项目」 means open
+- Browse into an existing folder opens it; it does not create over it
+
+## Acceptance
+
+1. Create with a folder name that already exists under the parent returns an error; disk contents are unchanged
+2. Opening the same path from the project list still works
+3. Create with a never-used name still creates the directory
+4. `npm test` and `npm run test:live` pass

package/.duaer/specs/277-project-dir-reuse/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 277-project-dir-reuse
+
+- [x] Refuse create when the target project directory already exists
+- [x] Keep open-from-list / browse-open working for existing paths
+- [x] Add tests, copy, and E2E row

package/.duaer/specs/278-project-create-unique/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Create uses only a short folder name under the product parent. Absolute paths, existing folders, and duplicate project titles are refused. Open from the list or browse still works.",
+  "verification": {
+    "L0": "node --check bin/live-repo-path.mjs bin/duaer-live.mjs — pass",
+    "L1": "npm test — pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/278-project-create-unique/spec.md

@@ -0,0 +1,27 @@
+# Feature Specification: Unique create — short name under parent only
+
+## Goal
+
+Create and open are separate. Creating a project only uses a short folder
+name under the product parent. Absolute paths, duplicate folders, and
+duplicate project titles are refused.
+
+## In scope
+
+- Create mode: short name only, must have parent set, refuse if folder exists
+- Create mode: refuse if an existing project already uses that path or title
+- Open from list / browse still accepts absolute paths
+- Copy and labels match the rule
+
+## Out of scope
+
+- Moving or renaming existing project folders on disk
+- Deleting stale list entries
+
+## Acceptance
+
+1. Create with `/Users/.../pcdemo` fails; asks for a short name under the parent
+2. Create with a short name that already exists on disk or in the project list fails
+3. Create with a title already used by another project fails
+4. Open from the list still works with absolute paths
+5. `npm test` and `npm run test:live` pass

package/.duaer/specs/278-project-create-unique/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 278-project-create-unique
+
+- [x] Create resolves only a short name under the product parent
+- [x] Refuse duplicate folder and duplicate project title on create
+- [x] Update labels, hints, and tests

package/.duaer/specs/279-arch-side-detour/delivery.json

@@ -0,0 +1,8 @@
+{
+  "status": "accepted",
+  "summary": "Corridor-aware Archify edge detours (validated bottom/top/side/gutter) plus vertical labelAt so stacked clean-flow IR renders.",
+  "verification": {
+    "commands": ["node --test test/live-archify.test.mjs"],
+    "result": "16 pass / 0 fail"
+  }
+}

package/.duaer/specs/279-arch-side-detour/spec.md

@@ -0,0 +1,28 @@
+# Feature Specification: Architecture corridor detour for clean-flow
+
+## Goal
+
+When Archify rejects edges that cross unrelated components, auto-routing
+must pick a corridor whose segments stay clear of other boxes — not a
+naive bottom exit through column neighbors, and not a side via whose
+horizontal leg clips co-row nodes. Vertical edge labels must sit in the
+gap between stacked boxes.
+
+## In scope
+
+- `routeCrossingEdges` validates candidate routes (bottom/top wrap, side
+  corridor, gutter wrap) and applies the first clear detour
+- Re-route edges that already have a bad bottom via
+- Vertical edge labels get `labelAt` in the inter-box gap
+- Regression test matching the speaker/editor/store failure
+
+## Out of scope
+
+- Changing Archify itself
+- Full force-directed relayout
+
+## Acceptance
+
+1. The reproduced IR (speaker→editor, store→gen, 初稿/定稿 labels) renders
+2. Existing same-row reverse-edge test still passes
+3. `npm test` live-archify tests pass

package/.duaer/specs/279-arch-side-detour/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 279-arch-side-detour
+
+- [x] Corridor-aware detour for edges that cross unrelated components
+- [x] Place vertical edge labels in the gap (`labelAt`)
+- [x] Regression test + docs

package/.duaer/specs/280-arch-bottom-via-label/delivery.json

@@ -0,0 +1,8 @@
+{
+  "status": "accepted",
+  "summary": "Bottom/top via edge labels pin labelAt on the via corridor so 改稿 no longer overlaps artifact.",
+  "verification": {
+    "commands": ["node --check bin/live-archify.mjs", "node --test test/live-archify.test.mjs"],
+    "result": "17 pass / 0 fail"
+  }
+}

package/.duaer/specs/280-arch-bottom-via-label/spec.md

@@ -0,0 +1,22 @@
+# Feature Specification: Bottom-via edge labels clear mid-row boxes
+
+## Goal
+
+When a same-row edge detours under the floor, its label must stay on the
+via (below) — not be pulled up with `labelDy: -36` onto mid-row components
+such as `artifact`.
+
+## In scope
+
+- `repairEdgeLabelPlacement` pins `labelAt` under bottom vias / above top vias
+- Overlap nudge when an offset mid still hits a box
+- Regression for speaker→revise「改稿」 overlapping artifact
+
+## Out of scope
+
+- Changing Archify itself
+
+## Acceptance
+
+1. Reproduced IR renders via Archify
+2. `node --test test/live-archify.test.mjs` passes

package/.duaer/specs/280-arch-bottom-via-label/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 280-arch-bottom-via-label
+
+- [x] Pin bottom/top via labels with labelAt on the via corridor
+- [x] Regression test for 改稿 / artifact overlap
+- [x] Docs + delivery stamp

package/.duaer/specs/281-release-0272/delivery.json

@@ -0,0 +1,8 @@
+{
+  "status": "accepted",
+  "summary": "Released 0.27.2: architecture clean-flow, project create uniqueness, FDE-08. Tag v0.27.2 published.",
+  "verification": {
+    "commands": ["gh release view v0.27.2"],
+    "result": "GitHub Release published; npm Trusted Publishing via release event"
+  }
+}

package/.duaer/specs/281-release-0272/spec.md

@@ -0,0 +1,13 @@
+# Feature Specification: Release 0.27.2
+
+## Goal
+
+Ship 0.27.2: architecture clean-flow corridor detours, bottom-via label
+placement, unique project create paths, and FDE-08 performance budget.
+Promote develop to main, publish a GitHub Release, and let npm Trusted
+Publishing run.
+
+## Acceptance
+
+1. `package.json` is `0.27.2`; CHANGELOG has `0.27.2` and an empty Unreleased section.
+2. Tag `v0.27.2` is on `main`; GitHub Release is published.

package/.duaer/specs/281-release-0272/tasks.md

@@ -0,0 +1,4 @@
+# Tasks — 281-release-0272
+
+- [x] Bump package.json to 0.27.2 and move CHANGELOG Unreleased
+- [x] Promote develop → main, tag, GitHub Release

package/.duaer/specs/282-dispatch-confirm-lock/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "summary": "After confirm+build, 确认人数并生成派工图 stays locked (chips too) until the dispatch graph is invalidated.",
+  "verification": {
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --test test/task-graph.test.mjs test/live-i18n-common.test.mjs test/live-i18n-ja.test.mjs",
+      "npm run test:live"
+    ],
+    "result": "all pass"
+  }
+}

package/.duaer/specs/282-dispatch-confirm-lock/spec.md

@@ -0,0 +1,26 @@
+# Feature Specification: Lock confirm-workers after dispatch graph
+
+## Goal
+
+After the operator confirms worker count and the dispatch graph builds
+successfully, **确认人数并生成派工图** stays locked so it cannot be
+re-clicked. Worker-count chips lock with it. Unlock only when the graph
+becomes stale (count/decompose/architecture invalidate).
+
+## In scope
+
+- Keep confirm button disabled + locked label when `dispatchGraphReady`
+- Lock worker-count chips while the graph is ready
+- Re-enable when the graph is marked stale or cleared
+- i18n + desk docs + E2E catalog + regression markers
+
+## Out of scope
+
+- Changing how the graph is generated
+- Locking「查看派工图」
+
+## Acceptance
+
+1. After a successful confirm+build, the confirm button is disabled and shows a locked label.
+2. Changing architecture / re-decompose / clearing ready unlocks the button again.
+3. `node --test test/task-graph.test.mjs` and live i18n key parity pass.

package/.duaer/specs/282-dispatch-confirm-lock/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 282-dispatch-confirm-lock
+
+- [x] Lock confirm button + worker chips when dispatchGraphReady
+- [x] Unlock on stale / arch invalidate; sync on project restore
+- [x] i18n + docs + tests

package/.duaer/specs/283-desk-theme-compact/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "summary": "Compact FDE desk with calm slate light/dark themes and a persistent top-bar toggle.",
+  "verification": {
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --test test/desk-theme.test.mjs test/live-i18n-common.test.mjs test/live-i18n-ja.test.mjs",
+      "npm run test:live"
+    ],
+    "result": "all pass"
+  }
+}

package/.duaer/specs/283-desk-theme-compact/spec.md

@@ -0,0 +1,26 @@
+# Feature Specification: Compact desk theme with light/dark toggle
+
+## Goal
+
+Make the FDE desk easier to stare at for long sessions: tighter spacing,
+calmer colors (less orange glow / hatch noise), and a light/dark theme
+toggle that persists.
+
+## In scope
+
+- Compact shell / header / layout / panel spacing
+- Soft dark + light palettes via `html[data-theme]`
+- Top-bar theme toggle; persist in `localStorage`; early boot to avoid flash
+- Same theme on dispatch-center page
+- i18n + docs + smoke markers
+
+## Out of scope
+
+- Redesigning Archify diagram chrome
+- Per-project theme overrides
+
+## Acceptance
+
+1. Desk feels denser (smaller brand, tighter gaps/padding).
+2. Light and dark themes both readable; toggle switches and persists across reload.
+3. `npm run test:live` and i18n key parity pass.

package/.duaer/specs/283-desk-theme-compact/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 283-desk-theme-compact
+
+- [x] CSS: compact density + light/dark palettes
+- [x] Theme toggle + persist + dispatch-center wire
+- [x] i18n + docs + tests

package/.duaer/specs/284-dispatch-graph-regen/delivery.json

@@ -0,0 +1,12 @@
+{
+  "status": "accepted",
+  "summary": "Each architecture/improve wave forces a fresh 派工图; confirm button shows regenerate when rebuilding; stale clears old URL.",
+  "verification": {
+    "commands": [
+      "node --check web/live-dev/app.js",
+      "node --test test/task-graph.test.mjs test/live-i18n-common.test.mjs test/live-i18n-ja.test.mjs",
+      "npm run test:live"
+    ],
+    "result": "all pass"
+  }
+}

package/.duaer/specs/284-dispatch-graph-regen/spec.md

@@ -0,0 +1,33 @@
+# Feature Specification: Regenerate dispatch graph each wave
+
+## Goal
+
+Every kickoff wave (first delivery and each **改进**) must build a **new**
+派工图. Confirm/lock buttons follow the operator flow: unlock and ask to
+regenerate when the wave changes; stay locked only for the current ready graph.
+
+## Findings (current gaps)
+
+1. `showDispatchPanel` reuses an old `taskPool` after architecture confirm and
+   does not force a fresh decompose / clear graph URL.
+2. `enterReviseMode` (再改一版) does not clear graph ready/URL/pool.
+3. `markDispatchGraphStale` leaves `dispatchGraphUrl` pointing at an old file.
+4. Button copy does not distinguish first confirm vs regenerate after stale.
+
+## In scope
+
+- Reset + redecompose on architecture confirm and revise entry
+- Clear URL on stale/invalidate; sync chips/button
+- Button labels: confirm / regenerate / locked
+- Docs + tests
+
+## Out of scope
+
+- Changing Archify render pipeline internals
+
+## Acceptance
+
+1. After「再改一版」→ plan → architecture confirm, confirm-workers is unlocked
+   and builds a new graph (new URL); old ready state is not reused.
+2. Stale / re-decompose / baseline open-change unlocks and prompts regenerate.
+3. `node --test` markers and live smoke pass.

package/.duaer/specs/284-dispatch-graph-regen/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 284-dispatch-graph-regen
+
+- [x] Central resetDispatchGraphForNewWave; call from arch confirm / revise / baseline
+- [x] showDispatchPanel always fresh pool after arch confirm; clear URL on stale
+- [x] Button labels confirm / regen / locked + i18n + tests

package/.duaer/specs/285-desk-light-compact/delivery.json

@@ -0,0 +1,11 @@
+{
+  "status": "accepted",
+  "summary": "Light theme uses shared tokens for inputs/composer/bubbles; denser compact spacing.",
+  "verification": {
+    "commands": [
+      "node --test test/desk-theme.test.mjs",
+      "npm run test:live"
+    ],
+    "result": "all pass"
+  }
+}

package/.duaer/specs/285-desk-light-compact/spec.md

@@ -0,0 +1,13 @@
+# Feature Specification: Light theme contrast + denser compact
+
+## Goal
+
+Fix unreadable black/dark hardcodes in light theme and tighten desk density
+another step.
+
+## Acceptance
+
+1. Light theme inputs, composer, chat bubbles, and primary/confirm buttons
+   use theme tokens and stay readable.
+2. Shell spacing is tighter than the previous compact pass.
+3. `node --test test/desk-theme.test.mjs` and `npm run test:live` pass.

package/.duaer/specs/285-desk-light-compact/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 285-desk-light-compact
+
+- [x] Replace dark hardcodes with theme tokens; improve light contrast
+- [x] Tighten compact spacing tokens
+- [x] Docs + tests + delivery

package/.duaer/specs/286-modules-bug-theme/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-23T09:45:00.000Z",
+  "verification": {
+    "L0": "node --check web/live-dev/app.js bin/live-modules.mjs web/live-dev/task-graph.mjs",
+    "L1": "npm test (pass)",
+    "L3": "npm run test:live (pass)"
+  },
+  "summary": "Bug path appends defect tab without wiping modules; light theme inset tokens; bug pool prefers id=bug."
+}

package/.duaer/specs/286-modules-bug-theme/spec.md

@@ -0,0 +1,26 @@
+# Feature Specification: Keep modules clickable during bug + theme leftovers
+
+## Goal
+
+After「改缺陷」, prior requirement module tabs must stay visible and clickable
+(view). Fix remaining light-theme dark overlays that still look wrong.
+
+## Cause
+
+`enterDeskKind("bug")` / `beginBugFixFromCta` replaced `state.modules` with a
+single bug card, and `renderModuleTabs` hid tabs when `deskKind === "bug"`.
+
+## In scope
+
+- Preserve feature modules; append/select a `bug` module instead of wiping
+- Show module tabs in bug mode; feature tabs viewable (readonly when confirmed)
+- Theme: replace leftover `rgba(8,14,20,…)` wells with tokens
+- Docs + tests
+
+## Acceptance
+
+1. After starting a defect from a multi-module feature project, prior module
+   tabs remain and switching shows that module's card (readonly if confirmed).
+2. Bug module is editable; confirming the defect does not delete feature modules.
+3. Light theme no longer uses fixed near-black overlay fills on wells.
+4. Targeted tests pass.

package/.duaer/specs/286-modules-bug-theme/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 286-modules-bug-theme
+
+- [x] Preserve modules on bug entry; show tabs; chat merge keeps features
+- [x] Theme overlay leftovers → tokens
+- [x] Tests + docs + delivery

package/.duaer/specs/287-progress-modules-ux/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-23T09:55:00.000Z",
+  "verification": {
+    "L0": "node --check web/live-dev/app.js bin/duaer-live.mjs bin/live-modules.mjs",
+    "L1": "npm test (pass)",
+    "L3": "npm run test:live (pass)"
+  },
+  "summary": "Bug confirm merges modules so prior tabs survive; progress run-blocks use inset tokens; denser desk spacing."
+}

package/.duaer/specs/287-progress-modules-ux/spec.md

@@ -0,0 +1,31 @@
+# Feature Specification: Progress theme + bug modules survive confirm
+
+## Goal
+
+Light theme「派工进度」must not look dark. Desk denser / smoother. After
+entering defect path (and after confirming the defect), prior requirement
+module tabs must stay visible.
+
+## Cause
+
+`/api/confirm` (bug) returned a one-item `modules` list (`bug` only). Client
+`applyConfirmSuccess` replaced `state.modules`, wiping feature tabs. Progress
+`.run-block` still used fixed dark `rgba(26,40,54,…)` fills.
+
+## In scope
+
+- Server + client: bug confirm merges into existing modules (keep features)
+- Progress column theme tokens + denser spacing / smoother scroll feel
+- Docs + tests (E2E catalog)
+
+## Out of scope
+
+- Changing bug task pool shape or hotfix branch rules
+
+## Acceptance
+
+1. Enter「改缺陷」with ≥1 prior module → tabs show prior + bug; after confirm
+   defect, prior tabs remain.
+2. Light theme progress run blocks / meters use theme inset tokens (no near-black
+   hardcodes).
+3. Progress column padding/gaps tighter than pre-fix; targeted tests pass.

package/.duaer/specs/287-progress-modules-ux/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 287-progress-modules-ux
+
+- [x] Bug confirm merge keeps feature modules (API + client)
+- [x] Progress column theme + denser compact
+- [x] Tests + docs + delivery + merge handoff

package/.duaer/specs/288-settings-close-compact/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-23T10:05:00.000Z",
+  "verification": {
+    "L0": "node --check web/live-dev/app.js",
+    "L1": "npm test (pass)",
+    "L3": "npm run test:live (pass)"
+  },
+  "summary": "Settings closes without ready gate; gear reopen keeps ready; denser drawers/shell."
+}

package/.duaer/specs/288-settings-close-compact/spec.md

@@ -0,0 +1,17 @@
+# Feature Specification: Settings always closable + denser desk
+
+## Goal
+
+Settings drawer must close via 关闭 / backdrop / gear toggle / Escape even when
+the model is not configured. Make drawers and shell denser.
+
+## Cause
+
+Close handlers gated on `state.ready`; gear toggle only closes when ready.
+Escape did not dismiss drawers.
+
+## Acceptance
+
+1. Settings closes without `state.ready` (button, backdrop, gear, Escape).
+2. Drawers and shell spacing tighter than pre-fix.
+3. Targeted tests pass.

package/.duaer/specs/288-settings-close-compact/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 288-settings-close-compact
+
+- [x] Remove ready gate on settings close; Escape closes drawers
+- [x] Densify drawers + shell tokens
+- [x] Tests + docs + delivery + merge

package/.duaer/specs/289-settings-close-click/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-23T10:35:00.000Z",
+  "verification": {
+    "L0": "node --check web/live-dev/app.js",
+    "L1": "npm test (pass)",
+    "L3": "npm run test:live (pass)"
+  },
+  "summary": "Cache-bust app.js/styles.css; harden Settings close with closeSettingsDrawer + capture listener."
+}

package/.duaer/specs/289-settings-close-click/spec.md

@@ -0,0 +1,16 @@
+# Feature Specification: Settings close click must work
+
+## Goal
+
+The Settings「关闭」button must dismiss the drawer on click.
+
+## Cause
+
+Close was gated on `state.ready` in older builds; `app.js?v=perf-budget-1`
+cache kept serving that gate after the logic fix.
+
+## Acceptance
+
+1. Clicking「关闭」hides `#settingsPanel` (with or without model ready).
+2. Cache-bust query on `app.js` / `styles.css` so operators get the fix.
+3. Tests assert no ready-gate and bumped asset version.