Site Admins tune quotas per user and per pond on the three-level ladder
(pond override → user override → instance default, data-model.md §Quotas).
- api `admin/`: a `QuotaAdminService` + Site-Admin-gated endpoints under
`/admin/quotas` — look up a user (username/e-mail) or pond (slug), list every
quota's override / instance default / effective value (resolved through the
existing QuotaService, the single consumption path, so a change takes effect
immediately) plus current usage, and set/clear a per-subject override. Every
change is audit-logged. A pond's effective values resolve on its own override
then its owner's, matching the consumption checks.
- web: the Admin area gains a 'Quotas' surface — the instance defaults move
into a proper number-input form (was raw settings, #19), and a per-subject
panel looks a user/pond up, shows the ladder with usage, flags subjects over
their effective limit, and sets/clears overrides. New `quotas` i18n
namespace (de+en).
- tests: `quota-admin.e2e.db.test.ts` (override → effective changes at once and
QuotaService sees it; clear → falls back to the default; lookup; Site-Admin
gating); a browser `admin-quotas` pack proving an override raised in the UI
immediately lets a user create another shared pond (issue #22 consumption).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1
