diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-08 15:39:43 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-08 15:39:43 +0000 |
| commit | 386aed031612abc118e3390638cb5aff144be971 (patch) | |
| tree | 0c9fc936f63a9fbd497f10c3fb10414a18b79ad4 /test/python/test_openapi.py | |
| parent | 336f18e1bc22cb330052dc1ff45d1d06073bfcc3 (diff) | |
| download | genenetwork4-386aed031612abc118e3390638cb5aff144be971.tar.gz | |
docs: tell users (and operators) to refetch the instructions when the build moves
`/version` reports the revision the *server* is running, and this deployment is updated in place, so an assistant that cached `ai-instruction.md` can end up calling an API that has grown options its copy never mentions -- by default, silently. The instructions now say what to do about it, in the two places a reader sees a revision: pull the repository and re-read the page when `git` is not the revision the session started with, and the same in the `/version` section where that field is explained. It matters for the last few commits in particular: covariates in `/compute/rqtl` and `/compute/gemma` were added, and a stale copy would never know to ask for them. `docs/www/operator-checklist.md` gets the operator's half: nothing here enforces it, so a release that adds endpoints or options should say so where tokens are handed out, and `source_digest` -- not the commit alone -- is what identifies a build in a bug report.
Diffstat (limited to 'test/python/test_openapi.py')
0 files changed, 0 insertions, 0 deletions
