Confirming Campaign feature write API limitations and Trigger timing (v6.0)

[jongdae.won]

Hi brainCloud team,

We're evaluating the LiveOps Campaign feature for a time-limited in-game event system, and based on the public documentation and our local SDK/CloudCode type definitions, we've drawn some conclusions we'd like to confirm before committing to a design around them. Could you help verify the following?

1. No write/update operation for Campaign definitions
   Per docs.braincloudservers.com/api/capi/campaign/ and .../api/s2s/campaign/, the only operations exposed are GetMyCampaigns, SysTriggerCampaignForUser, SysRemoveCampaignForUser, and SysRemoveAllCampaignsForUser — all of which manage a specific player's enrollment/participation, not the campaign definition itself. We see that GetMyCampaigns returns free-form campaignJson and scenarioJson fields, but we can't find any operation (Client API or S2S) that writes to campaignJson/scenarioJson/startAt/endAt/scenarios/overrides after the campaign is created.

Is this correct — is Campaign definition data (including campaignJson) only editable through the Design Portal UI, with no API path (including any Server-to-Server or "Sys"-prefixed operation) to create or update it programmatically?
Is there a separate Builder/Design API (e.g. using a personal team-member API key rather than app credentials) that does support programmatic campaign creation/updates? If so, could you point us to its documentation?

2. Trigger evaluation timing
   The docs state Trigger is "evaluated on LOGIN or REGISTRATION." For a player who is already in an active session when a campaign's startAt passes, will they be evaluated/enrolled into that campaign before their next login (e.g. on their next authenticated API call), or strictly only on an actual login/registration event? If the latter, is there any other mechanism (e.g. session refresh, heartbeat) that also triggers re-evaluation?

3. Feature maturity / plan tier
   LiveOps Campaigns is marked beta as of SDK 6.0 documentation.

Is this feature considered stable enough for production use in a live game (i.e. tied to real reward grants), or is it still recommended for experimentation only?
Our production app is on a Bulk+ 100M plan add-on over a Business Plus baseline. Does this tier fully support Campaign, or does it require a separate Enterprise-tier confirmation?

4. Cross-environment campaign management
   We maintain separate brainCloud apps for dev/staging/production and use our own internal tooling to diff and promote Custom Entity–based content between them via S2S. Since Campaign isn't a Custom Entity, is there any supported way (API-driven or otherwise) to keep a Campaign definition consistent across multiple apps, other than manually re-creating it in each app's Design Portal?

Thanks in advance — confirming these will directly decide whether we build our event schedule/targeting on Campaign or on an alternative (Custom Entity–based) mechanism.

Best regards