Skip to content

v0.151.0 — the chat draws a use case three ways

Choose a tag to compare

@robertblust robertblust released this 12 Oct 19:31
· 40 commits to main since this release
65b78c6

The chat widget draws a use case's three pictures (#279), the shapes usecase, scenario and requirements that companygraph/mcp-server v0.68.0 answers. A seventh mark joins the icon pack, the actor: the figure outlined, for someone who is not one of us, a seat nobody holds or a name that is no seat, defined in lib/marks.mjs beside the person and the agent and drawn at the firm brightness. The three pictures are captioned Use case, Scenario and Requirements, with Anwendungsfall, Szenario and Anforderungen in German, and each has its reading line under it in both languages. A scenario's step is a box named s0 and on, listed where its actor is a seat, so the node finder links the step to the seat; an extension's box has no fill, so it reads as a branch and not a step.

What breaks. Nothing. The marks, captions and reading lines of every other shape are as they were; a site adds nothing to the tag.

How to take it. Re-pin and run npm run design. A chat in front of a host on mcp-server v0.68.0 draws the three pictures once chat-server asks for them, from its own next release.

Verified: npm test (1017 pass), the browser suite drawing the five new fixtures in Chromium among them, conventions-format and conventions-check pass on the release commit.