duaer-spec 0.26.0 → 0.27.1

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

@@ -50,6 +50,8 @@ cd .worktree/feat-login
 - 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
+- Version: fast iteration bumps the **patch** (`0.27.1`, `0.27.2`, …). Next
+  after `0.27.1` is `0.27.2`. Do not bump the minor on every ship.
 - English docs: no Chinese (CJK); Chinese docs may include English terms
 
 ## GitHub issue / PR intake

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

@@ -33,6 +33,7 @@ For new behavior, fixes, refactors that change product behavior, or architecture
    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.
+   Version bump is the patch (`0.27.2` next).
 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

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

@@ -53,6 +53,8 @@ cd .worktree/feat-login
 - 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
+- Version: fast iteration bumps the **patch** (`0.27.1`, `0.27.2`, …). Next
+  after `0.27.1` is `0.27.2`. Do not bump the minor on every ship.
 - English docs: no Chinese (CJK); Chinese docs may include English terms
 
 ## GitHub issue / PR intake

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

@@ -37,6 +37,7 @@ For new behavior, fixes, refactors that change product behavior, or architecture
    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.
+   Version bump is the patch (`0.27.2` next).
 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

package/.duaer/active-job.json

@@ -1,5 +1,5 @@
 {
-  "feature": "260-release-026",
-  "branch": "feat/release-026",
-  "worktree": ".worktree/feat-release-026"
+  "feature": "275-release-0271",
+  "branch": "feat/release-0271",
+  "worktree": ".worktree/feat-release-0271"
 }

package/.duaer/specs/260-release-026/delivery.json

@@ -1,18 +1,19 @@
 {
   "status": "accepted",
-  "acceptedAt": "2026-09-20T13:33:00.000Z",
+  "acceptedAt": "2026-09-20T14:14:57.110Z",
   "verification": {
-    "levels": ["docs"],
+    "levels": [
+      "docs"
+    ],
     "commands": [
-      "git push origin develop main",
-      "gh release create v0.26.0",
-      "gh run view 35513791762"
+      "gh workflow run npm-publish.yml --ref main",
+      "npm view duaer-spec version"
     ],
-    "result": "partial",
-    "notes": "GitHub Release v0.26.0 on main. npm Trusted Publishing failed: GitHub Actions account locked (billing). Re-run workflow npm-publish.yml after billing is cleared."
+    "result": "pass",
+    "notes": "npm duaer-spec@0.26.0 published via Trusted Publishing after Duaer repo URL fix"
   },
   "preview": {
-    "url": "https://github.com/Duaer/duaer-spec/releases/tag/v0.26.0",
-    "label": "GitHub Release v0.26.0"
+    "url": "https://www.npmjs.com/package/duaer-spec/v/0.26.0",
+    "label": "npm duaer-spec@0.26.0"
   }
 }

package/.duaer/specs/260-release-026/tasks.md

@@ -1,5 +1,3 @@
-# Tasks: Release 0.26.0
-
 - [x] T001 Bump package.json to 0.26.0 and fold CHANGELOG
 - [x] T002 Merge develop, promote main, push, GitHub release
-- [x] T003 Stamp delivery.json (npm blocked: Actions billing lock — re-run npm-publish.yml after unlock)
+- [x] T003 npm 0.26.0 published (Trusted Publishing + Duaer provenance URL)

package/.duaer/specs/261-fde-baseline-sign/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-21T00:20:00.000Z",
+  "summary": "FDE-01: confirm card baseline fields, signed fingerprint gate before kickoff, change order + deliverables.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs web/live-dev/app.js web/live-dev/baseline.mjs bin/live-modules.mjs — pass",
+    "L1": "npm test — 225 pass (incl. baseline-sign)",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/261-fde-baseline-sign/spec.md

@@ -0,0 +1,37 @@
+# Feature Specification: FDE-01 scope + acceptance baseline sign gate
+
+## Goal
+
+Enforce a signed scope/acceptance baseline before kickoff (联调), per WeCom
+FDE pain FDE-01: no unsigned baseline may enter dispatch; post-sign scope
+changes require an explicit change order and re-sign.
+
+## In scope
+
+- Confirm card fields: device matrix, critical paths, exception cases (feature)
+- Project baseline sign (signer + time + fingerprint of confirmed modules)
+- Kickoff / dispatch hard-blocked until baseline signed and fingerprint matches
+- Change order: reason → unlock modules for re-confirm → clear sign → re-sign
+- Deliverables page shows baseline + change history
+- Docs / E2E / tests
+
+## Out of scope
+
+- Real e-sign / PKI
+- Automatic schedule recalculation
+- Cloud browser matrix execution
+- Full RACI (FDE-10)
+
+## Acceptance
+
+1. Feature confirm without device matrix / critical paths / exception cases fails local validate
+2. Unsigned baseline: 「写入 Brief 并启动」disabled or blocked with clear copy
+3. After sign, kickoff allowed when fingerprint matches confirmed modules
+4. Opening a change order with a reason clears the sign and returns modules to re-confirm
+5. Deliverables HTML shows signer, signed time, and change reasons when present
+6. `npm test` and `npm run test:live` pass
+
+## Assumptions
+
+- Bug desk skips the three new field requirements but still needs baseline sign before dispatch
+- Worktree: `.worktree/feat-fde-baseline-sign` · Brief: `.duaer/specs/261-fde-baseline-sign/`

