Referenced the upstream Qdrant Edge issues (#1035)

documentation/compatibility-shims/2026-10-qdrant-edge-wal-compaction.md

@@ -2,7 +2,7 @@
 
 - Status: Active
 - Introduced: 2026-10-09
-- Remove after: when a qdrant-edge release acknowledges its WAL in `EdgeShard::flush` by itself
+- Remove after: when a qdrant-edge release acknowledges its WAL in `EdgeShard::flush` by itself, see [qdrant/qdrant#11068](https://github.com/qdrant/qdrant/issues/11068)
 - Code references:
   - `runtime/src/qdrant_edge_database.rs` (`compact_wal`, `has_obsolete_wal_segments`, `remove_obsolete_wal_segments`, `wal_file_names`, `obsolete_wal_segments`, `optimize_store`)
 

runtime/src/log.rs

@@ -54,7 +54,8 @@ pub fn init_logging(bundle_identifier: &str) {
     // we cannot do it. Qdrant Edge then falls back to its defaults, which are correct
     // for us, but warns on every load and every optimization. On Windows, it logs every
     // ignored madvise call at debug level. Check these modules again for new warnings
-    // whenever qdrant-edge gets updated:
+    // whenever qdrant-edge gets updated, and drop the first two filters once
+    // https://github.com/qdrant/qdrant/issues/11069 is solved:
     log_config.push_str("qdrant_edge::common::flags=error, ");
     log_config.push_str("qdrant_edge::common::mmap::ops=error, ");
     log_config.push_str("qdrant_edge::common::mmap::advice=info");