cf8789f84c
splitByHeadingsImpl detects the dominant Markdown heading level via the profiler and splits the document at headings of that level (or shallower). Each resulting chunk gets a breadcrumb prefix like '# Chapter 1\n## Section 1.2' so downstream embedding sees the section context, not just the body. Sections larger than ChunkSize fall back to the legacy splitter for inner segmentation, with the breadcrumb prepended to every sub-chunk and ChunkSize reduced by the breadcrumb length so the final chunk still fits the budget. - DominantHeadingLevel: prefer the lowest level with ≥3 hits, else the deepest level with ≥1 hit (so small docs with H1+H2 still split at H2) - HeadingHierarchy state is updated for sub-headings within a section so later primary sections see the right active stack - Code-block contents are skipped during heading detection so a `# foo` inside ``` doesn't create a fake boundary - strategy.go uses context.Background() for the fallback log entry (GetLogger panics on nil context) https://claude.ai/code/session_01XADhx6mtu2ZYW3DE9Lun6k