F05-TO: Yes
Rationale
With onion-v3 client authorization enabled, the service retains authorized-client public-key records and the client retains service-bound private credentials across circuits and transport sessions. This supplies the persistent authorization context required by F05, beyond a stable service name. This does not establish immediate revocation of established streams.
Assessment method
Documentary analysis
Source context
Primary specification / explicit profile inference
Outstanding qualification
Pin Tor and use filesystem client authorization. Rebuild circuits and restart endpoints while preserving the authorization records; inspect descriptor refresh and removal behavior separately. No connection-migration or instantaneous revocation claim; no execution performed.