Every remote source is cloned into `.data/content` and kept there. Nothing in a
build mentions this directory, so nothing suggests it when it goes wrong.

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

## Why it matters

A stale directory here cost real time once: a tag was fetched as a branch, the
fetch failed, and the half-written folder kept answering for the fixed config
until it was deleted by hand. The build said nothing, because as far as it was
concerned the source was already downloaded.

**Drop** removes one entry; the next build downloads it again.

## Notes

Content keys a directory by repository **and** ref, so an entry for a ref you have
renamed is never reused — and never cleaned up either. This panel is where those
are found.

::callout{type="warning"}
Dropping an entry deletes a directory on your disk. It is only ever the cache —
never a source of truth — but it is a real deletion, and it is why this tab is not
registered in a build.
::