spec(config): align reference workflows with real parallelism and native report delivery

[LeXwDeX]

Blocked by: #293

Ticket 3/4 of the harness workstream (see #293). Primary source: docs/harness-review-2026-08-16.md (sections B-5, B-6, 七.4). Blocked by #293's merge SHA (incompatible block rule per runtime-compat.json policy). Work happens in the LeXwDeX/opencode-dag-config repository, not this one.

Problem Statement

The saved workflow library currently overpromises in two ways:

1. The full project-development route advertises "parallel slices", but the runtime compiled those slices into a serial chain. Once spec(dag): parallel workspace writers with implementation evidence aggregator #293 lands, the wording becomes truthful — and the plan blocks must carry the write-set discipline that real parallelism demands.
2. One route synthesizes its final report via a hand-rolled delivery contract (write a markdown file to a temp dir, submit only the path). The runtime now natively supports output-by-reference: submitting an absolute file path records a content_ref with size and SHA-256 into the managed workflow-reports area with automatic gitignore handling. The hand-rolled version bypasses the integrity receipt and writes outside the managed area.

Solution

1. Update the full project-development reference so its parallel-slice wording is honest, and bake the triple-disjoint write-set contract into the plan block's instruction: source files, generated artifacts, and lockfiles must all be disjoint across parallel writers, and no shared build may be triggered.
2. Delete the hand-rolled delivery-contract block from the full route; rely on the runtime's native output-by-reference for the final report.
3. Sweep remaining route/library wording for serialization promises.
4. Bump runtime-compat.json to the spec(dag): parallel workspace writers with implementation evidence aggregator #293 merge SHA and pass the config repo's template-validation CI in the same change.

User Stories

1. As a parent orchestrator reading a saved route, I want "parallel slices" to mean what it says, so that my concurrency budget is a real expectation.
2. As a plan block worker, I want my instruction to state the triple-disjoint rule explicitly, so that I partition write sets correctly before parallel slices spawn.
3. As a report consumer, I want final reports delivered through the managed reports area with an integrity receipt, so that report content is verifiable.
4. As the config-repo maintainer, I want runtime-compat pinned to the exact runtime merge SHA, so that CI template validation runs against the compiler that produced these shapes.

Implementation Decisions

1. Wording and contract changes only — no graph-shape changes in this ticket; the parallel compilation behaviour comes from spec(dag): parallel workspace writers with implementation evidence aggregator #293.
2. The triple-disjoint contract is expressed in block instructions (plan slice), not as new schema fields.
3. Native report delivery replaces the temp-file mechanism; the route keeps one synthesize block and depends on runtime file-ref capture.
4. Landing rule: runtime merge first, then this repo's PR bumps the SHA and updates templates in the same change, matching the documented policy for incompatible block rules.

Testing Decisions

• The config repository's own template-validation CI (which validates every root YAML with the runtime-owned validator at the pinned SHA) is the acceptance gate.
• Prior art: existing route YAMLs validated the same way.

Out of Scope

• Any compiler change (owned by spec(dag): parallel workspace writers with implementation evidence aggregator #293).
• Author-declared write_set fields, codegen-cache contention detection.

Further Notes

• While spec(dag): parallel workspace writers with implementation evidence aggregator #293 is unmerged, the full route's "parallel" wording is technically dishonest — acceptable interim state, documented here.

[LeXwDeX]

Prepared on the config repo branch feat/parallel-writers-contract (commit 20698f3): project-development-full plan block carries the triple-disjoint write-set contract; development-report now uses native output-by-reference instead of the hand-rolled temp-dir delivery contract; local route-catalog validation green (14/14). REMAINING (gated): runtime-compat.json bump to the #293 merge SHA + full template-validation CI — lands with the runtime merge, per the incompatible-block-rule policy.

[LeXwDeX]

已由配置库 PR LeXwDeX/opencode-dag-config#9 实现（commits 20698f3/ee6c5f7，标题含 issue #295），并随本仓库 v1.0.21 的 runtime 支持落地：三写集不相交契约 + 原生报告交付 + runtime-compat 对齐。模板侧已合并，运行时侧 v1.0.21/22 实机验证通过。