issue-277: reconcile error.json kind enum across DESIGN/IMPLEMENTATION_PLAN/README with DOMAIN.md #278
Loading…
Reference in a new issue
No description provided.
Delete branch "documentation/issue-277/reconcile-error-json-kind-enum-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
DESIGN.md, IMPLEMENTATION_PLAN.md, and README.md documented the
error.jsonkindenum as:missing
auto-merge-timeoutandauto-merge-failed. These two kinds are pre-existing validErrorKindvalues (from the--auto-mergefeature, PR #39) and are already supported by the code (src/orchestrator/types/orchestrator.ts,src/artifacts/helpers/validateErrorReport.ts) and already documented inDOMAIN.md'serror.json kindglossary row.Issue-267's remediate stage fixed the DOMAIN.md row (adding
network,auto-merge-timeout,auto-merge-failed) in response to a review finding, but only touched DOMAIN.md — leaving DESIGN.md, IMPLEMENTATION_PLAN.md, and README.md inconsistent (they hadnetworkfrom 267's stage-1 commit, but never got the auto-merge kinds).This PR brings all three docs in line with DOMAIN.md and the code, so the
error.jsonkindenum is documented consistently everywhere:Per-file breakdown
DESIGN.md— addedauto-merge-timeout|auto-merge-failedto theerror.jsonkindexample (§ artifact schemas).IMPLEMENTATION_PLAN.md— same addition to the matchingerror.jsonkindexample.README.md— same addition to the matchingerror.jsonkindexample (Error Handling section).Docs-only change; no code or test changes required.
Closes #277