Point In flight at the tracker instead of listing CF PRs

Val decided on #290. The In flight entry for native conversation fidelity
listed open PRs by number, and the list went stale within hours. It already
named #291 (merged into #286) and missed #295, #297, #298 and #299. The entry
now says the tracker's child issues link their open PRs, which GitHub keeps
current.

Coven-Harness: Claude Code / claude-opus-5-5

Author: BunsDev

docs/status.md

@@ -168,8 +168,8 @@ and [landing verification](reviews/2026-10-11-landing-clarity.md).
 
 
 - **Native conversation fidelity** ([tracker #273](https://github.com/TypeSafeAI/modex/issues/273)).
-  Slices that landed are under "On main, unreleased". Open: #283 and #288 (CF-4), #286 and #291
-  (CF-2), and #293 (CF-3). The tracker keeps the dependency order and each slice's evidence.
+  Slices that landed are under "On main, unreleased". The tracker keeps the dependency order and
+  each slice's evidence, and its child issues link their open PRs.
 
 - **Mac App Store edition.** A sandboxed Store front end with a separately installed signed
   host, as Val chose. [Investigation and parity matrix](mac-app-store.md).