Process boundary deployments

The two deployment shapes the framework supports, sharing one envelope contract. This cluster :satisfies: Connector framework (FEAT_0030).

Feature: Process boundary deployments FEAT_0035
status: open
satisfies: FEAT_0030
is satisfied by: REQ_0240, REQ_0241, REQ_0242, REQ_0243, REQ_0244
is refined by: ADR_0003

The framework supports two deployment shapes — gateway as an in-process tokio task or as a separate gateway binary — using the same envelope contract on both sides.
Requirement: Same envelope contract for both deployments REQ_0240
status: approved
satisfies: FEAT_0035
is refined by: ARCH_0020, ARCH_0021

The framework shall use the same ConnectorEnvelope definition, iceoryx2 service shape, and ChannelDescriptor semantics regardless of whether the gateway runs in-process or as a separate binary.
Requirement: In-process gateway is a tokio task REQ_0241
status: open
satisfies: FEAT_0035
is refined by: ARCH_0020
is verified by: TEST_0150

The framework shall support running the gateway as a tokio task spawned by ConnectorHost alongside the plugin’s executor, in a single process.
Requirement: Separate-process gateway is a self-contained binary REQ_0242
status: open
satisfies: FEAT_0035
is refined by: ARCH_0021
is verified by: TEST_0151

The framework shall support running the gateway as a self-contained binary in its own OS process, communicating with the plugin only through iceoryx2 shared memory.
Requirement: Clean exit on SIGINT / SIGTERM on both sides REQ_0243
status: open
satisfies: FEAT_0035
is refined by: ARCH_0013
is verified by: TEST_0152

Both the plugin host and a separate gateway binary shall return cleanly from Executor::run() on SIGINT/SIGTERM, drain any tokio runtime sidecar, and release iceoryx2 services.
Requirement: No app↔gateway control-plane envelopes REQ_0244
status: approved
satisfies: FEAT_0035
is verified by: TEST_0153

The framework shall not introduce envelopes carrying control-plane semantics (“ping”, “version”, “shutdown handshake”) on the SHM channel. Health is observed via ConnectorHealth, not negotiated.