package/.duaer/specs/261-fde-baseline-sign/tasks.md

@@ -0,0 +1,8 @@
+# Tasks: FDE-01 baseline sign
+
+- [x] T001 Clip card + session baseline helpers (`baseline.mjs` / modules / chat)
+- [x] T002 Confirm card UI fields + i18n (device / paths / exceptions)
+- [x] T003 Baseline sign + change-order UI in dispatch; gate doDispatch
+- [x] T004 Server validate + dispatch reject unsigned / stale fingerprint
+- [x] T005 Deliverables page + live-desk / E2E / CHANGELOG
+- [x] T006 L0/L1/L3 verify; stamp delivery

package/.duaer/specs/262-fde01-readme-docs/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-21T00:25:00.000Z",
+  "summary": "Document FDE-01 baseline sign in README zh-CN and en.",
+  "verification": {
+    "waiver": "docs-only",
+    "note": "README + CHANGELOG only; CJK scan on README.md clean"
+  }
+}

package/.duaer/specs/262-fde01-readme-docs/spec.md

@@ -0,0 +1,23 @@
+# Feature Specification: Document FDE-01 in README
+
+## Goal
+
+Update user-facing README (zh-CN + en) so FDE-01 baseline fields and sign
+gate match the live console.
+
+## In scope
+
+- `README.zh-CN.md` and `README.md` capability bullets + FDE flow steps
+- Brief / delivery stamp
+
+## Out of scope
+
+- Product code / i18n / ADR
+- Push / release
+
+## Acceptance
+
+1. zh-CN README mentions device matrix / critical paths / exception cases on feature confirm
+2. Both READMEs mention signed baseline before kickoff and change-order re-sign
+3. English README has no CJK
+4. Docs-only waiver in delivery verification

package/.duaer/specs/262-fde01-readme-docs/tasks.md

@@ -0,0 +1,5 @@
+# Tasks: Document FDE-01 in README
+
+- [x] T001 Update README.zh-CN.md capability + flow
+- [x] T002 Update README.md capability + flow
+- [x] T003 Stamp delivery (docs-only waiver)

package/.duaer/specs/263-arch-edge-via/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-21T00:35:00.000Z",
+  "summary": "Auto-detour architecture edges that would fail Archify clean-flow/edge-through-node.",
+  "verification": {
+    "L0": "node --check bin/live-archify.mjs — pass",
+    "L1": "node --test test/live-archify.test.mjs — 14 pass"
+  }
+}

package/.duaer/specs/263-arch-edge-via/spec.md

@@ -0,0 +1,25 @@
+# Feature Specification: Auto-route architecture edges that cross nodes
+
+## Goal
+
+When Archify rejects architecture IR with `clean-flow/edge-through-node`
+(long same-row reverse edges from LLM layout), duaer-live auto-detours those
+edges with `fromSide`/`toSide`/`via` so render succeeds.
+
+## In scope
+
+- `routeCrossingEdges` in `bin/live-archify.mjs` (called from layout)
+- Unit test using the failing PPT IR (state→gen)
+- CHANGELOG / brief note in live-desk if needed
+
+## Out of scope
+
+- Changing Archify itself
+- Relayouting all LLM positions from scratch
+- Showcase quality profile
+
+## Acceptance
+
+1. Saved IR `state`→`gen` (crosses user/ui/check/doc) renders via Archify without error
+2. Neighbor edges without intermediates keep no forced via
+3. `npm test` live-archify tests pass

package/.duaer/specs/263-arch-edge-via/tasks.md

@@ -0,0 +1,5 @@
+# Tasks: Auto-route crossing architecture edges
+
+- [x] T001 Implement `routeCrossingEdges` + wire into layout / viewBox
+- [x] T002 Unit test for PPT IR state→gen case
+- [x] T003 CHANGELOG; verify; stamp delivery

