• fix(provider): sortable_chunk_fields needs required `type` — handshake was broken

    vh released this 2026-07-15 09:11:08 -07:00 | 120 commits to main since this release

    DEPLOY-BREAKER caught by driving the live bind (unit tests + worldtree-dev's
    name-only parser + heid-bug-hunt all missed it). bifrost handshake_response
    SortableChunkField requires BOTH name and type (additionalProperties:false).
    We advertised [{"name":"updated_at"}] (no type), so the handshake_response
    failed wire-schema validation → bifrost.schema_validation_failed → the ENTIRE
    Bifrost bind (memory + affect) broke, not just the sort. Advertise
    {"name":"updated_at","type":"timestamp"} (matches the reference; type is
    advisory-only). Regression guard added to the caps test (asserts required name+type,
    no extra keys). Full suite 639 green.

    Downloads