Prose tests in the Go driver are fairly reliably kept in a [specname]_prose_test.go file, but it's still tough to tell which prose test corresponds with which prose test description in the specifications repository. This ambiguity could result in duplicate prose test implementations or, worse, no implementation.

We should either number our prose tests so developers can easily reference the spec, or provide a link to the relevant description in the spec above each prose test.