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/index.md

@@ -22,17 +22,20 @@ OpenAPI-based API docs.
 | Section                                      | Description                                        |
 |----------------------------------------------| -------------------------------------------------- |
 | [Overview](01_overview.md)                   | What docforge is and how it fits the pipeline      |
-| [Architecture](02_architecture.md)           | Loaders, models, nav, renderers, CLI               |
+| [Architecture](02_architecture.md)           | Loaders, models, nav, renderers, CLI, servers     |
 | [Conventions](03_conventions.md)             | GSDFC, `.pyi` stubs, and template conventions      |
 | [Iterative Workflow](04_iterative_workflow.md) | How a docs build runs end to end                  |
 | [Development](05_development/01_environment.md) | Environment setup and quality gates              |
+| [Docstring Guide](05_development/03_gsdfc_guide.md) | How to write GSDFC-conformant docstrings        |
+| [MCP Guide](05_development/04_mcp_guide.md)  | Building, serving, and consuming the MCP bundle   |
 
 ---
 
 ## 🔗 Related Resources
 
-- **Source Code:** `C:\Users\vishe\WorkSpace\code\aetos\doc-forge`
+- **Source Code:** the `doc-forge` repository
 - **Wiki Kind:** hand-written content lives in `docs/wiki/`
+- **MCP Bundle:** generated by `doc-forge build --mcp --module docforge` into `docs/mcp/`
 
 ---