package/.duaer/specs/264-baseline-field-guide/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-21T00:40:00.000Z",
+  "summary": "Guide chat and placeholders to fill FDE-01 baseline confirm fields.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs web/live-dev/app.js — pass",
+    "L1": "node --test test/live-i18n-common.test.mjs — pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/264-baseline-field-guide/spec.md

@@ -0,0 +1,23 @@
+# Feature Specification: Guide filling FDE-01 baseline fields
+
+## Goal
+
+Chat and confirm UX must guide (and preferably fill) device matrix, critical
+paths, and exception cases — not leave them as empty「待确认」forever.
+
+## In scope
+
+- Feature SYSTEM / ACCEPT / FIX / REVISE prompts include the three fields
+- Field-specific placeholders (examples) in UI + i18n
+- Smoke assert prompts mention the fields
+
+## Out of scope
+
+- Bug desk (still skips the three fields)
+- Changing validate rules
+
+## Acceptance
+
+1. `SYSTEM_PROMPT` / accept / fix prompts list `deviceMatrix` / `criticalPaths` / `exceptionCases`
+2. Feature confirm textareas use example placeholders (not bare「待确认」)
+3. `npm test` + `npm run test:live` pass

package/.duaer/specs/264-baseline-field-guide/tasks.md

@@ -0,0 +1,5 @@
+# Tasks: Guide filling FDE-01 baseline fields
+
+- [x] T001 Update chat / accept / fix / revise prompts
+- [x] T002 Per-field placeholders + i18n locales
+- [x] T003 Smoke assert; stamp delivery

package/.duaer/specs/265-baseline-chat-passthrough/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-21T00:45:00.000Z",
+  "summary": "Pass deviceMatrix/criticalPaths/exceptionCases through chat parse and SSE done.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs — pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/265-baseline-chat-passthrough/spec.md

@@ -0,0 +1,22 @@
+# Feature Specification: Pass baseline fields through chat parse/SSE
+
+## Goal
+
+When the model returns deviceMatrix / criticalPaths / exceptionCases in chat
+JSON, they must reach the middle confirm card (not be stripped by
+parseChatResult / chatDoneSsePayload).
+
+## In scope
+
+- parseChatResult + chatDoneSsePayload passthrough (top-level + modules[])
+- Unit / smoke coverage
+
+## Out of scope
+
+- Prompt wording (already done in 264)
+
+## Acceptance
+
+1. Parsed chat JSON with baseline fields retains them in the done payload shape
+2. Middle card merge path receives the three keys from SSE done
+3. `npm run test:live` + targeted unit pass

package/.duaer/specs/265-baseline-chat-passthrough/tasks.md

@@ -0,0 +1,4 @@
+# Tasks: Pass baseline fields through chat parse/SSE
+
+- [x] T001 Fix parseChatResult + chatDoneSsePayload
+- [x] T002 Unit test; smoke marker; stamp delivery

package/.duaer/specs/266-fde02-api-contract/delivery.json

