test(server): port core's UO suite onto the ctx harness

22 test files moved from core, plus the two that were split out of files core
keeps. 351 tests pass.

One change runs through every moved test, and it is the boundary rather than a
chore: core internals can no longer be stubbed by requiring them, because there
are none to require. `../utils/db` and `../model/settings` do not exist here.
What a test controls instead is the ctx core would have handed over, installed
once by test/_setup.js -- which is a better seam anyway, since it is exactly the
surface the contract promises and nothing wider.

The ctx _setup installs is deliberately unfrozen. Core freezes what it hands a
module and entry.test.js still asserts against a frozen one; but a test that
needs settings.get to return a path has to be able to say so.

Two tests changed SHAPE, and that is the boundary too. fromShardEvent used to
assert through publish() into pushDevices and a captured fetch -- which
endpoints were hit, how many requests went out. None of that is this module's
any more: publish is ctx.push.publish, and the device registry and the relay are
behind it. Reaching for them from here would be reaching past ctx. What remains
is what the module owns and is the part worth guarding: a game account resolves
to a website user, a personal target that resolves to nobody is dropped rather
than published, and a sensitive kind never reaches publish at all.

Co-Authored-By: Claude <noreply@anthropic.com>

server/test/_fakes.js

@@ -28,6 +28,10 @@ function fakeLog() {
 }
 
 function fakeCtx(overrides = {}) {
+  // `freeze: false` is for _setup.js, which installs one process-wide ctx a test
+  // may adjust. Core always freezes; the unfrozen variant is a test seam and
+  // never a claim about what a module is handed in production.
+  const { freeze = true, ...rest } = overrides
   const logs = []
   const ctx = {
     moduleId: 'uo',
@@ -50,10 +54,19 @@ function fakeCtx(overrides = {}) {
       siteMode: (req, res, next) => next(),
       validate: (req, res, next) => next(),
       noindex: (req, res, next) => next(),
+      // API 1.1.0. The factory returns a pass-through rather than a real
+      // limiter: a test that tripped a rate limit would be a test whose result
+      // depended on how many times the suite had run.
+      rateLimit: (options) => Object.assign((req, res, next) => next(), { options }),
+      accountChangeLimiter: (req, res, next) => next(),
     },
     uploads: { upload: {}, UPLOAD_DIR: '/tmp', MIME_EXT: {} },
     posts: { listAll: spy(Promise.resolve([])), getById: spy(Promise.resolve(null)), linkAnnounceJob: spy(Promise.resolve()), markAnnounced: spy(Promise.resolve()) },
-    ...overrides,
+    // The three §2.3 members API 1.1.0 added for this extraction.
+    activity: { log: spy(Promise.resolve()) },
+    users: { getById: spy(Promise.resolve(null)) },
+    site: { baseUrl: 'http://localhost:5173' },
+    ...rest,
   }
   // Non-enumerable, and that is not tidiness. Core freezes every object value on
   // `ctx` one level deep, so an enumerable recorder hung off it would be frozen
@@ -62,6 +75,7 @@ function fakeCtx(overrides = {}) {
   // faithful: a module iterating `ctx` sees exactly §2.3's members and nothing
   // a test put there.
   Object.defineProperty(ctx, 'logs', { value: logs, enumerable: false })
+  if (!freeze) return ctx
   for (const value of Object.values(ctx)) {
     if (value && typeof value === 'object') Object.freeze(value)
   }