diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-07 14:43:28 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-07 14:43:40 +0000 |
| commit | 84838f6e8f42a2a794641bc766f273fbd152e7fd (patch) | |
| tree | d905b315c64e0f1c1520211538e63204af3c3862 /test/python/test_publications.py | |
| parent | f346dc273ef38cdb268fd68bb5697a8ee30e5fde (diff) | |
| download | genenetwork4-84838f6e8f42a2a794641bc766f273fbd152e7fd.tar.gz | |
docs/www: say who issues tokens, and what the assistant should ask for
The page said a human issues tokens and to "stop and ask", without saying whose door to knock on -- and the operator commands belong in the operator file anyway. State it as the GeneNetwork team, with wording the assistant can relay to its user: what a token is for, how long the default lasts, and to pass it out of band rather than through a public issue or a shared chat. Same wording for renewal, since a 401 is the one failure the assistant cannot fix itself. * docs/www/ai-instruction.md (1. Get a token): "If you do not have one" and "If it stops working", the latter quoting request_id and retrying exactly once; the summary line and the 401 row of the error table say GeneNetwork team rather than "the operator". * docs/www/operator-checklist.md (Token issuance): the request path, so the team knows what the ask they receive looks like. * .gitignore: *.swp, after one got swept into this commit.
Diffstat (limited to 'test/python/test_publications.py')
0 files changed, 0 insertions, 0 deletions
