Merge Docusaurus site: all content under docs/, align with gregFramework split layout

- Move markdown and wiki-import tree into docs/; keep app shell at repo root
- Point docusaurus docs path to docs/; edit links to mleem97/gregWiki
- Sync and i18n scripts use gregWiki root and ../.wiki under gregFramework
- Sidebars: workspace layout from root docs ids; plugins under mods/extensions
- Fix redirects, module catalog URLs, release note paths, and wiki-import category keys
- Update repo inventory for split repos; Dockerfile for single-repo context

Made-with: Cursor

docs/contributors/docusaurus-workflow.md

@@ -0,0 +1,40 @@
+---
+id: docusaurus-workflow
+title: Docusaurus Contributor Workflow
+slug: /contributors/docusaurus-workflow
+---
+
+## Local workflow
+
+Markdown and MDX live in the repo-root `docs/` folder. The Docusaurus app is in `wiki/`.
+
+```bash
+cd wiki
+npm install
+npm run start
+```
+
+## Build workflow
+
+```bash
+cd wiki
+npm run build
+npm run serve
+```
+
+## Can we hide Docusaurus build stuff from non-contributors?
+
+Short answer for a **public repo**: **not fully**.
+
+What you can do:
+
+- Keep generated output (`build/`, `.docusaurus/`, `node_modules/`) out of Git using `.gitignore`.
+- Put docs tooling under `wiki/` so core runtime contributors can ignore it; content stays in `docs/`.
+- Use path-based CODEOWNERS to limit review noise.
+- Trigger docs CI on `docs/**` and `wiki/**` changes.
+
+What you cannot do in a public repo:
+
+- Fully hide tracked source files from non-contributors.
+
+If you need true visibility restriction, use a private repo/submodule for docs infra.