Reorganize docs into an audience-first file tree
The folder structure never caught up with the curriculum. Readers saw a clean module path in the sidebar while the files still sat in legacy buckets (learn/, value/, foundations/, get-started/) next to build/ and native-tokens/. Contributors had to hold two mental models. Collapse everything into the structure readers actually navigate: - docs/developers/ holds the developer sidebar: a curriculum/ tree with numbered module folders (01-fundamentals through 07-production) plus an integrations/ section. Numeric prefixes order the tree; Docusaurus strips them so URLs stay clean. - docs/operators/ holds the stake pool content (was operate-a-stake-pool/) plus a security/ folder for the air-gap and secure-workflow guides. - community/ and contribute/ stay top-level as cross-cutting meta. No get-started/, infrastructure/, learn/, build/, value/, foundations/, or first-steps/ buckets survive. Shared node pages live once under Module 7 and the operators sidebar cross-links them. Mechanics: ~260 file moves, every internal /docs/ link rewritten by prefix, sidebars.js re-keyed (networkSidebar is now operatorsSidebar), redirect targets repointed so old prod URLs resolve straight to the final location, and the llms path-fix script and includeOrder globs updated. Old prod URLs keep working through redirects; curriculum-spine URLs were never published so they need none. The developer sidebar groups the seven modules under a Curriculum category so the navigation mirrors the developers/curriculum/ tree, with Start Here on top and Integrations/Community/Contributing alongside. Also drops the two orphaned cardano-wallet REST-server pages. They sat in no sidebar, taught the legacy run-your-own-wallet-backend approach the curriculum already covers through SDKs and API providers, and only the payments-listening guide referenced them (now pointed at the upstream repo).