resolve TODO

Author: Carolyn Zech

scripts/autoharness_analyzer/README.md

@@ -14,5 +14,3 @@ on the standard library. The scanner_results/ directory contains the CSV files t
 The output is `autoharness_data.md`, which contains Markdown tables summarizing the autoharness application across all the crates in the standard library.
 
 One of the tables has a column for "Skipped Type Categories." Generally speaking, "precise types" are what we think of as actual Rust types, and "type categories" are my subjective sense of how to group those types further. For example, `&mut i32` and `&mut u32` are two precise types, but they're in the same type category `&mut`. See the code for exact details on how we create type categories; the TL;DR is that we have a few hardcoded ones for raw pointers and references, and the rest we create using a fully-qualified path splitting heuristic.
-
-See TODOs for known limitations and future work.

scripts/autoharness_analyzer/src/make_tables.rs

@@ -30,9 +30,8 @@ fn chosen_overview_table(
                 safe_count += 1;
             }
         } else {
-            // TODO: Note that we don't include these functions in the totals, so the metrics are still right,
-            // and thankfully it seems to affect a pretty small slice of the whole.
-            // (The todo is for Carolyn to investigate these mistakes).
+            // See https://github.com/model-checking/verify-rust-std/pull/350#discussion_r2091698600
+            // for examples of when such discrepancies appear
             println!(
                 "[WARNING] Function {} is in in autoharness metadata but absent in scanner tool output",
                 fn_name