Say in the JSON Schema which slots key a nested list

[jdkent]

The storage schema declares unique keys for the nested lists a claim path may index, but only in the LinkML YAML. Neurostore keeps its own copy of them (DECLARED_KEYS), and so does its review front end. This is the second of the schema-export PRs, after #34's x-reference.

What changes

• tools/generate_models.py writes "x-unique-keys": [[slot, ...], ...] on each class with LinkML unique_keys. A class's own keys come first, then those inherited through is_a and mixins. Keys are deduplicated by name, and the nearest declaration wins.
• study_schema.jsonschema.unique_keys(name) returns {class: ((slot, ...), ...)}, sorted by class.
• The two annotators share one walk over the classes, _class_definitions. The tests share the generator fixture and a schema-building helper in conftest.py.
• Only storage-study.schema.json changes, by the added keyword.

Keys (storage-study only; the other schemas declare none)

Class	Key
Cell	term, level
AnalysisGroup	group
ModelTerm	name
FactorLevel	level

These equal neurostore's DECLARED_KEYS. The test pins them as a golden check of the YAML. Keeping neurostore in sync belongs in neurostore, which will read them through unique_keys("storage-study").

Tests

• A unit test of the generator on a small LinkML schema covers: own and inherited keys, own before inherited, a redeclared key name with the subclass winning, a mixin's key, two keys on one class, and a class without keys.
• A shape test covers the helper's order and its tuples.
• With linkml 1.12, pytest tests passes: 105 passed, 2 skipped (pyarrow and pyarty). generate_models.py --check passes.
• All 9 mutants of the rule and the helper are killed.

🤖 Generated with Claude Code

[jdkent]

LGTM