Check resolved types at the public boundary

docs/roadmap/remediation.md

@@ -2,7 +2,7 @@
 
 Review baseline: `5dc7e18`. Reviewed commits `f81def9` through `5dc7e18` against
 `eb7de8e`, the agreed [roadmap](public.md), and [implementation plan](implementation.md).
-Status: three open findings; F1 resolved. Review evidence below describes the
+Status: two open findings; F1 and F2 resolved. Review evidence below describes the
 original baseline; resolution records describe the subsequent fixes.
 
 The previous provenance finding remains resolved; its record is preserved at
@@ -58,7 +58,15 @@ everyday check, and the race suite.
 
 ## F2 — Close the public-boundary check's type-resolution gaps
 
-Priority: medium. Status: open.
+Priority: medium. Status: resolved.
+
+Resolution: [public_boundary_test.go](../../public_boundary_test.go) loads the
+active build's compiler export data and walks resolved Go types, exported method
+sets, and generic constraints. Declaration fixtures cover exposure and valid
+private-backed wrappers. The original three probe declarations now each fail
+the actual root check; the temporary probe was removed afterwards. The everyday
+check passed with Go 1.26.7, and boundary tests passed with Go 1.25.5 and Go 1.26.7
+on Linux. No production behavior or public surface was changed.
 
 ### Evidence and impact