Render KOReader ribbon page bookmarks as "Bookmarked"

KOReader's ribbon (corner-tap) page bookmarks live alongside text
highlights in the same `annotations` array, distinguished by the
absence of a `pos0`/`pos1` selection range. KOReader auto-fills the
`text` field with "in <chapter>" for those rows so they render as
something in its own UI.

The plugin was passing that auto-text straight into the highlight
renderer, producing blocks like:

    > in Chapter 4: Natural and Spiritual Freedom
    chapter:: Chapter 4: Natural and Spiritual Freedom
    page:: 360

instead of the canonical bookmark shape:

    > Bookmarked
    chapter:: Chapter 4: Natural and Spiritual Freedom
    page:: 360

Detect the missing selection range in the parser and clear `text` so
the existing renderer's "empty text → page bookmark" path takes over.
Same fix on the legacy `bookmarks` array; also dropped the wrong
`b.notes` fallback that previously mirrored auto-text into `text`.

Author: CR0CKER

src/sidecar.ts

@@ -132,7 +132,7 @@ function extractHighlights(raw: any): KoreaderHighlight[] {
     for (const a of annotations) {
       if (!a) continue
       out.push({
-        text: stringOrUndefined(a.text) ?? '',
+        text: isRibbonBookmark(a) ? '' : stringOrUndefined(a.text) ?? '',
         note: stringOrUndefined(a.note),
         page: a.pageno ?? a.page,
         chapter: stringOrUndefined(a.chapter),
@@ -150,7 +150,7 @@ function extractHighlights(raw: any): KoreaderHighlight[] {
     for (const b of bookmarks) {
       if (!b) continue
       out.push({
-        text: stringOrUndefined(b.notes) ?? stringOrUndefined(b.text) ?? '',
+        text: isRibbonBookmark(b) ? '' : stringOrUndefined(b.text) ?? '',
         note: undefined,
         page: b.page,
         chapter: stringOrUndefined(b.chapter),
@@ -162,6 +162,19 @@ function extractHighlights(raw: any): KoreaderHighlight[] {
   return out
 }
 
+/**
+ * KOReader's ribbon page-bookmarks live alongside text highlights in
+ * the `annotations` (modern) and `bookmarks` (legacy) arrays. They have
+ * no `pos0`/`pos1` selection range — those are present on every text
+ * highlight — and KOReader auto-fills `text` with "in <chapter>" so the
+ * row renders as something in its own UI. We detect the shape via the
+ * absent selection range and discard the auto-text so the renderer's
+ * "empty text → page bookmark" path can produce `> Bookmarked`.
+ */
+function isRibbonBookmark(a: any): boolean {
+  return !stringOrUndefined(a?.pos0) && !stringOrUndefined(a?.pos1)
+}
+
 function deriveHighlightId(a: any): string {
   // Compose a stable per-highlight key. KOReader doesn't ship a UUID, but
   // the (datetime, pos0, pos1) tuple is unique within a sidecar; falling back