manual — collector requires explicit user input (TEXT, PASSWORD,
SINGLE_SELECT, MULTI_SELECT, PHONE_NUMBER,
DEVICE_REGISTRATION, DEVICE_AUTHENTICATION, etc.)output_only — display-only collector, no user input (LABEL)immediate — activating the collector immediately advances the flow
without waiting for other field values
(SUBMIT_BUTTON, ACTION, FLOW_BUTTON, FLOW_LINK)integration_required — collector is handled entirely by an external package
(e.g. rn-external-idp driving IdpCollector).
The bridge serialises the collector data; the external
package performs its action and then calls next().
No base-registry collector maps to this mode in 2.0.1 —
plugin collectors registered by future packages will.unsupported — collector type not recognised by the bridge or any
registered integration; skipped in the submit payloadNo auto_capable exists — every collector requires an explicit user gesture or
an external-package action.
Collector execution mode — controls how the UI should treat this collector.