v0.64.0

The server carries meta-model v0.91.0 (#161), core 0.66.0. The landscape pack's system schema changed twice there: vendor is written only on a system naming no processor, and a system a vendor runs keeps the vendor's own name for it. The server reads whatever the instance it serves wrote, so a host sees the change only through its content pin. Nothing in the server's own code moved, so the package moves to 0.64.0 alone.

What breaks. Nothing for a host.

How to take it. A host moves its pin to 0.64.0 and re-deploys; the content pin may move at the same time to an instance commit on core 0.66.0.

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