Test Implementing New SuperDoc Heading Detection

Difference between current and new process is explained in 3/31 meeting notes. Test to see if it's work spending the time to refactor it, will then decide if we will implement.

No files, tests, or commands are named, and the issue only references the 3/31 meeting notes. Begin by reading those notes, then map the described current vs new SuperDoc heading-detection process to the relevant code paths in the repo. Identify and run the corresponding heading-detection tests or processing flow once located, and mark the issue done only when results clearly justify whether a refactor is worth implementing.

Scritto dal modello di indicizzazione a partire dal testo della issue.