What chunking strategy actually works for dense technical documentation?

We've tried fixed-size, sentence-boundary, and section-heading chunking on API docs and engineering runbooks. Fixed-size splits code samples in half. Sentence-boundary misses context. Section chunks are too large. How are practitioners solving chunking for technical content where a paragraph reference earlier in the doc changes the meaning of a later paragraph?