Agreed. Retroactive conformance to UnsafeConcurrentValue is going to be critical for folks adopting concurrency before the libraries they depend on have annotated types with ConcurrentValue. Having the per-member @sendable(unsafe) or (my favorite spelling) @concurrent(unsafe) is gravy---it narrows the scope of ConcurrentValue---but doesn't obviate the need for UnsafeConcurrentValue.
Doug