docs: bring docforge docstrings and wiki to GSDFC standard

- fix GSDFC spec contradictions in __init__ docstring (parenthesized types, fenced-block rule) and sync generated README
- rewrite docstrings across loaders, models, nav, servers, renderers, cli; sync .pyi stubs
- add pydoclint (google style) gate to dev extras and pyproject config
- fix mcp nav resources doc:// -> docs://
- refresh docs/lib and docs/mcp, drop stale docforge/ duplicate group
- update wiki pages and add GSDFC + MCP guides under 05_development

docs/wiki/01_overview.md

@@ -11,7 +11,7 @@ and assembles a single MkDocs site from all available material.
 | `lib`     | GSDFC docstrings           | `docs/lib/**` rendered markdown |
 | `api`     | OpenAPI JSON spec          | `docs/api/**` rendered markdown |
 | `wiki`    | Hand-written markdown      | `docs/wiki/**` (unchanged)      |
-| `mcp`     | Griffe + renderers         | `docs/mcp/**` structured files  |
+| `mcp`     | GSDFC docstrings + renderers | `docs/mcp/**` structured JSON |
 
 ## Combined build
 
@@ -22,4 +22,10 @@ One `mkdocs.yml` and one MkDocs build serve all kinds:
 3. The wiki `index.md` becomes the site `Home`.
 
 Hand-written wiki content is never overwritten or regenerated — only its
-navigation is derived automatically.
+navigation is derived automatically.
+
+## MCP bundle
+
+`docs/mcp/**` is a self-contained, machine-readable reference generated from
+docforge's own GSDFC docstrings. `doc-forge serve --mcp --module docforge`
+serves it over MCP. See the [MCP Guide](05_development/04_mcp_guide.md).