@@ -0,0 +1,10 @@
+{
+  "status": "accepted",
+  "acceptedAt": "2026-09-21T00:55:00.000Z",
+  "summary": "FDE-02: apiContract confirm field, validate gate, kickoff contract tasks, deliverables.",
+  "verification": {
+    "L0": "node --check — pass",
+    "L1": "npm test — pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/266-fde02-api-contract/spec.md

@@ -0,0 +1,28 @@
+# Feature Specification: FDE-02 API contract gate
+
+## Goal
+
+Enforce an API contract declaration on feature confirm cards (OpenAPI/types
+path, or explicit「本模块无 HTTP API」). When HTTP APIs are in scope, kickoff
+injects contract sync / Mock / CI contract-test tasks so联调不再追字段.
+
+## In scope
+
+- Confirm card field `apiContract` + validate / chat prompts / SSE passthrough
+- Fingerprint includes the field
+- Task pool injects FDE-02 shared tasks when any module declares a contract path
+- Deliverables show the field
+- Docs / E2E / tests
+
+## Out of scope
+
+- Built-in OpenAPI editor, codegen, or running customer CI
+- Bug desk (skips field like other FDE-01 extras)
+
+## Acceptance
+
+1. Feature confirm without apiContract fails local validate
+2. 「本模块无 HTTP API」passes without injecting contract tasks
+3. A path like `openapi/openapi.yaml` injects three shared pool tasks
+4. Chat SSE / clip / deliverables carry the field
+5. `npm test` + `npm run test:live` pass

package/.duaer/specs/266-fde02-api-contract/tasks.md

@@ -0,0 +1,7 @@
+# Tasks: FDE-02 API contract gate
+
+- [x] T001 `api-contract.mjs` + clipCard / fingerprint / localAccept
+- [x] T002 Chat prompts + parseChatResult / SSE passthrough
+- [x] T003 UI + i18n placeholders; app.js merge/apply
+- [x] T004 Task pool inject + deliverables
+- [x] T005 Tests / docs / CHANGELOG; stamp delivery

package/.duaer/specs/267-baseline-restore/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Desk refresh restores device matrix, critical paths, exception cases, and API contract onto the confirm card.",
+  "verification": {
+    "L0": "node --check web/live-dev/app.js web/live-dev/confirm-card.mjs — pass",
+    "L1": "npm test — 234 pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/267-baseline-restore/spec.md

@@ -0,0 +1,24 @@
+# Feature Specification: Keep baseline fields after desk refresh
+
+## Goal
+
+Refreshing the Duaer console must keep the four feature confirm fields
+(device matrix, critical paths, exception cases, API contract) that were
+already on the card.
+
+## In scope
+
+- Session restore copies those four fields onto each module card before the
+  form is filled
+- Confirm fingerprint includes `apiContract` so a later edit re-validates
+
+## Out of scope
+
+- Bug desk (those fields stay hidden)
+- Changing validate rules
+
+## Acceptance
+
+1. Restoring a saved module card keeps deviceMatrix, criticalPaths,
+   exceptionCases, and apiContract
+2. `npm test` and `npm run test:live` pass

package/.duaer/specs/267-baseline-restore/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 267-baseline-restore
+
+- [x] Restore the four baseline fields when loading a saved desk session
+- [x] Include apiContract in the confirm fingerprint
+- [x] Tests, merge develop, handoff

package/.duaer/specs/268-fde07-uat/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Feature confirm requires a UAT pack (empty, failure, permission, timeout, retry) and kickoff schedules those checks.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs bin/live-modules.mjs web/live-dev/app.js — pass",
+    "L1": "npm test — 237 pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/268-fde07-uat/spec.md

@@ -0,0 +1,30 @@
+# Feature Specification: FDE-07 UAT pack on confirm
+
+## Goal
+
+Feature confirm must not treat a single happy-path note as acceptance.
+Exception cases have to cover the UAT pack, and kickoff must schedule
+those checks.
+
+## In scope
+
+- Local validate requires empty, failure, permission, timeout, and retry
+- When the module declares an API contract path, exception text must name
+  an error code or HTTP status
+- Kickoff adds a UAT task per confirmed module, plus a contract error-code
+  task when a path is declared
+- Confirm hints, placeholders, and chat/accept prompts match the pack
+
+## Out of scope
+
+- Bug desk
+- Running the UAT cases against a customer environment
+
+## Acceptance
+
+1. A feature card that only mentions one exception class fails local validate
+2. A card covering the five classes passes that check; a contract path also
+   needs an error code or status
+3. Confirmed modules get an FDE-07 UAT task; no-HTTP modules skip the
+   error-code task
+4. `npm test` and `npm run test:live` pass

package/.duaer/specs/268-fde07-uat/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 268-fde07-uat
+
+- [x] Validate exception cases against the UAT pack
+- [x] Inject FDE-07 kickoff tasks
+- [x] Update hints, prompts, docs, and tests

package/.duaer/specs/269-release-027/spec.md

@@ -0,0 +1,12 @@
+# Feature Specification: Release 0.27.0
+
+## Goal
+
+Ship 0.27.0: FDE-01 signed baseline, FDE-02 API contract gate, FDE-07 UAT
+pack, baseline field restore, architecture edge detour. Promote develop to
+main, publish a GitHub Release, and let npm Trusted Publishing run.
+
+## Acceptance
+
+1. `package.json` is `0.27.0`; CHANGELOG has `0.27.0` and an empty Unreleased section.
+2. Tag `v0.27.0` is on `main`; GitHub Release is published.

package/.duaer/specs/269-release-027/tasks.md

@@ -0,0 +1,4 @@
+# Tasks — 269-release-027
+
+- [x] Bump 0.27.0 and move changelog notes
+- [ ] Promote develop to main, tag, GitHub Release

package/.duaer/specs/270-patch-version/delivery.json

@@ -0,0 +1,7 @@
+{
+  "status": "accepted",
+  "summary": "Fast iteration ships as patch versions. Next release after 0.27.0 is 0.27.1.",
+  "verification": {
+    "docs": "Policy only; no runtime change. testing.md docs waiver."
+  }
+}

package/.duaer/specs/270-patch-version/spec.md

@@ -0,0 +1,19 @@
+# Feature Specification: Patch versions for fast iteration
+
+## Goal
+
+Ships after 0.27.0 increment the patch number. The next release is 0.27.1.
+
+## In scope
+
+- Release docs and agent rules state the default bump is the last number
+
+## Out of scope
+
+- Cutting 0.27.1 now
+- Changing npm or GitHub release automation
+
+## Acceptance
+
+1. Branching docs say 0.27.0 is followed by 0.27.1, not 0.28.0
+2. Agent rules repeat that patch bump

package/.duaer/specs/270-patch-version/tasks.md

@@ -0,0 +1,4 @@
+# Tasks — 270-patch-version
+
+- [x] Document patch bumps (next release 0.27.1)
+- [x] Repeat the rule in agent workflow files

package/.duaer/specs/271-fde04-compat/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Feature device matrix must name two targets, evidence, and a fallback; kickoff schedules the compat check.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs bin/live-modules.mjs — pass",
+    "L1": "npm test — 239 pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/271-fde04-compat/spec.md

@@ -0,0 +1,25 @@
+# Feature Specification: FDE-04 browser matrix evidence
+
+## Goal
+
+A feature confirm card cannot pass with a vague browser line. The device
+matrix must name real targets, point at evidence, and state a fallback.
+Kickoff schedules that check.
+
+## In scope
+
+- Local validate on deviceMatrix
+- One FDE-04 task per confirmed module
+- Hint, placeholder, and chat/accept prompts
+
+## Out of scope
+
+- Bug desk
+- Running a device lab
+
+## Acceptance
+
+1. "主流浏览器" or a single browser name fails local validate
+2. Two named targets plus screenshot/cloud evidence plus a fallback passes
+3. Kickoff adds an FDE-04 compat evidence task
+4. npm test and npm run test:live pass

package/.duaer/specs/271-fde04-compat/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 271-fde04-compat
+
+- [x] Validate the browser matrix as evidence
+- [x] Inject an FDE-04 kickoff task
+- [x] Update hints, prompts, docs, and tests

package/.duaer/specs/272-fde03-env-check/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Feature confirm requires a passed DNS/TLS/CORS/auth/third-party checklist, or a no-customer opt-out. Kickoff schedules the probe before implement.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs bin/live-modules.mjs web/live-dev/app.js web/live-dev/env-check.mjs — pass",
+    "L1": "npm test — 242 pass",
+    "L3": "npm run test:live — pass"
+  }
+}

package/.duaer/specs/272-fde03-env-check/spec.md

@@ -0,0 +1,34 @@
+# Feature Specification: FDE-03 environment checklist
+
+## Goal
+
+A feature confirm card cannot pass until the environment checklist records
+DNS, TLS, CORS, auth, and third-party reachability as passed. A failed probe
+blocks confirm. Kickoff schedules that probe before implementation.
+
+## In scope
+
+- Local validate on envChecklist
+- One FDE-03 task per confirmed module that declares a customer environment,
+  placed before that module's implement task
+- Hint, placeholder, and chat/accept prompts
+- Explicit opt-out: no customer environment
+
+## Out of scope
+
+- Bug desk
+- Scanning the customer network from the desk
+
+## Assumptions
+
+- The desk records the checklist; the digital employee runs the probes.
+- 「无客户联调环境」 / "no customer environment" skips the five probes and
+  the kickoff task.
+
+## Acceptance
+
+1. A vague line, a missing probe, or any failed probe fails local validate
+2. All five probes marked passed, or the no-customer opt-out, passes
+3. Kickoff adds an FDE-03 env probe before implement when a customer
+   environment is declared, and skips it on the opt-out
+4. npm test and npm run test:live pass

package/.duaer/specs/272-fde03-env-check/tasks.md

@@ -0,0 +1,5 @@
+# Tasks — 272-fde03-env-check
+
+- [x] Validate the environment checklist (five probes passed, or no-customer opt-out)
+- [x] Inject an FDE-03 kickoff task before implement
+- [x] Update hints, prompts, docs, and tests

package/.duaer/specs/273-fde06-data-precheck/delivery.json

@@ -0,0 +1,9 @@
+{
+  "status": "accepted",
+  "summary": "Feature confirm requires a field mapping, an import failure list, and an export, or a no-import opt-out. Kickoff schedules the precheck before implement.",
+  "verification": {
+    "L0": "node --check bin/duaer-live.mjs bin/live-modules.mjs web/live-dev/app.js web/live-dev/data-precheck.mjs — pass",
+    "L1": "npm test — 246 pass",
+    "L3": "npm run test:live — pass"
+  }
+}