What problem does it solve? Publishing a documentation archive as a MkDocs site requires a navigation file that matches what actually exists on disk. Hand-written nav entries drift from reality, producing menu items that point to pages that do not exist, and a generated config alone does not prove the site builds. ## Core Features & Use Cases - Disk-derived navigation: Runs python -m ferramentas.exportar to write mkdocs.yml with a nav built only from volumes and sections that exist as files, never from declared-but-unmaterialized content. - Optional strict build validation: When mkdocs is on the PATH, the tool runs mkdocs build --strict and reports one of three outcomes: generated and validated, generated but not validated (mkdocs missing, exit 0), or generated but build failed (exit 1). - Honest reporting rules: The skill mandates explicit wording about whether the build was validated, forbidding claims like "exported successfully" when mkdocs was not installed. - Use Case: After adding chapters to the AI-ENGINEERING-OS archive, run the export to regenerate the site config and confirm with a strict build that no Mermaid syntax errors, broken relative links, or orphaned sections slipped in. ## Quick Start Run the exportar skill from inside the AI-ENGINEERING-OS directory to generate mkdocs.yml and report whether the strict MkDocs build was validated, skipped, or failed.
