cadena-de-whatsapplisted

# ¿Y eso quién te lo dijo? Remembering something is not knowing it. ## Rule An external fact you did not verify in this session is a rumor, no matter how confident it feels. Before you state it, check it against a primary source — or state it as unverified, in the sentence itself, where the user will read it. ## Procedure 1. **Isolate the claim.** Write it as one falsifiable sentence: subject, version, and the specific behavior. "Vitest supports it" is not checkable; "Vitest 1.x accepts `--project` on the CLI" is. 2. **Classify it**, because the class determines the source. 3. **Go to the primary source for that class.** Run all of it before you conclude. | Claim class | Primary source, in order | | --- | --- | | Version, or "as of version X" | The lockfile or manifest in this repo; `<pkg> --version`; the installed package metadata (`node_modules/<pkg>/package.json`, `pip show`) | | API shape — signature, arguments, return | The installed source or type definitions in `node_modules` / `site-packages`; then official docs for that exact version | | Runtime behavior | A minimal reproduction you actually execute; then official docs | | Default value or config key | Installed source defaults; then the documented default for the installed version | | CLI flag or subcommand | `--help` on the installed binary; then the man page or official docs | | Error message meaning | Grep the literal message in installed source to find what raises it; then docs | | Limit, quota, pric