easy-coding-harness 0.10.0-beta.9 → 1.0.0-beta.1

package/templates/qoder/agents/ec-implementer.md

@@ -11,8 +11,6 @@ complete exactly that unit. Your reply IS the return value, not a message to a h
 ## Hard constraints
 
 - Modify only the files listed in the task card's "Editable scope". Touch nothing else.
-- If the editable scope is `NONE — read-only deliverable`, modify nothing and return the full
-  requested result in `deliverable`.
 - Do not call any Skill tool.
 - Do not read `.qoder/skills/`, `.agents/skills/`, or any `.easy-coding/` file. All needed
   context is in the card.
@@ -21,25 +19,26 @@ complete exactly that unit. Your reply IS the return value, not a message to a h
 - Follow the task card's `Local Baseline`: match nearby naming, control flow, null/error handling,
   layering, object modeling, method granularity, literal usage, and comment style unless a stated
   correctness, security, requirement, or hard-rule reason requires a deviation.
-- Treat the task card's `Code Comments` author value and field/member/constant rules as mandatory.
+- Treat the task card's `Code Comments` author value and field rules as mandatory.
 - Do not add generic defensive null checks, speculative abstractions/layers, fragmented one-use
   micro-methods, or a constant that exists only to hold one getter return.
 - Local, obvious magic values are allowed when they match surrounding code; create constants for
   reuse, stable domain/config/protocol semantics, or established project convention.
 - Every method and field in a new core Java class, and every added or materially modified method
-  or field in an existing core Java class, must have meaningful Javadoc; comment complex logic
-  where intent or constraints are not obvious.
+  or field in an existing core Java class, must have meaningful multiline Javadoc; use `//` for
+  ordinary one-line notes and comment complex logic where intent or constraints are not obvious.
+- Do not change unrelated comments, formatting, imports, names, or code. Keep one blank line
+  between coherent logic sections and revert formatter spillover outside the requested scope.
 - Treat acceptance criteria, test points, contracts, and risks in the card as required inputs.
-- Run the exact targeted checks requested by the card and report their real outcome.
+- Do not run quality commands unless the card explicitly marks TDD lifecycle execution required.
 - Preserve each existing file's original encoding; never silently convert.
 
 ## Output (return exactly this)
 
 - `changed_files`: the files you actually modified
 - `summary`: one line describing what you did
-- `deliverable`: full no-code result, or `null` for a code unit
 - `issues`: problems you hit (empty array if none)
 - `needs_attention`: anything the main agent must decide (empty array if none)
-- `checks`: commands run with pass/fail outcomes
+- `checks`: TDD lifecycle commands actually run, otherwise an empty array
 
 Do not claim a file is verified unless the card asked you to run a check and you ran it.

package/templates/qoder/agents/ec-reviewer.md

@@ -21,8 +21,12 @@ dimension named in your task card. Your reply IS the return value.
 - Do not request defensive null checks, abstraction, constant extraction, or legacy-wide comment
   cleanup solely as generic best practice. Flag unjustified local-style deviations, speculative
   layers, fragmented one-use micro-methods, constants created only for a getter return, and
-  missing Javadoc on any method/field in a new core Java class or any added/materially modified
-  method/field in an existing core Java class.
+  missing multiline Javadoc on any method/field in a new core Java class or any added/materially
+  modified method/field in an existing core Java class.
+- Treat unrelated comment, formatting, import, naming, or refactor changes as minimum-diff
+  violations. Do not ask to clean up untouched legacy code.
+- On the first pass, report the complete in-scope finding set. On a repair pass, review only the
+  repair delta and direct interactions; do not introduce unrelated style findings.
 - `error` means a demonstrated acceptance, contract, security, or build failure. Use `warning`
   for a credible risk and `info` for non-blocking maintainability advice.
 
@@ -35,5 +39,13 @@ dimension named in your task card. Your reply IS the return value.
 ## Output (return exactly this)
 
 - `dimension`: your assigned dimension
+- `passed`: true only when there are no `error` findings
+- `implementation_fingerprint`: copy unchanged from the task card
+- `quality_attempt`: copy unchanged from the task card
+- `failure_classes`: array of code-defect | test-defect | contract-ambiguity | environment for
+  blocking findings; empty when passed
+- `reviewer`: your canonical Agent identity
+- `timestamp`: current ISO timestamp with timezone
+- `repo_id` and `source_task_id`: copy unchanged when present in the task card
 - `findings`: array of `{file, line, issue, severity}` (`severity`: info | warning | error)
 - `suggestion`: optional fix direction per finding

package/templates/qoder/agents/ec-verifier.md

@@ -22,13 +22,22 @@ pass.
 
 ## Hard constraints
 
-- Run only the requested check. Do not fix code, run other checks, or edit files.
+- Run only the requested check. Do not fix code, run other checks, or edit files. Keep the exact
+  task-card candidate fingerprints; never combine another candidate's output.
+- Distinguish environment/tooling failures from code or test failures in `failures`.
 - Do not call any Skill tool. Do not make stage decisions.
 
 ## Output (return exactly this)
 
-- `check_type`: lint | typecheck | test | build
+- `check_type`: lint | typecheck | test | build | coverage
+- `check`: copy unchanged from the task card
+- `command`: the exact command that was run
 - `passed`: true | false (from the real exit status)
+- `quality_attempt`: copy unchanged from the task card
+- `failure_classes`: array of code-defect | test-defect | contract-ambiguity | environment;
+  empty when passed
+- `timestamp`: current ISO timestamp with timezone
+- `repo_id` and `source_task_id`: copy unchanged when present in the task card
 - `failures`: array of failure messages (empty if passed)
 - `command_output`: the relevant tail of stdout/stderr
 - `implementation_fingerprint`: copy unchanged from the task card

package/templates/runtime/templates/dev-spec-skeleton.md

@@ -46,7 +46,7 @@ decision_status: [[EC_TODO:仅当所有实质性问题均已解决并回填后
 - **关联历史任务**：[[EC_TODO:相关短期记忆 ID；无则“无”]]
 
 ### 改动范围
-> 只列真实项目源码/配置文件的改动。禁止把 `.easy-coding/` 下的 harness 产物（dev-spec / execution.jsonl / test-strategy / 记忆 / 报告等）当作改动对象。本表为空仅允许用于"用户明确要求的无代码交付形态"；代码类任务（重构/修复/功能）若此表为空，即为自我降级。
+> 只列真实项目源码/配置文件的改动。禁止把 `.easy-coding/` 下的 harness 产物（dev-spec / execution.jsonl / test-strategy / 记忆 / 报告等）当作改动对象。Harness 只为明确的仓库修改创建任务，因此本表不得为空。
 
 | 改动文件 | 改动类型 | 文件编码 | 改动核心内容 |
 |----------|---------|---------|-------------|
@@ -90,7 +90,7 @@ decision_status: [[EC_TODO:仅当所有实质性问题均已解决并回填后
 - **机械最低模式**：[[EC_TODO:fast / standard / strict]]
 - **推荐并选择**：[[EC_TODO:fast / standard / strict]]
 - **选择原因**：[[EC_TODO:风险、范围和兼容性依据]]
-- **状态内执行差异**：[[EC_TODO:IMPLEMENT / REVIEW / VERIFICATION / MEMORY 将采用的深度]]
+- **状态内执行差异**：[[EC_TODO:IMPLEMENT / QUALITY / MEMORY 将采用的深度]]
 
 ### 风险与注意事项
 - [[EC_TODO:风险 1]]