@tea-agent/loop-agent 0.41.1-beta.0 → 0.42.0-next.1

package/docs/architecture/runtime-boundaries.md

@@ -160,18 +160,18 @@ Runner / Loop         ──(迁移中)──>  逐步改为仅经 Store / Appli
 
 | From | May import | Must not import |
 | ------ | ------------ | ----------------- |
-| `src/commands/**` | application, workflows, infrastructure, task, records, executors, shared | — |
-| `src/workflows/**` | executors, task, records, shared, application（目标） | `src/commands/**` |
+| `src/commands/**` | application, workflows, infrastructure, task, records, executors, shared | `src/worker/**` |
+| `src/workflows/**` | executors, task, records, shared, infrastructure, application（目标） | `src/commands/**` |
 | `src/executors/**` | shared, 外部 SDK | `src/commands/**`, `src/cli/**` |
-| `src/worker/**` | worker-local modules, task contracts, shared, Node APIs | `src/commands/**`, `src/cli/**`, `src/application/**` |
-| `src/cli/**` | commands, adapters, shared, application（目标） | — |
+| `src/worker/**` | worker-local modules, task contracts, shared, infrastructure, Node APIs | `src/commands/**`, `src/cli/**`, `src/application/**` |
+| `src/cli/**` | commands, adapters, shared, infrastructure, application（目标） | — |
 | `.agents/skills/**` | （Markdown 引用，非 TS import） | 运行时 TS 模块 |
 
 ## 已知过渡耦合
 
-当前没有允许的 `src/workflows/**` / `src/executors/**` forbidden import，也没有允许的 `src/worker/**` → `src/{cli,commands,application}/**` TypeScript import。
+当前没有允许的 `src/workflows/**` / `src/executors/**` forbidden import，也没有允许的 `src/worker/**` → `src/{cli,commands,application}/**` 或 `src/commands/**` → `src/worker/**` TypeScript import。Console app-data 存储（operations、context exports、artifact revisions、app-data path helpers）位于 `src/infrastructure/console/**`，由 Console（worker 层）与 CLI 命令共同向下依赖；Console 专属的 route/action 编排仍留在 `src/worker/console/**`。
 
-`scripts/check-architecture-boundaries.sh` 的 transitional allowlist 保持为空。任何新增的 `workflows/executors/worker` forbidden import 必须导致检查 **exit 1**；如果未来确有临时例外，必须先写入 active exec plan，说明移除时间和验证门禁。
+`scripts/check-architecture-boundaries.sh` 的 transitional allowlist 保持为空。任何新增的 `workflows/executors/worker/commands` forbidden import 必须导致检查 **exit 1**；如果未来确有临时例外，必须先写入 active exec plan，说明移除时间和验证门禁。
 
 ## Governance 钩子
 

package/docs/architecture/worker-and-feature.md

@@ -61,7 +61,7 @@ controller identity 与 DAG skill snapshot 是两个不同冻结层（前者跨
 
 - schema/validate：`src/worker/task-spec/{schema,validate}.ts`。
 - 校验验收条件、依赖、验证命令；`agent-worker task validate-feature` 等用之。
-- **0.16.0+**：可选 `execution.workflow` 映射到 loop-agent `taskKind`（如 agent-dag / frontend-implementation / backend-test / frontend-test）；typed Task Outcome 与 artifact-aware Ready 门禁见 completed `2026-07-19-taskspec-workflow-routing.md`。
+- **0.16.0+**：可选 `execution.workflow` 映射到 loop-agent `taskKind`（agent-dag / frontend-implementation / backend-test-analysis / backend-test / frontend-test）；`backend-test-analysis` 只读生成严格 analysis artifact，不执行测试；typed Task Outcome 与 artifact-aware Ready 门禁见 completed `2026-07-19-taskspec-workflow-routing.md`。
 - 文档映射镜像：`docs/architecture/taskspec-to-loop-agent-mapping.md`（runtime 真源仍在 `src/worker/` 与 materialize 路径）。
 
 ### Task Pool

package/docs/init-surface.manifest.json

@@ -34,7 +34,6 @@
     "docs/templates/worker-dogfood-setup.md",
     "docs/templates/worker-dogfood-evidence.md",
     "docs/templates/harness.schema.json",
-    "docs/templates/spec-registry.schema.json",
     "docs/templates/interactive-ui-round2-experiment.md",
     "docs/templates/product-line/README.md",
     "docs/templates/product-line/AGENTS.md",
