docs: clear the last eight findings and bound three metrics to what they measure - #609
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Thank you for following the naming conventions! 🙏 |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
648b344 to
2b2b4ec
Compare
commit: |
…st-findings # Conflicts: # .agents/skills/write-evlog-content/references/corrections.md
1 participant
Stacked on #608. The corpus is at 120 clean pages of 120, average 100.0.
Four of the eight were the scanner overreaching, all recorded in
corrections.md:T-11called two paragraphs adjacent when 87 and 141 lines separated them. A seam is a stitch, so the metric now only compares paragraphs at most three apart on the page.U-12readWithout \setup`, OpenTelemetry export is untouchedas a claim about OpenTelemetry.withoutandinstead of` only compare what directly follows them.U-14never saw--, which is the same mark typed with the keys at hand. The README carried five. Fenced code and table cells keep theirs, sinceevlog-map-disable-next-line wide-event -- reasonis the CLI's own syntax.The other four were real:
three orders of magnitude below the cheapest thing the request already does), and the three comparisons against pino and consola link the benchmark rows that back them.