v0.6.0 — OBSL 2.16 camelCase contract + schema-validation errors
Aligns the runner with OrionBelt Semantic Layer v2.16 and pins the 0.6.x line to OBSL 2.16.x.
camelCase contract
- OBSL 2.16 validates model-load and query payloads against its published JSON Schemas at the ingestion boundary and returns a structured
422on a violation. - New
ObslSchemaErrorsurfaces those per-field errors with a readable message and a hint (camelCase keys, lowercase enums, numeric modelversion). - Query field
order_byis noworderBy(the last snake_case query key; the query schema rejectsorder_by). The bundledexamples/monthly-revenue.yamlwas updated. - Re-synced the vendored OBML schema from 2.16 (camelCase-only — the snake_case
max_staleness/intent_tagsaliases were dropped).
Compatibility pin
SUPPORTED_OBSL_MINORbumped to 16; the startup/healthpreflight now requires the server to be in the 2.16.x line (distinct too-old / too-new messages), with--skip-preflightto bypass.
Compatibility: requires OrionBelt Semantic Layer 2.16.x.