This audit found that main currently fails cargo check --lib with 172 errors, root-caused to what looks like an incompletely resolved merge conflict (duplicate StorageKey/type/method definitions alongside missing types and error variants referenced by otherwise-unmerged feature code). Once the individual fix issues in this batch are resolved and the build is green again, the incident itself is worth documenting so future contributors understand what happened and why the safeguards proposed alongside it (CI compile gate, branch-protection audit, StorageKey/Error completeness checks) exist.
Suggested fix: once the build is restored, add an ADR (or a dedicated postmortem doc) describing the timeline, root cause, impact, and the specific process/tooling changes made in response, following the existing ADR format used elsewhere in docs/adr/.
Acceptance criteria: a postmortem document exists in docs/adr/ (or docs/) describing the incident and links to the CI/tooling safeguards added as a result.
This audit found that
maincurrently failscargo check --libwith 172 errors, root-caused to what looks like an incompletely resolved merge conflict (duplicateStorageKey/type/method definitions alongside missing types and error variants referenced by otherwise-unmerged feature code). Once the individual fix issues in this batch are resolved and the build is green again, the incident itself is worth documenting so future contributors understand what happened and why the safeguards proposed alongside it (CI compile gate, branch-protection audit, StorageKey/Error completeness checks) exist.Suggested fix: once the build is restored, add an ADR (or a dedicated postmortem doc) describing the timeline, root cause, impact, and the specific process/tooling changes made in response, following the existing ADR format used elsewhere in
docs/adr/.Acceptance criteria: a postmortem document exists in
docs/adr/(ordocs/) describing the incident and links to the CI/tooling safeguards added as a result.