ci: re-trigger bisect to verify fix on baseline entry

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: backspace

.github/workflows/bisect-cs-10966.yaml

@@ -1,7 +1,15 @@
 name: Bisect CS-10966
 
-# Manually-triggered bisect for the "displays highlights filter" failing host
-# test. Each matrix entry checks out a different `bisect-*` tag (each tag is
+# Verification run after applying the fix at store.ts:1880 (normalize
+# non-resolvable instance ids before deserialization). The 'baseline'
+# matrix entry now includes the fix; if it passes the failing test, the
+# regression is resolved. The other bisect-* tags are unchanged and still
+# pinned to the original revert baseline, so re-running them is mostly
+# redundant — kept as a control to confirm the matrix infrastructure itself
+# is healthy.
+#
+# Manually-triggered bisect for the "displays highlights filter" failing
+# host test. Each matrix entry checks out a different `bisect-*` tag (each tag is
 # the rri-widen-relativeTo-cs-10966 baseline + ONE re-introduced runtime
 # behavior change). Matrix entries run in parallel; the failing entries
 # identify the specific edit(s) that trigger the realm-server 500