diff --git a/src/srf_opts.zig b/src/srf_opts.zig
index 58be8d6..2e24060 100644
--- a/src/srf_opts.zig
+++ b/src/srf_opts.zig
@@ -32,14 +32,6 @@ const srf = @import("srf");
 /// every `zfin portfolio` run; the fix was to turn this on for
 /// `portfolio.srf` alone, which left every other hand-edited file
 /// exposed to the same typo.
-///
-/// This is mitigation, not a cure. Two holes remain, both needing an
-/// upstream fix in SRF's `coerce`:
-///
-///   - a non-string, non-number value in a numeric field (say
-///     `harvested:bool:true`) still reaches the unchecked access;
-///   - enum fields ignore this option entirely, so a typo like
-///     `security_type::stok` still hits `stringToEnum(...).?`.
 pub const user_edited: srf.CoercionOptions = .{ .strings_to_numbers = true };
 
 /// For files ZFIN writes: the candle, quote, and options caches,