Fork, join and choice states in state diagrams are now named
A `<<fork>>` and a `<<join>>` used to draw identical bars with no label, so you had to read the transitions to tell them apart. Each now carries its state's name, as does a `<<choice>>` diamond.
A stateDiagram-v2 state declared as state Fork <<fork>>, state Join <<join>> or state Check <<choice>> renders as a bar or a diamond rather than a box, which left no room for the state's name — and no name was drawn at all. A fork and a join were therefore two identical 70×6 rectangles, distinguishable only by which way the transitions flowed, and the choice diamond was anonymous:
stateDiagram-v2
[*] --> Fork
state Fork <<fork>>
state Join <<join>>
Fork --> Charge
Fork --> Notify
Charge --> Join
Notify --> Join
Join --> Check
state Check <<choice>>
Check --> Done : card ok
Check --> Failed : declined
Done --> [*]
Failed --> [*]
Each of those states now carries its name beside the shape, in the same font and colour as any other state label — to the right of the bar or diamond when the diagram flows top-to-bottom, and above it when it flows left-to-right, so the name never sits on a transition.
This applies everywhere Mermaid is rendered: fenced ```mermaid blocks in POST /api/v1/md, the canvas renderer, the CLI, and the /mermaid/state syntax page, whose example now shows the names and no longer lists them as unsupported. If you have a diagram with these states, render it again to get the labelled output.