1.20.0

Everything from the 1.20.0 betas, listed in full below, plus two fixes: Debug mode now logs, and the reply box in the side panel follows Send comment on Enter.

Added

• Click the "Original text" of an addressed comment in the Thread tab to jump to that comment in the note. It also works from the keyboard (Tab to it, then Enter or Space). Selecting text in the block to copy it does not jump. (#82)
• Focus mode in the Thread tab. Press Focus on an expanded comment and the tab shows only that comment, with its full conversation, reply box and actions, so a long thread does not run into the others. Show all brings the list back with the comment still selected. The focus stays put while you switch notes, follows the note through a rename, and keeps showing the comment after you resolve it. Clicking a different comment's marker in the editor leaves focus. (#83)
• Open in tab opens one comment in a tab of its own in the main area, titled with its category and id, showing only that comment's conversation with the reply box and every action. Opening the same comment again brings its tab forward instead of adding another. The tab comes back after a restart and follows its note through a rename. Comments without an id cannot have a tab. (#83)
• Range comments. A comment made on a selection now also marks where the selection ends, with a closing marker <!-- /annoteca <id> --> after the passage. The comment then covers exactly that text, however long, across lines and paragraphs: the underline, the highlight and the jump flash cover exactly that span, and Reject restores exactly that span instead of only the rest of the marker's line. Reject refuses, and says why, when the text it would overwrite holds another comment, which it would otherwise delete. Deleting a comment, "Resolve and remove" and "Delete all resolved comments" remove its closing marker with it. Comments made at the cursor, and every existing comment, keep marking only where their passage starts and work exactly as before. A selection that starts or ends inside a code block, inline code or the note properties gets no closing marker, and a notice says why. Older versions of Annoteca read a closing marker as an ordinary hidden HTML comment. (#84)
• A comment made with a closing marker says so in its own marker ([range=closed], or "range": "closed" with end-of-file storage). The orphan check reports a closing marker that went missing, for example one an edit dropped along with the old text, and closing markers that pair with nothing: one whose comment is gone, one above its own comment, two with the same id, or one whose comment was copied.
• The exported AI skill teaches closing markers and the [range=closed] line (skill version 10), so re-export it: an assistant on the old skill does not know to keep the closing marker at the end of a passage it rewrites.
• The Pandoc filter strips closing markers from published output.
• API: anchorsFor reports a range comment as exactly the text between its markers.
• API (version 4): promote takes an optional closeRange per request. With it set, Annoteca also writes a closing marker at the end of the range, so the comment covers exactly that text, and each created comment reports closed, saying whether one was written. Without the option nothing changes, and an older Annoteca ignores it.
• Jumping to a comment briefly highlights it, so you can see where you landed. For an addressed comment the highlight covers the edited text after the marker; otherwise it covers the commented passage, or the marker when there is none. With reduced motion turned on in your system, the highlight shows as a steady tint instead of a fade. (#82)
• Add comment for current sentence, in the command palette and the right-click menu. Click inside a sentence and run it: Annoteca selects that sentence and opens the comment form, and the comment covers exactly the sentence. A sentence ends at ., !, ? or … followed by a space, keeps its closing quotes, and never runs past its paragraph. Each list item, heading and quote is its own block, and their markup stays outside the sentence. Common abbreviations, initials and decimals do not end a sentence. A table row is not a sentence, since a comment marker inside a row would break the table; select the text yourself there. (#84)
• The Outline tab is now a tree. Headings nest under their parent headings, and List items adds the note's list items under them, nested as the note nests them. Each line shows a badge for the comments on it, and each heading shows its open and resolved counts rolled up from everything below it, so a collapsed branch still shows its work. Only with comments hides the lines that have none. Click a row to jump to it and see its comments, with buttons to open the thread, go to the text, or open the comment in its own tab. The button on each row comments on exactly that line, leaving out list, task and heading markup. The tree works from the keyboard: Enter selects a row, and the left and right arrows fold and unfold. (#84)
• API (version 5): compose(path, range) lets another plugin ask you to comment on exact text in a note. Annoteca opens the note, selects that text and opens its own comment form, so the comment is yours, with a closing marker. Nothing is written until you save. It is the hook a companion view, such as a mind map, needs for a "comment on this" action.

Fixed

• Debug mode did nothing. The setting and its log destination have been in the settings tab since the first version, but nothing read them, so turning it on logged nothing. It now records how long Annoteca takes to index each note, how long a comment write waits behind earlier writes and how long it takes, how long the frontmatter summary waits and takes to write, and when Obsidian's metadata cache picks the summary up, which is when a Bases view can see it. Each entry is one line of JSON, sent to the developer console or to debug.log in the plugin folder. The file keeps roughly the newest 1 MB, and Copy debug log copies it so you can paste it into an issue.
• The reply box in the Thread tab and in a comment's own tab ignored Send comment on Enter, so Enter always started a new line there. It now follows the setting, like the comment form and the reply box in the note.
• Clicking a card in the Thread tab moved the cursor to its comment but left the editor highlight on the comment selected before. The highlight now follows the card you click.
• On a note saved with Windows line endings, the Outline tab could count a comment under the wrong heading.
• The Outline tab could show the previous version of a note, or "No headings" for a new one, until something else refreshed it. It now updates when Obsidian finishes reading the note.
• Clicking a comment's text in an open card in the Thread tab now jumps to the comment in the note, the same as the original text of an addressed comment. Clicking a link in the text still follows the link, and selecting text to copy it does not jump. (#82)
• Opening a comment from a note in a pop-out window opened the comment panel in the main window, on whatever note the main window had open, so it often showed the wrong comment. A pop-out window has no side panel, so the comment now opens in a tab beside the note in the pop-out, and the popover's button there reads Open beside note. This covers clicking a marker, the popover's buttons, the reading-view indicator, the right-click menu, Reply to comment here, and next and previous comment. One tab follows you from comment to comment instead of a new tab opening for each. A comment without a unique ID cannot have a tab, so a notice says to open the note in the main window instead. Clicking a comment in the side panel still selects it there.

VirusTotal

• main.js
• manifest.json