@tea-agent/loop-agent 0.42.0-next.1 → 0.42.0-next.10

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

@@ -1,17 +1,23 @@
 ---
 name: frontend-bounded-implement
 description: >-
-  Use only for frontend implementation and repair writers after the canonical
+  Use only for frontend implementation 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.
@@ -25,7 +31,7 @@ description: >-
 - 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
-  with `IMPLEMENTATION_OUTCOME: blocked`; do not compensate with broader scouting.
+  without writing and explain the blocker; do not compensate with broader scouting.
 
 ## Implementation Discipline
 
@@ -39,15 +45,10 @@ description: >-
 - Run only the focused checks already frozen by the task. Leave full verification
   to downstream deterministic nodes.
 
-## 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.
+## Completion Summary
 
-Then report changed files, requirements/interactions implemented, tests or focused
-checks attempted, and residual risks. Never report `changed` for an empty diff.
+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.

package/skills/frontend-bounded-implement/references/code-standards.md

@@ -0,0 +1,19 @@
+# Bounded Frontend Code Standards
+
+Apply the canonical contract and the conventions visible in target files and their
+direct local dependencies. Do not reopen task sources, OpenSpec, `ai_workspace`, or
+unrelated repository areas to discover new rules or redesign approved decisions.
+
+- Work test-first when behavior changes and preserve unrelated behavior.
+- Reuse existing public helpers, APIs, components, tokens, schemas, and test
+  patterns that are directly available from the bounded target surface.
+- Keep rendering, transitions, validation, request lifecycle, errors, and side
+  effects testable; cover relevant races and boundaries.
+- Keep real API behavior enabled by default. Mock activation must follow the
+  approved strategy, remain explicit and dev/test-only, and never import test mocks
+  into production code.
+- Trace fixtures to the approved API/schema evidence and never store secrets.
+- Do not add unapproved dependencies, relax lint/type/test/build configuration,
+  add `.skip`/`.only`, comment out real requests, or write outside `writeSet`.
+- Run only frozen focused checks and report their real status. Downstream shell
+  verification remains authoritative.

package/skills/frontend-contract/SKILL.md

@@ -0,0 +1,23 @@
+---
+name: frontend-contract
+description: Use only for the read-only frontend requirement contract node.
+references:
+  - path: references/contract-protocol.md
+    required: true
+    maxChars: 4200
+---
+
+# Frontend Contract
+
+Use task sources, explicit references, constraints, and the frozen source-fidelity
+ledger. Preserve canonical requirement IDs, source fragments, commands, paths, and
+language. Do not inspect implementation files or choose components, routes, Mock
+mechanisms, dependencies, or target code as requirement facts.
+
+Submit confirmed facts incrementally with the contract `record_*` tools and finish
+with exactly one `finalize_contract`. Start recording as soon as a requirement or
+constraint is confirmed; do not accumulate the whole contract in one response.
+
+Missing product semantics may be explicit assumptions only when they do not change
+observable behavior. Otherwise record a blocking question or a split proposal.
+This node is read-only.

package/skills/frontend-contract/references/contract-protocol.md

@@ -0,0 +1,34 @@
+# Frontend Contract Protocol
+
+## Requirement fidelity
+
+- Use the frozen canonical requirement ID for every requirement. Never invent a
+  replacement REQ/BR/AC ID.
+- Bind every requirement to exactly the source fragment IDs supplied by the
+  source-fidelity ledger. Do not infer fragment IDs from prose.
+- Record observable outcomes, applicable UI states, runtime/environment constraints,
+  non-goals, risks, and verification expectations without choosing implementation.
+- Classify each requirement as `explicit`, `repository-resolvable`, `assumption`, or
+  `blocking`. Blocking facts name their owner and evidence.
+
+## Evidence and handoff
+
+- Register static, behavior, Mock, and real-integration evidence expectations as
+  required, optional, or not-applicable. The classification follows the source and
+  risk; it is not selected for model convenience.
+- Register a non-blocking frontend-test handoff for UI-visible or interactive work.
+- Preserve exact command labels and referenced paths. Do not invent evidence,
+  connector results, APIs, or verification commands.
+
+## OpenSpec selection
+
+When the frozen task exposes OpenSpec candidates, record only candidates actually
+used by the contract as `required` or `relevant`. Explicit required paths and task
+source citations remain required. Unmentioned candidates are irrelevant; do not
+enumerate or downgrade them.
+
+## Terminal
+
+Commit facts in small batches and call `finalize_contract` exactly once with
+`ready`, `ready-with-assumptions`, or `blocked`. If the task is too large for one
+bounded writer, record a split proposal instead of broadening the contract.

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