@@ -78,16 +77,11 @@
     "skills/webapp-testing/SKILL.md",
     "skills/playwright-cli/SKILL.md",
     "skills/playwright-cli-case-generator/SKILL.md",
-    "skills/frontend-contract/SKILL.md",
-    "skills/frontend-contract/references/contract-protocol.md",
-    "skills/frontend-scout/SKILL.md",
-    "skills/frontend-scout/references/scout-evidence.md",
-    "skills/frontend-scout/references/design-evidence.md",
-    "skills/frontend-plan/SKILL.md",
-    "skills/frontend-plan/references/decision-contract.md",
-    "skills/frontend-plan/references/design-decisions.md",
+    "skills/frontend-implementation/SKILL.md",
+    "skills/frontend-implementation/references/node-contracts.md",
+    "skills/frontend-implementation/references/design-spec.md",
+    "skills/frontend-implementation/references/code-standards.md",
     "skills/frontend-bounded-implement/SKILL.md",
-    "skills/frontend-bounded-implement/references/code-standards.md",
     "skills/frontend-design-review/SKILL.md",
     "skills/frontend-design-review/references/review-checklist.md",
     "skills/frontend-review/SKILL.md",
@@ -109,7 +103,6 @@
     "docs/feature-workflow.md",
     "docs/verification-matrix.md",
     "docs/loop-agent-harness.md",
-    "docs/spec-registry.json",
     "docs/harness-methodology-tdd.md",
     "docs/harness-methodology-verification.md",
     "docs/harness-methodology-debugging.md",
@@ -164,16 +157,11 @@
     ".agents/skills/webapp-testing/SKILL.md",
     ".agents/skills/playwright-cli/SKILL.md",
     ".agents/skills/playwright-cli-case-generator/SKILL.md",
-    ".agents/skills/frontend-contract/SKILL.md",
-    ".agents/skills/frontend-contract/references/contract-protocol.md",
-    ".agents/skills/frontend-scout/SKILL.md",
-    ".agents/skills/frontend-scout/references/scout-evidence.md",
-    ".agents/skills/frontend-scout/references/design-evidence.md",
-    ".agents/skills/frontend-plan/SKILL.md",
-    ".agents/skills/frontend-plan/references/decision-contract.md",
-    ".agents/skills/frontend-plan/references/design-decisions.md",
+    ".agents/skills/frontend-implementation/SKILL.md",
+    ".agents/skills/frontend-implementation/references/node-contracts.md",
+    ".agents/skills/frontend-implementation/references/design-spec.md",
+    ".agents/skills/frontend-implementation/references/code-standards.md",
     ".agents/skills/frontend-bounded-implement/SKILL.md",
-    ".agents/skills/frontend-bounded-implement/references/code-standards.md",
     ".agents/skills/frontend-design-review/SKILL.md",
     ".agents/skills/frontend-design-review/references/review-checklist.md",
     ".agents/skills/frontend-review/SKILL.md",
