@tea-agent/loop-agent 0.20.1 → 0.22.0

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

@@ -2,7 +2,7 @@
 
 ## Severity
 
-- **Critical**: blocks primary flow, corrupts data, violates security/privacy, writes forbidden paths, or bypasses required verification.
+- **Critical**: blocks primary flow, corrupts data, violates security/privacy, writes forbidden paths, bypasses required verification.
 - **Important**: acceptance/state/validation gap, material convention drift, missing behavior tests, unauthorized dependency, unsafe mock activation/import, mock-contract drift, misleading real-integration claim, or failed/missing required verification.
 - **Minor**: non-blocking maintainability, copy, layout, or cleanup issue.
 
@@ -10,43 +10,41 @@
 
 - Cite tight file locations, exact commands/results, or named DAG artifacts.
 - Never invent evidence; name the missing check. An implementation summary is not the actual diff.
-- Failed required static/behavior verification is at least Important unless proven unrelated.
-- Treat the knowledge base and `openspec/` as parallel sources. Record
-  connector/query, source ID/version, and retrieval time for knowledge-base
-  claims. Regardless of that result, evidence must show
-  `<repoRoot>/openspec/**` search terms and matched paths/headings; label
-  `openspec`, `repository fallback`, or `unavailable` accurately.
+- Failed required static/behavior verification is at least Important. Lint may be
+  `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.
 
 ## Review Sequence
 
 1. Establish changed-file inventory and write boundaries.
 2. Compare original requirement with derived contract/constraints.
 3. Map each criterion to code, states, tests, and evidence.
-4. Inspect interactions, state/data/API behavior, failure paths, and regression risk.
+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, optional Mock-specific verification,
-   production imports, evidence scope, and the documented real-integration gap.
-6. Check component/design evidence, responsive/accessibility behavior, dependencies, and maintenance fit when applicable.
+   handler/fixture/adapter and consumer diff, verification, production imports, and
+   the real-integration gap.
+6. Check design evidence, responsive/a11y behavior, dependencies, and maintenance.
 7. Classify findings and derive the verdict mechanically.
 
-Skipping the required `openspec/` search after knowledge-base failure is Important
-when component/design compliance affects acceptance or implementation choices.
-
-Use one issue per finding:
+Skipping either directory is Important when design compliance affects acceptance.
 
 ```text
 - [Critical|Important|Minor] path:line — Problem; impact; required correction; evidence.
 ```
 
-Avoid vague advice. When no source location exists, cite the command or artifact.
-
 ## Pass Rules
 
 - No Critical or Important findings remain.
 - Required static and behavior nodes ran and passed.
+- Lint is `passed` or evidence-backed `baseline-debt`; typecheck, build, and test are
+  passed. Any debt count and affected unchanged files remain disclosed.
 - Changed files are authorized.
 - Criteria and applicable states have implementation and evidence.
 - Required Mock-backed behavior passed; any generated Mock-specific verification also
   passed; Mock is not enabled by default in production. For default-auto skipped
   Mock, the real request remains default and the Real Integration Gap is preserved.
-- Optional unavailable knowledge-base, browser, visual, or manual checks remain explicit risks.
+- Optional unavailable knowledge/browser/visual/manual checks remain explicit risks.

package/skills/frontend-verification/SKILL.md

@@ -17,18 +17,22 @@ verdict/findings, and required browser, visual, manual, or knowledge evidence.
 
 ## Evidence Rules
 
-- Static evidence covers type/lint/build/schema; behavior evidence must exercise the flow.
+- Static evidence covers type/build/schema; behavior evidence must exercise the flow.
+  Lint has its own assessment status: `passed`, `baseline-debt`, `failed`, or
+  `unavailable`.
 - Shell exit status is authoritative. Classify as `passed`, `failed`, `not-run`,
   `blocked`, or `unavailable`; only passed satisfies a required check.
 - Never use static success as behavior proof, or tests as visual/browser proof they did not exercise.
 - Mock-backed behavior proves frontend rendering and state transitions only. It never
   proves backend readiness, transport compatibility, or real API integration.
 - Unavailable commands remain gaps.
-- Resolve design evidence from two parallel sources: query the execution environment's
-  knowledge base connector when available; regardless of result, also read
-  `<repoRoot>/openspec/**` for index and task-relevant specification content.
-  The connector format remains TODO; never invent it. Applied `openspec` rules
-  from successful reads are available project evidence.
+- `baseline-debt` is not lint passed. It requires
+  `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.
+- Resolve design evidence from parallel sources: query the available knowledge
+  connector and always read task-relevant `<repoRoot>/openspec/schemas/`,
+  `<repoRoot>/openspec/project-specs/`, and `<repoRoot>/ai_workspace/`. Connector format is TODO; never invent it.
 - Separate Mock service/handler checks from page consumption and record the
   dev/test-only boundary; handler tests alone do not prove page use.
 
@@ -40,18 +44,17 @@ only proven changes.
 Return Markdown headings:
 
 - `Changes`: changed behavior and areas.
-- `Mock Decision`, `Mock Files`, `Mock Verification`, `Production Boundary`: status is `passed`, `failed`, `not-required`, `blocked`, or `unavailable`.
+- `Mock Decision`, `Mock Files`, `Mock Verification`, `Production Boundary`.
 - `Verification Evidence`: table of check, command/source, status, and artifact/result.
+  Keep lint `baseline-debt` verbatim rather than converting it to `passed`.
 - `Review Result`: exact review verdict and findings.
 - `Known Risks`: missing optional checks and environment caveats.
 - `Follow-up`: concrete work or `None`.
 
-When the backend remains unavailable but required mock-backed checks pass, state
-`Frontend status: mock-validated` and `Real integration: pending`. When default
-`auto` skipped Mock and no real API evidence passed, state
-`Frontend status: locally-validated` and `Real integration: pending`. Use a completed
-`<task-id>-real-api-integration-verify` task before changing the latter to complete;
-the follow-up is explicit, not auto-created or auto-executed.
+With only Mock evidence, state `Frontend status: mock-validated`; when default `auto`
+skipped Mock without real API evidence, state `Frontend status: locally-validated`.
+Both require `Real integration: pending` and explicit
+`<task-id>-real-api-integration-verify` follow-up; it is not auto-created/executed.
 
 Do not edit files. Do not claim complete when review is not pass or a required check
 is failed, not-run, blocked, unavailable, stale, or contradicted.

package/skills/frontend-verification/references/verification-checklist.md

@@ -3,19 +3,26 @@
 ## Static And Behavior Evidence
 
 - Required type/compile, lint/format, build, schema/client, browser/e2e/manual checks ran.
+- Lint is recorded as `passed | baseline-debt | failed | unavailable`.
+  `baseline-debt` cites `frontend-lint-baseline-v1` and
+  `frontend-lint-assessment-v1`, writer changed files, tolerated diagnostic count,
+  command identity, and raw output hashes; it is never labeled passed.
+- Every remaining lint diagnostic is on an unchanged file and matches the
+  writer-preceding baseline. Changed-file diagnostics, new unmatched diagnostics,
+  command drift, timeout, worktree mutation, or unparseable output fail closed.
+- Typecheck, build, and test are fully passed; none accepts baseline debt.
 - Generated output was authorized; tests cover changed logic, flows, and regressions.
-- Fixed DAG entrypoints prove selected-strategy behavior and applicable loading/empty/error/success/disabled/permission/retry/boundary states.
+- Fixed entrypoints prove selected-strategy behavior and applicable UI states.
 - Mock-specific checks cover service/handler/schema/fixtures; behavior evidence separately proves page consumption.
 - Mock activation is explicit/non-production; a default-real-path build with Mock off proves the real request remains default.
-- `not-needed` has real/no-remote evidence, or default-auto skipped-Mock rationale with Real Integration Gap preserved when no project Mock capability exists.
+- `not-needed` has real/no-remote evidence or a default-auto skipped-Mock rationale.
 - Mock-backed evidence is frontend-only and never satisfies real API integration.
 
 ## Design And Component Evidence
 
-- Claims cite two parallel sources: knowledge-base retrieval and
-  `<repoRoot>/openspec/**`.
-- Evidence records query/source/time for knowledge base plus openspec search terms, paths, headings, and applied rules for both.
-- Relevant `openspec/` matches satisfy source availability; missing both sources blocks explicit compliance or required design decisions.
+- Claims cite knowledge-base, OpenSpec, and `<repoRoot>/ai_workspace/` sources.
+- Evidence records query/source/time, local-spec terms, paths, headings, and rules.
+- OpenSpec or `ai_workspace/` matches satisfy source availability; none blocks required design decisions.
 
 ## Status
 
@@ -25,7 +32,8 @@
 - `blocked`: a prerequisite prevented execution.
 - `unavailable`: tool, environment, connector, or source was absent.
 
-Only passed satisfies a required check. Other optional statuses remain disclosed risks.
+Only passed satisfies a required check. For lint alone, evidence-backed
+`baseline-debt` may continue as explicit debt; it replaces no other check.
 
 ## Closeout Checks
 
@@ -35,26 +43,6 @@ Only passed satisfies a required check. Other optional statuses remain disclosed
 - If only Mock evidence exists, report `Frontend status: mock-validated` and `Real integration: pending`, with actual API verification follow-up.
 - If default `auto` skipped Mock and no real API evidence exists, report `Frontend status: locally-validated` and `Real integration: pending`.
 
-```markdown
-## Changes
-- ...
-
-## Verification Evidence
-| Check | Command or source | Status | Evidence |
-|---|---|---|---|
-| ... | ... | passed | ... |
-
-## Mock Decision / Mock Files / Mock Verification / Production Boundary
-- Status: `passed | failed | not-required | blocked | unavailable`
-
-## Review Result
-- Verdict: `VERDICT: pass`
-
-## Known Risks
-- ...
-
-## Follow-up
-- None.
-```
-
-If review is not pass or a required check is not passed, describe the task as incomplete and list concrete follow-up.
+Output uses Changes, Verification Evidence, Mock Decision/Files/Verification,
+Production Boundary, Review Result, Known Risks, and Follow-up headings. If review is
+not pass or a required check fails, describe the task as incomplete with follow-up.

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

@@ -326,6 +326,8 @@ loop-agent dag resume --run-id <run-id>                  # approve 后继续
 - operator 聚焦最新 paused run 用 `dag report --paused-latest`（等同 `--lifecycle paused --latest`；勿与显式 `--lifecycle` 并用）。
 - 需 operator 关注的 run 用 `dag report --failed-only`、`--latest`、`--action <recovery-action>` 收窄。category→action 映射见 `ai_workspace/loop-agent/agent-dag-recovery-playbook.md`。
 - 只读扫描 `.harness/dag-runs/` 下所有 run 的生命周期 health issue 与建议 action 用 `dag doctor`（`advisoryOnly: true`；不 mutate facts）。
+- `dag status` / `dag doctor` 的 runner heartbeat 只表示 lease；Pi meaningful progress 由 Provider/tool/output 活动决定。节点可显示 `quiet`、`suspected-stall`、`probing` 或 `needs-attention`，不要仅凭运行时长手工结束。
+- Pi 默认 4h absolute max，`agent-worker` 默认不设置外层 `run-dag` wall-clock；显式 `worker.timeout_ms` 仍是 hard timeout。`termination-unconfirmed` 表示旧 attempt 的退出无法确认，禁止自动 retry，先保留现场并完成 operator 对账。
 - approve/resume 前用 `dag status --run-id <id>` 看单次 lifecycle、`approvalFlow`、`hasHumanApproval`。
 - lifecycle、raw status 与 liveness 冲突时先用 `dag reconcile-run --run-id <id>` 只读检查。只有 runner 已证明停止且 operator 明确给出 `supersede|abandon` 与 reason 时才允许收口；它保存原始 state，不把未执行节点标成成功。
 - task status、source/artifacts、DAG outcome、verification 记录可能 drift 时用 `dag reconcile-tasks --glob '<pattern>'`。默认仅报告；`--patch` 显式且不能伪造 verification evidence。

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

@@ -19,9 +19,9 @@
 前端专用链保留独立 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。
 
 
-> Backend-test Markdown-first：先由确定性环境 Shell 检查 clean env 中 Python/pytest、常见配置、conftest/fixture、test root、server entry 和 HTML renderer，失败时不消耗模型调用。随后 Pi 生成中文 README 索引与模块用例卡片并独立 Review `testcase/md/**`，Shell 校验 Case ID、AC/source traceability、中文或历史英文分节、步骤、可断言预期与 secret 安全；pytest writer 仅转换最终 Markdown，不重读 `source/**`。traceability 同时支持模块级函数和 pytest 测试类方法；pytest 只运行一次，生成 JUnit，并把 Markdown 名称/场景/脚本映射与同一 JUnit 合成为逐条中文 self-contained HTML 主报告和 Markdown facts。最终 Pi 只解释事实并生成 Markdown 报告和 L-5 结论。active 流程不要求模型生成 backend-test 业务 JSON。
+> 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。
 
-显式专用 `taskKind` 保持兼容并优先于任务源分类。`backend-test` 选择固定 **8 个真实顶层节点**的 Markdown-first DAG：环境硬门、Markdown cases、独立 Review/修订、Markdown gate、pytest 转换、确定性 traceability、单次 pytest + JUnit/HTML/facts、最终 Markdown 报告与 L-5。历史 JSON contract/materializer 可继续读取旧 DAG，但新 runtime/template 不再生成模型业务 JSON。`knowledge-sync` 与 `knowledge-graph-bootstrap` 继续通过各自显式 taskKind 选择知识回写/图谱开荒 DAG。治理等级仍由 `minimal|standard|reviewed|supervised` 推断。
+显式专用 `taskKind` 保持兼容并优先于任务源分类。`backend-test` 选择固定 **8 个真实顶层节点**的 Markdown-first DAG：环境硬门、Markdown cases、独立 Review/修订、第 4 节点 advisory Markdown 校验、pytest 转换、第 6 节点 scoped advisory traceability、单次 pytest + JUnit/HTML/facts、最终 Markdown 报告与 L-5。历史 JSON contract/materializer 可继续读取旧 DAG，但新 runtime/template 不再生成模型业务 JSON。`knowledge-sync` 与 `knowledge-graph-bootstrap` 继续通过各自显式 taskKind 选择知识回写/图谱开荒 DAG。治理等级仍由 `minimal|standard|reviewed|supervised` 推断。
 
 ### DAG workflow 层级