doc-generation

To prevent documentation drift, enforce strict doc queue ordering and treat api.md as the single source of truth. This ensures setup.md, user_manual.md, api.md, and examples are updated first, with README.md always generated last.

Documentation generation supports resumption after hitting token limits by applying partial versus full regeneration rules. This continuation behavior safely resumes the workflow without losing previously generated content or breaking the strict file ordering.

Safe README updates require constrained integration using only overview-level changes, generating README.md last in the doc queue. This enforces correct structure and ensures acknowledgments, disclaimers, and licenses appear only at the end in the proper order.

Diff-based updates maintain stable documentation structures by routing content to the correct files and applying changes only where needed. Using api.md as the authoritative source, this approach generates code and docs based on validated function signatures and options.

Automated documentation generation supports multiple markdown files by enforcing a strict processing queue. It routes content to setup.md, user_manual.md, api.md, examples/example.md, and README.md sequentially, ensuring correct ordering and compliance across the package documentation.