docs(style): record readability validation
This commit is contained in:
parent
3a740eb95d
commit
d29532a735
1 changed files with 7 additions and 0 deletions
|
|
@ -1323,3 +1323,10 @@ GCC 16.2.1 now compiles beyond the former `misleading-indentation` failures in
|
||||||
blocked by distinct pre-existing `format-truncation` diagnostics in the Web
|
blocked by distinct pre-existing `format-truncation` diagnostics in the Web
|
||||||
accepted-response buffer and bounded test path buffers. Warning policy remains
|
accepted-response buffer and bounded test path buffers. Warning policy remains
|
||||||
unchanged; GCC is not reported as green.
|
unchanged; GCC is not reported as green.
|
||||||
|
|
||||||
|
The readability closeout preserves the **81/81** normal Meson and **81/81**
|
||||||
|
ASan/UBSan inventories. The isolated Android run reports **220 tests: 215
|
||||||
|
passed, five skipped, zero failures/errors**, and `assembleDebug` succeeds on
|
||||||
|
JDK 17. The real Firefox/object-I/O-boundary MTP conversation also passes after
|
||||||
|
formatting. A source comparison against the pre-readability commit confirms
|
||||||
|
that the scoped test names and assertion counts are unchanged.
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue