feat(superadmin): migrate internal docs from docusaurus to guava kb

docs/ops/deployment/docker.md

@@ -117,11 +117,10 @@ Because the app image keeps the authoritative copy of the code, each container r
 - Configure backups for the `storage` directories and database dumps.
 - Hook into your observability stack (e.g., ship container logs to Loki or ELK).
 
-## 9. Internal docs publishing
+## 9. Internal docs access
 
-- Build the static docs site locally or in CI via `./scripts/build-docs-site.sh` (runs `npm ci && npm run build` in `docs/site/` and outputs to `docs/site/build`).
-- The Nginx container mounts that build directory and serves it at `/internal-docs/`. History fallback is already configured in `docker/nginx/default.conf`.
-- Access is protected with HTTP Basic Auth. Update `docker/nginx/.htpasswd-docs` with real credentials (`htpasswd -c docker/nginx/.htpasswd-docs <user>`). The repo ships with a weak default for local use—never reuse it in production.
-- Optionally run the build script inside your CI pipeline before deploying so the static output is always up to date. A typical GitHub Actions job would simply call the script after checkout and upload `docs/site/build` as an artifact or rsync it to the server.
+- Internal operations/admin documentation is now delivered in Filament through the Guava Knowledge Base plugin.
+- Access path: `/super-admin/docs` (same auth guard as SuperAdmin).
+- No separate static docs build/container is required.
 
 With the provided configuration you can bootstrap a consistent Docker-based deployment across environments while keeping queue workers, migrations, and asset builds manageable. Adjust service definitions as needed for staging vs. production.