v0.65.0 — a system is drawn in its landscape and by what it holds

diagram draws one system two ways (#163). system takes a system's id and draws it in its landscape, a flowchart from left to right: the system with the class middle, what it runs on and what runs on it by dotted lines, every system it exchanges data with by a solid arrow from the system the data comes from, labeled with the interface, what is carried and how, every service it provides as a rounded box, and every row of its ## Holds as a cylinder, the data object over its concept, reached by an arrow labeled with the access, heavy for master, solid for writes, dotted for reads. holds takes the same id and draws those cylinders among every other system that masters, writes or reads the same concepts, so the picture says whose copy the system's is, or who copies its own; it is refused as empty where the system holds nothing. A box's label begins with fak:fa- and the ArchiMate element the system's kind names, a token a client draws as a mark, and ends with the kind's name as a stereotype; a planned or retiring system carries a class the source defines. links carries the model's word for every line, and nodes types each as system, service, data-object or concept. Both shapes are refused with unknown_type on an instance without the landscape pack.

What breaks. Nothing for a host: an instance without the landscape pack refuses the two shapes by code, and every other shape is unchanged.

How to take it. A host moves its pin to 0.65.0 and re-deploys. A chat that asks for the shapes needs robertblust/design v0.147.0 on its site to draw the marks; on an older widget a box shows its name without one.

Verified: npm test, build:check, typecheck and the conventions check and format pass on the branch.