docs(readme): refresh three stale Metrics rows from their own commands - #380
Open
dmitrii-f-t27 wants to merge 1 commit into
Open
docs(readme): refresh three stale Metrics rows from their own commands#380dmitrii-f-t27 wants to merge 1 commit into
dmitrii-f-t27 wants to merge 1 commit into
Conversation
Each row in the "Metrics (что уже измерено)" table prints the shell command that produces its value, under the promise "Все числа — с on-device логов, без hearsay". Three rows had drifted from what their own command returns. Values below are the verbatim output of the printed command run at 759f5e9. README.md:91 — Rust `#[test]` blocks: 110 → 432. `grep -rE '^\s*#\[test\]' src tests | wc -l` => 432 (same count under BSD grep, ugrep, and with [[:space:]] in place of \s) README.md:92 — Rust source lines: 4 463 → 10 350. `find src -name '*.rs' | xargs wc -l` => 10350 total (38 files, single xargs batch, so one total line) README.md:100 — T27 spec files: 1 (`specs/wire.t27`) → 107. `find specs -name '*.t27' | wc -l` => 107 The row's command was `find specs -name '*.t27'`, which lists names rather than counting them; added `| wc -l` so the printed command reproduces the printed value. NOTE: the label says "ported" but the command measures files present — relabel if "ported" was meant to track a smaller subset. No other row of the table and no part of the earlier status table is touched. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
dmitrii-f-t27
force-pushed
the
fix/readme-metrics
branch
from
August 11, 2026 11:51
4cdeb95 to
68d90a4
Compare
This was referenced Aug 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Each row of the «Metrics (что уже измерено)» table prints the shell command that produces its value, under the promise «Все числа — с on-device логов, без hearsay». Three rows had drifted from what their own command returns. Every value below is the verbatim output of the printed command, run at
759f5e9.README.md:91Rust#[test]blocksREADME.md:92Rust source linesREADME.md:100T27 spec filesspecs/wire.t27)The spec-file row also printed
find specs -name '*.t27', which lists paths rather than counting them, so it could never have produced the number beside it. Added| wc -lso the printed command reproduces the printed value.One decision left to you: that row is labelled «ported». The command measures files present. If «ported» was meant to track a smaller subset, the label and the value still measure different things — relabel as you see fit.
Nothing else in the Metrics table is touched. The status table above it is deliberately untouched: its M3/M4 rows are correctly
-sim, and the silicon row (NO ROUTE — no die exists, none is scheduled) reads correctly as written.Pipeline compliance: documentation only. No
.t27spec, no Rust and nogen/file is touched, so the spec, parse and build items are n/a andcargo build --releaseis unaffected. This README is Russian by design, so the English+ASCII rule does not apply to it. No issue referenced — this came out of a documentation audit.phi^2 + phi^-2 = 3