Diagram fix: Kernel doesn't update Y doc, Server does

[cben]

Based on my understanding of code, please check

Before | After

• Kernel doesn't touch Y doc, it's the Server that updates it
• also moved Shared document left between Frontend and Server
• using actor stick figure shapes for actual separate processes
  • "Shared Document" is abstraction, actually exists as separate Y models inside Frontend(s) and inside Server. But I think it's fine for this diagram.
  • ExecutionStack is an object inside Server. Mermaid can group participants but that might look too messy?
    • WDYT re-wording to e.g. "put() request into queue", "get() task result" to imply these are local function calls, not network messages?
• After execute_reply, I wasn't sure if diagram should elaborate on Server updating the Y model with 'idle' state & count? It does, but it also returns them over HTTP as already shown in diagram; not sure which drives notebook changing [*] -> [15]...

[github-actions]

👈 Launch a Binder on branch cben/jupyter-server-nbmodel/diagram

[krassowski]

not sure which drives notebook changing [*] -> [15].

It is the y model which does that in recent versions (otherwise if you closed the browser when the execution completed, the state would not be updated).

[cben]

Updated, PTAL. Before | After links to the branch, so reflects the new commits.

[echarles]

LGTM Thx @cben