F23-TO: Yes
Rationale
The declared profile already includes optional Conflux onion-service resumption as design. A client changing access can rebuild paths to the same service and associate them with the retained circuit set using its secret nonce and sequence state. Buffered missing data can be retransmitted, including after both legs disappear, preserving the logical stream. This supplies an architectural mobility witness; it does not establish deployed Tor support. Section 2.7 explicitly says full resumption is not supported in C-Tor. Retained endpoint state, adequate buffering and a reachable service are required; memory pressure or unrecoverable loss can terminate the set.
Assessment method
Architectural inference from selected optional design; no execution
Source context
Tor proposal 329, sections 2.3, 2.4 and 2.7
Outstanding qualification
Identify an implementation of full onion-service resumption. Change the client access/address while keeping its local application connection alive; verify stream identity, ordering and recovery after both legs close. Exercise buffer exhaustion and timeout. Ordinary C-Tor cannot be assumed to pass this experiment.