The Context Budget Index · Stale-Reference Receipts · November 2026 · counted with ctxcap

Stale-Reference Receipts

An instruction file that names a path which no longer exists is not a style problem. It is a factual defect with a one-line fix. This page scans the context files of the most-starred repositories, reports the references that do not resolve, and states what was done about each one.

The scanner is deliberately conservative. It checks paths, globs, and npm run scripts named in a context file against the repository, and stays quiet when a reference could be a name, an example, or one of two alternatives. What it reports is still a candidate, not a verdict: every row below was read before it was called a defect, and receipts/reviews.json records the reading. The excluded list is published too, because a measurement that hides its false positives is not one.

Confirmed defects

Repository and lineReferenceThe line
twbs/bootstrapAGENTS.md:3 CLAUDE.md Guidance for AI coding agents working in this repository. Tool-agnostic; `CLAUDE.md` points here.
avelino/awesome-goAGENTS.md:38 .github/scripts/check-quality.js - The `PR Quality Checks` workflow will run `.github/scripts/check-quality.js`; ensure referenced links in PR bodies are reachable.

Read and excluded

Found by the scanner, and not published as defects. The reason is the reading, not a rule.

Not scanned

Absence cannot be proved for these, so they are listed rather than guessed at.

How it was counted

Run it on a repository

npx ctxcap --stale          # every reference that does not resolve
npx ctxcap --stale-fix      # a deletion diff for the ones it is sure about

To send one in: open an audit issue with the repository. The series is time-boxed to ten, and the before and after are published here with the line that changed.

Data for this month: 2026-11.json. Pull request drafts: receipts/prs. Method: receipts/README.md. Something wrong with a row? Open an issue.