refactor: lay the repository out by role

local/ held six unrelated things under a name that stopped being true once it
became the production runtime: the service, the frontend, the tests, the ops
commands, the container definitions and the dependency lock, 65 files with
nothing to tell them apart.

  app/      the service: api/ routers, core/ for identity, database, models,
            prices and secret loading, and the worker, bootstrap and schema
  tests/    the twelve suites, no longer inside the shipped package
  ops/      backup, readiness, dependency audit, security summary
  infra/    Dockerfiles, gateway templates, ClamAV and storage configuration,
            the requirements and their hash lock
  web/      the Site, Kanban and portal pages with their scripts

deploy/Dockerfile.api now copies app/ alone, so the tests stop shipping to
production; the local image still carries them, because the suites run inside
the stack's network.

Five kinds of reference had to follow, and each was found by something different
rather than by reading. Imports of the form "from . import db" survived a rewrite
that only matched "from .db import". Tests kept relative imports of modules that
had left the package. A mock.patch target names its module in a string, where no
import rewriting can see it. The browser test resolves a fixture by path. And the
release gate's markers pointed at local/runtime.py and local/worker.py, which is
the decay its new marker test exists to catch — it caught it.

Verified from docker compose down -v: the stack starts, all six integration
suites, both browser suites and the twenty-nine unit tests pass.

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

ROADMAP.md

@@ -12,7 +12,7 @@
 client inputs (1.1, 1.2, 2.10). Block 1 still waits on client inputs for
 1.1/1.2.
 
-**Last audit:** 2026-09-18, full read of `local/`, `dtf-site.html`, `deploy/`,
+**Last audit:** 2026-09-18, full read of `app/`, `dtf-site.html`, `deploy/`,
 `.gitea/`, docs and legacy prototypes. Findings below carry their audit IDs.
 
 | Status | Meaning |
@@ -279,7 +279,7 @@ deliberately not bundled here.
 
 Accounts now live in `dtf_local.operators`, one per person, with `movements.operator`
 and `order_files.created_by` recording who actually acted. Administered from the API
-container with `python -m local.operators` (list, add, password, disable, enable);
+container with `python3 -m app.operators` (list, add, password, disable, enable);
 passwords are read from the terminal so they never reach shell history or the
 process list, and disabling revokes open sessions immediately rather than leaving
 them valid for the rest of the eight-hour window.
@@ -417,9 +417,9 @@ charges. Fix as part of 1.1.
   with a header saying they are background, not instructions.
 - `[x]` 5.3 — Root `requirements.txt` deleted. It pinned by wildcard, listed
   packages the system does not use, and sat next to the hash-locked
-  `local/requirements.lock` inviting the wrong one to be installed. Only historical
+  `infra/requirements.lock` inviting the wrong one to be installed. Only historical
   documentation referred to it.
-- `[x]` 5.4 — `pip` removed from `local/requirements.txt` and from the lock. Nothing
+- `[x]` 5.4 — `pip` removed from `infra/requirements.txt` and from the lock. Nothing
   depended on it; it was pinned only because it was listed directly, and installing
   it put a package manager inside the read-only runtime image. The base image's own
   pip performs the hash-enforced install. Verified: the image builds under