fix: Remove ** from StaticRoute.directory() path examples

[Copilot]

StaticRoute.directory() now automatically appends tail matching via tailMatch, so manually including ** in the path is incorrect. The docs were still showing the old pattern.

Changes

• 01-overview.md — Remove ** from two StaticRoute.directory() path examples
• 05-static-files.md — Remove ** from three path examples; update info box from "required" to "automatically handled"
• 02-routing.md — Remove ** from virtual-host StaticRoute.directory() example
• 08-upgrading/01-upgrade-to-three.md — Remove ** from the "After" examples (old RouteStaticDirectory "Before" examples unchanged)

Before / After

// Before (incorrect)
pod.webServer.addRoute(StaticRoute.directory(Directory('web/static')), '/static/**');

// After (correct)
pod.webServer.addRoute(StaticRoute.directory(Directory('web/static')), '/static/');

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix stale documentation for StaticRoute.directory() usage</issue_title>
<issue_description>## Description

The documentation for StaticRoute.directory() is stale and needs to be updated to reflect recent changes in how tail-matching is handled.

Issue

Users are currently instructed to add the ** pattern themselves when setting up static routes, but this is now handled automatically by the StaticRoute._ constructor via the tailMatch parameter.

What needs to be fixed

Update the documentation to show that users should not include ** in the path when calling StaticRoute.directory().

Current (incorrect) documentation suggests:

server.webServer.addRoute(
  StaticRoute.directory(Directory('web/files')),
  'files/**', // <-- don't add ** manually
);

Correct usage:

server.webServer.addRoute(
  StaticRoute.directory(Directory('web/files')),
  'files/', // <-- no **
);

The ** pattern is now automatically set up in:

StaticRoute._(this._handler, {required bool tailMatch})
    : super(methods: {Method.get, Method.head}, path: tailMatch ? '/**' : '/');

Related

• Issue "Cannot attach at a tail path. Tail segments (**) cannot be extended" when adding static dir route relic#335
• Requested by @nielsenko
• Discussion: "Cannot attach at a tail path. Tail segments (**) cannot be extended" when adding static dir route relic#335</issue_description>

Comments on the Issue (you are @copilot in this section)

@nielsenko This should be moved to serverpod_docs repo

• Fixes Fix stale documentation for StaticRoute.directory() usage #428

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.