Skip to content

docs: fix Mermaid parse error in PROTOCOL.md 3.5 diagram#725

Merged
jasonacox merged 1 commit into
masterfrom
fable5/fix-protocol-mermaid
Jul 6, 2026
Merged

docs: fix Mermaid parse error in PROTOCOL.md 3.5 diagram#725
jasonacox merged 1 commit into
masterfrom
fable5/fix-protocol-mermaid

Conversation

@jasonacox

Copy link
Copy Markdown
Owner

Fixes a Mermaid rendering error in the Full 3.5 Control Flow sequence diagram in PROTOCOL.md.

The DP_QUERY_NEW message text contained a semicolon:

C->>D: DP_QUERY_NEW (0x10) (GCM, JSON encrypted; no version header)

In Mermaid, ; is a statement separator, so the parser split the message mid-line and then expected an arrow token — producing Parse error on line 9 ... got 'NEWLINE' and an Unable to render rich display box on GitHub. Replaced the semicolon with a comma.

The other two Mermaid diagrams in the file were checked and contain no semicolons in their message text.

🤖 Generated with Claude Code

A semicolon in the DP_QUERY_NEW message text was interpreted as a Mermaid
statement separator, breaking the "Full 3.5 Control Flow" sequence diagram
("Parse error on line 9 ... got 'NEWLINE'"). Replace the semicolon with a
comma so the note renders.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings July 6, 2026 04:47
@jasonacox
jasonacox merged commit 712a81f into master Jul 6, 2026
32 checks passed

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes a GitHub Mermaid rendering/parsing error in the “Full 3.5 Control Flow” sequence diagram in PROTOCOL.md by replacing a semicolon in the DP_QUERY_NEW message label with a comma (Mermaid treats ; as a statement separator).

Changes:

  • Replace JSON encrypted; no version header with JSON encrypted, no version header in the v3.5 control-flow Mermaid diagram label.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants