We should expose an endpoint in the MEDS-DEV codebase to report in structured form the information necessary about current models, tasks, datasets, and results for display in the website

[mmcdermott]

This code endpoint should either be used for:

1. Direct retrieval by the website engine to source current list of supported things, or
2. Usage in the context of the results writing GitHub action to track deltas as versions within MEDS-DEV change over time, so that historical results can be interpreted w.r.t. the set of dataets/tasks/models supported at that time.

# 2 is likely the better solution, though it is more complex.