The path debugger, and the panel most version bugs are found in. Every one this
layer has had was a disagreement between what a URL looks like and which source
claims it — `/workflows/v0.7.0` returning a 404, `/workflows/v0.7.0/v0.7.0` being
generated. Both were arithmetic on prefixes that nothing printed.

::devtools-panel{tab="paths"}
::

## The steps

1. **The locale segment is stripped.** `/de/sdk/guides/caching` is the page
   `/sdk/guides/caching` in German — the locale translates the interface, never
   the content tree, so every lookup in the theme means the stripped path.
2. **The longest matching prefix wins.** `/sdk/v1-9` and `/sdk` both match a page
   under the first; taking the shorter one is how a tag ends up rendering `main`.
3. **The claiming collection is queried** for that exact path.
4. **The same page is looked for in the sibling sources** — the other versions
   and languages of the same repository, never of a different one.

## Reading a miss

A page missing here and present in another column is the **fallback's** case: the
version switcher offers it, and the reader is sent to the nearest ancestor rather
than to a 404.

A page missing everywhere is a typo, and the panel then lists the nearest paths in
the collection — the ones sharing the longest leading run with what you pasted.

::callout{type="tip"}
Paste the URL exactly as the browser shows it, locale segment and all. The panel
does the stripping, and seeing it happen is half the answer.
::