Port metadata in model.yaml

Keep the existing io.inputs and io.outputs structure and runtime interfaces. Structural signal declarations remain authoritative. Legacy contract mappings and compatibility pins are preserved as descriptive metadata; unknown scientific profile names do not block execution.

io:
  outputs:
    - name: score
      signal_type: scalar
      dtype: float64
      contract:
        profile: historical.score/v1

This metadata does not constrain the numeric score’s biological meaning. Use an explicit computation when the user requests a particular check, and return the measured result without a platform grade.