rpc spec: conflicting behaviour for relative paths in connect points

rpc-connect-sketch.md says:

On a RPC client, some errors are fatal and cause the connect point to abort; others are nonfatal and cause the connect point to be declined.

[...]

The following errors are not tolerated; when an Arti RPC client encounters any of them, the corresponding entry aborts the entire search process.

• [...]
• A filename within a connect point is not absolute.

It later says:

If the socket member has a schema prefix other than inet: or unix:, or if it is a relative unix: path, then the connection attempt is declined.

These are conflicting. The first quote says that a non-absolute filename within a connect point should cause an "abort", and the second quote says a relative unix: path within a connect point should only be "declined".