v2.1.0

Configs created by chap-core now take effect, and the forecast horizon is a per-request value.

What changed

• BaseConfig accepts chap-core's nested payload. chap-core posts configs as {"name": ..., "user_option_values": {...}}; chapkit now hoists those keys into the declared fields before validation, with flat keys winning on conflict. Services that declare tunables receive the values set in the CHAP UI instead of silently running on defaults. (#110)
• BaseConfig.prediction_periods defaults to 3. chap-core never sends it, so it no longer has to be redeclared in every service. (#110)
• The prediction horizon is resolved per request: from chap-core's run_info (prediction_periods, with prediction_length accepted as an alias), else from the future frame at predict time, else from the stored config. The min/max bounds check uses the resolved value, runners and validate hooks receive a config copy carrying it, and ShellModelRunner rewrites config.yml for each predict request so scripts see the current horizon. $validate warns when run_info and the future frame disagree. (#111)
• chapkit test sends run_info and keeps its generated horizon inside the service's declared bounds; $generate-sample-data does the same for predict payloads. (#111)

Upgrading

No model changes are required. Two behaviours change on purpose: user options set through chap-core now apply, and a $predict whose future frame exceeds the service's max_prediction_periods is rejected instead of passing on a constant. A service that added its own user_option_values hoist can remove it. chap-core still sends prediction_length=1 at train time; a chap-core fix is pending, so do not rely on the train-time horizon yet.

What's Changed

• chore(deps): bump the python-dependencies group with 4 updates by @dependabot[bot] in #108
• chore(deps): bump astral-sh/setup-uv from 10.0.1 to 10.1.0 in the github-actions group by @dependabot[bot] in #107
• fix(config): accept chap-core's nested user_option_values in BaseConfig by @mortenoh in #110
• feat(ml): resolve the prediction horizon from run_info instead of a config constant by @mortenoh in #111
• chore(deps): bump the frontend-dependencies group in /frontend with 9 updates by @dependabot[bot] in #109
• chore: release 2.1.0 by @mortenoh in #112

Full Changelog: v2.0.1...v2.1.0