Remove the legacy Fresh application and relocate shared assets

[dahlia]

Problem

Once traffic and responsibilities have moved away from web/, the Fresh application and its remaining build assumptions should be removed as one deliberate cleanup. Leaving dormant code, dependencies, or tasks behind would keep Deno and the old architecture alive implicitly.

Tasks

• Move shared fonts and other reusable assets out of web/.
• Remove the legacy application source, tests, localization files, and Fresh-specific configuration.
• Remove Fresh and Preact dependencies that are not used elsewhere.
• Remove dev:web, build:web, prod:web, and legacy health-check tasks.
• Update Docker, Compose, CI, documentation, examples, and environment defaults.
• Remove reverse-proxy and deployment routes that target the legacy service.
• Verify that no maintained code or build step imports files from web/.

Acceptance criteria

• The web/ directory is removed.
• No Fresh-only dependency, task, container step, route, or document remains.
• Shared assets have runtime-neutral ownership.
• web-next, GraphQL, federation, tests, code generation, and production builds pass without the legacy source tree.

AI assistance: This issue was drafted and organized with Codex after a maintainer-led code audit.