calendar and contacts, extracted from the officer platform

one sidecar, one permission, one install — and two screens, because Calendar and
Contacts are two places you go rather than two sections of one page. the first
plugin to declare `screens`, which the platform gained for this.

what moved: the radicale sidecar, the four routers, the panel apps, the
app-password table and the settings form. the form became a modal on the
calendar screen — a plugin ships panels and cannot contribute a settings
section, which is the same wall the email plugin hit and the same answer.

the routes are /calendar and /contacts, not /caldav/calendar. they were core
routes and keeping them is not cosmetic: a bookmark, a dock tile someone
arranged, and a persisted layout all address them. only a first-party plugin may
choose its own segment; a third-party one is confined to /p/<publisher>/.

four paths outside /api come with it, above the account gate, because phones are
not browsers: DAVx5, iOS and thunderbird send HTTP basic on every request and
have nowhere to put a JWT. that is not "open" — the sync door demands a scoped
app password and resolves it to one user before radicale sees anything.

two things deliberately unchanged. the table is still dav_app_passwords, not
caldav_app_passwords: installs hold real rows and a naming convention is not
worth a data migration on a live machine. and the panel names still resolve
through the platform's catalogs, so the six locales they had as core screens
survive rather than dropping to english to make the refactor tidier.

per-user was already true and is worth writing down because the config said
otherwise: the sync door resolves an app password to an account, tells radicale
that id is the principal, and owner_only does the rest. the comment claiming
"the owner is the only principal that exists" had been stale since multi-user
landed on 2026-08-07.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

api/sidecar-server.ts

@@ -0,0 +1,17 @@
+import { createSidecarProxy } from '@@/sidecar/create-proxy';
+
+// The officer-caldav sidecar has TWO consumers in the platform and they need different things, so the
+// port capture lives here and both import it.
+//
+//  • `caldavRouter` — the ordinary JSON door for Officer's own UI. Behind userMiddleware, forwarded by
+//    the shared factory with `X-Officer-User`, exactly like every other sidecar.
+//  • `davSyncRouter` — the DAV door for phones. Cannot use the factory: it forwards only three headers
+//    (`create-proxy.ts:88`) and DAV dies without `Depth`, and it derives the user from a platform JWT
+//    that a DAV client has no way to hold.
+//
+// Hence one registration, two forwarders. The factory's own comment says it must never grow per-app
+// logic, so the DAV-specific half is a separate file rather than a branch inside it.
+const proxy = createSidecarProxy({ name: 'caldav', prefix: '/api/caldav' });
+
+export const caldavRouter = proxy.router;
+export const getCaldavUrl = proxy.getHttpUrl;