What
After PR #38 lands the canonical envelope { ok, errors?, data? } (docs/contracts.md §4) as the single shape for ALL agent endpoints, DESIGN.md §3.4 still describes the legacy { accepted: true | false, errors } shape for submit_result. The two now disagree.
Fix
Update DESIGN.md §3.4 to reference docs/contracts.md §4 (and §4.4 for the validation-error subshape) as authoritative. Either rewrite §3.4 inline or replace it with a one-paragraph pointer.
Why a separate PR
Spec changes get their own PRs (per AGENTS.md). This is purely a docs reconciliation — no code touched.
Discovered while
Reviewing PR #38 (M0 boundary contracts).
cc orchestrator session
What
After PR #38 lands the canonical envelope
{ ok, errors?, data? }(docs/contracts.md §4) as the single shape for ALL agent endpoints, DESIGN.md §3.4 still describes the legacy{ accepted: true | false, errors }shape forsubmit_result. The two now disagree.Fix
Update DESIGN.md §3.4 to reference docs/contracts.md §4 (and §4.4 for the validation-error subshape) as authoritative. Either rewrite §3.4 inline or replace it with a one-paragraph pointer.
Why a separate PR
Spec changes get their own PRs (per AGENTS.md). This is purely a docs reconciliation — no code touched.
Discovered while
Reviewing PR #38 (M0 boundary contracts).
cc orchestrator session