docs: link issue #161 from the Page.xaml.cs timer FP re-triage notes

Cross-reference the tracked precision follow-up (non-IDisposable timer local
flagged OWN001) from the baseline entry and oracle-known-fps.md root-cause #1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019846YSZ35c7CdkWQ1qX5gm

Author: claude

corpus/oracle-fp-baseline.txt

@@ -43,7 +43,7 @@ protobuf-net/protobuf-net | ProtoTranscoder.cs | OWN001 | 'sync' | non-product (
 # btnRunTest_Click has a DispatcherTimer local) — neither is IDisposable. So the using-statement
 # fix does NOT apply here (confirmed: still emitted, still baselined). It stays a non-product FP;
 # the open question is WHY a non-IDisposable timer-shaped local is flagged at all (needs a local
-# extractor repro). See docs/notes/oracle-known-fps.md root-cause #1.
+# extractor repro; tracked in issue #161). See docs/notes/oracle-known-fps.md root-cause #1.
 protobuf-net/protobuf-net | Page.xaml.cs | OWN001 | local 'timer' | non-product (assorted/ Silverlight perf sample); `timer` is a non-IDisposable Stopwatch/DispatcherTimer and the only using(timer) block is commented out — not a missed-using; flagging it is a separate precision question, kept baselined
 
 # --- JamesNK/Newtonsoft.Json ----------------------------------------------------

docs/notes/oracle-known-fps.md

@@ -155,7 +155,7 @@ entry and let the oracle re-confirm clean.
    local (`btnRunTest_Click`) — neither is `IDisposable`. So the entry stays baselined as a
    non-product sample FP; the real open question is **why a non-`IDisposable` timer-shaped
    local is flagged at all** (a precision follow-up needing a local extractor repro, not a
-   missed `using`). Other custom-sink fixtures: `field-dispose-via-helper`,
+   missed `using`; tracked in issue #161). Other custom-sink fixtures: `field-dispose-via-helper`,
    `field-dispose-via-exchange`.
 
 2. **No-op `Dispose` not modelled — PARTLY FIXED** *(Newtonsoft `TraceJsonReader.