Fix GET /api crash on server notification docs

[dominicletz]

Summary

• Fixes FunctionClauseError on GET /api when rendering server-to-client notification endpoints (dio_ticket_request, dio_notify) that have no client request example
• Skips the example request block when example_request is absent and labels the payload "Example notification" instead of "Example response"
• Adds a notify/2 helper in Network.RpcDocs so notification examples are JSON-encoded strings like other RPC examples

Test plan

• mix compile
• Render api_docs.html.eex with Network.RpcDocs.all() and confirm no crash
• Hit GET /api on a running node and verify the page loads
• Confirm dio_ticket_request and dio_notify show notification examples without an empty request block

Made with Cursor

[gemini-code-assist]

Code Review

This pull request refactors the API and RPC documentation generation. In lib/network/api_docs.html.eex, it conditionally displays the example request block and dynamically labels the response section as either "Example response" or "Example notification" depending on the presence of an example request. In lib/network/rpc_docs.ex, it introduces a notify/2 helper function to clean up the generation of JSON-RPC notification examples. Feedback was provided to use the more idiomatic Elixir Access syntax (doc[:example_request]) instead of mixing Map.get/2 and dot-notation, which helps prevent potential KeyError exceptions.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.