React, Next.js, Svelte, Zod: none of them can tell AI who they're actually for

Your coding agent is good at reading code. Point Claude Code or Cursor at a repo and it will figure out the language, the framework, the build command — it just costs you tokens and a few tool calls every session to re-derive what it forgot. What it can't read is the part that isn't in the code: who the project is for,and why it exists. So it guesses. Confidently, in the same tone it uses for the facts it actually verified. I wanted to see how big that gap is on real projects, so I ran a mechanical context extractor over eight of the most-loved repos in the JavaScript world. The method faf git <url> clones a repo and fills in a small typed context file ( project.faf ) from what it can find — README, package.json , project structure, config. No hand-authoring, no LLM writing prose. It fills what's there and leaves the rest blank. Nine-ish slots: the identity (name, goal, language) and the six W's — who, what, why, where, when, how. Run it yourself: npx faf-cli git https://github.com/facebook/react The result repo extracted who why facebook/react 56% — blank — — blank — vercel/next.js 44% — blank — — blank — expressjs/express 50% — blank — — blank — colinhacks/zod 67% — blank — — blank — sveltejs/svelte 88% — blank — — blank — prettier/prettier 75% — blank — — blank — Eight repos in total (React, Next.js, Express, Zod, Hono, Svelte, Vue, Prettier). Every one of them: who is this for and why does this exist came back empty. Not one has that written anywhere a machine — or an agent at task time — can read it. Svelte scored 88%. The who and why are still blank. This isn't a documentation-quality problem, and it's not a knock on any of these projects. The stack lives in the files. The intent lives in maintainers' heads, design docs, old RFC threads, and Discord history — none of which your agent has open when it's editing a file. Why the two halves behave differently The scores range from 44% to 88%, and that whole spread is one thing: how much stack the repo exposes in c