ai4l-library 0.1.4 → 0.1.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,14 @@
1
1
  # AI4L Library — Change Log
2
2
 
3
+ ### v0.1.6 — 2026-11-07
4
+
5
+ * No change to the server. The fleet TUI (dev repo, not in the package) pulls its checkout with each rescan (`AI4L_LIBRARY_TUI_PULL=1`) instead of on its own timer.
6
+
7
+ ### v0.1.5 — 2026-11-07
8
+
9
+ * `library.log`: a message starting with `!!` is an alert — a service refused the deployment itself (Bright Data's reason from its `x-brd-err-msg` header, e.g. a token not allowed from this IP; a verify model failure; an unknown tier name at startup).
10
+ * Fixed: `AI4L_LIBRARY_DIR` set in `.env` was ignored (the library directory was resolved before `.env` was loaded); only the environment worked.
11
+
3
12
  ### v0.1.4 — 2026-11-07
4
13
 
5
14
  * `.env` is the whole configuration: every value an environment variable, the tier set and the defaults built in. `library/config.json` and `AI4L_LIBRARY_CONFIG` are gone, and with them `${NAME}` references and the per-tier `description`.
package/README.md CHANGED
@@ -1,4 +1,4 @@
1
- ![Version 0.1.3](https://img.shields.io/badge/Version-0.1.4-green.svg)
1
+ ![Version 0.1.3](https://img.shields.io/badge/Version-0.1.6-green.svg)
2
2
  ![License MIT](https://img.shields.io/badge/License-MIT-yellow.svg)
3
3
  [![Forever Healthy](https://img.shields.io/badge/(c)_2026-Forever_Healthy-573D7D.svg)](https://forever-healthy.org)
4
4
  [![npm](https://img.shields.io/badge/npm-ai4l--library-cb3837.svg)](https://www.npmjs.com/package/ai4l-library)
@@ -147,7 +147,7 @@ PubMed's book records — National Academies reports, NTP monographs, StatPearls
147
147
 
148
148
  **Why a notice may have no PMID.** PubMed gives the notice's PMID only when the notice is itself a PubMed record. For about a quarter of the errata in a 6,900-entry library it is not: the journal printed the correction, PubMed recorded the citation in the paper's record, and never indexed the correction as a record of its own (NEJM, JAMA and Lancet errata from 1988 to 2014 are typical). There is nothing to redirect to, so `pmid` is null and `source` — the citation as PubMed wrote it — is the notice's only identifier. Measured on the 79 such errata in the library (2026-11-04): PubMed's citation matcher resolves 18 after all (13 directly, 5 after picking the "Published Erratum" among two candidates), Crossref gives a DOI for 38 more when journal, volume and page match, and 23 have no identifier anywhere. The planned second stage resolves them at ingest (PMID first, then DOI, the citation always kept), fetches the notice's text and classifies it once per paper as major (a number, table, figure, result or conclusion changed) or minor (authors, funding, typos): a major erratum makes the paper not citable, like a retraction, so the audit never has to apply a correction; until then an erratum is a note on a citable paper.
149
149
 
150
- Every action is appended to `library/library.log`, one line per call, starting with a local timestamp and the host name — so several workers sharing one library can be told apart. Past 50 MB the file is renamed to `library.log.1` (one old file kept) and the next line starts a new one. Entry files are written to a temporary name and renamed into place, so a reader never sees a half-written file, and several servers may write one library directory:
150
+ Every action is appended to `library/library.log`, one line per call, starting with a local timestamp and the host name — so several workers sharing one library can be told apart. Past 50 MB the file is renamed to `library.log.1` (one old file kept) and the next line starts a new one. Entry files are written to a temporary name and renamed into place, so a reader never sees a half-written file, and several servers may write one library directory. A line whose message starts with `!!` is an alert: a service refused the deployment itself, not a paper — the Bright Data token rejected from this IP, the verify model unreachable or answering an error, an unknown name in `AI4L_LIBRARY_TIERS` at startup — so it stands out from the papers' own misses:
151
151
 
152
152
  ```
153
153
  2026-10-26 17:12:31 omacvm-berlin add pmid:30955454 fetched pubmed level=abstract