Document pipeline configuration migration workflow

This commit is contained in:
2026-08-30 15:19:30 +00:00
parent fcb5f825e1
commit 4c203d8588
6 changed files with 27 additions and 3 deletions

View File

@@ -74,6 +74,18 @@ family members and generated publish rules participate after expansion; moving
an equal value between eligible root/import sources does not create a
difference.
### Migrating to the maintained bundle
Use the [production/testing bundle](../examples/production-testing/pipeline.yml)
as the complete copyable migration reference. Split stable pipeline settings
into explicit additive imports, place production/testing differences in one
selected overlay, and retain a production `default_profile`. Convert campaign
rosters to [canonical party input](integrations/party.md), remove a separate
`players_file`, then express character work as families. Inspect the result
with `config validate`, `config show`, and `config sources`; use `config diff`
to review profiles before running a session. Unversioned parties and their
`players_file` remain a clearly bounded legacy compatibility path.
### Identity segments
Campaign IDs (`campaign_id` and `default_campaign_id`), session IDs, previous