v0.91.0

The landscape pack's system schema changed twice, so core moves to 0.66.0 and the three packs' manifests move with it, and the package moves to 0.91.0 with both reusable workflows' refs.

• The README names the landscape pack whole: four types, aligned to ArchiMate 4 (#338).
• A system a vendor runs and the company only connects to keeps the vendor's own name for it, GitHub, Cloud Run; and a kind is never named Service, which would collide with the service type (#339).
• vendor is written only on a system naming no processor: the processor's page says which party the contract is with, and a vendor beside it is the same party written twice, once in a form nothing resolves. A yields: { field, unless } row on a type's entry holds the pair under R16; a maker who is another party than the contract's goes to the tagline (#340).

What breaks. An instance that writes vendor beside processor on one system fails check on that page until it drops the vendor line. CompanyGraph's own instance already has (companygraph/mental-model #123); robertblust's and guestgraph's do not take the pack; the retailer's instance names no processor.

How to take it. Move the pin to v0.91.0 and run companygraph upgrade, which moves the vendored core and packs to 0.66.0; an instance with the landscape pack then drops any vendor line that stands beside a processor.

Verified: npm run verify with its release check, typecheck, build:check and every test:* script pass, as do conventions-format and conventions-check; robertblust, companygraph and guestgraph mental-model, cloned at their main commits and upgraded with this checkout's CLI, go from core 0.65.0 to 0.66.0, pass check, and find nothing to do on a second upgrade.