update-backend-runtimeslisted
Install: claude install-skill sesori-ai/sesori_apps_monorepo
# Update Backend Runtimes
Plan and deliver current stable targets for **every included harness**. Audit
the actual protocol seam Sesori uses and report worthwhile upstream changes;
ask before adding optional features, not before doing the requested update.
Updating this skill alone does not start a runtime audit.
## Update-first policy
- An implementation request authorizes bringing every included target up to
date. Keeping old pins because testing is inconvenient or unavailable is not
an acceptable completion outcome. Preserve separately approved scope exclusions
and compatibility floors; updating a target does not authorize raising a floor.
- Missing credentials, configured fixtures, native runners, or incomplete
verification are **final-plan follow-ups**, not routine pin blockers. Deliver
the update, run useful available checks, then group unresolved tests, feature
questions and user-assisted validation in the final plan stages. Do not ask
repeatedly whether to proceed, hold a version, or obtain a fixture now.
- Distinguish update status from verification status. A target can be updated
while a check is `Not run`, `Blocked` or `Fail`; never turn that into a false
pass, conceal a failure, or declare the whole plan verified.
- Fix demonstrated compatibility problems as update work rather than allowing
permanent divergence. Only an exceptional, concrete risk—such as credible
data loss, a security regression, or a demonstrated unusable core flow—can