@@ -190,7 +178,6 @@
     ".pi/settings.json"
   ],
   "initSurface": {
-    "docs/spec-registry.json": "generated",
     "README.md": "managed-block",
     "AGENTS.md": "managed-block",
     ".gitignore": "managed-block",
@@ -255,16 +242,11 @@
     ".agents/skills/webapp-testing/SKILL.md": "copied",
     ".agents/skills/playwright-cli/SKILL.md": "copied",
     ".agents/skills/playwright-cli-case-generator/SKILL.md": "copied",
-    ".agents/skills/frontend-contract/SKILL.md": "copied",
-    ".agents/skills/frontend-contract/references/contract-protocol.md": "copied",
-    ".agents/skills/frontend-scout/SKILL.md": "copied",
-    ".agents/skills/frontend-scout/references/scout-evidence.md": "copied",
-    ".agents/skills/frontend-scout/references/design-evidence.md": "copied",
-    ".agents/skills/frontend-plan/SKILL.md": "copied",
-    ".agents/skills/frontend-plan/references/decision-contract.md": "copied",
-    ".agents/skills/frontend-plan/references/design-decisions.md": "copied",
+    ".agents/skills/frontend-implementation/SKILL.md": "copied",
+    ".agents/skills/frontend-implementation/references/node-contracts.md": "copied",
+    ".agents/skills/frontend-implementation/references/design-spec.md": "copied",
+    ".agents/skills/frontend-implementation/references/code-standards.md": "copied",
     ".agents/skills/frontend-bounded-implement/SKILL.md": "copied",
-    ".agents/skills/frontend-bounded-implement/references/code-standards.md": "copied",
     ".agents/skills/frontend-design-review/SKILL.md": "copied",
     ".agents/skills/frontend-design-review/references/review-checklist.md": "copied",
     ".agents/skills/frontend-review/SKILL.md": "copied",

package/docs/skills/vetted-skill-registry.md

@@ -16,13 +16,11 @@ The entries below are local wrappers or existing local skills. They are not whol
 | `code-review-core` | local wrapper inspired by code review practice | `skills/code-review-core/SKILL.md` | reviewer | reviewer | No external tools or network by default. |
 | `codebase-scout` | local wrapper | `skills/codebase-scout/SKILL.md` | scout | scout | Read-only reconnaissance guidance. |
 | `init-capability-evolution` | local wrapper | `skills/init-capability-evolution/SKILL.md` | supervisor, maintenance | optional | Used only when changes may affect target-project initialization, package surface, or init projection rules. |
-| `frontend-contract` | local frontend hybrid DAG contract skill | `skills/frontend-contract/SKILL.md` | `frontend-contract-pi` only | frontend-implementation DAG only | Required contract-protocol ref stays complete under the default runtime budget; does not inject design or implementation guidance. |
-| `frontend-scout` | local frontend hybrid DAG scouting skill | `skills/frontend-scout/SKILL.md` | `frontend-scout-pi` only | frontend-implementation DAG only | Required target-surface and design-evidence refs are bounded and complete; discovery does not leak into Plan. |
-| `frontend-plan` | local frontend hybrid DAG planning skill | `skills/frontend-plan/SKILL.md` | `frontend-plan-pi` and legacy Mock assessment only | frontend-implementation DAG only | Required decision/design refs carry stable trace IDs, Mock/data and dependency decisions without the full lifecycle contract. |
+| `frontend-implementation` | local existing (frontend hybrid DAG) | `skills/frontend-implementation/SKILL.md` | frontend plan / contract / scout / mock nodes (spec-level `skillsByRole`) | frontend-implementation DAG only | Required refs node-contracts / design-spec / code-standards; injected by `init-hybrid.ts` spec generation and `src/adapters/loop-agent.ts`; projected via init-surface manifest. Not in `DEFAULT_SKILLS_BY_ROLE`. |
 | `frontend-review` | local existing (frontend hybrid DAG) | `skills/frontend-review/SKILL.md` | reviewer (frontend review nodes, spec-level) | frontend-implementation / repair DAGs | Consumed by `init-hybrid.ts` / `frontend-repair.ts` / `shell-executor.ts`; required ref review-findings (maxChars 2800). |
 | `frontend-verification` | local existing (frontend hybrid DAG) | `skills/frontend-verification/SKILL.md` | verifier / closeout (frontend evidence, spec-level) | frontend DAG closeout | Consumed by `shell-executor.ts` / `frontend-repair.ts` / `frontend-review-context.ts`; required ref verification-checklist. |
 | `frontend-design-review` | local existing (frontend hybrid DAG) | `skills/frontend-design-review/SKILL.md` | design-gate reviewer (before any writer) | frontend-implementation DAG design gate | Injected by `init-hybrid.ts`; runs before the prewrite gate authorizes writers; required ref review-checklist. |
-| `frontend-bounded-implement` | local existing (frontend hybrid DAG) | `skills/frontend-bounded-implement/SKILL.md` | implementer (writer nodes, spec-level) | frontend writers after canonical contract gate | Injected by `init-hybrid.ts`; its required bounded code-standards ref applies only inside canonical targets and does not authorize OpenSpec/source rediscovery. |
+| `frontend-bounded-implement` | local existing (frontend hybrid DAG) | `skills/frontend-bounded-implement/SKILL.md` | implementer (writer nodes, spec-level) | frontend writers after canonical contract gate | Injected by `init-hybrid.ts`; writers run only after the canonical contract gate accepts and only inside the frozen writeSet (ADR 0015/0016 discipline). |
 | `grill-with-docs` | local operator skill adapted from domain grilling + ADR/glossary discipline | `skills/grill-with-docs/SKILL.md` | explicit interactive operator only | never a default DAG role | Resolves decisions via `harness.json.governanceRoot`; required refs `context-format.md` / `adr-format.md`; respects writeSet; not in `DEFAULT_SKILLS_BY_ROLE`. |
 | `grill-me` | local interview question engine wrapper | `skills/grill-me/SKILL.md` | interview runtime dependency (not a DAG role) | never a default DAG role | Question engine lives in `src/worker/console/interview/grill-me.ts` (Console interview / operator-actions); intentionally NOT projected by init-surface manifest — runs in this repo's Console only. |
 | `analyze-product-requirements` | local org-internal Product Analysis V4 skill | `skills/analyze-product-requirements/SKILL.md` | source-prepare dependency (not a DAG role) | never a default DAG role | Loaded by `src/task/source-prepare/prepare.ts` during 任务源 preparation; IRON-LAW freeze semantics on `product-analysis.md`; intentionally NOT projected by init-surface manifest. |

package/docs/templates/README.md

@@ -38,7 +38,6 @@
 
 - `frontend-task-requirement.md`、`frontend-task-constraints.md`、`frontend-design-contract.md` — 前端任务输入与设计合同。
 - `frontend-implementation-contract.schema.json` — 前端实现合同 schema（sourceBinding v2 ledger 字段 all-or-none：任一出现则四项齐全，禁止 v1+optional 冒充 v2）。`requirements[].sourceRefs[].items` 使用合法 `$ref: #/$defs/path`（相对路径、无 `..` 逃逸、无反斜杠），模板 JSON 无非法键，运行时加载器可直接编译（AC-003）。
-- `frontend-implementation-dag.json` — 自包含的前端实现 DAG 模板：契约 → 侦察 → 计划 → 设计策略/评审 → writer 准入 → 有界写入 → 验证 → 真实 diff 审查 → closeout。它不依赖 runtime builder 或其他模板；执行前必须将所有 `REPLACE/WITH/...` 路径和确定性命令替换为当前项目的具体值。
 - `frontend-test-dag.json` — frontend-test DAG 模板；其 deterministic checklist 会拒绝 alternative executable instructions，仅允许 allowlisted `playwright-cli` command。Pi generator/reviser 的 runtime writeSet 仅授权下列目标项目生成路径（不是本仓库文档索引目标）：
 
   ~~~text
@@ -57,7 +56,6 @@
 - `knowledge-sync-dag.json`、`knowledge-graph-bootstrap-dag.json` — 知识同步与图谱初始化 DAG。
 - `knowledge-sync-draft.schema.json` — 知识同步草稿 schema。
 - `harness.schema.json` — `harness.json` 的 IDE JSON Schema。
-- `spec-registry.schema.json` — 项目级 `ai_workspace/loop-agent/spec-registry.json` 的机器校验 schema。
 
 ## 子目录
 

package/docs/templates/agent-dag-report.schema.json

@@ -176,8 +176,7 @@
         "humanEscalationJson",
         "humanEscalationMd",
         "humanApproval",
-        "humanRejection",
-        "changeManifest"
+        "humanRejection"
       ],
       "properties": {
         "resultSummary": { "$ref": "#/$defs/dagArtifactRef" },
@@ -189,12 +188,7 @@
         "humanEscalationJson": { "$ref": "#/$defs/dagArtifactRef" },
         "humanEscalationMd": { "$ref": "#/$defs/dagArtifactRef" },
         "humanApproval": { "$ref": "#/$defs/dagArtifactRef" },
-        "humanRejection": { "$ref": "#/$defs/dagArtifactRef" },
-        "changeManifest": { "$ref": "#/$defs/dagArtifactRef" },
-        "changeManifestChangedFiles": {
-          "type": "array",
-          "items": { "type": "string" }
-        }
+        "humanRejection": { "$ref": "#/$defs/dagArtifactRef" }
       }
     },
     "repairArtifact": {

package/docs/templates/agent-dag.schema.json

@@ -466,7 +466,7 @@
         "retryCategories": {
           "type": "array",
           "items": {
-            "enum": ["timeout", "network", "rate-limit", "unavailable", "empty-output", "output-too-large", "protocol-invalid", "invalid-output", "writer-empty-diff", "incomplete-write-set", "writer-clean-timeout", "read-burst", "context-overflow"]
+            "enum": ["timeout", "network", "rate-limit", "unavailable", "empty-output", "output-too-large", "protocol-invalid", "invalid-output", "writer-empty-diff", "incomplete-write-set", "writer-clean-timeout"]
           },
           "default": ["timeout", "network", "rate-limit", "unavailable", "empty-output"],
           "description": "Failure categories eligible for retry. quota/auth/write-guard are never eligible. invalid-output is allowed only on explicit structured/protocol policies; writer-empty-diff and incomplete-write-set are reserved for requireChangedFiles generation/completeness writers; writer-clean-timeout is reserved for standard bounded writers after explicit zero-write-tool-call and empty-diff evidence."
@@ -483,6 +483,28 @@
         "sha256": { "type": "string", "minLength": 1 }
       }
     },
