Set Trigger Mode
Persist the onboarding trigger-mode choice (SMMT content-driven).
This is the wizard’s first question, posted after the team already exists (checkout/webhook create it strategy-driven). Flipping to “content-driven” makes the wizard show the Content Sources step and makes cycle-start skip strategy generation. Validated server-side (flag + team-type gate).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
Body
Persist the onboarding trigger-mode choice (SMMT content-driven).
Validated server-side: "content-driven" requires the feature flag + a content-driven-capable team type, else 400.
trigger_mode is deliberately REQUIRED here (no None): this request is
the wizard's explicit set-trigger-mode action, so the client always sends
a concrete choice. The nullable state lives on the STORED column —
AgentTeam.trigger_mode may be NULL (= classic strategy-driven default,
resolved by team_service._resolve_trigger_mode) for teams that never
answered the wizard question. Don't widen this Literal to | None; a
client with nothing to set simply doesn't call the endpoint.
'strategy-driven' or 'content-driven'
strategy-driven, content-driven Response
Successful Response