[Medformatik]

Data now opens as a directory with focused OSM, Overture, Search & places, Transit, Coverage, Prepared transfers and Advanced operations workspaces. Only the opened domain mounts its status queries. Launchers open one existing schema-driven form; previews, destructive confirmations, specialized recovery actions and exact job links remain intact.

Transit has addressable Sources, Catalog, Credentials, Pipeline and Mobility tabs. A completed matching credential reauthentication returns to its reviewed actor/origin-scoped intent without replaying a write. Privacy cases are addressable independently of queue membership, with capability-based sections, visible denial/conflict reasons, bounded events and a narrow-screen case selector. History-driven case changes clear pending delivery; a missing case on reauth return restores it.

Stack: #782 → #784 → #785 → Stage D. Base is feat/admin-ux-stage-c.

Before: the Data monolith mounts acquisition forms together.

After: a directory that reads the aggregate inventory without polling every family.

OSM: one addressed operation form alongside inventory and unknown-evidence states.

Transit: desired acquisition is distinct from active publication.

Prepared artifact transfer has its own destination and retains bounded transfer controls.

Before: privacy readiness and case forms share a long page.

After: concise readiness, due/state header and addressable capability-based case sections.

390px dark layout with a case selector in place of the side queue.

Privacy administrators receive contact guidance without settings links, admin search or the job tray.

Hosted Data offers only available Transit and Coverage destinations.

ops-agent Data topics are hidden on hosted deployments and direct URLs explain their unavailability. Privacy casework names each blocked readiness check, including for privacy administrators without setup access. Completed/canceled Transit credential continuations retire when leaving their tab. Canonical destination links in the administration docs were updated.

Local verification: 109 focused admin/route/library and fixture files (887 tests), workspace TypeScript checks, lint, the documentation build and the production web build passed. A later complete serial portable run passed 26,816 tests with 785 skipped; its only failure was an owned Biome formatter stuck on stdin, which was terminated after about 40 minutes. The entire affected six-test Entur file then passed separately. That full run remains recorded as failed; no assertion or timeout was relaxed. Each PR’s current-head CI is the final Linux and database gate.

Screenshots show the hydrated production Next app against a synthetic loopback API that never forwards requests. Before views use archived main 1a7daf60; its isolated preview required dependency-root/type-check accommodations for duplicated package paths, and is visual evidence only. Final product builds and type checks were not bypassed. Additional narrow-layout checks used doubled root text size, not native browser zoom. No real host, data, privacy, email or credential mutation was performed; native-device and production acceptance are not established.

A direct host-only Data URL explains availability and links to Transit and Coverage.

CI follow-up: the required Linux deployment-user gate now runs its complete suite selection with one Vitest file worker, reducing competition between filesystem-heavy fixtures. Its 578 discovered files, UID 1001, umask 002, pinned Node image, test and hook timeouts, runtime deadlines and strict aggregate checks are preserved. Concurrency inside each case stays intact; failures are not retried. CI records the serial execution time in the Linux gate under its existing 30-minute job budget.

The new workflow contract failed before the worker flag and passed after it. All 58 related CI contract tests, exact before/after file-set comparison, lint and the documentation build pass locally. Opus reviewed the plan and concrete patch as READY; both wording nits were corrected.