Two issues in the protocol validation logic during connection initialization:

1. finally block causes UnboundLocalError when ValueError is raised

When protocol is a non-numeric string like "abc", int(protocol) raises ValueError. The except ValueError clause re-raises as ConnectionError. But the finally block always executes — and p was never assigned, so p < 2 raises UnboundLocalError, replacing the meaningful error message with a confusing one.

Changed finally to else so the range check only runs after successful parsing.

2. Async connection stores raw protocol instead of parsed p

The sync version correctly does self.protocol = p (the validated integer), but the async version had self.protocol = protocol (the raw input, which could be a string). This forces workarounds throughout the async codebase (self.protocol not in [2, "2"], int(self.protocol), etc.). Fixed to store the parsed integer p, consistent with the sync version.