+    "producedArtifact": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["artifactId", "kind", "path", "mediaType", "revisionPolicy"],
+      "properties": {
+        "artifactId": { "type": "string", "pattern": "^[a-z][a-z0-9]*(?:[.-][a-z0-9]+)*$" },
+        "kind": { "enum": ["structured", "assistant", "stdout"] },
+        "path": { "type": "string", "pattern": "^(?!/)(?![A-Za-z]:)(?!.*(?:^|/)\\.\\.(?:/|$))(?!.*\\\\).+$" },
+        "mediaType": { "type": "string", "minLength": 1 },
+        "schemaId": { "type": "string", "minLength": 1 },
+        "revisionPolicy": { "enum": ["immutable", "replace-file"] }
+      }
+    },
+    "consumedArtifact": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["artifactId"],
+      "properties": {
+        "artifactId": { "type": "string", "pattern": "^[a-z][a-z0-9]*(?:[.-][a-z0-9]+)*$" },
+        "required": { "type": "boolean", "default": true }
+      }
+    },
     "task": {
       "type": "object",
       "additionalProperties": false,
@@ -570,6 +592,16 @@
           "type": "string",
           "minLength": 1
         },
+        "producesArtifacts": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/producedArtifact" },
+          "description": "Frozen producer declarations. Artifact lineage and impact analysis must use these declarations, never prompt/outputContract/path heuristics."
+        },
+        "consumesArtifacts": {
+          "type": "array",
+          "items": { "$ref": "#/$defs/consumedArtifact" },
+          "description": "Frozen logical artifact inputs consumed by this node."
+        },
         "outputMode": {
           "enum": ["default", "structured-required"],
           "description": "Optional output semantics for Pi nodes. structured-required means oversized assistant output must not be accepted as a truncated success; eligible read-only nodes may compact-retry and downstream gates should rely on canonical structured artifacts."

package/docs/templates/frontend-implementation-contract.schema.json

@@ -502,12 +502,9 @@
               ]
             },
             "then": {
-              "required": [
-                "specReference"
-              ],
               "properties": {
                 "specReference": {
-                  "$ref": "#/$defs/uiComponentSpecReference"
+                  "type": "null"
                 }
               }
             }