@@ -9,31 +9,26 @@ references:
 
 # Frontend Design Review
 
-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.
+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.
 
-## Verdict Contract
+## Authoritative Terminal
 
-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.
+Complete the review with exactly one committed typed tool call:
 
-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.
+- `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.
 
-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.
+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.
 
 ## Blocking Conditions
 
@@ -51,29 +46,15 @@ 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 Output
+## Method And Human-readable Output
 
 Map criteria to steps/files/states/checks, audit paths/evidence, classify Blocking
 or Advisory, and never edit files.
 
 ### Spec Evidence Rules
 
-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.
+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.

package/skills/frontend-plan/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: frontend-plan
+description: Use only for the tool-only frontend decision planning node.
+references:
+  - path: references/decision-contract.md
+    required: true
+    maxChars: 5200
+  - path: references/design-decisions.md
+    required: true
+    maxChars: 3400
+---
+
+# Frontend Plan
+
+Plan only the delta between frozen Contract facts and the Scout target surface.
+Do not reread task sources, Contract/Scout prose, or target files, and do not repeat
+requirements or repository discovery.
+
+Commit the smallest necessary typed decisions through the plan `record_*` tools:
+requirement coverage, component/styling choices, applicable states and interactions,
+data/Mock strategy, deviations, and dependency policy. Process a bounded requirement
+slice and record facts immediately rather than reasoning over the whole task first.
+
+The runtime owns protected skeleton fields, path/command validation, materialization,
+and final schema checks. Finish with exactly one `finalize_plan`; return no Markdown
+narrative. Record a genuine evidence gap when frozen facts are insufficient.

package/skills/frontend-plan/references/decision-contract.md

@@ -0,0 +1,37 @@
+# Frontend Plan Decision Contract
+
+## Requirement-local decisions
+
+- Cover each frozen requirement exactly once and map it to Scout-confirmed
+  implementation paths and verification target IDs.
+- Record observable state and interaction behavior, including trigger and expected
+  behavior. IDs and paths alone are not behavioral coverage.
+- One behavior target may cover multiple related requirements when one observable
+  test behavior proves them together.
+- Every non-static verification target `id` is the stable machine trace token and
+  must later appear in a real `describe` / `it` / `test` title. There is no free-form
+  `symbol` field.
+- Static targets are for project-wide commands and are traced by file and command
+  only.
+
+## Global decisions
+
+Keep route/component placement, Mock/data strategy, and dependency/deviation policy
+as explicit global decisions rather than duplicating them across each requirement.
+Use only frozen command labels and Scout-confirmed paths.
+
+For Mock/API, keep the real request path enabled by default. Select only a strategy
+allowed by the frozen task capability. Active Mock requires deterministic Mock-backed
+verification and production-default-off activation. `not-needed` requires positive
+real/no-remote evidence or records a real-integration gap.
+
+Add dependencies only when authorized. Record unsupported dependency, path, API,
+design, or verification needs as blocking evidence gaps; never invent a command or
+widen the write set.
+
+## Runtime-owned fields and terminal
+
+The runtime owns `schemaVersion`, `sourceBinding`, risk, canonical target files,
+aliases, command allowlisting, path containment, and final validation. Submit only
+editable decision facts, then call `finalize_plan` exactly once. The deterministic
+design policy materializes the canonical implementation contract.

package/skills/frontend-plan/references/design-decisions.md

@@ -0,0 +1,17 @@
+# Frontend Design Decisions
+
+Use only design evidence already committed by Scout and frozen selections from
+Contract. Do not search specification roots or nearby code from Plan.
+
+- Reuse confirmed components, variants, tokens, helpers, and state patterns unless
+  the task authorizes a new pattern.
+- Record `uiComponentChoices` per UI purpose. `purpose` is the stable coverage key
+  matching an interaction or UI state; behavior remains in the corresponding
+  expected behavior and rationale.
+- `specified` requires an exact bound OpenSpec reference. `reuse-existing` identifies
+  the proven existing component/path. Task-mandated `new` choices bind the frozen
+  source requirement/fragment so the runtime can derive the PRD citation.
+- Define applicable success, loading, empty, error, permission, disabled, boundary,
+  responsive, and accessibility behavior; use not-applicable only with a reason.
+- Record styling strategy, deviations, conflicts, and unresolved gaps explicitly.
+  Never silently replace a spec-defined component or claim unread evidence.

package/skills/frontend-review/SKILL.md

@@ -9,17 +9,25 @@ references:
 
 # Frontend Review
 
-Use for `frontend-review-pi`; read the findings guide first. Required inputs are
-original task/reference material, effective plan/design branch, implementation summary,
-and `contracts/frontend-review-context.json`. That canonical context binds the validated
-implementation contract, effective verification trace, repair assessment, optional
-`frontend-lint-assessment-v1`, and run-owned diff. The diff is authoritative.
+Use for `frontend-review-pi`; read the findings guide and capacity diagnostic first.
+Inputs are `contracts/frontend-review-context.json`, its hash-bound contract
+reference/index and diff fragments, and only source files named by that diff. Use
+indexed contract sections when recommended. Do not reopen task sources, plans,
+design-review prose, OpenSpec, or `ai_workspace/`; the bound context is authoritative.
 
-## Verdict Contract
+## Authoritative Terminal
 
-The first non-empty line must be exactly `VERDICT: pass` or
-`VERDICT: request-revision`. Any Critical/Important finding, failed or missing
-required check, forbidden write, or unmet acceptance criterion forces revision.
+Complete the review with exactly one committed typed tool call:
+
+- `approve_review` when no Critical/Important finding remains;
+- `request_review_changes` for a defect, missing required evidence, forbidden
+  write, or unmet acceptance criterion. It must include a typed `issueCategory`,
+  at least one `evidenceRef`, and non-empty findings.
+
+The typed terminal is the only authoritative outcome. Do not require or emit a
+`VERDICT:` line or response-text JSON verdict. A request for review changes ends
+this run and is handled by the recovery controller rather than a same-run repair
+branch.
 
 ## Review Scope
 
@@ -27,7 +35,7 @@ required check, forbidden write, or unmet acceptance criterion forces revision.
 - Inspect every changed file against allowed, forbidden, and approved write scope.
 - Map criteria to behavior, applicable UI states, tests, and shell evidence.
 - Review state/data flow, validation, async/error behavior, design, responsive/a11y,
-  dependencies, maintenance, and regression risk when applicable.
+  dependencies, and regression risk when applicable.
 - Inspect static, behavior, and available Mock-specific artifacts directly. For Mock
   strategies, compare the endpoint matrix, handler/fixture/adapter and consumer diff;
   require the real request as default, contract-aligned fixtures, production isolation,
@@ -38,11 +46,8 @@ required check, forbidden write, or unmet acceptance criterion forces revision.
   baseline-matched diagnostics on unchanged files, and none on writer-changed files.
   Report debt, never `lint passed`; `failed`/`unavailable` blocks. Typecheck, build,
   and test still require successful final exits.
-- Component/design claims need both knowledge-base and local openspec evidence. Query
-  the connector when available and always read task-relevant files under
-  `<repoRoot>/openspec/schemas/`, `<repoRoot>/openspec/project-specs/`, and `<repoRoot>/ai_workspace/`.
-  Connector format is TODO; never invent evidence. Only successful `read` calls are
-  observable as "已读取规范文件".
+- Evaluate component/design claims against bound evidence; do not replace it with a
+  repository-wide search or connector query.
 - Treat shell exit status as authoritative. Do not edit files.
 
 ## Evidence And Output

package/skills/frontend-review/references/review-findings.md

@@ -14,24 +14,23 @@
   `baseline-debt` only with a valid `frontend-lint-assessment-v1`; this is not a
   passed lint result. A changed-file lint diagnostic, new unmatched diagnostic,
   command drift, missing baseline, timeout, or unparseable output is Important.
-- Treat knowledge base, `openspec/schemas/`, `openspec/project-specs/`, and `ai_workspace/` as
-  parallel sources. Record connector/query/source/time plus openspec search terms and
-  matched paths/headings; label fallback or unavailable accurately.
+- Treat the design evidence already bound in the canonical review context as the
+  source of truth. Do not launch a connector query or repository-wide OpenSpec/
+  `ai_workspace` search to replace frozen evidence; label a missing bound evidence
+  reference accurately instead.
 
 ## Review Sequence
 
 1. Establish changed-file inventory and write boundaries.
-2. Compare original requirement with derived contract/constraints.
+2. Compare the bound contract with the approved constraints and cumulative diff.
 3. Map each criterion to code, states, tests, and evidence.
 4. Inspect interactions, state/data/API behavior, failure paths, and regressions.
 5. Check mock selection, contract-to-fixture mapping, activation/default path,
    handler/fixture/adapter and consumer diff, verification, production imports, and
    the real-integration gap.
-6. Check design evidence, responsive/a11y behavior, dependencies, and maintenance.
+6. Check bound design evidence, responsive/a11y behavior, dependencies, and maintenance.
 7. Classify findings and derive the verdict mechanically.
 
-Skipping either directory is Important when design compliance affects acceptance.
-
 ```text
 - [Critical|Important|Minor] path:line — Problem; impact; required correction; evidence.
 ```

package/skills/frontend-scout/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: frontend-scout
+description: Use only for read-only frontend target-surface and design-evidence scouting.
+references:
+  - path: references/scout-evidence.md
+    required: true
+    maxChars: 4200
+  - path: references/design-evidence.md
+    required: true
+    maxChars: 3600
+---
+
+# Frontend Scout
+
+Inspect only enough repository evidence to prove the target surface and applicable
+design rules. Separate facts, inferences, and unresolved gaps. Reuse the frozen
+capability context and contract selections before running bounded task-term searches.
+
+Submit findings incrementally through `record_target_surface` and
+`record_design_evidence`. A complete surface names proven entrypoints, routes or
+mounts, implementation paths, test paths, data sources, and any allowed-path
+conflicts. If ownership remains unresolved, commit `completeness=blocked` with the
+specific gaps rather than guessing.
+
+This node is read-only and does not make plan decisions.

package/skills/frontend-scout/references/design-evidence.md

@@ -0,0 +1,16 @@
+# Frontend Design Evidence
+
+Use the generation-frozen component/design capability context and cited candidate
+set. When a connector is available, query the configured knowledge base; regardless
+of its result, inspect relevant frozen OpenSpec or `ai_workspace` candidates. Search
+local specification roots only for unresolved task terms and never recursively read
+all supported files.
+
+Record evidence as `knowledge-base`, `openspec fallback`, `repository fallback`, or
+`unavailable`. Include query/search terms, paths, headings or tight line ranges,
+applied rules, and conflicts. Filename-only and unread search matches are not rules.
+
+Look for components, variants, composition, tokens, layout, responsive behavior,
+accessibility, state patterns, data/Mock conventions, deprecations, exceptions, and
+forbidden patterns. Explicit task requirements remain authoritative; report source
+conflicts instead of merging them silently.

package/skills/frontend-scout/references/scout-evidence.md

@@ -0,0 +1,23 @@
+# Frontend Scout Evidence
+
+## Target surface
+
+Prove the current frontend stack and the files that own the requested behavior:
+
+- entrypoint, route or mount;
+- page/component/style implementation paths;
+- state and data/API/Mock flow;
+- supported scripts and test entrypoints;
+- reusable components, tokens, helpers, fixtures, and assets;
+- paths discovered outside task `allowedPaths`;
+- unresolved ownership or missing evidence.
+
+Use repository-relative POSIX paths. A search hit, lockfile, fixture, or filename is
+not proof by itself. Read the relevant surrounding code or configuration and report
+the exact evidence. Do not recursively inspect unrelated directories.
+
+## Completeness
+
+Commit `complete` only when the target surface is sufficiently proven for Plan to
+reuse without repository discovery. Otherwise commit `blocked` and list every
+unresolved path or ownership question. Do not shift discovery work into Plan.

package/skills/frontend-verification/SKILL.md

@@ -30,7 +30,7 @@ verdict/findings, and required browser, visual, manual, or knowledge evidence.
   `frontend-lint-assessment-v1` proving only pre-writer diagnostics on unchanged
   files. Report debt count, changed files, and raw evidence. Typecheck/build/test do
   not support debt.
-- Use design and requirement evidence already bound inside
+- Use design and requirement evidence referenced and hash-bound by
   `contracts/frontend-review-context.json`. Closeout must not query connectors,
   re-open task sources, OpenSpec, AI workspace, upstream model prose, or start new
   repository research.

package/skills/loop-agent/references/command-reference.md

@@ -354,6 +354,7 @@ loop-agent dag artifact revision stage --run-id <run-id> --node-id <producer> --
 loop-agent dag artifact revision discard --revision-id <revision-id> --request-id <key> --json
 loop-agent dag rerun --run-id <run-id> --artifact-revision <revision-id> --plan [--json]  # 单产物影响闭包预检
 loop-agent dag rerun-task --run-id <run-id> --reason "..." --request-id <key> [--profile auto] [--task-id <id>] [--json]  # standalone 完整任务重跑
+loop-agent dag follow-up <parent-run-id> [--task-id <id>] [--execute] [--profile auto|minimal|standard|reviewed|supervised]  # 将 frontend review 的 request_review_changes findings 物化为下游 frontend task；默认只创建并返回 task advance 命令
 loop-agent dag request-interrupt --run-id <run-id> --request-id <key> --target-operation-id <op-id> --reason-code <code> --reason "..." --expected-runner-pid <pid> --expected-runner-hostname <host> --expected-runner-started-at <ts> --expected-controller-fingerprint <fingerprint>  # 协作式中止：经 Human Gate 登记 interrupt.json，runner 等当前节点安全收敛后再停调度，不直接 SIGKILL
 loop-agent dag reconcile-tasks --glob '<pattern>'         # 仅报告的 task/run/artifact/verify drift audit
 loop-agent dag final-verification <task-id>               # 生成 closeout DAG，closeout artifact 后再 final verify

package/skills/loop-agent/references/hybrid-dag.md

@@ -16,7 +16,7 @@
 
 对于默认 `standard` 任务，生成器先读取 `source/需求.md` 中的结构化任务类型，再结合 `allowedPaths` 与 React/Next/Vue 强工程证据做确定性分类。确认是前端项目且任务不是明确后端、前后端混合、排除前端或仅文档/测试范围时，默认选择 `frontend-implementation` DAG，不依赖需求关键词。分类不会把普通后端实现路由到 `backend-test`；显式 profile、`workflowPolicy` 或 supervised quality gate 只记录治理强度，不把已识别的前端业务 workflow 换回通用模板。
 
-前端专用链保留独立 contract/scout；plan 同时选择 Mock/API 策略并输出结构化 implementation contract。design initial pass 直接使用原计划，只有 request-revision 才运行 revision/final review；small-risk 只执行一次 design review。`frontend-prewrite-gate-shell` 合并生效 verdict、REQ/BR/AC 覆盖、Mock policy 和 contract 物化，是唯一写入授权。实现后 `frontend-verify-assess-shell` 合并 Mock/static/behavior/trace/assessment；只有 `eligible=true` 才运行同 writeSet 的 repair 和 `frontend-reverify-shell`。`frontend-review-context-shell` 绑定真实 diff 与有效验证证据后再 review/closeout。standard/high-risk 为 15 个顶层节点，small-risk 为 13；绿色路径执行 11 个节点、7 次 Pi。生成期 blocked Mock 只生成一个确定性阻塞节点且没有 writer。
+前端专用链保留独立 contract/scout；plan 通过增量 typed `record_*` 工具提交决策账本并以唯一 `finalize_plan` 收口（无 fenced JSON 文本协议）。写授权由 `frontend-design-policy-shell`（确定性设计检查 + 物化唯一 authoritative `frontend-implementation-contract-v1`）与 `frontend-writer-admission-shell`（唯一写入授权：派生并冻结 writeSet、pre-writer baseline、admission digest，`admitted` 才放行 writer）承接；design review 与 final review 的权威终态是 committed typed tool（`approve_design|request_design_changes`、`approve_review|request_review_changes`）。实现后 `frontend-verify-shell` 合并 lint/Mock/static/behavior/trace；任何验证失败都是 terminal，物化 `frontend-verify-failure-v1` 供 recovery 路由，无同 run repair。`frontend-review-context-shell` 绑定真实 diff 与有效验证证据后再 review/closeout。拓扑按 shape 路由：Micro 7 / Small 10 / Standard-High 11 个顶层节点；Standard/High 完整主链为 `frontend-contract-pi` → `frontend-scout-pi` → `frontend-plan-pi` → `frontend-design-policy-shell` → `frontend-design-review-pi` → `frontend-writer-admission-shell` → `frontend-implement-pi` → `frontend-verify-shell` → `frontend-review-context-shell` → `frontend-review-pi` → `frontend-closeout-shell`，Small 去掉独立 `frontend-design-review-pi`，Micro 为 `frontend-contract-import-shell` → `frontend-writer-admission-shell` → `frontend-implement-pi` → `frontend-verify-shell` → `frontend-review-context-shell` → `frontend-review-pi` → `frontend-closeout-shell`。生成期 blocked Mock 只生成一个确定性阻塞节点且没有 writer。
 
 > Backend-test Markdown-first：先由确定性环境 Shell 检查 clean env 中 Python/pytest、常见配置、conftest/fixture、test root、server entry 和 HTML renderer，失败时不消耗模型调用。随后 Pi 生成中文 README 索引与模块用例卡片并独立 Review `testcase/md/**`。第 4 节点只把前置条件、操作步骤、预期结果作为必选章节，并检查 Case ID、业务 AC、步骤/预期和占位措辞；不校验需求来源引用有效性或 Markdown sensitive-shaped 内容。pytest writer 为每次真实接口调用记录脱敏、有界的请求 method/URL/参数摘要和响应 status/body 摘要。第 6 节点只扫描每条 Case 明确映射的 pytest 脚本，同时支持模块级函数和 pytest class 方法，并把缺少请求/响应日志、递归脱敏或有界截断证据记录为 advisory。第 4/6 节点均写 PASS/FAIL findings 而不阻断后续；pytest 仍只运行一次，生成 JUnit，并把 Markdown 名称/场景/脚本映射与同一 JUnit 合成为按测试概览、质量校验、失败概览、用例执行明细和技术证据组织的中文 self-contained HTML 与 Markdown facts。最终 Pi 按固定简洁结构汇总 advisory 状态、执行事实和 L-5 结论。active 流程不要求模型生成 backend-test 业务 JSON。
 
@@ -91,7 +91,7 @@ loop-agent dag execute --dag <temp-dir>/hybrid-dag.json --init-only --canvas-pat
 - **Source binding / recovery**：新生成 DAG 在顶层冻结 `sourceBinding`（任务源相对路径、SHA-256、显式 `REQ/BR/AC`）。前端计划在存在显式编号时经过 `frontend-requirement-coverage-shell`；修订计划为 primary，只在条件分支未产生输出时 fallback 到原计划。主来源存在但缺号时仍在 writer 前 fail closed。中断后重新生成完整 DAG，不要从二手摘要拼接 impl-only DAG；v3 孤立 exclusive writer 若无 `sourceBinding` 且没有只读 planner 上游，会被 strict governance 拒绝。
 - **勿宣称 live smoke 已通过**，除非真实 `dag execute` execution 中 Pi read-only、Pi writer、显式 Cursor 或 shell node 均按 DAG 完成。
 
-可复用 template：`docs/templates/agent-dag.base.json`（model 生成 DAG 的首选 base template）、`docs/templates/agent-dag.schema.json`（JSON Schema）、`docs/templates/agent-dag.supervised-implementation.json`（supervised implementation：writeSet audit、soft/hard verify、process supervisor、repair、review verdict gate）、`docs/templates/backend-test-dag.json`（后端测试专用模板）、`docs/templates/frontend-test-dag.json`（FE-test RAG：Markdown case manifest、串行 Playwright CLI case 子节点与逐 case 证据）、`docs/templates/agent-dag-process-supervisor.prompt.md`、`docs/templates/agent-dag-review-verdict.prompt.md`、`docs/templates/agent-dag-authority-surface-audit.prompt.md`（可选 authority surface verifier；authority signal 或显式 enablement 匹配时由 `dag init-hybrid` 插入）、`examples/hybrid-loop-agent-dag.json`、`docs/templates/hybrid-dag.json`。
+可复用 template：`docs/templates/agent-dag.base.json`（model 生成 DAG 的首选 base template）、`docs/templates/agent-dag.schema.json`（JSON Schema）、`docs/templates/agent-dag.supervised-implementation.json`（supervised implementation：writeSet audit、soft/hard verify、process supervisor、repair、review verdict gate）、`docs/templates/frontend-implementation-dag.json`（自包含的前端实现完整默认链：contract、scout、plan、design policy/review、writer admission、implement、verify、review context/review、closeout；不依赖 runtime builder 或其他模板，执行前替换全部 `REPLACE/WITH/...` 值）、`docs/templates/backend-test-dag.json`（后端测试专用模板）、`docs/templates/frontend-test-dag.json`（FE-test RAG：Markdown case manifest、串行 Playwright CLI case 子节点与逐 case 证据）、`docs/templates/agent-dag-process-supervisor.prompt.md`、`docs/templates/agent-dag-review-verdict.prompt.md`、`docs/templates/agent-dag-authority-surface-audit.prompt.md`（可选 authority surface verifier；authority signal 或显式 enablement 匹配时由 `dag init-hybrid` 插入）、`examples/hybrid-loop-agent-dag.json`、`docs/templates/hybrid-dag.json`。
 
 ### Supervised implementation flow（减少 operator 中途介入）
 

package/dist/worker/console/static/assets/channel-BU5gOilw.js

@@ -1 +0,0 @@
-import{ag as o,ah as n}from"./mermaid.core-BQe6fpqj.js";const t=(a,r)=>o.lang.round(n.parse(a)[r]);export{t as c};

package/dist/worker/console/static/assets/classDiagram-JCYQIIEL-DIzKJGHr.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-GF5L2VYU-D_OWvXzX.js";import{_ as i}from"./mermaid.core-BQe6fpqj.js";import"./chunk-5VM5RSS4-C0o2Du1e.js";import"./chunk-XXDRQBXY-CqLw_eqB.js";import"./chunk-KBJHAD2P-Cj8lRrla.js";import"./chunk-2GRJ4B5K-DYwR0im2.js";import"./index-xwu9GxEc.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dist/worker/console/static/assets/classDiagram-v2-OCEON4UE-DIzKJGHr.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-GF5L2VYU-D_OWvXzX.js";import{_ as i}from"./mermaid.core-BQe6fpqj.js";import"./chunk-5VM5RSS4-C0o2Du1e.js";import"./chunk-XXDRQBXY-CqLw_eqB.js";import"./chunk-KBJHAD2P-Cj8lRrla.js";import"./chunk-2GRJ4B5K-DYwR0im2.js";import"./index-xwu9GxEc.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};