Rename the journey "conditions" concept to "triggers" throughout the
codebase, REST API, CLI, and SDKs to better reflect their role as
activation signals.
- Core: Journey.triggers replaces Journey.conditions on the model and
store interfaces. The journey_conditions document collection (with a
condition field) becomes journey_triggers (with a trigger field).
Journey schema bumped to 0.7.0 with a v0.6.0 -> v0.7.0 identity loader
migration, plus a cross-collection migration in
parlant-prepare-migration that copies and renames.
- REST API: hard rename — request bodies, response fields, and
JourneyTriggerUpdateParams replace the old condition variants. No
aliases.
- SDK: Server.create_journey now takes triggers=, and Journey.triggers
exposes the Guideline list. The conditions= keyword and conditions
property remain as deprecated aliases that emit DeprecationWarning;
passing both raises an error.
- CLI: subcommands renamed to journey add-trigger / remove-trigger with
a --trigger flag and a "Trigger Guideline IDs" display column.
- LLM-facing prompt strings ("Journey activation condition: ...") are
intentionally preserved.
Edge transition conditions and the singular Guideline.condition field
are unrelated and unchanged.
