Skip to content

Phase 4c: migrate session and registry messaging state to plans #4947

@sandl99

Description

@sandl99

Summary

Phase 4c of #3896 migrates onboard-session and sandbox registry messaging state to the manifest-backed SandboxMessagingPlan.

Scope

  • Persist onboard session state as messagingPlan instead of messagingChannels, messagingChannelConfig, and disabledChannels.
  • Persist sandbox registry state as messaging.plan instead of top-level messagingChannels, messagingChannelConfig, and disabledChannels.
  • Update onboard, rebuild, status, doctor, inventory, and channel lifecycle flows to derive channel config, active channels, and disabled channels from plans.
  • Remove stale legacy conflict/backfill code and tests for the old messaging fields.
  • Make this a clean cutover: no compatibility fallback or legacy backfill is required for messagingChannels, messagingChannelConfig, or disabledChannels.

Closing PR

Closed by #4945.

Metadata

Metadata

Assignees

Labels

area: messagingMessaging channels, bridges, manifests, or channel lifecyclearea: project-managementTaxonomy, triage, workflow, roadmap, or project process
No fields configured for Enhancement.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions