@tea-agent/loop-agent 0.42.0-next.9 → 0.43.0-next.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +65 -59
- package/dist/application/dag/run-dag.js +3 -2
- package/dist/application/task-lifecycle/advance.js +9 -4
- package/dist/build-stamp.json +3 -3
- package/dist/cli/program.js +1 -1
- package/dist/commands/dag-rerun-task.js +2 -0
- package/dist/commands/task-source-prepare.js +3 -1
- package/dist/executors/dag-pi-executor.js +1514 -175
- package/dist/executors/pi-extension-resolver.js +14 -2
- package/dist/executors/shell-executor.js +131 -54
- package/dist/shared/dag-failure-category.js +6 -0
- package/dist/task/contract/apply.js +36 -2
- package/dist/task/source-prepare/parse-intent.js +7 -0
- package/dist/worker/console/chat/chat-event-store.js +4 -2
- package/dist/worker/console/chat/pi-runtime.js +45 -2
- package/dist/worker/console/chat/resource-loader.js +4 -1
- package/dist/worker/console/chat/routes.js +28 -12
- package/dist/worker/console/chat/sdd-data-alignment.js +13 -2
- package/dist/worker/console/chat/session-store.js +5 -1
- package/dist/worker/console/chat/subagents/agent-tool.js +62 -0
- package/dist/worker/console/chat/subagents/explore-agent.js +169 -0
- package/dist/worker/console/chat/subagents/index.js +5 -0
- package/dist/worker/console/chat/subagents/orchestrator.js +273 -0
- package/dist/worker/console/chat/subagents/tool-policy.js +53 -0
- package/dist/worker/console/chat/subagents/types.js +13 -0
- package/dist/worker/console/chat/tool-preview.js +10 -0
- package/dist/worker/console/chat/tools.js +11 -1
- package/dist/worker/console/chat/turn-process.js +1 -0
- package/dist/worker/console/interview/tools.js +1 -0
- package/dist/worker/console/static/assets/{abnfDiagram-N423BO3Z-C6n9_m0P.js → abnfDiagram-N423BO3Z-B0Q0nClf.js} +1 -1
- package/dist/worker/console/static/assets/{arc-DQh-IfZ1.js → arc-DCPjC19G.js} +1 -1
- package/dist/worker/console/static/assets/{architectureDiagram-T3A2C74G-54NnrwUC.js → architectureDiagram-T3A2C74G-CP5n9jmG.js} +1 -1
- package/dist/worker/console/static/assets/{blockDiagram-VBNYF7ZC-pivRALGK.js → blockDiagram-VBNYF7ZC-CmaWi_Wg.js} +1 -1
- package/dist/worker/console/static/assets/{c4Diagram-5PPSVZJV-BR7OV2NJ.js → c4Diagram-5PPSVZJV-Ct5tcMfZ.js} +1 -1
- package/dist/worker/console/static/assets/channel-DAS07MdS.js +1 -0
- package/dist/worker/console/static/assets/{chunk-2GRJ4B5K-B1Aq6BcK.js → chunk-2GRJ4B5K-C0osm1Zf.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-2Q5K7J3B-CbdU0rjo.js → chunk-2Q5K7J3B-CDWviED7.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-5RXB4S5H-Dqi2GJeD.js → chunk-5RXB4S5H-mtSk1-j7.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-5VM5RSS4-BYn1Hu4R.js → chunk-5VM5RSS4-D5J9PHC7.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-6Q2QTUOP-DRLjDL0k.js → chunk-6Q2QTUOP-Begg4WAa.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-GF5L2VYU-CY9Xx2jV.js → chunk-GF5L2VYU-sF1AEy7T.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-JWPE2WC7-BNCZs7_z.js → chunk-JWPE2WC7-BqbsWXZb.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-KBJHAD2P-DZ8AStLL.js → chunk-KBJHAD2P-BKJrPcJ6.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-RYQCIY6F-DsxjYrzz.js → chunk-RYQCIY6F-CcwNMRho.js} +1 -1
- package/dist/worker/console/static/assets/{chunk-XXDRQBXY-Ddx1KC1l.js → chunk-XXDRQBXY-BEJi3iIs.js} +1 -1
- package/dist/worker/console/static/assets/classDiagram-JCYQIIEL-Cwk-5jiW.js +1 -0
- package/dist/worker/console/static/assets/classDiagram-v2-OCEON4UE-Cwk-5jiW.js +1 -0
- package/dist/worker/console/static/assets/{cose-bilkent-JH36ORCC-W9TveCnK.js → cose-bilkent-JH36ORCC-DRLgTvVu.js} +1 -1
- package/dist/worker/console/static/assets/{cynefin-VYW2F7L2-l9j_ztZH.js → cynefin-VYW2F7L2-BoAVG3cs.js} +1 -1
- package/dist/worker/console/static/assets/{cynefinDiagram-MW4NZA55-BMJMKi4G.js → cynefinDiagram-MW4NZA55-Bzol06hR.js} +1 -1
- package/dist/worker/console/static/assets/{dagre-VZM6K2ZE-Bb4mG9pH.js → dagre-VZM6K2ZE-UmliJM77.js} +1 -1
- package/dist/worker/console/static/assets/{diagram-7IWD3JNH-BMgL_Qv0.js → diagram-7IWD3JNH-BWLcJkFo.js} +1 -1
- package/dist/worker/console/static/assets/{diagram-B4RE2ZJO-Bvo2T4OQ.js → diagram-B4RE2ZJO-CgApOm-O.js} +1 -1
- package/dist/worker/console/static/assets/{diagram-LBJQPF4R-_5kWRN9c.js → diagram-LBJQPF4R-Bh3RgTLs.js} +1 -1
- package/dist/worker/console/static/assets/{diagram-Q27KOJAE-DqdMrltM.js → diagram-Q27KOJAE-Dsh-D5nE.js} +1 -1
- package/dist/worker/console/static/assets/{diagram-UB23O5K3-CDDYsNkp.js → diagram-UB23O5K3-Dkbbpcpb.js} +1 -1
- package/dist/worker/console/static/assets/{ebnfDiagram-BXEA7PRR-c4nfnZUV.js → ebnfDiagram-BXEA7PRR-3EBaA3t3.js} +1 -1
- package/dist/worker/console/static/assets/{erDiagram-JOGREHBK-DnkUcNMs.js → erDiagram-JOGREHBK-Bq2Dc5ok.js} +1 -1
- package/dist/worker/console/static/assets/{flowDiagram-UKHOOZJN-Dz0KGLZE.js → flowDiagram-UKHOOZJN-De7y55ha.js} +1 -1
- package/dist/worker/console/static/assets/{ganttDiagram-PKOTCBZU-Cj1t1uka.js → ganttDiagram-PKOTCBZU-fLiDbQRh.js} +1 -1
- package/dist/worker/console/static/assets/{gitGraphDiagram-DS77QQ5N-tp2FrBHd.js → gitGraphDiagram-DS77QQ5N-Du617mp1.js} +1 -1
- package/dist/worker/console/static/assets/index-C0O48S_P.js +449 -0
- package/dist/worker/console/static/assets/index-CzKf4U8P.css +1 -0
- package/dist/worker/console/static/assets/{infoDiagram-6WML65LV-DQwJS8DH.js → infoDiagram-6WML65LV-BwmlF-XP.js} +1 -1
- package/dist/worker/console/static/assets/{ishikawaDiagram-WSZJBQD7-eimCQWD4.js → ishikawaDiagram-WSZJBQD7-zsGtS59u.js} +1 -1
- package/dist/worker/console/static/assets/{journeyDiagram-NVQOT4AX-Dd9Gbwgv.js → journeyDiagram-NVQOT4AX-DTTPTe3f.js} +1 -1
- package/dist/worker/console/static/assets/{kanban-definition-27J2QSJJ-Qve3cyft.js → kanban-definition-27J2QSJJ-BkXg9aP-.js} +1 -1
- package/dist/worker/console/static/assets/{linear-UXKSe36Z.js → linear-7U2ue5IE.js} +1 -1
- package/dist/worker/console/static/assets/{mermaid.core-CWhj4JXN.js → mermaid.core-BUuGHmWO.js} +5 -5
- package/dist/worker/console/static/assets/{mindmap-definition-FAOFIHXS-yTcwf4SJ.js → mindmap-definition-FAOFIHXS-7q6fX0Sv.js} +1 -1
- package/dist/worker/console/static/assets/{pegDiagram-VL7TDLO6-_7qToaZP.js → pegDiagram-VL7TDLO6-CkQPJN55.js} +1 -1
- package/dist/worker/console/static/assets/{pieDiagram-7S7Q4E2Y-CXmrKmDm.js → pieDiagram-7S7Q4E2Y-CCal_tfX.js} +1 -1
- package/dist/worker/console/static/assets/{quadrantDiagram-CIZ2JOQS-hMmrJyaS.js → quadrantDiagram-CIZ2JOQS-B7bpxyAZ.js} +1 -1
- package/dist/worker/console/static/assets/{railroadDiagram-AXF67PYL-BXw8tCBe.js → railroadDiagram-AXF67PYL-CJmww7D-.js} +1 -1
- package/dist/worker/console/static/assets/{requirementDiagram-LRYGKXZP-BmjgnLZl.js → requirementDiagram-LRYGKXZP-D6ldWJEv.js} +1 -1
- package/dist/worker/console/static/assets/{sankeyDiagram-W5VNT64P-Bj77SPpN.js → sankeyDiagram-W5VNT64P-VGh33I9e.js} +1 -1
- package/dist/worker/console/static/assets/{sequenceDiagram-SI44F4Z6-B2FDVysL.js → sequenceDiagram-SI44F4Z6-CCkDrIjU.js} +1 -1
- package/dist/worker/console/static/assets/{sizeCapture-X5ZJPWSS-UChNY9ZZ.js → sizeCapture-X5ZJPWSS-NC8f5Otb.js} +1 -1
- package/dist/worker/console/static/assets/{stateDiagram-OKZ733FA-wbAEkbd7.js → stateDiagram-OKZ733FA-_92ezZdF.js} +1 -1
- package/dist/worker/console/static/assets/stateDiagram-v2-UEYNNEHI-DyJg5gzW.js +1 -0
- package/dist/worker/console/static/assets/{swimlanes-SLNWSIFB-DCEkU8HR.js → swimlanes-SLNWSIFB-BdUCGtbP.js} +2 -2
- package/dist/worker/console/static/assets/swimlanesDiagram-ULZ7WXOC-B1cw_0Uy.js +8 -0
- package/dist/worker/console/static/assets/{timeline-definition-Z64GVDOM-BGp7H06U.js → timeline-definition-Z64GVDOM-CdD1H8ia.js} +1 -1
- package/dist/worker/console/static/assets/{vennDiagram-T6HMQDX7-DsCIQuWR.js → vennDiagram-T6HMQDX7-Dkdk3oFo.js} +1 -1
- package/dist/worker/console/static/assets/{wardleyDiagram-T6FBY63Y-cRZLP4Xe.js → wardleyDiagram-T6FBY63Y-CKu2uPPY.js} +1 -1
- package/dist/worker/console/static/assets/{xychartDiagram-ELKLHX3M-CP0xLR9Y.js → xychartDiagram-ELKLHX3M-ClqAnuG8.js} +1 -1
- package/dist/worker/console/static/index.html +2 -2
- package/dist/worker/console/static-src/chat-view-types.js +1 -1
- package/dist/worker/console/static-src/operator-chat/chat-sse-events.js +23 -0
- package/dist/worker/console/static-src/operator-chat/pending-user-message.js +32 -0
- package/dist/worker/console/static-src/operator-chat/tools-catalog.js +21 -2
- package/dist/worker/console/static-src/operator-chat/turn-stream-controller.js +2 -0
- package/dist/worker/console/static-src/operator-chat/useChatSessions.js +2 -0
- package/dist/worker/console/static-src/operator-chat/useChatStream.js +30 -14
- package/dist/worker/console/static-src/operator-chat/useChatThread.js +133 -5
- package/dist/worker/console/static-src/shell/workspace-route.js +4 -0
- package/dist/worker/observe/static/constants.js +22 -22
- package/dist/worker/observe/static/dag-context-reason-labels.js +19 -0
- package/dist/worker/observe/static/dag-history-labels.js +1 -0
- package/dist/worker/observe/static/dag-inspector-humanize.d.ts +16 -0
- package/dist/worker/observe/static/dag-inspector-humanize.js +339 -0
- package/dist/worker/observe/static/dag-node-purpose.js +10 -10
- package/dist/worker/observe/static/index.html +4 -4
- package/dist/worker/observe/static/prompt-restart-candidates.js +4 -2
- package/dist/worker/observe/static/relations.js +5 -5
- package/dist/worker/observe/static/styles.css +171 -0
- package/dist/worker/observe/static/views/dag-graph.js +1 -1
- package/dist/worker/observe/static/views/dag-inspector.js +329 -174
- package/dist/worker/observe/static/views/dag.js +16 -12
- package/dist/worker/observe/static/views/session-timeline.js +5 -3
- package/dist/workflows/dag/backend-test-plan-protocol.js +104 -0
- package/dist/workflows/dag/dag-retry-schema.js +3 -0
- package/dist/workflows/dag/frontend-contract-facts.js +130 -0
- package/dist/workflows/dag/frontend-design-policy.js +101 -16
- package/dist/workflows/dag/frontend-implementation-contract.js +410 -41
- package/dist/workflows/dag/frontend-plan-render.js +13 -2
- package/dist/workflows/dag/frontend-prewrite-gate.js +1 -1
- package/dist/workflows/dag/frontend-recovery-controller.js +25 -1
- package/dist/workflows/dag/frontend-recovery-plan.js +4 -1
- package/dist/workflows/dag/frontend-recovery-run.js +142 -16
- package/dist/workflows/dag/frontend-risk.js +2 -0
- package/dist/workflows/dag/frontend-shadow-dual-write.js +17 -1
- package/dist/workflows/dag/frontend-shape.js +16 -6
- package/dist/workflows/dag/frontend-test-execution-evidence.js +48 -0
- package/dist/workflows/dag/frontend-typed-event-store.js +3 -0
- package/dist/workflows/dag/frontend-verification-trace.js +38 -4
- package/dist/workflows/dag/frontend-writer-admission.js +2 -2
- package/dist/workflows/dag/init-hybrid.js +57 -28
- package/dist/workflows/dag/node-execution.js +201 -85
- package/dist/workflows/dag/recovery-lease.js +106 -16
- package/dist/workflows/dag/rerun-feedback.js +1 -0
- package/dist/workflows/dag/rerun-plan.js +90 -4
- package/dist/workflows/dag/rerun-run.js +28 -6
- package/dist/workflows/dag/rerun-task.js +221 -18
- package/dist/workflows/dag/retry-policy.js +27 -10
- package/dist/workflows/dag/runner-exit-diagnostics.js +125 -0
- package/dist/workflows/dag/runner.js +220 -18
- package/dist/workflows/dag/structured-output-repair.js +4 -1
- package/dist/workflows/dag/types.js +4 -3
- package/dist/workflows/dag/validate.js +10 -8
- package/dist/workflows/dag/workspace-checkpoint.js +66 -0
- package/docs/operations/README.md +1 -0
- package/docs/templates/agent-dag.schema.json +2 -2
- package/docs/templates/backend-test-dag.json +6 -4
- package/docs/templates/frontend-implementation-contract.schema.json +34 -2
- package/harness.json +1 -1
- package/package.json +4 -5
- package/skills/frontend-plan/SKILL.md +14 -1
- package/skills/frontend-plan/references/decision-contract.md +101 -5
- package/skills/frontend-plan/references/design-decisions.md +32 -0
- package/dist/worker/console/static/assets/channel-DsZxrgqe.js +0 -1
- package/dist/worker/console/static/assets/classDiagram-JCYQIIEL-CuToPeGV.js +0 -1
- package/dist/worker/console/static/assets/classDiagram-v2-OCEON4UE-CuToPeGV.js +0 -1
- package/dist/worker/console/static/assets/index-D9Sc0f0y.js +0 -449
- package/dist/worker/console/static/assets/index-DDQc5a50.css +0 -1
- package/dist/worker/console/static/assets/stateDiagram-v2-UEYNNEHI-yPoT19ft.js +0 -1
- package/dist/worker/console/static/assets/swimlanesDiagram-ULZ7WXOC-VWdarchG.js +0 -8
|
@@ -148,7 +148,7 @@
|
|
|
148
148
|
"validate-backend-test-environment-shell"
|
|
149
149
|
],
|
|
150
150
|
"complexity": "MED",
|
|
151
|
-
"subtask_prompt": "This is a required plan-generation node. Read only the strict read set and return the complete Markdown plan in the assistant response. The runtime persists the response as a run-owned Harness artifact named generate-backend-md-plan-pi/plan.md. Do not write testcase/md/README.md or any project file; module case cards are written by downstream sharded nodes.\n\nOutput budget protocol (hard, max output <=16K per turn): Never paste full Matrix, case bodies, or source text into assistant chat. README holds only Scope+Matrix+module index; never inline full case bodies. If a Completeness Gate / OUTPUT_LIMIT_RECOVERY retry is injected, continue only listed target paths.\n\nReturn the complete plan as plain Markdown. Do not emit JSON or code fences. The plan must contain the exact English protocol headings ## Coverage Scope, ## Coverage Matrix, ## Scenario Partitions when applicable, and ## Module Index. Never translate those headings into 覆盖范围/覆盖矩阵/场景分区/模块索引.\n\nRead the upstream environment report only through the strict read set. Generate the Markdown-first backend test plan; it will be persisted under the current DAG run's Harness artifacts, not under testcase/md/.\n\nWrite human-readable content in Simplified Chinese by default. Keep English protocol literals exact: section headings, table headers, Partition IDs, TP IDs, Case IDs, HTTP methods, paths, field names, enum values, commands, filenames, code symbols and source citations. Never translate ## Module Index into ## 模块索引.\n\nCreate the concise plan entry page: test objective, target/environment, isolation/cleanup, module summary and a linked case index table with Case ID, Chinese case name, scenario type, endpoint and expected status/result. Avoid repeating every case body in the plan artifact.\n\nBefore the Coverage Matrix, write a mandatory machine-readable `## Coverage Scope` section in the plan artifact using exactly `| Field | Value |`, immediately followed by the separator row `|---|---|`, and these six unique rows: `Change Classification`, `Coverage Policy`, `Affected Operations`, `Affected Rule Keys`, `Regression Floor`, `Scope Evidence`. Always set `Change Classification` to `new-operation` and `Coverage Policy` to `full-contract`; do NOT reason about whether operations are new or existing. Cover all in-scope rules from the requirement document at full depth; treat the product requirement as the coverage baseline and use API contract evidence (fields/status/enum/boundary/format) to supplement scenario dimensions. Scope is limited to operations/rules the requirement document (or its referenced API contract) explicitly describes; do not expand to unrelated operations that the requirement does not mention. List affected operations exactly as `METHOD /path`, stable rule keys separated by semicolons, and precise source pointers as Scope Evidence.\n\nCoverage depth is full over the in-scope rules: fully cover every documented status, request/response field rule, requiredness, enum, boundary, format, auth and business state of each affected operation the requirement describes, but do not re-test unrelated operations the requirement does not mention. Inspect shared validator/helper/DTO/query builder evidence and expand Affected Operations when the same affected path can affect them; unresolved impact stays visible as GAP/CONFLICT.\n\nBefore writing cases, build the mandatory machine-readable Coverage Matrix inside the plan artifact itself. Its section heading line must be exactly `## Coverage Matrix` with no numeric prefix/suffix; never place the canonical Matrix only in a module file. Use this exact header: `| Rule Key | Priority | Source | Endpoint/Field | Dimension | Rule | Required Test Points | Case IDs | Status |`. Every data row must contain exactly 9 pipe-delimited cells and must never omit `Dimension`; use concise dimensions such as requirement, operation, response-status, requiredness, enum, boundary, format, business-state or error. Use only P0/P1/P2 and COVERED/PARTIAL/GAP/CONFLICT. Use stable `TP-<UPPERCASE-HYPHENATED-ID>` test points separated by semicolons.\n\nEach Rule Key must appear in exactly one Matrix row. Preserve each AC/REQ/BR Rule Key as one row; if one product rule spans multiple dimensions, use a concise composite Dimension in that single row instead of duplicating the key. Derive OpenAPI Rule Keys exactly as the deterministic analyzer does: operation token is `<HTTP-METHOD>-<PATH>` with braces removed and every non-alphanumeric run replaced by a hyphen, uppercase (for example POST `/api/resource-notes` → `POST-API-RESOURCE-NOTES`); response statuses use `API-<OPERATION>-RESPONSE-STATUS`; body/parameter fields use `API-<OPERATION>-<FIELD>-REQUIRED|ENUM|MIN-LENGTH|MAX-LENGTH|MINIMUM|MAXIMUM|PATTERN|FORMAT`. Do not invent aliases such as API-CREATE-FIELDS when a deterministic key applies.\n\nCoverage priority is strict inside the declared scope: P0 product requirements/task hard constraints always remain in scope; P1 exhaustively supplements documented operations, fields, business rules, statuses and errors only for Affected Operations; P2 adds bounded protocol robustness only when it is relevant to the change and does not invent product behavior. Coverage percentages describe the declared affected scope, never whole-API completeness unless every operation is explicitly listed. Conflicts or undefined expectations must stay visible as GAP/CONFLICT with precise source pointers, never guessed.\n\nFor uniqueness/lifecycle rules cover absent, active-existing, deleted-existing, create-delete-recreate, restore-then-recreate and documented scope/case-normalization states. For every enum cover every valid value plus bounded invalid equivalence classes (unknown, case variant, whitespace, empty, null/missing and wrong types as applicable). For every length/number rule cover min-1, min, nominal, max and max+1. For format rules cover each allowed class separately plus a valid mixed value, and representative forbidden classes including uppercase, internal/leading/trailing whitespace, tab/newline, unsupported punctuation, slash, emoji or control characters when the source contract supports that expectation.\n\nMandatory module layout contract: first inspect the PRIMARY requirement for an explicit list of required Markdown/Python output path pairs. When explicit paths are present, they are authoritative `explicit-user-layout`: reproduce their exact filenames, count and one-to-one pairs in Module Index; do not rename, merge, split, omit or add a module from reference/example scripts. Only when the primary requirement has no explicit file layout may you derive the smallest `business-resource-layout`. Existing examples, historical regression functions and shared setup may add evidence/assertions to an existing required module, but never create an extra physical module by themselves. A reference-only `resp_regression`, positive/negative/boundary/error/response module is forbidden. The Module Stem cell must contain only the plain filename stem; never put Markdown link syntax or a path in that cell.\n\nInclude exactly one `## Module Index` table with this exact header: `| Module Stem | Business Resource | Owned Operations | Owned Rule Keys | Case IDs | Split Reason | Markdown Path | Pytest Path |`. Use canonical relative links `[label](./<stem>.md)` inside the Markdown Path cell followed by the resolved `${layout.markdownDir}/<stem>.md` path. Split Reason is exactly one of `explicit-user-layout`, `primary-business-resource`, `independent-business-resource`, or `output-budget`. Group by stable business resource/domain, not by CRUD operation, AC, parameter/field axis, scenario type or regression purpose: one resource's list/detail/create/update/delete and its filters/response assertions/regression floor belong in one module. Multiple modules owning the same exact `METHOD /path` are forbidden unless every such row is `explicit-user-layout` from primary-requirement path pairs or has a documented `output-budget` proof. Keep the total module count at the smallest safe value and never exceed 8 modules. Name model-derived modules with stable lowercase business stems such as `health` or `resource_notes`; explicit-user-layout preserves the primary requirement filename stem even when it is more specific. Do not use priority-only stems `p0`, `p1` or `p2`; Priority belongs only in the Coverage Matrix. Pure hexadecimal/hash-like opaque stems and test-purpose-only stems are forbidden. Do not use Case-ID-like module filenames. The relative link target, Markdown Path, Pytest Path and downstream automation mapping must be one-to-one and exact; for model-derived modules the default pair remains `testcase/md/<module>.md` and `testcase/test_<module>.py`, while explicit-user-layout preserves the primary requirement paths. Do not hand-write a conflicting module count in prose; the Module Index row count is the only count truth.\n\nScenario Partitions (query/filter axes): inspect every affected GET/list operation for query/path parameters whose bound source documents a finite enum or classification domain. If at least one such axis exists, add exactly one machine-readable `## Scenario Partitions` section after the Coverage Matrix using exactly `| Partition ID | Operation | Axis | Domain | Required Slots | Expected by Slot | Bind Rule |` with the separator row and one row per eligible axis. If no affected axis has a source-backed finite domain, omit the entire `## Scenario Partitions` heading and section; do not emit an explanatory prose-only section. Partition ID is a stable `SP-<OPERATION>-<AXIS>` token; Domain must copy the legal values verbatim from the bound OpenAPI enum or requirement sentence (never guess), using bare semicolon-separated identifier values inside the single table cell (for example `ACTIVE; ARCHIVED`, with no Markdown backticks or prose); Required Slots must contain `each-value` and exactly one `not-in-set`, plus `omitted` only when the parameter is optional. Before returning, expand every declared partition into its complete deterministic exact slot ID set: one `TP-<Partition ID>-<VALUE-TOKEN>` per Domain value, `TP-<Partition ID>-OMITTED` only for an optional axis, and exactly one `TP-<Partition ID>-NOT-IN-SET`. Every expanded slot ID must appear verbatim in the binding Rule's `Required Test Points` cell and be assigned to concrete Case IDs in that same Coverage Matrix row; ordinary alias/family Test Points do not replace this inventory. Scheme A: Case count may be smaller than the enum count, but every exact slot still needs an independent variant Test Point and pytest.param id; never use SINGLE/MULTIPLE aliases as coverage. Expected by Slot states the documented expectation per slot kind (`domain-value`, `default-behavior`, `empty-result`/`excluded-result` when documented, or `GAP` when the source does not document the complement expectation — never invent 空列表/400). POST/PUT body field-validation enums stay in the Coverage Matrix as `TP-<FIELD>-ENUM-*` and MUST NOT get a Scenario Partition row. Do not create partitions for axes without a documented legal-value domain. Only GET/list query or path parameters whose bound source documents a finite enum or classification set may become a Scenario Partition. Do not create partitions for free-form strings, primary keys, required-or-optional-only parameters, or boundary/format-only axes. If an axis has no finite legal-value domain, do not declare a Partition row and do not invent NOT-IN-SET cases. Cross-axis combinations stay as ONE nominal Case; never declare a cross-axis cartesian partition.\n\nBefore finalizing README, calculate the predicted collected-item count as `sum(max(1, number of variant Test Points in each Case))`. If the task declares an item budget, the prediction must not exceed it. Reduce excess only by removing duplicate execution and converting same-request checkpoints to assertions; never drop required rules, boundaries, enums, operation-specific inputs, or business states. Record the prediction in README. Use only environment-supported fixtures/targets/isolation, record evidence gaps in Chinese, and do not emit JSON, pytest, or execute commands.\n\n## Derived task contract: 需求.md\n\n# Backend test\n- AC-001 proof\n\n## Authoritative reference index\n\n[]\n\nFor each index entry, use `readPath` for Pi read-tool calls and copy `path` exactly into Markdown Source References. Bound files under .harness/tasks/<taskId>/source/** are read-only inputs: reading them is allowed even though writing .harness/** is forbidden. Never resolve `path` relative to the repository root, search for substitutes, or fall back to docs/** when a bound read fails.\n\nRead only precise indexed references needed for AC/API/field/rule evidence; references remain authoritative over derived text.",
|
|
151
|
+
"subtask_prompt": "This is a required plan-generation node. Read only the strict read set and return the complete Markdown plan in the assistant response. Start the response with the final Markdown artifact immediately; never narrate analysis, reasoning, source summaries, or plans for producing the plan. The runtime persists the response as a run-owned Harness artifact named generate-backend-md-plan-pi/plan.md. Do not write testcase/md/README.md or any project file; module case cards are written by downstream sharded nodes.\n\nOutput budget protocol (hard, max output <=16K per turn): Emit the complete required section skeleton before filling long table rows, including exactly one Module Index table with at least one module row. Never paste full Matrix, case bodies, source text, analysis or reasoning into assistant chat. README holds only Scope+Matrix+module index; never inline full case bodies. If a Completeness Gate / OUTPUT_LIMIT_RECOVERY retry is injected, continue only listed target paths.\n\nReturn the complete plan as plain Markdown. Do not emit JSON or code fences. The plan must contain the exact English protocol headings ## Coverage Scope, ## Coverage Matrix, ## Scenario Partitions when applicable, and ## Module Index. Never translate those headings into 覆盖范围/覆盖矩阵/场景分区/模块索引.\n\nRead the upstream environment report only through the strict read set. Generate the Markdown-first backend test plan; it will be persisted under the current DAG run's Harness artifacts, not under testcase/md/.\n\nWrite human-readable content in Simplified Chinese by default. Keep English protocol literals exact: section headings, table headers, Partition IDs, TP IDs, Case IDs, HTTP methods, paths, field names, enum values, commands, filenames, code symbols and source citations. Never translate ## Module Index into ## 模块索引.\n\nCreate the concise plan entry page: test objective, target/environment, isolation/cleanup, module summary and a linked case index table with Case ID, Chinese case name, scenario type, endpoint and expected status/result. Avoid repeating every case body in the plan artifact.\n\nBefore the Coverage Matrix, write a mandatory machine-readable `## Coverage Scope` section in the plan artifact using exactly `| Field | Value |`, immediately followed by the separator row `|---|---|`, and these six unique rows: `Change Classification`, `Coverage Policy`, `Affected Operations`, `Affected Rule Keys`, `Regression Floor`, `Scope Evidence`. Always set `Change Classification` to `new-operation` and `Coverage Policy` to `full-contract`; do NOT reason about whether operations are new or existing. Cover all in-scope rules from the requirement document at full depth; treat the product requirement as the coverage baseline and use API contract evidence (fields/status/enum/boundary/format) to supplement scenario dimensions. Scope is limited to operations/rules the requirement document (or its referenced API contract) explicitly describes; do not expand to unrelated operations that the requirement does not mention. List affected operations exactly as `METHOD /path`, stable rule keys separated by semicolons, and precise source pointers as Scope Evidence.\n\nCoverage depth is full over the in-scope rules: fully cover every documented status, request/response field rule, requiredness, enum, boundary, format, auth and business state of each affected operation the requirement describes, but do not re-test unrelated operations the requirement does not mention. Inspect shared validator/helper/DTO/query builder evidence and expand Affected Operations when the same affected path can affect them; unresolved impact stays visible as GAP/CONFLICT.\n\nBefore writing cases, build the mandatory machine-readable Coverage Matrix inside the plan artifact itself. Its section heading line must be exactly `## Coverage Matrix` with no numeric prefix/suffix; never place the canonical Matrix only in a module file. Use this exact header: `| Rule Key | Priority | Source | Endpoint/Field | Dimension | Rule | Required Test Points | Case IDs | Status |`. Every data row must contain exactly 9 pipe-delimited cells and must never omit `Dimension`; use concise dimensions such as requirement, operation, response-status, requiredness, enum, boundary, format, business-state or error. Use only P0/P1/P2 and COVERED/PARTIAL/GAP/CONFLICT. Use stable `TP-<UPPERCASE-HYPHENATED-ID>` test points separated by semicolons.\n\nEach Rule Key must appear in exactly one Matrix row. Preserve each AC/REQ/BR Rule Key as one row; if one product rule spans multiple dimensions, use a concise composite Dimension in that single row instead of duplicating the key. Derive OpenAPI Rule Keys exactly as the deterministic analyzer does: operation token is `<HTTP-METHOD>-<PATH>` with braces removed and every non-alphanumeric run replaced by a hyphen, uppercase (for example POST `/api/resource-notes` → `POST-API-RESOURCE-NOTES`); response statuses use `API-<OPERATION>-RESPONSE-STATUS`; body/parameter fields use `API-<OPERATION>-<FIELD>-REQUIRED|ENUM|MIN-LENGTH|MAX-LENGTH|MINIMUM|MAXIMUM|PATTERN|FORMAT`. Do not invent aliases such as API-CREATE-FIELDS when a deterministic key applies.\n\nCoverage priority is strict inside the declared scope: P0 product requirements/task hard constraints always remain in scope; P1 exhaustively supplements documented operations, fields, business rules, statuses and errors only for Affected Operations; P2 adds bounded protocol robustness only when it is relevant to the change and does not invent product behavior. Coverage percentages describe the declared affected scope, never whole-API completeness unless every operation is explicitly listed. Conflicts or undefined expectations must stay visible as GAP/CONFLICT with precise source pointers, never guessed.\n\nFor uniqueness/lifecycle rules cover absent, active-existing, deleted-existing, create-delete-recreate, restore-then-recreate and documented scope/case-normalization states. For every enum cover every valid value plus bounded invalid equivalence classes (unknown, case variant, whitespace, empty, null/missing and wrong types as applicable). For every length/number rule cover min-1, min, nominal, max and max+1. For format rules cover each allowed class separately plus a valid mixed value, and representative forbidden classes including uppercase, internal/leading/trailing whitespace, tab/newline, unsupported punctuation, slash, emoji or control characters when the source contract supports that expectation.\n\nMandatory module layout contract: first inspect the PRIMARY requirement for an explicit list of required Markdown/Python output path pairs. When explicit paths are present, they are authoritative `explicit-user-layout`: reproduce their exact filenames, count and one-to-one pairs in Module Index; do not rename, merge, split, omit or add a module from reference/example scripts. Only when the primary requirement has no explicit file layout may you derive the smallest `business-resource-layout`. Existing examples, historical regression functions and shared setup may add evidence/assertions to an existing required module, but never create an extra physical module by themselves. A reference-only `resp_regression`, positive/negative/boundary/error/response module is forbidden. The Module Stem cell must contain only the plain filename stem; never put Markdown link syntax or a path in that cell.\n\nInclude exactly one `## Module Index` table with this exact header: `| Module Stem | Business Resource | Owned Operations | Owned Rule Keys | Case IDs | Split Reason | Markdown Path | Pytest Path |`. Use canonical relative links `[label](./<stem>.md)` inside the Markdown Path cell followed by the resolved `${layout.markdownDir}/<stem>.md` path. Split Reason is exactly one of `explicit-user-layout`, `primary-business-resource`, `independent-business-resource`, or `output-budget`. Group by stable business resource/domain, not by CRUD operation, AC, parameter/field axis, scenario type or regression purpose: one resource's list/detail/create/update/delete and its filters/response assertions/regression floor belong in one module. Multiple modules owning the same exact `METHOD /path` are forbidden unless every such row is `explicit-user-layout` from primary-requirement path pairs or has a documented `output-budget` proof. Keep the total module count at the smallest safe value and never exceed 8 modules. Name model-derived modules with stable lowercase business stems such as `health` or `resource_notes`; explicit-user-layout preserves the primary requirement filename stem even when it is more specific. Do not use priority-only stems `p0`, `p1` or `p2`; Priority belongs only in the Coverage Matrix. Pure hexadecimal/hash-like opaque stems and test-purpose-only stems are forbidden. Do not use Case-ID-like module filenames. The relative link target, Markdown Path, Pytest Path and downstream automation mapping must be one-to-one and exact; for model-derived modules the default pair remains `testcase/md/<module>.md` and `testcase/test_<module>.py`, while explicit-user-layout preserves the primary requirement paths. Do not hand-write a conflicting module count in prose; the Module Index row count is the only count truth.\n\nScenario Partitions (query/filter axes): inspect every affected GET/list operation for query/path parameters whose bound source documents a finite enum or classification domain. If at least one such axis exists, add exactly one machine-readable `## Scenario Partitions` section after the Coverage Matrix using exactly `| Partition ID | Operation | Axis | Domain | Required Slots | Expected by Slot | Bind Rule |` with the separator row and one row per eligible axis. If no affected axis has a source-backed finite domain, omit the entire `## Scenario Partitions` heading and section; do not emit an explanatory prose-only section. Partition ID is a stable `SP-<OPERATION>-<AXIS>` token; Domain must copy the legal values verbatim from the bound OpenAPI enum or requirement sentence (never guess), using bare semicolon-separated identifier values inside the single table cell (for example `ACTIVE; ARCHIVED`, with no Markdown backticks or prose); Required Slots must contain `each-value` and exactly one `not-in-set`, plus `omitted` only when the parameter is optional. Before returning, expand every declared partition into its complete deterministic exact slot ID set: one `TP-<Partition ID>-<VALUE-TOKEN>` per Domain value, `TP-<Partition ID>-OMITTED` only for an optional axis, and exactly one `TP-<Partition ID>-NOT-IN-SET`. Every expanded slot ID must appear verbatim in the binding Rule's `Required Test Points` cell and be assigned to concrete Case IDs in that same Coverage Matrix row; ordinary alias/family Test Points do not replace this inventory. Scheme A: Case count may be smaller than the enum count, but every exact slot still needs an independent variant Test Point and pytest.param id; never use SINGLE/MULTIPLE aliases as coverage. Expected by Slot states the documented expectation per slot kind (`domain-value`, `default-behavior`, `empty-result`/`excluded-result` when documented, or `GAP` when the source does not document the complement expectation — never invent 空列表/400). POST/PUT body field-validation enums stay in the Coverage Matrix as `TP-<FIELD>-ENUM-*` and MUST NOT get a Scenario Partition row. Do not create partitions for axes without a documented legal-value domain. Only GET/list query or path parameters whose bound source documents a finite enum or classification set may become a Scenario Partition. Do not create partitions for free-form strings, primary keys, required-or-optional-only parameters, or boundary/format-only axes. If an axis has no finite legal-value domain, do not declare a Partition row and do not invent NOT-IN-SET cases. Cross-axis combinations stay as ONE nominal Case; never declare a cross-axis cartesian partition.\n\nBefore finalizing README, calculate the predicted collected-item count as `sum(max(1, number of variant Test Points in each Case))`. If the task declares an item budget, the prediction must not exceed it. Reduce excess only by removing duplicate execution and converting same-request checkpoints to assertions; never drop required rules, boundaries, enums, operation-specific inputs, or business states. Record the prediction in README. Use only environment-supported fixtures/targets/isolation, record evidence gaps in Chinese, and do not emit JSON, pytest, or execute commands.\n\n## Derived task contract: 需求.md\n\n# Backend test\n- AC-001 proof\n\n## Authoritative reference index\n\n[]\n\nFor each index entry, use `readPath` for Pi read-tool calls and copy `path` exactly into Markdown Source References. Bound files under .harness/tasks/<taskId>/source/** are read-only inputs: reading them is allowed even though writing .harness/** is forbidden. Never resolve `path` relative to the repository root, search for substitutes, or fall back to docs/** when a bound read fails.\n\nRead only precise indexed references needed for AC/API/field/rule evidence; references remain authoritative over derived text.",
|
|
152
152
|
"executor": "pi",
|
|
153
153
|
"role": "planner",
|
|
154
154
|
"toolProfile": "read-only",
|
|
@@ -176,6 +176,8 @@
|
|
|
176
176
|
"unavailable",
|
|
177
177
|
"empty-output",
|
|
178
178
|
"output-too-large",
|
|
179
|
+
"invalid-output",
|
|
180
|
+
"structured-output-truncated",
|
|
179
181
|
"read-burst",
|
|
180
182
|
"context-overflow"
|
|
181
183
|
]
|
|
@@ -193,7 +195,7 @@
|
|
|
193
195
|
"writePolicy": "read-only",
|
|
194
196
|
"shell": {
|
|
195
197
|
"commands": [
|
|
196
|
-
"node -e \"eval(require('zlib').inflateRawSync(Buffer.from('
|
|
198
|
+
"node -e \"eval(require('zlib').inflateRawSync(Buffer.from('zTvJcuNIdvf6CmiqQokcAqCqxlPdTTZYoVq6W3ZVSSGpesImUYoUkJRyhK0zQS0t6OSICR/66i3aDod9cNgnX8aXif6dmh6f5hccLxcgAZKSyjMO+yKRub738u3vMS5yUTlzEXL6zYJx6qK5QNgrSXXaDsE3hL2YX5VV0Q6r7wh736bsuB2GbwiPH8Ty6Cx5yXj4k4qKKiaCDrPkJ2ZKxJyVVWe6nas4i6vX5KpYVGG+SNNVEwen5MnPn3amqYhDEU5EwGmZkpi6w+lsOouub1z808Gz94/q2SwannhoNnu02QLJL98ke4ByTi+cfXry6rJ0qYhdCTweoNls6E63/b8g/rdb/mdHgR8N8GwWZAny0Il1zCIHbEpexFSIgObnwVfb+29fHRwcvdz+8mj/3dujlzv7dY3Q+AGbuxtqPb42G0SVUM6DC84q6qKMCcHyE2fFEc684M4xic9onvhAO+cN4WdJcZE7ZUpyh/CKzUlczXKExw04l6xyn+DxjYYWVkqk4XmDXxYsdxVAHjqhOeWkor65I0t8WO6XDHkIPgHuWGExl0eLShxc5bFrTsV3oXUP8EcOGpjzBmgNMimtHE5JktFwDs9Oki9YSjuweGhRzT9t3ykveAZcclBxlp+4AgdV8bq4oPwFEdTFFu+8Vy8eDYBnjpA19f5oUB8NHsG4PXxkVpq7jqtQXRPMeZG9OCX8RZFQ97On2Obo8jmJzyoWnwnFvaJMWeUeV1i9C2rPY/k5SVmyT4ko8pCTi3Bybc4JATGXkws8ZnN3+L6cbvlPokfDAGjsigpjTqsFzx1UclZwVl35RZ5e+VmRLFLqi4pmSO2cEn8ewR9A/vqp9/RnN6uOKUryzYL6p0ScLh0iqjAMkXoZ1OzgVFB+TpOl5Rvy0m/hUilj0U9XXaix98VVXpFLDaz7bHRM66qsSVxz+k19zPH0yI+GbHk/6Bg/ZWe0e7+elorkxlBa3qQo3CG6JHAYdtQOv9yn6WuWn4XD2XT6fhZFg1k0c2fBKsURZMkMD0/M3lNKEpafbKeMiPAa/fbf/vnDP/7tj7/+lw8//DUaoTcSTmcnT+gl8tDv/vVXP37/N7/77i8/fP9rNEIvinPKyQl1DuKipM38j//07//1d/9pz78hFWdwwId/+M1v//4/PvzVrz589xs0QgcxzQlnhbMHQlexIheooQBJAScKxgFeseXyGZ/lUovmNu/PeDOm+FeJrJRQjeQ+LQnj4Zykgo4fzAvuwiQLt8bsc3NbkNL8pDods8EAXxtAgDbD9w8fzsTAtSlU2wSpbexrG1M8E8BP9JLGrrlnyqKg4ixzsRQXeQe+tmZD9PChgwb2+0zlqunjKBp3Mar4go5vlDYqDSm72GqtS3j1FSXJIWdZOI3G96CBBK4PMwjXw4fOqvfD9h1BuRCnLgNNyeZuZ0bdEYbhY3z9wHE0fAcV4VVoL5xuRYPHY4nZqzwJ+zC2GKi9t6ChX3B2oEV7xVPga3kJGx9zSs6ApA1kL2iaijBlOQ0n8NdwWQ0Ml7KYuo89/zEOMlK65412Pwd7i5uXbo8D9CgPp6ghnbPzEnlotwTbx4oceWj7kgnkoZdFRhh831dOTuIcpEUFM68uSxpXNHGOr+QY8tBzlifO/iKlKILbVpAHMFQ0eeA4jgPaz6YEy+N0kVAhMcMAbsXyBR3LxVrfFBehoodNQzw25/HiQtP+8/CT/hHABwr5gJ5TfuW65x5LLnE44cXFlCWXURiG52tuLlmiDRpcMt2KbPLaC+llxYkIARL1OJ8YYzZuFMRwOvZ+/8N3v//h+2jYvNu5PmyFEcTBnKUV5e7zokgpyTsXlpzO2WWIDvd8NChZElTFu7I0Rn2AfNSgr2DTFHI2NzWwmhxVOBm+P9zzQXFv+Z/50eCRsSUV3tx0q+7JgYBnFb9g1amrYMB1fcsaAPBgz0cYmF1C5DgdrVM7aNCSbctrCOfUDsID5NQaE2dJ1Ug1JOdAbm4eSKHvaKq67u3B2nlqZFbdpVR3x0KJP4K+6pgzbA7uKqlmVB26IRXUSmeyvzQMw61nxsM0Jp7Ju0YoWZQpi8Gr7UzgARo7Onhx6CWJq/TKKXL92enB7AgaA+1u9azlY4cGtlZ90lu1p/hjKE/a1Z0aHgVze7fiLHmhR/MEr3hz8HumkfmWSjdAn2NbdyOQaThJe4rL7I0/Rm2TdEHDSdclVqOWCjcKRqneRo/rdzoAl85DzxcCgBbOPhXFgsfgHe1e5DRxGgUvmiFQ186f0SsYAYl1dl7CxwOA1FFuH/JQE6VAUIE8tHclgxf5LbKFhXLJLBJpEcxZnsjvriLCdavDJW3kMDZOaBetRkMDCTzJsUZPw2epqSV1xjcqHLOu/3xrXQxm3GhbEHy1c9SVBefYkLG4yCkXp6x0SJ44EDM6cZEuslzcKgsJqch+cSE0LdSDW0AOnqiXl5Ro2AloM2mN2CT8dHNTmRvzfyMMOw+OLae1uKCJfDoZzx/Qyp0iegnSzyp/ISj3U5k/gFiWs4zwK9+g6fOWW4AsJc0Tmlcr54tFVS5gKjmhFYoaCArDX7uSZBKIN6R08VgLBMmLnMUkPaA0b0A0swmNU8JpopCTOle6XinRCnu7LFNGk/B2ta6864bTnGLePIXl7XFyAdRbb9E9g6+95HF3SYOvsBc90Yu0tIPRtyRc/jMS3bfqntxjH/bzJTfDZJfekCo+BTIFQWBteKo3ZDC9naauSfFg6ZSxudtsvdvMIC0nmZZ/H7jfz5iQp0OWwtWErGu0yM/y4iJfb1ea53c6+mSNFDkOvD6EqSq6b8CebkXTxxH2DFAyldOZ3TKo2jmzzc0N+2ugUBOBKDLqMrhmAn+DzrFhaH8FH32JG6Xn0TiMN+riDcM9dySDlsULiApIr037yPNl7M+pKItc0Bo+1JyecCoEK/K6LASr2Dmtc3pC5IfjYpEnhF/VlPOC13GRHRe1Yj7sPhtNjxw/qh9h4+010K8DH1b55YKXhaC34eD4E/Dp9PjtOG3YCiw4JcKV0rAWhp4ul4t9Lk1WHwA5d/vtrSxbLtVdrwemIfGbrfd4O6nRpPWU/GUJ7idacNtEGyRRht0s22wGmYYhwprBIXlkZVmGfjSYBeWVySC1N+G6br9Y/koQoPsSWO2XKqBP3/boW1DXilcHki9InrCEVOBdWWL5bKWMajV5TykdTVfL//LV99CAb3Zfvnv96uj19p/vvjs8erH79ovXOy8OR05eOIucfbOgDUaOglamqDsKzkEDG757kyhcBrhVbRtmcnPTJD9BD+ONMISXwWsUldps9uowTCpZMxbAtyZg/Mizu6B1XsmOBGV5YQB8XNftaotBrbVNsUSvX314l6OtVR/N9eseXPGS9P+EUywqwRLqzHnxLc0dXhSVkA9/pwJQJtgCfSMMV6JkC6y9ph0FLJViteeNNjbef13/6cHu20BITcPmV5amgwftTTbHSNXWBgy4rqUStW+SAypGWGsYFcodaV2J7dhSiitQbfM7Ky6HCLvrkjbpBZMgKYq5TSFYtAeD2vUsKbir91Q91vbNzf5IcMKLRbmThGFY2t+xSVyAfMiZulYLqKhYRiqa7EoUoFAiPtebM3Jpje5R/gvgUV7Xb4CfY8pSd/0hQ7koI5fuY08iqLUdxpM7Tler+46RjSXLS1OF3DCYWmN1vbRDQ1jwrykHJ6XZ1p9YK5g7b7/efr3z8mj33eHeu8Oj5+9efvnq8Ghvf3f3i3sYXpMYMjwhEbuGTR1H0mt5zutL0shw0LO1wjYyEun15GfF3v6KVi7VZgjNITIfWU7Cz/6A2AJKQDtJ57g/+UNDFSWAK5CzZ+VnLwgCt7VZq4Tx2bX1ZbRqxc3o+gbfaCPWiSalvyiZTlqodTzUpsKa3XZBDPioOQTCGG3SGYTCrLpysgVUNqk2/evteAc0kiQWaAB9L9TVWUAz28avDUtAFCuP6KtlnVJROYqwF4AHJ7Rq1T2u62k0VivVjYr95fOMFIDtq93gcf80YZ/mqYMAX5m7tJWnFWdrT/keunWjTxSpf0hcLUgaTtR/ScEwDK2HNkGtuseouI+07bL4burzPX9OgPumTwfhsDSihECnED0V9ya0ojxjORMVi509aB2ASrPDpWkExsgLWcumeSWTb0OZdWtyTGtYStWw+ibWonNFjlMaTmUKvZdI66fQPVQvrQHEXBxOkO/7yKBUw4YageT236YlhLxx2pDD04q/qxa9VbxriiIOwta80XpLs1p9LY1bPOuhaUd+IzcYdgaCLMFGxDtaX460qj9aIhqOOqlix3ReQPall13e8joJcOzJt/GWF0ICun/sXCheXW7lUBe2HR03Dk0Fde4uc1x/3LFW+mzal/YI9FBPLcgUvdYqOmn5eHNzQ4+oLK78Ek7kP/Vg4LOtzEzWdW9Vz7NbJ9pQ709JWcqw3ECodbsAvd4MmqBVQwis3IVvWaozyk8oVDqbpLCx807BnYWgDjTvLKpT6C2RGRdnFXKrhVvK9saS/myfARLIQHiZSNaure6xIZyGvZqByqnLRe0RGeyH1SvygviakwtlEDJIrI2No9Tbboog1gm692PVETfdth1TQdMRLpwH3SSmIqD8+F63iexOUFNYT1l2a6RCU0jUanslCWkWGkPQXgoyLu2oWoFX8pFUBOrEAVpyB+RLQ5XrOKXLvDBMZLVchtO3lgayNsP9YBm+nq6V8iUhtv2bbNlzkOib8btzWDQrq6tOIaStgJDKSSkBvyKnS+iqLWsQXAJh8ulaAC5hkJ03Zcm4WOSy9a17wgA5E+dTSwirU+qIjKQpVSXH2x+D3t0MuE9J0jYEcppKEXbNlvgicbHX9Pdpb1muFbQ0qmLYVmJgqW7RVK2iQcwpqehXRJy6SMgZhINFCTkdV2lgHCTsBHJ26BRqs02PXFpUh8VZaLV1mGJAr9Bu9e6p8r3q3fM7KUV/UPumd6/fmPO/3ZSzuiGnsRl3u+xCn+43Fk6MbZbNCs2xTQF7BTz3q2OnRfX8SglgU8XKLN8nCydT7fBMowibEtYiJ0Kwk5xKYq5A8/aeo/8v/Uaq963nrag7Pdh0e/H7f9q21K99/x+2LpnbQkWKpUL2chcRDie6LUnaX2hnka1EOjwpv1pfk36zc3Cw8/bLo73t/cOdw53dt0eH289fvxrdxr3OKRGQgm5LaqqyDBXPO7LLpSxKl52n/coUoxUObTU6nPCmEv3J5iZXdWhdhe68QS9y1ZXXsim73quNyivKW8qtSqOHa9MhtzZVLScwihJgJ2k4LDJWmdLXcnYEe8cs7wD9dG3vl27FGr4/aLqoIv0/OPKhtVdfU7IEP3PXtGzhUdMrNdAGwC1K2cnVfF8uOOMOJLBuJ1HlYUU4QxEFY+ewc4xlfsaQ5Nm0WbT7Zufw8NVLFI2mEfaa4be7h/7OW//g1aGSGHOtTkT0IvwsnLi9+A6SEbjVHUBiXNfuUpSo1slcQNHYwMIuiQlp5xzUM4hhGBbl3cu6VFN5Hd2+AKQzTQp2sBBOCu2FRU1e2t7Y0fWWf5dIL1q9C7ZNjMzT2CdMtyKszWVi0pcm2lvy8D7mEr15uhXpMGfVJa0VU9NBEJgDx21znbXq9qRLu7A13D4cKMMy6xgr5LrTOu/IDErBr8JrEZ/SjOwkI2T/smKFt6Au9c8fI6/10DwTIvbMuw4ytJE3OaGvCWckr6QlGdn8sUxpRWDJvtENxl6L6IEi5mga3YwfzEWQnSWMq6h86Qcp0FjASVzBb5OuOY0XHDzmEdRWoO9pOa6/5QTvfgQKfglNX9jrVYY6VPfgNwDeExAe69Eht6cevbf3ehWRVf7IvQ6CAD56tie+muBdGKw0Yp7Ak2XL6cG6vl79dNENqJDlGXipDiBLnKJC9NE6ttOxjAr4ffgxj+I4XR/o1LpRRcSZbx4IjeQPjPyEcnZOE+SZCXX9aPkHYABR98jNzX6ildY1WmrQaNrArJRiVUFE+ELGYEuZxmePR1vW4t1FFRcZXbEOxackP6EJGqG8gHYMRWJ04zVcpl6g85Q3wEj/DQ==','base64')).toString('utf8'))\""
|
|
197
199
|
],
|
|
198
200
|
"timeoutMs": 60000,
|
|
199
201
|
"cwd": "."
|
|
@@ -392,7 +394,7 @@
|
|
|
392
394
|
"writePolicy": "read-only",
|
|
393
395
|
"shell": {
|
|
394
396
|
"commands": [
|
|
395
|
-
"node -e \"eval(require('zlib').inflateRawSync(Buffer.from('
|
|
397
|
+
"node -e \"eval(require('zlib').inflateRawSync(Buffer.from('zTvJcuNIdvf6CmiqQokcAqCqxlPdTTZYoVq6W3ZVSSGpesImUYoUkJRyhK0zQS0t6OSICR/66i3aDod9cNgnX8aXif6dmh6f5hccLxcgAZKSyjMO+yKRub738u3vMS5yUTlzEXL6zYJx6qK5QNgrSXXaDsE3hL2YX5VV0Q6r7wh736bsuB2GbwiPH8Ty6Cx5yXj4k4qKKiaCDrPkJ2ZKxJyVVWe6nas4i6vX5KpYVGG+SNNVEwen5MnPn3amqYhDEU5EwGmZkpi6w+lsOouub1z808Gz94/q2SwannhoNnu02QLJL98ke4ByTi+cfXry6rJ0qYhdCTweoNls6E63/b8g/rdb/mdHgR8N8GwWZAny0Il1zCIHbEpexFSIgObnwVfb+29fHRwcvdz+8mj/3dujlzv7dY3Q+AGbuxtqPb42G0SVUM6DC84q6qKMCcHyE2fFEc684M4xic9onvhAO+cN4WdJcZE7ZUpyh/CKzUlczXKExw04l6xyn+DxjYYWVkqk4XmDXxYsdxVAHjqhOeWkor65I0t8WO6XDHkIPgHuWGExl0eLShxc5bFrTsV3oXUP8EcOGpjzBmgNMimtHE5JktFwDs9Oki9YSjuweGhRzT9t3ykveAZcclBxlp+4AgdV8bq4oPwFEdTFFu+8Vy8eDYBnjpA19f5oUB8NHsG4PXxkVpq7jqtQXRPMeZG9OCX8RZFQ97On2Obo8jmJzyoWnwnFvaJMWeUeV1i9C2rPY/k5SVmyT4ko8pCTi3Bybc4JATGXkws8ZnN3+L6cbvlPokfDAGjsigpjTqsFzx1UclZwVl35RZ5e+VmRLFLqi4pmSO2cEn8ewR9A/vqp9/RnN6uOKUryzYL6p0ScLh0iqjAMkXoZ1OzgVFB+TpOl5Rvy0m/hUilj0U9XXaix98VVXpFLDaz7bHRM66qsSVxz+k19zPH0yI+GbHk/6Bg/ZWe0e7+elorkxlBa3qQo3CG6JHAYdtQOv9yn6WuWn4XD2XT6fhZFg1k0c2fBKsURZMkMD0/M3lNKEpafbKeMiPAa/fbf/vnDP/7tj7/+lw8//DUaoTcSTmcnT+gl8tDv/vVXP37/N7/77i8/fP9rNEIvinPKyQl1DuKipM38j//07//1d/9pz78hFWdwwId/+M1v//4/PvzVrz589xs0QgcxzQlnhbMHQlexIheooQBJAScKxgFeseXyGZ/lUovmNu/PeDOm+FeJrJRQjeQ+LQnj4Zykgo4fzAvuwiQLt8bsc3NbkNL8pDods8EAXxtAgDbD9w8fzsTAtSlU2wSpbexrG1M8E8BP9JLGrrlnyqKg4ixzsRQXeQe+tmZD9PChgwb2+0zlqunjKBp3Mar4go5vlDYqDSm72GqtS3j1FSXJIWdZOI3G96CBBK4PMwjXw4fOqvfD9h1BuRCnLgNNyeZuZ0bdEYbhY3z9wHE0fAcV4VVoL5xuRYPHY4nZqzwJ+zC2GKi9t6ChX3B2oEV7xVPga3kJGx9zSs6ApA1kL2iaijBlOQ0n8NdwWQ0Ml7KYuo89/zEOMlK65412Pwd7i5uXbo8D9CgPp6ghnbPzEnlotwTbx4oceWj7kgnkoZdFRhh831dOTuIcpEUFM68uSxpXNHGOr+QY8tBzlifO/iKlKILbVpAHMFQ0eeA4jgPaz6YEy+N0kVAhMcMAbsXyBR3LxVrfFBehoodNQzw25/HiQtP+8/CT/hHABwr5gJ5TfuW65x5LLnE44cXFlCWXURiG52tuLlmiDRpcMt2KbPLaC+llxYkIARL1OJ8YYzZuFMRwOvZ+/8N3v//h+2jYvNu5PmyFEcTBnKUV5e7zokgpyTsXlpzO2WWIDvd8NChZElTFu7I0Rn2AfNSgr2DTFHI2NzWwmhxVOBm+P9zzQXFv+Z/50eCRsSUV3tx0q+7JgYBnFb9g1amrYMB1fcsaAPBgz0cYmF1C5DgdrVM7aNCSbctrCOfUDsID5NQaE2dJ1Ug1JOdAbm4eSKHvaKq67u3B2nlqZFbdpVR3x0KJP4K+6pgzbA7uKqlmVB26IRXUSmeyvzQMw61nxsM0Jp7Ju0YoWZQpi8Gr7UzgARo7Onhx6CWJq/TKKXL92enB7AgaA+1u9azlY4cGtlZ90lu1p/hjKE/a1Z0aHgVze7fiLHmhR/MEr3hz8HumkfmWSjdAn2NbdyOQaThJe4rL7I0/Rm2TdEHDSdclVqOWCjcKRqneRo/rdzoAl85DzxcCgBbOPhXFgsfgHe1e5DRxGgUvmiFQ186f0SsYAYl1dl7CxwOA1FFuH/JQE6VAUIE8tHclgxf5LbKFhXLJLBJpEcxZnsjvriLCdavDJW3kMDZOaBetRkMDCTzJsUZPw2epqSV1xjcqHLOu/3xrXQxm3GhbEHy1c9SVBefYkLG4yCkXp6x0SJ44EDM6cZEuslzcKgsJqch+cSE0LdSDW0AOnqiXl5Ro2AloM2mN2CT8dHNTmRvzfyMMOw+OLae1uKCJfDoZzx/Qyp0iegnSzyp/ISj3U5k/gFiWs4zwK9+g6fOWW4AsJc0Tmlcr54tFVS5gKjmhFYoaCArDX7uSZBKIN6R08VgLBMmLnMUkPaA0b0A0swmNU8JpopCTOle6XinRCnu7LFNGk/B2ta6864bTnGLePIXl7XFyAdRbb9E9g6+95HF3SYOvsBc90Yu0tIPRtyRc/jMS3bfqntxjH/bzJTfDZJfekCo+BTIFQWBteKo3ZDC9naauSfFg6ZSxudtsvdvMIC0nmZZ/H7jfz5iQp0OWwtWErGu0yM/y4iJfb1ea53c6+mSNFDkOvD6EqSq6b8CebkXTxxH2DFAyldOZ3TKo2jmzzc0N+2ugUBOBKDLqMrhmAn+DzrFhaH8FH32JG6Xn0TiMN+riDcM9dySDlsULiApIr037yPNl7M+pKItc0Bo+1JyecCoEK/K6LASr2Dmtc3pC5IfjYpEnhF/VlPOC13GRHRe1Yj7sPhtNjxw/qh9h4+010K8DH1b55YKXhaC34eD4E/Dp9PjtOG3YCiw4JcKV0rAWhp4ul4t9Lk1WHwA5d/vtrSxbLtVdrwemIfGbrfd4O6nRpPWU/GUJ7idacNtEGyRRht0s22wGmYYhwprBIXlkZVmGfjSYBeWVySC1N+G6br9Y/koQoPsSWO2XKqBP3/boW1DXilcHki9InrCEVOBdWWL5bKWMajV5TykdTVfL//LV99CAb3Zfvnv96uj19p/vvjs8erH79ovXOy8OR05eOIucfbOgDUaOglamqDsKzkEDG757kyhcBrhVbRtmcnPTJD9BD+ONMISXwWsUldps9uowTCpZMxbAtyZg/Mizu6B1XsmOBGV5YQB8XNftaotBrbVNsUSvX314l6OtVR/N9eseXPGS9P+EUywqwRLqzHnxLc0dXhSVkA9/pwJQJtgCfSMMV6JkC6y9ph0FLJViteeNNjbef13/6cHu20BITcPmV5amgwftTTbHSNXWBgy4rqUStW+SAypGWGsYFcodaV2J7dhSiitQbfM7Ky6HCLvrkjbpBZMgKYq5TSFYtAeD2vUsKbir91Q91vbNzf5IcMKLRbmThGFY2t+xSVyAfMiZulYLqKhYRiqa7EoUoFAiPtebM3Jpje5R/gvgUV7Xb4CfY8pSd/0hQ7koI5fuY08iqLUdxpM7Tler+46RjSXLS1OF3DCYWmN1vbRDQ1jwrykHJ6XZ1p9YK5g7b7/efr3z8mj33eHeu8Oj5+9efvnq8Ghvf3f3i3sYXpMYMjwhEbuGTR1H0mt5zutL0shw0LO1wjYyEun15GfF3v6KVi7VZgjNITIfWU7Cz/6A2AJKQDtJ57g/+UNDFSWAK5CzZ+VnLwgCt7VZq4Tx2bX1ZbRqxc3o+gbfaCPWiSalvyiZTlqodTzUpsKa3XZBDPioOQTCGG3SGYTCrLpysgVUNqk2/evteAc0kiQWaAB9L9TVWUAz28avDUtAFCuP6KtlnVJROYqwF4AHJ7Rq1T2u62k0VivVjYr95fOMFIDtq93gcf80YZ/mqYMAX5m7tJWnFWdrT/keunWjTxSpf0hcLUgaTtR/ScEwDK2HNkGtuseouI+07bL4burzPX9OgPumTwfhsDSihECnED0V9ya0ojxjORMVi509aB2ASrPDpWkExsgLWcumeSWTb0OZdWtyTGtYStWw+ibWonNFjlMaTmUKvZdI66fQPVQvrQHEXBxOkO/7yKBUw4YageT236YlhLxx2pDD04q/qxa9VbxriiIOwta80XpLs1p9LY1bPOuhaUd+IzcYdgaCLMFGxDtaX460qj9aIhqOOqlix3ReQPall13e8joJcOzJt/GWF0ICun/sXCheXW7lUBe2HR03Dk0Fde4uc1x/3LFW+mzal/YI9FBPLcgUvdYqOmn5eHNzQ4+oLK78Ek7kP/Vg4LOtzEzWdW9Vz7NbJ9pQ709JWcqw3ECodbsAvd4MmqBVQwis3IVvWaozyk8oVDqbpLCx807BnYWgDjTvLKpT6C2RGRdnFXKrhVvK9saS/myfARLIQHiZSNaure6xIZyGvZqByqnLRe0RGeyH1SvygviakwtlEDJIrI2No9Tbboog1gm692PVETfdth1TQdMRLpwH3SSmIqD8+F63iexOUFNYT1l2a6RCU0jUanslCWkWGkPQXgoyLu2oWoFX8pFUBOrEAVpyB+RLQ5XrOKXLvDBMZLVchtO3lgayNsP9YBm+nq6V8iUhtv2bbNlzkOib8btzWDQrq6tOIaStgJDKSSkBvyKnS+iqLWsQXAJh8ulaAC5hkJ03Zcm4WOSy9a17wgA5E+dTSwirU+qIjKQpVSXH2x+D3t0MuE9J0jYEcppKEXbNlvgicbHX9Pdpb1muFbQ0qmLYVmJgqW7RVK2iQcwpqehXRJy6SMgZhINFCTkdV2lgHCTsBHJ26BRqs02PXFpUh8VZaLV1mGJAr9Bu9e6p8r3q3fM7KUV/UPumd6/fmPO/3ZSzuiGnsRl3u+xCn+43Fk6MbZbNCs2xTQF7BTz3q2OnRfX8SglgU8XKLN8nCydT7fBMowibEtYiJ0Kwk5xKYq5A8/aeo/8v/Uaq963nrag7Pdh0e/H7f9q21K99/x+2LpnbQkWKpUL2chcRDie6LUnaX2hnka1EOjwpv1pfk36zc3Cw8/bLo73t/cOdw53dt0eH289fvxrdxr3OKRGQgm5LaqqyDBXPO7LLpSxKl52n/coUoxUObTU6nPCmEv3J5iZXdWhdhe68QS9y1ZXXsim73quNyivKW8qtSqOHa9MhtzZVLScwihJgJ2k4LDJWmdLXcnYEe8cs7wD9dG3vl27FGr4/aLqoIv0/OPKhtVdfU7IEP3PXtGzhUdMrNdAGwC1K2cnVfF8uOOMOJLBuJ1HlYUU4QxEFY+ewc4xlfsaQ5Nm0WbT7Zufw8NVLFI2mEfaa4be7h/7OW//g1aGSGHOtTkT0IvwsnLi9+A6SEbjVHUBiXNfuUpSo1slcQNHYwMIuiQlp5xzUM4hhGBbl3cu6VFN5Hd2+AKQzTQp2sBBOCu2FRU1e2t7Y0fWWf5dIL1q9C7ZNjMzT2CdMtyKszWVi0pcm2lvy8D7mEr15uhXpMGfVJa0VU9NBEJgDx21znbXq9qRLu7A13D4cKMMy6xgr5LrTOu/IDErBr8JrEZ/SjOwkI2T/smKFt6Au9c8fI6/10DwTIvbMuw4ytJE3OaGvCWckr6QlGdn8sUxpRWDJvtENxl6L6IEi5mga3YwfzEWQnSWMq6h86Qcp0FjASVzBb5OuOY0XHDzmEdRWoO9pOa6/5QTvfgQKfglNX9jrVYY6VPfgNwDeExAe69Eht6cevbf3ehWRVf7IvQ6CAD56tie+muBdGKw0Yp7Ak2XL6cG6vl79dNENqJDlGXipDiBLnKJC9NE6ttOxjAr4ffgxj+I4XR/o1LpRRcSZbx4IjeQPjPyEcnZOE+SZCXX9aPkHYABR98jNzX6ildY1WmrQaNrArJRiVUFE+ELGYEuZxmePR1vW4t1FFRcZXbEOxackP6EJGqG8gHYMRWJ04zVcpl6g85Q3wEj/DQ==','base64')).toString('utf8'))\""
|
|
396
398
|
],
|
|
397
399
|
"timeoutMs": 60000,
|
|
398
400
|
"cwd": "."
|
|
@@ -444,7 +446,7 @@
|
|
|
444
446
|
"verification-before-completion"
|
|
445
447
|
],
|
|
446
448
|
"complexity": "MED",
|
|
447
|
-
"subtaskPromptTemplate": "Convert the single frozen Markdown module `{{item.markdownPath}}` into one self-contained pytest module. Before writing, also read the run-owned Markdown plan artifact at `{{item.planReadPath}}` and use its explicit API target/environment table as the authoritative fallback base URL for every module. A task/Markdown `API_BASE_URL` target takes precedence over project README dev-server URLs; never infer a backend API fallback from a frontend/Vite port such as localhost:3000. After reading the module Markdown, the run-owned plan artifact, and the bounded pytest config/conftest, immediately use write tools to create the single frozen file `{{item.pytestPath}}`. Define any bounded HTTP client fixture, request logging/redaction/truncation helper and payload builders needed by this module inside that same file; do not import generated testcase/**/helpers/** or testcase/**/factories/** assets. Do not end after analysis or planning. Do not modify Markdown, conftest, helpers/factories, or any other module's pytest script.\n\nOutput budget protocol (hard, max output <=16K per turn): Write exactly the frozen `{{item.pytestPath}}`. Never paste full Python modules into assistant chat. Do not merge or split modules. Do not reduce params/assertions/skips to fit. If OUTPUT_LIMIT_RECOVERY is injected, continue only listed missing/broken scripts.\n\nAlign every variant pytest.param payload with the Markdown scenario intent (empty/missing/null/length/pattern/enum/wrong-type/nominal). Prefer literal payloads over Faker for intent-critical fields so pre-execution scenario-param checks can verify them. Hard contract: intent=enum-invalid MUST pass a concrete invalid value literal (string/number/boolean), never `_OMIT`/None/missing key; intent=missing/empty may use `_OMIT` or delete the key; intent=custom-literal:trim|whitespace-padded requires a leading/trailing whitespace string with non-empty trimmed content (all-whitespace belongs to empty/whitespace-only, not trim); intent=custom-literal:ACTIVE|ARCHIVED requires the exact enum string, never descriptive tokens like filter-active; intent=max/min/max+1 should pass a repeated-string length expression, a bare length number N, or a helper named _*_LEN{N} / _*_MAX_LENGTH / _*_OVER_LENGTH — never a bare 1 for oversize. Hard contract: request payload dicts may only contain DTO field keys from Payload Allowed Paths; never put expect/expected/echo_* helper keys inside the JSON body dict. Path/query/header identifiers and scenario-control metadata (including `id`, expected codes, and selector labels) must stay in separate pytest parameters and helper arguments; never merge them into a DTO patch or JSON body unless that exact path is allowed by the Markdown payload contract. Normalize the configured API base URL with `rstrip(\"/\")` (or equivalently join exactly one slash) before appending endpoint paths; generated requests must never contain a `//api/...` path. When the bound source documents a concrete non-secret local API URL, generated clients must use it as the fallback in `os.environ.get(\"API_BASE_URL\", \"<documented-url>\")`; do not require an otherwise-uninjected environment variable or fail setup solely because it is absent. Missing-field helpers must remove keys idempotently with `payload.pop(field, None)`, never `del payload[field]`, because optional fields may already be absent.\n\nFor every response contract that requires an object or pagination envelope, first assert that each envelope/data value is a dict and that required keys exist, then index fields and assert values. Never let an incidental KeyError or list/string TypeError stand in for the explicit response-shape contract failure.\n\nEnsure every automatable final Markdown Case ID in this module appears in exactly one primary pytest test function or pytest test class method region, using the exact `primary symbol` declared by Markdown. Skip evidence-only meta Cases that declare `脚本/primary symbol=无` with empty variants; do not invent a business pytest symbol for them. The symbol must start with `test_BE_<MODULE>_<NNN>_` so every parameterized collected item remains associated with its Case. Module-level functions and class-based pytest methods are both supported. Only `变体测试点` may use stable `pytest.param(..., id=\"TP-...\")` IDs, and every atomic variant ID must appear exactly once with a genuine input/state/outcome change. Use a literal direct `pytest.param(..., id=...)` expression for every row; never hide or wrap it behind `_post_case`, `_put_case`, row-factory functions, comprehensions, generators, or dynamically returned parameter lists; do not use decorator-level `ids=[...]`, generated suffixes, or IDs that extend/shorten the exact Markdown TP. Do not parameterize `场景断言测试点` or `横切证据测试点`; execute all assertion checkpoints within the same business journey/item and use shared helpers for cross-cutting evidence. The primary symbol docstring must contain exact metadata lines `Case-ID: BE-...`, `Assertion-Test-Points: TP-...;TP-...` and `Cross-Cutting-Test-Points: TP-...;TP-...` (use `none` when empty). Implement request dictionaries so their direct and nested key paths and enum literals exactly satisfy the Case `Payload Required Paths`, `Payload Allowed Paths`, and `Payload Enum`; for `Payload Contract: none`, do not invent a JSON/body DTO. GET/DELETE setup journeys may create resources, but their setup DTO must not change the target operation's no-body payload contract. No Test Point may be invented, renamed, omitted or bound in two modes. The generated pytest collection shape must equal the Markdown prediction `sum(max(1, variant count per Case))`; keep it at or below the task's explicit budget by removing duplicate execution, never by collapsing multiple parameter rows under a coarse family TP. Assertions come only from 预期结果 and setup comes only from 前置条件/测试数据/自动化映射.\n\nName the generated pytest file so it corresponds one-to-one with its source Markdown module file: this module stem `{{item.stem}}` maps to exactly the frozen `{{item.pytestPath}}`. The <module> stem is the Markdown filename without the `.md` extension, lowercased and with non-alphanumeric characters replaced by underscores. For example, `resource_notes` → `testcase/test_resource_notes.py`, `health` → `testcase/test_health.py`. If Markdown automation mapping names a different path than this module stem path, still write the frozen manifest pytest path and do not invent prefixes. Never merge multiple Markdown modules into one pytest file, never split one module across several files, and never invent pytest filenames unrelated to the Markdown modules.\n\nScenario Partition slots: every `TP-<Partition ID>-...` variant Test Point declared by this module's Markdown MUST become exactly one literal direct `pytest.param(..., id=\"TP-<Partition ID>-...\")` row with the exact slot ID; the not-in-set slot passes a concrete literal absent from the documented Domain (e.g. `UNKNOWN_TYPE`) — never `_OMIT`, never a descriptive token. Never split one slot into multiple params or merge several slots under a family TP id. Slot filtering requests hit the documented list endpoint with the slot value as the query/path filter.\n\nKeep this module self-contained: define module-local fixtures and helpers directly in `{{item.pytestPath}}`, so pytest discovers every fixture dependency without external plugin registration. The request log must include method, URL/path, and request parameters (query plus JSON/body/payload summary). The response log must include status code and response result (JSON/text/body summary), and both records must be visible in pytest stdout/stderr without changing assertions. Recursively redact sensitive values and apply bounded truncation before logging.\n\nMaterialize every automatable Markdown Case exactly once as one canonical primary pytest symbol. Preserve every explicit variant Test Point as a stable pytest.param id and every assertion/cross-cutting binding as declared. Build request payloads from the effective Markdown test data literally: keep all declared DTO keys, nested shapes, enum values, missing/null/boundary variants and business-state preconditions; never substitute guessed convenience fields or rename contract fields. Never assert an identifier's concrete Python/JSON type unless the Markdown or bound contract explicitly declares that type; when only presence is required, accept any non-null scalar identifier and serialize it safely into the path. For a nonexistent-resource 404 Case whose identifier syntax/type is not declared, obtain a syntactically valid identifier from a live create response and delete it before the 404 request; never invent an arbitrary UUID/text identifier that may fail path conversion with 400. Respect every local helper's actual return signature: never tuple-unpack a scalar status/id/helper result, and never treat a tuple response as a scalar.\n\nDo not read source/**, add cases, reassign ACs, modify conftest/config/production code, use skip/xfail, swallow assertions, execute pytest, or emit JSON. For best-effort cleanup, catch only the narrow transport exception actually raised by the selected HTTP client (for example `requests.RequestException` or `urllib.error.URLError`); never use bare `except`, `Exception`, or `BaseException` with `pass`.",
|
|
449
|
+
"subtaskPromptTemplate": "Convert the single frozen Markdown module `{{item.markdownPath}}` into one self-contained pytest module. Before writing, also read the run-owned Markdown plan artifact at `{{item.planReadPath}}` and use its explicit API target/environment table as the authoritative fallback base URL for every module. A task/Markdown `API_BASE_URL` target takes precedence over project README dev-server URLs; never infer a backend API fallback from a frontend/Vite port such as localhost:3000. After reading the module Markdown, the run-owned plan artifact, and the bounded pytest config/conftest, immediately use write tools to create the single frozen file `{{item.pytestPath}}`. Define any bounded HTTP client fixture, request logging/redaction/truncation helper and payload builders needed by this module inside that same file; do not import generated testcase/**/helpers/** or testcase/**/factories/** assets. Do not end after analysis or planning. Do not modify Markdown, conftest, helpers/factories, or any other module's pytest script.\n\nOutput budget protocol (hard, max output <=16K per turn): Write exactly the frozen `{{item.pytestPath}}`. Never paste full Python modules into assistant chat. Do not merge or split modules. Do not reduce params/assertions/skips to fit. If OUTPUT_LIMIT_RECOVERY is injected, continue only listed missing/broken scripts.\n\nAlign every variant pytest.param payload with the Markdown scenario intent (empty/missing/null/length/pattern/enum/wrong-type/nominal). Prefer literal payloads over Faker for intent-critical fields so pre-execution scenario-param checks can verify them. Hard contract: intent=enum-invalid MUST pass a concrete invalid value literal (string/number/boolean), never `_OMIT`/None/missing key; intent=missing/empty may use `_OMIT` or delete the key; intent=custom-literal:trim|whitespace-padded requires a leading/trailing whitespace string with non-empty trimmed content (all-whitespace belongs to empty/whitespace-only, not trim); intent=custom-literal:ACTIVE|ARCHIVED requires the exact enum string, never descriptive tokens like filter-active; intent=max/min/max+1 should pass a repeated-string length expression, a bare length number N, or a helper named _*_LEN{N} / _*_MAX_LENGTH / _*_OVER_LENGTH — never a bare 1 for oversize. Hard contract: request payload dicts may only contain DTO field keys from Payload Allowed Paths; never put expect/expected/echo_* helper keys inside the JSON body dict. Path/query/header identifiers and scenario-control metadata (including `id`, expected codes, and selector labels) must stay in separate pytest parameters and helper arguments; never merge them into a DTO patch or JSON body unless that exact path is allowed by the Markdown payload contract. Normalize the configured API base URL with `rstrip(\"/\")` (or equivalently join exactly one slash) before appending endpoint paths; generated requests must never contain a `//api/...` path. When the bound source documents a concrete non-secret local API URL, generated clients must use it as the fallback in `os.environ.get(\"API_BASE_URL\", \"<documented-url>\")`; do not require an otherwise-uninjected environment variable or fail setup solely because it is absent. Missing-field helpers must remove keys idempotently with `payload.pop(field, None)`, never `del payload[field]`, because optional fields may already be absent.\n\nFor every response contract that requires an object or pagination envelope, first assert that each envelope/data value is a dict and that required keys exist, then index fields and assert values. Never let an incidental KeyError or list/string TypeError stand in for the explicit response-shape contract failure.\n\nEnsure every automatable final Markdown Case ID in this module appears in exactly one primary pytest test function or pytest test class method region, using the exact `primary symbol` declared by Markdown. Skip evidence-only meta Cases that declare `脚本/primary symbol=无` with empty variants; do not invent a business pytest symbol for them. The symbol must start with `test_BE_<MODULE>_<NNN>_` so every parameterized collected item remains associated with its Case. Module-level functions and class-based pytest methods are both supported. Only `变体测试点` may use stable `pytest.param(..., id=\"TP-...\")` IDs, and every atomic variant ID must appear exactly once with a genuine input/state/outcome change. A Case with exactly one variant Test Point still needs one literal `pytest.param(..., id=\"TP-...\")` row; never leave a single-variant Case as a bare function with the TP only in the docstring. Use a literal direct `pytest.param(..., id=...)` expression for every row; never hide or wrap it behind `_post_case`, `_put_case`, row-factory functions, comprehensions, generators, or dynamically returned parameter lists; do not use decorator-level `ids=[...]`, generated suffixes, or IDs that extend/shorten the exact Markdown TP. Do not parameterize `场景断言测试点` or `横切证据测试点`; execute all assertion checkpoints within the same business journey/item and use shared helpers for cross-cutting evidence. The primary symbol docstring must contain exact metadata lines `Case-ID: BE-...`, `Assertion-Test-Points: TP-...;TP-...` and `Cross-Cutting-Test-Points: TP-...;TP-...` (use `none` when empty). Implement request dictionaries so their direct and nested key paths and enum literals exactly satisfy the Case `Payload Required Paths`, `Payload Allowed Paths`, and `Payload Enum`; for `Payload Contract: none`, do not invent a JSON/body DTO. GET/list filters still declare query fields in those payload labels when the Case varies `params=`/`query=` keys. Python `True`/`False` may implement JSON/OpenAPI `true`/`false` query or body booleans. GET/DELETE setup journeys may create resources, but their setup DTO must not change the target operation's no-body payload contract. No Test Point may be invented, renamed, omitted or bound in two modes. The generated pytest collection shape must equal the Markdown prediction `sum(max(1, variant count per Case))`; keep it at or below the task's explicit budget by removing duplicate execution, never by collapsing multiple parameter rows under a coarse family TP. Assertions come only from 预期结果 and setup comes only from 前置条件/测试数据/自动化映射.\n\nName the generated pytest file so it corresponds one-to-one with its source Markdown module file: this module stem `{{item.stem}}` maps to exactly the frozen `{{item.pytestPath}}`. The <module> stem is the Markdown filename without the `.md` extension, lowercased and with non-alphanumeric characters replaced by underscores. For example, `resource_notes` → `testcase/test_resource_notes.py`, `health` → `testcase/test_health.py`. If Markdown automation mapping names a different path than this module stem path, still write the frozen manifest pytest path and do not invent prefixes. Never merge multiple Markdown modules into one pytest file, never split one module across several files, and never invent pytest filenames unrelated to the Markdown modules.\n\nScenario Partition slots: every `TP-<Partition ID>-...` variant Test Point declared by this module's Markdown MUST become exactly one literal direct `pytest.param(..., id=\"TP-<Partition ID>-...\")` row with the exact slot ID; the not-in-set slot passes a concrete literal absent from the documented Domain (e.g. `UNKNOWN_TYPE`) — never `_OMIT`, never a descriptive token. Never split one slot into multiple params or merge several slots under a family TP id. Slot filtering requests hit the documented list endpoint with the slot value as the query/path filter.\n\nKeep this module self-contained: define module-local fixtures and helpers directly in `{{item.pytestPath}}`, so pytest discovers every fixture dependency without external plugin registration. The request log must include method, URL/path, and request parameters (query plus JSON/body/payload summary). The response log must include status code and response result (JSON/text/body summary), and both records must be visible in pytest stdout/stderr without changing assertions. Recursively redact sensitive values and apply bounded truncation before logging.\n\nMaterialize every automatable Markdown Case exactly once as one canonical primary pytest symbol. Preserve every explicit variant Test Point as a stable pytest.param id and every assertion/cross-cutting binding as declared. Build request payloads from the effective Markdown test data literally: keep all declared DTO keys, nested shapes, enum values, missing/null/boundary variants and business-state preconditions; never substitute guessed convenience fields or rename contract fields. Never assert an identifier's concrete Python/JSON type unless the Markdown or bound contract explicitly declares that type; when only presence is required, accept any non-null scalar identifier and serialize it safely into the path. For a nonexistent-resource 404 Case whose identifier syntax/type is not declared, obtain a syntactically valid identifier from a live create response and delete it before the 404 request; never invent an arbitrary UUID/text identifier that may fail path conversion with 400. Respect every local helper's actual return signature: never tuple-unpack a scalar status/id/helper result, and never treat a tuple response as a scalar.\n\nDo not read source/**, add cases, reassign ACs, modify conftest/config/production code, use skip/xfail, swallow assertions, execute pytest, or emit JSON. For best-effort cleanup, catch only the narrow transport exception actually raised by the selected HTTP client (for example `requests.RequestException` or `urllib.error.URLError`); never use bare `except`, `Exception`, or `BaseException` with `pass`.",
|
|
448
450
|
"outputContract": "Write exactly the frozen pytest module file `{{item.pytestPath}}` whose actual test function region contains the exact Case ID, preferably in the function name or docstring. the frozen `{{item.markdownPath}}` maps one-to-one to `{{item.pytestPath}}`; never merge or split modules. No JSON and no pytest execution.",
|
|
449
451
|
"toolProfile": "write",
|
|
450
452
|
"writePolicy": "exclusive",
|
|
@@ -58,6 +58,12 @@
|
|
|
58
58
|
"type": "string",
|
|
59
59
|
"minLength": 1
|
|
60
60
|
}
|
|
61
|
+
},
|
|
62
|
+
"requiredDeliverables": {
|
|
63
|
+
"type": "array",
|
|
64
|
+
"items": {
|
|
65
|
+
"$ref": "#/$defs/path"
|
|
66
|
+
}
|
|
61
67
|
}
|
|
62
68
|
}
|
|
63
69
|
},
|
|
@@ -433,8 +439,7 @@
|
|
|
433
439
|
"required": [
|
|
434
440
|
"purpose",
|
|
435
441
|
"component",
|
|
436
|
-
"decision"
|
|
437
|
-
"rationale"
|
|
442
|
+
"decision"
|
|
438
443
|
],
|
|
439
444
|
"properties": {
|
|
440
445
|
"purpose": {
|
|
@@ -465,6 +470,16 @@
|
|
|
465
470
|
"rationale": {
|
|
466
471
|
"type": "string",
|
|
467
472
|
"minLength": 1
|
|
473
|
+
},
|
|
474
|
+
"covers": {
|
|
475
|
+
"type": "array",
|
|
476
|
+
"items": {
|
|
477
|
+
"type": "string",
|
|
478
|
+
"minLength": 1
|
|
479
|
+
}
|
|
480
|
+
},
|
|
481
|
+
"evidencePath": {
|
|
482
|
+
"$ref": "#/$defs/path"
|
|
468
483
|
}
|
|
469
484
|
},
|
|
470
485
|
"allOf": [
|
|
@@ -511,6 +526,23 @@
|
|
|
511
526
|
}
|
|
512
527
|
}
|
|
513
528
|
}
|
|
529
|
+
},
|
|
530
|
+
{
|
|
531
|
+
"if": {
|
|
532
|
+
"properties": {
|
|
533
|
+
"decision": {
|
|
534
|
+
"const": "reuse-existing"
|
|
535
|
+
}
|
|
536
|
+
},
|
|
537
|
+
"required": [
|
|
538
|
+
"decision"
|
|
539
|
+
]
|
|
540
|
+
},
|
|
541
|
+
"then": {
|
|
542
|
+
"required": [
|
|
543
|
+
"evidencePath"
|
|
544
|
+
]
|
|
545
|
+
}
|
|
514
546
|
}
|
|
515
547
|
]
|
|
516
548
|
}
|
package/harness.json
CHANGED
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"executors": {
|
|
83
83
|
"pi": {
|
|
84
84
|
"description": "Pi 负责规划、评审、诊断;当 DAG toolProfile=write 时也可做有界写入。模型按复杂度三档配置,支持 provider/model 字符串或带 thinking 的对象;斜杠前为 Pi provider,后为 modelId,勿只写裸 modelId。",
|
|
85
|
-
"LOW": "wizard-local/
|
|
85
|
+
"LOW": "wizard-local/glm-5.3-flash",
|
|
86
86
|
"MED": "wizard-local/glm-5.3",
|
|
87
87
|
"HIGH": "wizard-local/gpt-5.6-sol"
|
|
88
88
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tea-agent/loop-agent",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.43.0-next.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"bin": {
|
|
6
6
|
"loop-agent": "bin/loop-agent.js",
|
|
@@ -91,7 +91,7 @@
|
|
|
91
91
|
},
|
|
92
92
|
"optionalDependencies": {
|
|
93
93
|
"@cursor/sdk": "^1.0.7",
|
|
94
|
-
"@agent-context/sift": "0.0.1-alpha.
|
|
94
|
+
"@agent-context/sift": "0.0.1-alpha.7"
|
|
95
95
|
},
|
|
96
96
|
"devDependencies": {
|
|
97
97
|
"@remixicon/react": "^4.9.0",
|
|
@@ -106,7 +106,6 @@
|
|
|
106
106
|
"tsx": "^4.20.6",
|
|
107
107
|
"typescript": "^5.9.3",
|
|
108
108
|
"vite": "^7.0.0",
|
|
109
|
-
"vitest": "^
|
|
110
|
-
}
|
|
111
|
-
"packageManager": "pnpm@10.33.0+sha512.10568bb4a6afb58c9eb3630da90cc9516417abebd3fabbe6739f0ae795728da1491e9db5a544c76ad8eb7570f5c4bb3d6c637b2cb41bfdcdb47fa823c8649319"
|
|
109
|
+
"vitest": "^4.1.11"
|
|
110
|
+
}
|
|
112
111
|
}
|
|
@@ -4,7 +4,7 @@ description: Use only for the tool-only frontend decision planning node.
|
|
|
4
4
|
references:
|
|
5
5
|
- path: references/decision-contract.md
|
|
6
6
|
required: true
|
|
7
|
-
maxChars:
|
|
7
|
+
maxChars: 5600
|
|
8
8
|
- path: references/design-decisions.md
|
|
9
9
|
required: true
|
|
10
10
|
maxChars: 3400
|
|
@@ -21,6 +21,19 @@ requirement coverage, component/styling choices, applicable states and interacti
|
|
|
21
21
|
data/Mock strategy, deviations, and dependency policy. Process a bounded requirement
|
|
22
22
|
slice and record facts immediately rather than reasoning over the whole task first.
|
|
23
23
|
|
|
24
|
+
UX vocabulary is global, not per-requirement: commit `record_state_registry`
|
|
25
|
+
(one stable behavior-domain name per state/interaction) before any
|
|
26
|
+
`record_state_flow`, bind UI states to the contract's declared authoritative ids,
|
|
27
|
+
and let one component choice cover many ids via `covers`. `reuse-existing` must
|
|
28
|
+
cite `evidencePath` of an existing file; greenfield is `decision=new`.
|
|
29
|
+
Bind every file in the Contract-owned `requiredDeliverables` inventory. It records
|
|
30
|
+
explicit source obligations, not every path mentioned by a requirement.
|
|
31
|
+
|
|
32
|
+
Cross-slice citations must close in the same session: when a requirement cites a
|
|
33
|
+
verification target committed in another slice's session, re-commit that target
|
|
34
|
+
here with the same id and `replace=true` (union backfill) before finalize. A
|
|
35
|
+
`duplicate` receipt is a correction invitation, not a prohibition.
|
|
36
|
+
|
|
24
37
|
The runtime owns protected skeleton fields, path/command validation, materialization,
|
|
25
38
|
and final schema checks. Finish with exactly one `finalize_plan`; return no Markdown
|
|
26
39
|
narrative. Record a genuine evidence gap when frozen facts are insufficient.
|
|
@@ -14,11 +14,101 @@
|
|
|
14
14
|
- Static targets are for project-wide commands and are traced by file and command
|
|
15
15
|
only.
|
|
16
16
|
|
|
17
|
+
### Behavior target shape (canonical example)
|
|
18
|
+
|
|
19
|
+
Each behavior target names the requirements it proves and declared UI states it
|
|
20
|
+
exercises. Empty `requirementIds`, or empty `uiStates` when any state/interaction
|
|
21
|
+
is declared, is rejected. Copy state names verbatim; never invent synonyms.
|
|
22
|
+
|
|
23
|
+
```json
|
|
24
|
+
{
|
|
25
|
+
"id": "VT-COUNTER-LOCAL-CONSTRAINTS",
|
|
26
|
+
"file": "src/App.test.tsx",
|
|
27
|
+
"requirementIds": ["AC-FE-001", "AC-FE-005"],
|
|
28
|
+
"uiStates": ["disabled-minus", "default"]
|
|
29
|
+
}
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
`stylingStrategy` describes how the frozen look is achieved; it must stay inside
|
|
33
|
+
the task's declared scope. Capabilities the task source lists as non-goals (e.g.
|
|
34
|
+
responsive/mobile layout, animations) must not be promised here, and themes or
|
|
35
|
+
CSS conventions must not be claimed without a Scout-confirmed repository fact.
|
|
36
|
+
|
|
37
|
+
### UI state declaration shape (canonical example)
|
|
38
|
+
|
|
39
|
+
Use the exact state names referenced by behavior targets. Each applicable state
|
|
40
|
+
carries behavior, implementation targets, and verification target ids:
|
|
41
|
+
|
|
42
|
+
```json
|
|
43
|
+
{
|
|
44
|
+
"uiStates": [
|
|
45
|
+
{
|
|
46
|
+
"name": "disabled-minus",
|
|
47
|
+
"applicable": true,
|
|
48
|
+
"expectedBehavior": "minus button disabled at count 0",
|
|
49
|
+
"implementationTargets": ["src/components/SmokeCounter.tsx"],
|
|
50
|
+
"verificationTargetIds": ["VT-COUNTER-LOCAL-CONSTRAINTS"]
|
|
51
|
+
}
|
|
52
|
+
],
|
|
53
|
+
"interactions": [
|
|
54
|
+
{
|
|
55
|
+
"name": "refresh",
|
|
56
|
+
"trigger": "User clicks refresh",
|
|
57
|
+
"expectedBehavior": "reloads runs",
|
|
58
|
+
"implementationTargets": ["src/App.tsx"],
|
|
59
|
+
"verificationTargetIds": ["VT-SMOKE-COUNTER-BEHAVIOR"]
|
|
60
|
+
}
|
|
61
|
+
]
|
|
62
|
+
}
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
### Implementation target coverage (canonical example)
|
|
66
|
+
|
|
67
|
+
`targets.files` is the union of every requirement's `implementationTargets`; list
|
|
68
|
+
each required component, integration point, and sibling source. Admission adds
|
|
69
|
+
non-static verification target files to the writer writeSet separately.
|
|
70
|
+
|
|
71
|
+
```json
|
|
72
|
+
{
|
|
73
|
+
"id": "AC-FE-001",
|
|
74
|
+
"implementationTargets": [
|
|
75
|
+
"src/components/SmokeCounter.tsx",
|
|
76
|
+
"src/App.tsx"
|
|
77
|
+
],
|
|
78
|
+
"verificationTargetIds": [
|
|
79
|
+
"VT-SMOKE-COUNTER-BEHAVIOR",
|
|
80
|
+
"VT-COUNTER-LOCAL-CONSTRAINTS"
|
|
81
|
+
]
|
|
82
|
+
}
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
### Bidirectional VT cross-reference invariant
|
|
86
|
+
|
|
87
|
+
Every requirement → VT citation must close in both directions: the cited VT's
|
|
88
|
+
`requirementIds` must list the citing requirement back. The checker reports the
|
|
89
|
+
missing direction; fix it in-node by re-submitting the corrected VT entry with
|
|
90
|
+
the same id and `replace=true`. `replace` is a full replacement: the latest
|
|
91
|
+
submission under an id becomes the authoritative entry (a subset re-submission
|
|
92
|
+
is the new rule). A `duplicate` receipt is a correction invitation, not a
|
|
93
|
+
prohibition, and a reverse-reference backfill is not "re-deriving committed
|
|
94
|
+
facts".
|
|
95
|
+
|
|
96
|
+
## UX vocabulary (registry first)
|
|
97
|
+
|
|
98
|
+
- Record `record_state_registry` BEFORE `record_state_flow`: one global vocabulary.
|
|
99
|
+
Coverage may slice by requirement; UX must not. Use stable kebab-case behavior
|
|
100
|
+
names, never AC-number-derived names or renamed committed concepts.
|
|
101
|
+
- UI states use the contract's declared authoritative ids (`declaredUiStates`
|
|
102
|
+
in the plan input) when the source declares a state table.
|
|
103
|
+
- Retry slices see `committedUx` in the plan input: reuse those exact names.
|
|
104
|
+
|
|
17
105
|
## Global decisions
|
|
18
106
|
|
|
19
107
|
Keep route/component placement, Mock/data strategy, and dependency/deviation policy
|
|
20
|
-
|
|
21
|
-
|
|
108
|
+
global. Use only frozen command labels and Scout-confirmed paths.
|
|
109
|
+
|
|
110
|
+
One component choice may cover many states/interactions via `covers`.
|
|
111
|
+
`reuse-existing` requires an existing-file `evidencePath`; greenfield uses `new`.
|
|
22
112
|
|
|
23
113
|
For Mock/API, keep the real request path enabled by default. Select only a strategy
|
|
24
114
|
allowed by the frozen task capability. Active Mock requires deterministic Mock-backed
|
|
@@ -32,6 +122,12 @@ widen the write set.
|
|
|
32
122
|
## Runtime-owned fields and terminal
|
|
33
123
|
|
|
34
124
|
The runtime owns `schemaVersion`, `sourceBinding`, risk, canonical target files,
|
|
35
|
-
aliases, command allowlisting, path containment, and final
|
|
36
|
-
editable decision facts, then call `finalize_plan` exactly
|
|
37
|
-
design policy materializes the canonical implementation
|
|
125
|
+
`requiredDeliverables`, aliases, command allowlisting, path containment, and final
|
|
126
|
+
validation. Submit only editable decision facts, then call `finalize_plan` exactly
|
|
127
|
+
once. The deterministic design policy materializes the canonical implementation
|
|
128
|
+
contract: every file in the Contract's explicit source-bound delivery inventory
|
|
129
|
+
must be planned (`requiredDeliverables` gate). Permissions, prohibitions, examples
|
|
130
|
+
and read-only references do not create delivery obligations. Plan receives this
|
|
131
|
+
inventory as `requiredDeliverables`; it cannot add, remove or reinterpret it.
|
|
132
|
+
Missing files and UX name collisions are reported by finalize_plan before commit
|
|
133
|
+
and checked again by the policy shell.
|
|
@@ -15,3 +15,35 @@ Contract. Do not search specification roots or nearby code from Plan.
|
|
|
15
15
|
responsive, and accessibility behavior; use not-applicable only with a reason.
|
|
16
16
|
- Record styling strategy, deviations, conflicts, and unresolved gaps explicitly.
|
|
17
17
|
Never silently replace a spec-defined component or claim unread evidence.
|
|
18
|
+
|
|
19
|
+
### Component choice shape (canonical example)
|
|
20
|
+
|
|
21
|
+
`purpose` must exactly match a declared UI state or interaction name — it is the
|
|
22
|
+
coverage key the deterministic policy checks. Do not invent synonyms, and never
|
|
23
|
+
swap a task-mandated component for another name without recording a deviation.
|
|
24
|
+
|
|
25
|
+
```json
|
|
26
|
+
[
|
|
27
|
+
{
|
|
28
|
+
"purpose": "disabled-minus",
|
|
29
|
+
"component": "SmokeCounter",
|
|
30
|
+
"decision": "new",
|
|
31
|
+
"sourceRequirementIds": ["AC-FE-001"],
|
|
32
|
+
"sourceFragmentId": "REQ-SRC-AC-FE-001",
|
|
33
|
+
"rationale": "task mandates a new SmokeCounter card on the home surface"
|
|
34
|
+
},
|
|
35
|
+
{
|
|
36
|
+
"purpose": "refresh",
|
|
37
|
+
"component": "RunFilterBar",
|
|
38
|
+
"decision": "reuse-existing",
|
|
39
|
+
"rationale": "reuses the Scout-confirmed filter bar for the refresh interaction"
|
|
40
|
+
}
|
|
41
|
+
]
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
For `decision: "new"`, pass `sourceRequirementIds` + `sourceFragmentId` and let
|
|
45
|
+
the runtime derive the exact task-source citation — never hand-write a
|
|
46
|
+
`specReference`. A `reuse-existing` choice covers behavioural interactions
|
|
47
|
+
without one row per interaction; each applicable visual UI state still needs its
|
|
48
|
+
own `purpose` match (or an explicitly scoped stylingStrategy covering the visual
|
|
49
|
+
dimension).
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
import{ag as o,ah as n}from"./mermaid.core-CWhj4JXN.js";const t=(a,r)=>o.lang.round(n.parse(a)[r]);export{t as c};
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
import{s as a,c as s,a as e,C as t}from"./chunk-GF5L2VYU-CY9Xx2jV.js";import{_ as i}from"./mermaid.core-CWhj4JXN.js";import"./chunk-5VM5RSS4-BYn1Hu4R.js";import"./chunk-XXDRQBXY-Ddx1KC1l.js";import"./chunk-KBJHAD2P-DZ8AStLL.js";import"./chunk-2GRJ4B5K-B1Aq6BcK.js";import"./index-D9Sc0f0y.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};
|
|
@@ -1 +0,0 @@
|
|
|
1
|
-
import{s as a,c as s,a as e,C as t}from"./chunk-GF5L2VYU-CY9Xx2jV.js";import{_ as i}from"./mermaid.core-CWhj4JXN.js";import"./chunk-5VM5RSS4-BYn1Hu4R.js";import"./chunk-XXDRQBXY-Ddx1KC1l.js";import"./chunk-KBJHAD2P-DZ8AStLL.js";import"./chunk-2GRJ4B5K-B1Aq6BcK.js";import"./index-D9Sc0f0y.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};
|