Heads-up: campus-suite #981 changes campus.yapper client construction - no action required #64

Summary

campus-suite commit c6f034b (nyjc-computing/campus PR #981, merged 2026-10-28) changed how campus.yapper clients are constructed. Verdict for this repo: no action required. Since we track campus-suite@weekly, the change arrives on the next build/lock bump — this issue records the assessment so the bump is not a surprise.

Assessment evidence

• This repo has no campus.yapper imports (org-wide sweep: zero hits outside the campus monorepo).
• We never boot campus apps in-process: main.py / apps/* build this repo's own Flask app, and no STORAGE_MODE rigs exist here.
• Railway/deploy environment carries no YAPPERDB_URI or STORAGE_MODE variables.

What changed in campus.yapper

1. Self-contained: campus.yapper imports no campus package at all (boundary-enforced). The lazy yapper ↔ campus.auth cycle is gone.
2. create() signature: now keyword-only db_uri / db_uri_provider plus backend kwargs. The event DB URI resolves in priority order: db_uri argument → db_uri_provider() callable → YAPPERDB_URI env var → remote campus vault "campus.yapper" via campus_python.
3. DEPLOY=campus.auth special case removed: yapper no longer consults DEPLOY; the auth service injects its own vault reader internally.
4. YAPPERDB_URI is now honored as an environment fallback (priority 3). It was never read before, so no current deployment sets it — but if this repo ever sets it, it would override remote-vault resolution for bare create() calls.

When an upgrade step WOULD be required here

• Emitting events directly: call campus.yapper.create() bare (deployments) or pass db_uri= / db_uri_provider= explicitly. Docs: https://github.com/nyjc-computing/campus/blob/weekly/docs/yapper.md
• Booting campus apps in-process under STORAGE_MODE=1 (test rigs): set YAPPERDB_URI to a SQLite file path first (note: :memory: does not work across connections — use a temp file, like tests/fixtures/yapper.py in the campus repo). Test mode never contacts external services; with no URI resolvable it raises instead.
• Environment audit: if we ever introduce YAPPERDB_URI/STORAGE_MODE variables, re-read the resolution order in docs/yapper.md first.

References

• campus PR: refactor(yapper): inject event DB URI provider; campus.yapper imports no campus packages campus#981
• Parent design: Carve out campus-core: phased separation of shared layers from service imports campus#970 (phase 2)
• Consumer guide: https://github.com/nyjc-computing/campus/blob/weekly/docs/yapper.md