Repository navigation
diagram draws the meta-model a unit at a time (#173). A picture of the schemas was refused once an instance declared more types than one picture holds, with the hint to name a single type; an instance that takes all four packs passed that limit, and the meta-model, the first thing a chat offers a visitor, drew nothing. The schema shape now takes unit, core or a pack the instance takes, and draws that unit's own types and what they declare: each reference a type of the unit declares, with the type it reaches, and each nesting of a type of the unit. A pack is drawn with the core types it rests on and core is drawn alone, since a pack declares into core and core never into a pack. Asked for whole, a meta-model past the limit is drawn as core rather than refused. Every schema answer carries units, each unit with how many types it declares, core first, and an answer narrowed to a unit carries that unit and has it as its title. The interface document shows the organization pack drawn as a unit.
What breaks. Nothing for a caller that reads what it asked for. The tool's input gains an optional argument and its answer two optional fields, so a strict client that validates answers against an output schema it cached has to read the tool list again. A meta-model within the limit is drawn whole as before, and type narrows as before; unit beside type is refused, and a unit the instance does not have is refused with the units it has.
How to take it. Re-pin the host to v0.69.0 and deploy. A chat in front of the host draws core for the whole meta-model at once; it says which unit it drew and names the others once chat-server takes its own next release. A connector that caches the tool list wants a refresh.
Verified: npm test (390 pass), build:check, typecheck, conventions-format and conventions-check pass on the release commit; served over companygraph/mental-model, the whole meta-model drew core with the four packs named and the requirements and landscape packs drew by name.