Dig report

Barely Cold

The two finds freshest when they were dug — a complete feature PR closed when its own CI went unstable, and a patch to a dependency, removed at the owner's request after the empty sections it was meant to prevent kept appearing.

the Plainer Cut·2 finds·assessed 16 Jul 2026
In this report · 2 finds
  1. copy-link affordance on session/digest headsFresh
  2. the @nuxt/content #236 client-DB patchFresh

These two are graded fresh: not because they are unfinished, but because they had been discarded so recently when they were dug that they read as if they might yet be picked back up. A grade is never re-derived once set, so read them as they were: barely cold.

Fresh

the Plainer Cut · 14 Jul 2026 – 24 Jul 2026

the @nuxt/content #236 client-DB patch

commit b23e8d3 · @nuxt__content@3.15.0.patchclosed by ownerassessed 16 Jul 2026

One hundred and seven lines patched into a dependency's compiled dist: retry the SQL dump fetch four times, and evict the cached load promise in a finally so one rejected fetch could no longer leave a collection blank for the life of the page. Carried eight days, then given up rather than fork a vendor's build. Empty sections kept appearing with it in place, and the owner asked for it to be dropped rather than carried. Three days later the first real capture showed that the failure the owner had been hitting was a different one — a piece of the site's own code failing to load, not the fetch the patch was written to retry. It did not go alone: pnpm-workspace.yaml, which never listed a package or a workspace member — one key, patchedDependencies, mapping @nuxt/content@3.15.0 to the file beside it — was created in the patch's first commit and deleted in the patch's last, having served exactly one dependency for exactly as long as it existed.

“chore(deps): drop the @nuxt/content #236 client-DB patch (ADR-0019)”commit b23e8d3, subject

remainsthe patch, both hunksthe workspace file, in full — its whole reason to existADR-0019 before it was marked superseded