package/docs/templates/product-line/task.yaml

@@ -31,7 +31,7 @@ constraints:
   hard_constraints:
     - Do not access production secrets
 # Explicit runtime workflow → taskKind. For fullstack-v1 packets this should be set
-# on every TaskSpec. Allowed: agent-dag | frontend-implementation | backend-test | frontend-test
+# on every TaskSpec. Allowed: agent-dag | frontend-implementation | backend-test-analysis | backend-test | frontend-test
 execution:
   workflow: agent-dag
 verify:

package/harness.json

@@ -83,8 +83,8 @@
     "pi": {
       "description": "Pi 负责规划、评审、诊断；当 DAG toolProfile=write 时也可做有界写入。模型按复杂度三档配置，支持 provider/model 字符串或带 thinking 的对象；斜杠前为 Pi provider，后为 modelId，勿只写裸 modelId。",
       "LOW": "wizard-local/minimax-m3",
-      "MED": "wizard-local/gpt-5.5",
-      "HIGH": "wizard-local/gpt-5.5"
+			"MED": "wizard-local/glm-5.3",
+      "HIGH": "wizard-local/gpt-5.6-sol"
     }
   }
-}
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tea-agent/loop-agent",
-  "version": "0.41.1-beta.0",
+  "version": "0.42.0-next.1",
   "type": "module",
   "bin": {
     "loop-agent": "bin/loop-agent.js",
@@ -72,7 +72,9 @@
     "verify:tree": "node scripts/pre-push-verify.mjs --verify-current-tree"
   },
   "dependencies": {
+    "@deepseek-ai/cordis": "4.0.1",
     "@deepseek-ai/dsh-host-directory-picker-native": "0.1.1-rc.2",
+    "@deepseek-ai/dsh-invariants": "0.1.1-rc.2",
     "@earendil-works/pi-ai": "0.83.0",
     "@earendil-works/pi-coding-agent": "0.83.0",
     "commander": "^12.1.0",

package/skills/frontend-bounded-implement/SKILL.md

@@ -1,23 +1,17 @@
 ---
 name: frontend-bounded-implement
 description: >-
-  Use only for frontend implementation writers after the canonical
+  Use only for frontend implementation and repair writers after the canonical
   contract gate has authorized a bounded write set.
-references:
-  - path: references/code-standards.md
-    required: true
-    maxChars: 2600
 ---
 
 # Frontend Bounded Implement
 
-Read the bounded code standards before editing. They apply only inside the
-canonical targets and do not authorize additional discovery.
-
 ## Authoritative Inputs
 
 - For implementation, use the run-owned
   `contracts/frontend-implementation-contract.json`.
+- For repair, also use `contracts/frontend-repair-assessment.json`.
 - Treat requirement `expectedOutcome`, interaction `trigger` /
   `expectedBehavior`, target files, UI states, Mock/API strategy, and verification
   targets as closed decisions. Do not rediscover or reinterpret them.
@@ -31,7 +25,7 @@ canonical targets and do not authorize additional discovery.
 - Start the bounded edit after confirming the contract and targets. Optional
   context is not a reason to postpone implementation.
 - If behavior is still ambiguous or a required target is outside `writeSet`, stop
-  without writing and explain the blocker; do not compensate with broader scouting.
+  with `IMPLEMENTATION_OUTCOME: blocked`; do not compensate with broader scouting.
 
 ## Implementation Discipline
 
@@ -45,10 +39,15 @@ canonical targets and do not authorize additional discovery.
 - Run only the focused checks already frozen by the task. Leave full verification
   to downstream deterministic nodes.
 
-## Completion Summary
+## Required Outcome
+
+The first non-empty response line must be exactly one of:
+
+- `IMPLEMENTATION_OUTCOME: changed` — a non-empty bounded diff was produced.
+- `IMPLEMENTATION_OUTCOME: already-satisfied` — the contract was already met and
+  no file changed.
+- `IMPLEMENTATION_OUTCOME: blocked` — implementation cannot proceed without
+  guessing or exceeding the write boundary.
 
-Briefly report changed files, implemented requirements/interactions, focused checks
-attempted, blockers, and residual risks. This summary is human-readable only: the
-runtime derives implementation state from persisted write events, run delta, write
-guard, requirement coverage, and focused checks. Do not use a mandatory
-`IMPLEMENTATION_OUTCOME:` response-text protocol.
+Then report changed files, requirements/interactions implemented, tests or focused
+checks attempted, and residual risks. Never report `changed` for an empty diff.

package/skills/frontend-design-review/SKILL.md

@@ -9,26 +9,31 @@ references:
 
 # Frontend Design Review
 
-For frontend design review nodes. Read the checklist and the non-blocking contract
-capacity diagnostic first. Audit either the canonical contract or, when the
-diagnostic recommends indexed reading, its hash-bound field sections. Check the
-bound Mock strategy, task bounds, and traceable design evidence supplied by the
-upstream context. Do not rediscover task sources, search specification roots, or
-replace frozen evidence with nearby-code conventions. Use only exact, bound evidence
-paths when additional reading is necessary; never invent connector results.
+For frontend design review nodes. Read the checklist; audit contract, scout, Mock
+strategy, effective plan, task bounds, and traceable design evidence.
+Knowledge base, OpenSpec, and `ai_workspace/` are parallel sources. Query the
+knowledge-base connector when available; always search/read `openspec/schemas/**`,
+`openspec/project-specs/**`, and `ai_workspace/**` before accepting conventions.
+Connector format is TODO: never invent results.
 
-## Authoritative Terminal
+## Verdict Contract
 
-Complete the review with exactly one committed typed tool call:
+First non-empty line: exactly `VERDICT: pass` or `VERDICT: request-revision`.
+Any blocker requires request-revision. An initial pass is the effective verdict;
+there is no intermediate first-design shell gate.
 
-- `approve_design` when no blocking design defect remains;
-- `request_design_changes` when a blocker exists. It must include a typed
-  `issueCategory`, at least one `evidenceRef`, and non-empty findings.
+In standard/full topology, revision and final review run only after initial
+`VERDICT: request-revision`. Verify every Required Plan Correction against the
+complete revision; reject remaining, incomplete, or new gaps. An initial pass uses
+the original plan and skips both conditional nodes.
 
-The typed terminal is the only authoritative outcome. Do not require or emit a
-`VERDICT:` line, JSON verdict, revision patch, or a second final-design-review
-verdict. A requested design change ends this run; the recovery controller creates
-any bounded follow-up run from the appropriate phase.
+Small-risk topology instead removes initial review and revision, then runs
+`frontend-final-design-review-pi` as the sole review of the original plan. Do not
+expect initial findings or a revision there.
+
+The deterministic gate prefers final-review output and falls back to initial review
+only when no current-run final output exists. Existing malformed/non-pass primary
+output fails closed.
 
 ## Blocking Conditions
 
@@ -46,15 +51,29 @@ Knowledge-base absence is advisory if relevant rules from either openspec
 specification directory were read and applied. Block skipped fallback, unresolved
 conflict, or unresolved UI decisions.
 
-## Method And Human-readable Output
+## Method And Output
 
 Map criteria to steps/files/states/checks, audit paths/evidence, classify Blocking
 or Advisory, and never edit files.
 
 ### Spec Evidence Rules
 
-Read only the canonical contract (or its indexed, hash-bound sections) and any exact
-evidence paths bound in its upstream context. Successful paired reads are the only proof that a specification was read;
-summaries do not substitute for them. A concise human-readable summary may list
-checked items and findings, but it is never a control protocol. Each requested
-change names its criterion/section, gap, and required plan change.
+Run `grep`/`find`, then explicit `read` calls for applicable specs/checklist. Only
+successful paired reads count as “已读取规范文件”; summaries do not. List each path/
+section in `Checked Items`; search/read both openspec specification directories
+before accepting conventions.
+
+```markdown
+VERDICT: pass
+
+## Findings
+- None blocking.
+
+## Required Plan Corrections
+- None.
+
+## Checked Items
+- ...
+```
+
+Each correction names its criterion/section, gap, and exact plan change.

package/skills/frontend-implementation/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: frontend-implementation
+description: >-
+  Use for frontend contract, scout, mock strategy, and plan DAG nodes.
+references:
+  - path: references/node-contracts.md
+    required: true
+    # Compact contract index must stay under skill total budget (~10k with body + other refs).
+    # Headroom above current ~4k file; do not raise alone without checking totalMaxChars.
+    maxChars: 6000
+  - path: references/design-spec.md
+    required: true
+    maxChars: 3000
+  - path: references/code-standards.md
+    required: true
+    maxChars: 3000
+---
+
+# Frontend Implementation
+
+Read all required references before running any listed frontend node.
+
+## Source And Evidence Rules
+
+Use task sources/references, constraints, then `task.json`. Follow `design-spec.md`:
+query the knowledge base when available and always inspect `openspec/schemas/`,
+`openspec/project-specs/`, and `ai_workspace/`; then use repo evidence. Cite tight paths/symbols, and never invent APIs,
+rules, commands, or retrievals. Scout/planners locate and explicitly read applicable
+specs; only successful paired reads count. Lockfile-only, fixture-only, or unread
+search hits do not prove a reusable Mock service.
+
+This broad discovery rule applies only to contract, scout, and plan phases.
+Implementation and repair use the separate `frontend-bounded-implement` skill.
+
+## Implementation Discipline
+
+- Reuse confirmed specs, components, tokens, helpers, APIs, mocks, schemas, and tests.
+- Keep real requests enabled by default; never comment them out for a mock.
+- Prefer native Mock support; otherwise use existing browser interception for e2e or
+  a reversible request adapter/DI seam for local preview.
+- Trace fixtures to API/schema evidence. Activation is explicit, dev/test-only,
+  production-off; Mock evidence never proves real API integration.
+- Add dependencies only when approved. Cover applicable success/loading/empty/error/
+  permission/boundary states and justify N/A.
+- Keep state testable. Stay in `writeSet`, preserve behavior, and update tests.
+- Never relax lint/type/test/build config or write unauthorized generated output.
+
+## Output And Failure Rules
+
+- Follow `node-contracts.md`; read-only nodes never edit. Missing input blocks work
+  when proceeding would guess behavior, bounds, or verification.
+- Preserve tokens, commands, paths, IDs, and language. Completion needs fresh shell evidence.

package/skills/frontend-implementation/references/code-standards.md

@@ -0,0 +1,33 @@
+# Frontend Code Standards
+
+Discover rules from task constraints, `design-spec.md` source order, config, code,
+tests, manifests, and generated types. Regardless of knowledge-base results,
+applicable `openspec/schemas/`, `openspec/project-specs/`, and `ai_workspace/` rules are normative.
+Preferences are not rules, and docs do not override installed APIs without an
+explicit compatibility decision.
+
+## Discover And Cite
+
+- Find routing and server/client boundaries; state, forms, data/cache, and errors;
+  API/mock/UI/schema/test locations and naming; supported tests; dependency rules.
+
+Cite representative files/config for each convention. Describe conflicts instead of
+silently selecting one.
+
+## Plan And Implement
+
+- Map criteria to code and checks. Define placement, state ownership, request
+  lifecycle, validation/failures, API compatibility, mocks, and fixtures.
+- Trace fixtures to API evidence; label gaps. Prefer native mocks, then browser
+  interception for existing e2e, then a reversible request adapter/DI preview seam.
+- Real API stays default; mock activation is explicit, local/test-only,
+  non-production, and removable.
+- Reuse helpers/public APIs and preserve out-of-contract behavior. Keep rendering,
+  transitions, validation, and side effects testable; cover lifecycle races/bounds
+  when relevant. Update supported tests; stay in `writeSet`.
+
+## Prohibited
+
+- Do not relax checks, add unapproved dependencies, comment real requests, hardcode
+  fixtures in production UI, import test mocks into production, store fixture
+  secrets, equate mock evidence with real integration, or report unrun checks as verified.

package/skills/frontend-implementation/references/design-spec.md

@@ -0,0 +1,56 @@
+# Frontend Design And Component Specification
+
+## Required Source Sequence
+
+Knowledge base, OpenSpec, and `ai_workspace/` are parallel specification sources:
+
+1. Attempt the configured component/design knowledge-base query first when a
+   connector is available.
+2. Regardless of knowledge-base success/failure/timeout/no-match, also
+   recursively search `openspec/schemas/`, `openspec/project-specs/`, and
+   `ai_workspace/` for index files and relevant content.
+3. Treat relevant matches from both sources as the current project's
+   specification for this run.
+4. Only then use component source, tokens, stories, tests, and pages as
+   non-normative repository fallback.
+
+Never skip local OpenSpec or `ai_workspace/` for neighboring-code conventions,
+even when a knowledge-base query returned results. Report source conflicts instead
+of combining them. Explicit task requirements remain the contract.
+
+Connector format is TODO; attempt only an available connector, otherwise record
+`not-configured` and run the openspec fallback (never invent a connection).
+
+## openspec Fallback Procedure
+
+- Inspect `<repoRoot>/openspec/schemas/`, `<repoRoot>/openspec/project-specs/`,
+  and `<repoRoot>/ai_workspace/` when present; enumerate supported files recursively.
+- Read indexes first, then search names/content using task, route, component,
+  interaction, theme, token, and state terms.
+- Read matches in context; a filename-only hit is not a rule.
+- Record search terms, inspected/matched paths, headings or tight line ranges,
+  applied rules, and conflicts.
+- If both directories or relevant rules are absent, record that before using
+  repository fallback.
+
+## Retrieval Evidence
+
+Record source as `knowledge-base`, `openspec fallback`, `repository fallback`, or
+`unavailable`. Knowledge-base evidence includes query, source ID/version/time, rules,
+and conflicts. `openspec fallback` includes terms, paths/headings/lines, rules, and conflicts.
+
+## Rules To Retrieve Or Discover
+
+- Components, variants, props, composition, accessibility, deprecations, placement, forms, overlays, navigation, and state patterns.
+- Tokens, typography, color, layout, breakpoints, motion, focus/keyboard/contrast, exceptions, design debt, and forbidden patterns.
+
+## Gate Expectations
+
+- Reuse confirmed primitives unless a new pattern is authorized.
+- Define applicable states and responsive behavior before implementation.
+- Cite knowledge-base or openspec spec evidence for component/token choices;
+  label weaker repo fallback.
+- Make deviations and unresolved gaps explicit.
+- Contract `uiComponentChoices[]` per UI purpose: `specified` needs
+  `specReference {path,section,line}`; `new` needs null ref + rationale; never
+  silently replace a spec-defined component.