Found in the second review of PR #316. Documentation/UX only.
1. Self-contradiction. The crash summary still tells the reader "a malformed community YAML will do this", which the comment added three lines above in the same commit explicitly declares false — a single malformed YAML lands in errors (exit 3), not crash (exit 2). The comment was corrected; the user-facing text it describes was not.
2. Incomplete error wording, inconsistently. The error note in both the job summary and the PR comment reads "an interaction, causal edge or discussion anchor names something the record does not contain" — omitting UNREADABLE and ID_MISMATCH. The same commit updated the equivalent wording on the Fail on broken references step to mention UNREADABLE but not ID_MISMATCH.
So one run can now say two different things about what turned it red.
Found in the second review of PR #316. Documentation/UX only.
1. Self-contradiction. The crash summary still tells the reader "a malformed community YAML will do this", which the comment added three lines above in the same commit explicitly declares false — a single malformed YAML lands in
errors(exit 3), notcrash(exit 2). The comment was corrected; the user-facing text it describes was not.2. Incomplete error wording, inconsistently. The error note in both the job summary and the PR comment reads "an interaction, causal edge or discussion anchor names something the record does not contain" — omitting
UNREADABLEandID_MISMATCH. The same commit updated the equivalent wording on theFail on broken referencesstep to mention UNREADABLE but not ID_MISMATCH.So one run can now say two different things about what turned it red.