Spec deltas
Per-capability spec changes proposed by complete-self-service-connection-onboarding.
The reference implementation SHALL materialize or activate connector instances only through typed setup lifecycles appropriate to the connector's setup modality. A setup intent or setup plan SHALL NOT silently create an active connection row unless the modality's proof boundary has been satisfied.
The reference implementation SHALL provide one owner-mediated setup engine as the source of truth for connector setup modality, support state, deployment readiness, owner next steps, proof gates, and secret boundaries. Console, owner-agent REST, CLI, and SDK-style helpers SHALL consume that engine or a serialized projection of it rather than maintaining separate setup classification tables.
The owner-agent control surface SHALL initiate connector setup by projecting the shared owner-mediated setup engine. It SHALL return typed next steps, support states, deployment-readiness requirements, and proof-gate reasons, but SHALL NOT return provider credentials, owner-session credentials, browser session credentials, or grant-scoped MCP tokens.