Weekly literature reading list (Jev), tests for the Jev tools, maintenance tools documented

CONTRIBUTING.md

@@ -67,6 +67,23 @@ is sent to the API, never data. The key comes from `TYPESAFE_API_KEY` or `~/.con
 enters the repository; a full check costs well under one cent. `--dry-run` shows the claims and evidence without
 calling the API.
 
+## Maintenance tools (TypeSafe Jev)
+
+Small tools in `scripts/jev/` use TypeSafe System One judgments (Jev) where plain code needs semantic understanding.
+Code always collects the evidence and decides what to do; the model only answers typed questions. They are never
+part of the `simurg` commands, which stay offline. The key comes from `TYPESAFE_API_KEY` or
+`~/.config/typesafe/credentials` (a repository secret of the same name for the issue workflow).
+
+* `scripts/docs/check_claims.py FILES`: numeric claims of public texts against the validation reports.
+* `scripts/jev/spec_coverage.py`: which spec items have a test; writes `spec_coverage_report.md`.
+* `scripts/jev/voice_check.py FILES`: brand voice rules (dashes, banned words, claims without limits, hype, tone).
+* `scripts/jev/nightly_triage.py NIGHT`: which known finding explains a failed nightly step; `scripts/nightly.py`
+  runs it automatically when a night fails.
+* `scripts/jev/issue_triage.py`: first triage of new issues (`.gitea/workflows/issue_triage.yml`).
+* `scripts/jev/literature_watch.py`: weekly reading list from bioRxiv and PubMed into `data/literature/`.
+
+Each run costs a fraction of a cent; answers are cached in `.cache/jev/`.
+
 ## Pull requests
 
 * One topic per pull request, with tests.