|
docs/www/SKILL.md: the workflow example now calls /compute/gemma/ravanan,
and a new "Which GEMMA endpoint" section says when not to: Slurm down or
submission failing, the user asks, a field ravanan refuses (covariates,
normalization), or verifying results -- where the wrapper endpoint is the
reference and scripts/gemma-compare.py is the check.
docs/dev/SKILL.md: the same rule from the developer side, in Testing --
verify mapping changes by sending one body to both endpoints and never
'fix' a difference by switching endpoints, plus the reminder that the
wrapper's cache only hits from 5eb53fa on, so a stale gemma-wrapper on
PATH looks like a broken cache.
|