docs: record the test state the previous commit omitted

92d7b8e repaired the module graph and reported only "build exit 1 -> 0". That
was accurate but incomplete: `go test ./...` is 9 ok / 12 FAILING.

Those 12 are NOT a regression from that commit. The packages could not compile
before it, so their tests never ran at all — repairing the build made
pre-existing failures reachable for the first time. Recording it because a
build-fixed commit that quietly leaves a dozen red tests is exactly the kind of
thing that reads as "done" and is not.

Left failing rather than papered over; they need someone who knows the intent.
This commit is contained in:
zeekay
2026-07-26 06:45:55 -07:00
parent 92d7b8e105
commit bc73f1f3f5

Diff Content Not Available