Allow links to /routine pages

cfa++

xt/rakudoc-types.rakutest

@@ -10,7 +10,10 @@ Any other formatting code that refers to a type will fail the test; any C<>
 that isn't inside of an L<> will fail, and any L<> that doesn't have a C<>
 will fail. Links may end with an optional #id.
 
-One exception: Referring to a type on its own page should only use C<>.
+Eexceptions:
+
+=item Referring to a type on its own page should only use C<>.
+=item It's Ok to refer to a routine page with the same name instead.
 
 =end overview
 
@@ -108,8 +111,14 @@ sub is-valid-type($node, $parent, $file) {
         # \o/
         pass "L<{render-node($node)}|$meta>";
     } else {
-        # Wrapped in an L<> with wrong URL
-        flunk "L<{render-node($node)}|$meta> should be L<C<$type>|/type/$type-colon> - bad link";
+        if $meta.starts-with('/routine/') {
+            # Is this pointing to an routine page? /routine is generated, so we cannot verify
+            # the existence of an actual file; trust if present.
+            pass "L<{render-node($node)}|$meta> - routine";
+        } else {
+            # Wrapped in an L<> with wrong URL
+            flunk "L<{render-node($node)}|$meta> should be L<C<$type>|/type/$type-colon> - bad link";
+        }
     }
 }