Write JSON Schema properties in the LinkML's declared order

[jdkent]

The generated JSON Schemas list each class's properties alphabetically. The LinkML declares a deliberate order: Group, for example, keeps the counts together, then the criteria, then age_mean, age_standard_deviation, age_minimum, age_maximum, age_median, age_unit. Consumers that show fields in schema order lose it. neurostore's review app scattered the age fields across the card.

The order was lost in two places:

• LinkML's JsonSchemaGenerator.serialize() dumps with sort_keys=True;
• tools/generate_models.py sorts again.

Changes

• render() takes the generator's dict (generate().to_json()) and sorts every key except each object's properties, which keep LinkML's induced slot order: parent slots first, so stable_id and local_id lead. $defs, top-level keys and each property's own keys stay sorted, so diffs stay stable.
• The four schemas are regenerated. Each loads equal (==) to the previous version; only property order changes.
• New tests/test_declared_order.py: every class's properties in all four schemas follow SchemaView.class_induced_slots, and generation is deterministic.
• The README notes the order.

The Pydantic models are unchanged. Their field order differs from the LinkML in a few classes (the modality and *Details classes put stable_id/local_id or details_type first), which nothing reads by position.

The diff is large (+4887/−4874) but is reordering only. If #43 or #44 regenerate the schemas, they'll conflict here; regenerating after merging resolves it.

🤖 Generated with Claude Code