Say in the POD of the bundle route which lists it serves, and who declares them

The route answers 404 for a list of real scripts that no route declared.
Its POD did not say so, or say that the declarations come from
TCMS::build_routes() at startup and from finish_render() when it links a
bundle.  A reader of the route could not tell why a hand-written bundle URL
fails, or that this is what keeps a URL from making tCMS build a bundle.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

lib/Trog/Routes/HTML.pm

@@ -3399,6 +3399,12 @@ The body of a bundle is the same at a given href, so the browser keeps it.  An
 href with an old version is redirected to the current one, so a page that was
 cached before a script changed still gets its scripts.
 
+It serves only a list that a route declared, and is a 404 for any other list,
+even one of real scripts.  TCMS::build_routes() declares the C<scripts> and
+C<authenticated_scripts> of every route at startup, and finish_render() declares
+the list of each page that it links.  Both take the lists from the routing
+table, so a URL cannot name a list for this route to build.
+
 =cut
 
 sub bundle ($query) {