fix: MarkdownHeaderSplitter silently drops a trailing header with no body text

[lntutor]

What's broken

With keep_headers=True (the default), MarkdownHeaderSplitter buffers a header whose only content is whitespace into pending_headers and prepends it to the next content chunk. But a header (or run of headers) at the end of the document has no next chunk, so the buffer is never flushed and the header text is dropped:

text = "# Header 1\nContent 1.\n# Header 2\n"
docs = MarkdownHeaderSplitter().run(documents=[Document(content=text)])["documents"]
"".join(d.content for d in docs)   # '# Header 1\nContent 1.\n'  -- '# Header 2' is gone

This breaks the reconstruction invariant the existing tests assert (test_basic_split, test_keep_headers_preserves_parent_headers_for_first_child both check "".join(doc.content) == original), and it's inconsistent: a middle empty header is preserved (prepended to the next chunk), a trailing one is dropped.

Fix

Track the start offset / text / level of buffered trailing headers and, before returning, flush them as a final chunk sliced from the original text (so byte-level reconstruction and downstream page counting stay exact) — mirroring how a middle empty header is already preserved.

Distinct from #11920 (content dropped before an embedded header/code-fence).

Tests

Adds test_trailing_header_without_content_is_not_dropped. Full test/components/preprocessors/test_markdown_header_splitter.py passes (35). Release note included.

[vercel]

@lntutor is attempting to deploy a commit to the deepset Team on Vercel.

A member of the Team first needs to authorize it.

[CLAassistant]

All committers have signed the CLA.

[HaystackBot]

Hi @lntutor, thanks a lot for your contribution! 🙏

We noticed that the Contributor License Agreement (CLA) check (license/cla) hasn't passed yet, so we've temporarily moved this PR to draft and paused the review assignment.

To get your PR reviewed, please sign the CLA via the link in the license/cla check below (or in the CLA bot comment). As soon as the check turns green, this PR will automatically be marked ready for review again and a reviewer will be re-assigned.

[HaystackBot]

Hi @lntutor, just a friendly reminder: this PR is still in draft because the Contributor License Agreement (CLA) hasn't been signed yet. We'd love to review your contribution! Please sign the CLA via the link in the license/cla check, and this PR will automatically be marked ready for review.

[HaystackBot]

Thanks for signing the CLA, @lntutor! 🎉 This PR is now ready for review again and the reviewer has been re-assigned.