add-to-librarylisted

## Boundary: where this sits `add-to-library` is the **direct-to-library** route, deliberately outside the project pipeline: - `ingest-source` reads an acquired source **into a project's wiki** (source page + entities + a project-local BibTeX entry) with a full read. It is project-scoped. - `acquire-sources` **downloads** the PDFs a `literature-review` guide lists. - `add-to-library` takes **one PDF you already have** and adds it to the shared master so it surfaces in `bib-search.py` for every future project — **no wiki content, no full read.** Later, if a project actually cites it, `ingest-source` reads it as usual; the master entry is already there. Use it when a colleague sends a PDF, or you download one, and you want it in the collection now without ingesting it. # Add a document directly to the master library **Announce at start:** "Using add-to-library to add `<pdf>` to the shared master library — I'll verify the metadata before writing anything." The deterministic mechanics (compute the bibkey, place the PDF, append the entry) live in `scripts/add-to-library.py`. **Your** job is the judgement the script cannot do: verify the metadata against a real record, and curate the keywords. Never let the script mint a key from data you have not verified. <SOFT-GATE> Before closing, check: (1) the metadata was **verified** against Crossref/OpenAlex (or a manual Crossref lookup) — not taken from the PDF's docinfo alone, (2) the PDF is placed at `<library>/pdf/<bibkey>.pdf`