# Which RFC 3986 vectors this project claims to resolve correctly.
#
# TWO-WAY GATE. Three things are violations, not one:
#
#   * a row recorded as passing whose vector failed  -- a regression
#   * a row recorded as deferred whose vector passed -- an unrecorded gain
#   * an id in one set and not the other             -- an orphan or stale row
#
# The third is what keeps the first two honest: without it, deleting a row is
# a way to make either of the others disappear quietly.
#
# All 42 rows pass: the resolver is (uri path) + (uri resolve) + (uri
# recompose). The two-way gate keeps the record honest: a passing row that
# regresses AND a row that starts passing unrecorded are both violations, so
# this file cannot silently drift.
#
# id = <section>/<reference>, derived from the vector rather than written
# twice. Section 5.4.1's empty reference is therefore the row `5.4.1/`.
#
# Format: <status><whitespace><id>. An id may contain anything but whitespace,
# which is what keeps `5.4.2/g;x=1/../y` in one piece.

passing  5.4.1/g:h
passing  5.4.1/g
passing  5.4.1/./g
passing  5.4.1/g/
passing  5.4.1//g
passing  5.4.1///g
passing  5.4.1/?y
passing  5.4.1/g?y
passing  5.4.1/#s
passing  5.4.1/g#s
passing  5.4.1/g?y#s
passing  5.4.1/;x
passing  5.4.1/g;x
passing  5.4.1/g;x?y#s
passing  5.4.1/
passing  5.4.1/.
passing  5.4.1/./
passing  5.4.1/..
passing  5.4.1/../
passing  5.4.1/../g
passing  5.4.1/../..
passing  5.4.1/../../
passing  5.4.1/../../g
passing  5.4.2/../../../g
passing  5.4.2/../../../../g
passing  5.4.2//./g
passing  5.4.2//../g
passing  5.4.2/g.
passing  5.4.2/.g
passing  5.4.2/g..
passing  5.4.2/..g
passing  5.4.2/./../g
passing  5.4.2/./g/.
passing  5.4.2/g/./h
passing  5.4.2/g/../h
passing  5.4.2/g;x=1/./y
passing  5.4.2/g;x=1/../y
passing  5.4.2/g?y/./x
passing  5.4.2/g?y/../x
passing  5.4.2/g#s/./x
passing  5.4.2/g#s/../x
passing  5.4.2/http:g
