🌴 Palm Engine 0.25.0 — Definition Revisioning, Migration & Design Service

This release is a single jump from 0.23.1 that delivers the full definition evolution stack Palm has been building toward since the 0.24 vision.

Definition revisioning (0.24)

Flow catalog is append-only — update_flow publishes revision N+1, not an in-place overwrite
Instances pin flow_revision at submit and keep their snapshot until explicitly migrated
Migration rules registry with can_migrate / migrate_state hooks
Impact query — see which instances are behind a target revision and whether migration is compatible, blocked, or snapshot-only
Instance migration — dry-run or apply via REST/MCP; migration_* metadata preserved across job sync

Design Service (0.25)

Sixth service domain: propose → validate → impact → commit
host.design, REST /v1/api/design/proposals, MCP palm_design_*
Durable proposals on StorageEngine when storage is active
Auto-migrate compatible instances on commit (blocked instances skipped; revision not rolled back)
Agent safety — commit_token from validate/impact; strict mode via PALM_MCP_REQUIRE_INPUT_TOKEN
palm_assist design paths — design/propose, design/impact, design/commit, etc.
Wizard design contributor — slug uniqueness, collection schema checks

palm_design_propose_flow → palm_design_validate → palm_design_impact → palm_design_commit

Agents should prefer palm_design_* for catalog writes. Direct palm_definitions_* CRUD remains for integrators and Explorer.

Read MIGRATION-0.24.md (revision semantics, impact/migrate) and MIGRATION-0.25.md (design workflow).

Breaking semantic change: PUT /v1/api/definitions/flows/{id} appends a revision; running instances are not silently upgraded.

Palm 0.25.0: revisioned definitions, instance migration, and Design Service — safe, inspectable catalog evolution for agents and operators.

Provide feedback