chore: introduced expectation that "repo" is cloneable.

Based on feedback in [1].

[1]: #280

Signed-off-by: Andrew Lilley Brinker <[email protected]>

Author: alilleybrinker

schema/docs/versions.md

@@ -425,8 +425,11 @@ Git commits, declaring them `unaffected` unless specified otherwise by status
 changes. (The conventional `0` and `*` specify “no lower bound, no upper bound”
 for the range.) Because the Git version identifiers cannot be understood
 without reference to a specific Git repository, this form adds a new `repo`
-field containing the URL of the repository. Let's suppose the repository's
-commit graph looks like this:
+field containing the URL of the repository. This URL is expected to be
+"Git-cloneable," meaning a `git clone` command which used the URL would
+succeed.
+
+Let's suppose the repository's commit graph looks like this:
 
 ```
 	            1.0.0           1.0.3