Metadata cache: a note with a footnote gets two extra zero-length sections after its last block

Steps to reproduce

  1. Create a note Test.md with this content:

    Text[^1]
    
    [^1]: Note ^abc
    
  2. Open the developer console (Ctrl+Shift+I) and run:

    app.metadataCache.getFileCache(app.vault.getAbstractFileByPath('Test.md')).sections
    

Did you follow the troubleshooting guide?

Yes (reproduced in the sandbox vault, no community plugins).

Expected result

Two sections, one per block: a paragraph and a footnoteDefinition.

Actual result

Four sections. After the two blocks come a section of type text and one of type element, both zero-length (start equals end), placed at the start of the line after the last block. The element section also carries id: "abc", the block id written inside the footnote definition.

The same two sections appear for an inline footnote (Text^[note]), and when two definitions share a label. A note without footnotes (Text / More ^abc) gets only its real sections.

The block index is affected too: getFileCache(...).blocks.abc points at that empty position on the line after the definition (line 3, column 0, start equals end), not at the footnote definition that holds ^abc.

Environment

SYSTEM INFO:
	Obsidian version: 1.14.5
	Installer version: 1.14.4
	Operating system: Windows 11 Pro 10.0.26300
	Login status: not logged in
	Language: en
	Insider build toggle: off
	Live preview: on
	Base theme: adapt to system
	Community theme: none
	Snippets enabled: 0
	Restricted mode: on

RECOMMENDATIONS:
	none

Sandbox vault, no community plugins, default theme and settings.

Additional information

These look like leftovers of the footnotes section the indexer builds internally. A plugin that walks sections (to map lines to blocks, or to find a block by its id) meets two blocks that are not in the note, and an element section that claims a block id with no content.