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>

CONTEXT.md

@@ -249,7 +249,7 @@ supports subsequent corrections or scoped enhancements.
 
 The current implementation target is localhost before any production connection.
 Use `docker-compose.yml`, `.env.example`, and `LOCAL_SETUP.md`. The runtime is in
-`local/`; historical `portal/`, `kanban/`, `agente/`, and `schema.sql` are preserved
+`app/`; historical `portal/`, `kanban/`, `agente/`, and `schema.sql` are preserved
 as references and are not imported or started by Compose.
 
 - One local `dtf-cloud` Compose project runs seven long-lived services: Site and
@@ -308,10 +308,10 @@ as references and are not imported or started by Compose.
   `security_status` command summarizes authentication, rate-limit, scan, and
   scanner/signature alerts without exposing secrets. Security regression tests,
   exact-runtime Python dependency auditing, and Trivy image reports live under
-  `local/` and `output/security/`; open findings are documented in
+  `app/` and `output/security/`; open findings are documented in
   `SECURITY_REPORT.md` and are not a production-readiness claim.
 - All direct and transitive Python packages are pinned with artifact hashes in
-  `local/requirements.lock`; the API image build requires those hashes. The lock
+  `infra/requirements.lock`; the API image build requires those hashes. The lock
   is regenerated in a disposable Python 3.12 container by
   `local/lock_dependencies.sh`. A fresh exact-runtime audit found no known Python
   advisories on 2026-09-15; this does not cover OS/container findings.
@@ -327,7 +327,7 @@ as references and are not imported or started by Compose.
   not been deployed. Its fail-closed preflight intentionally rejects the current
   source until production adapters, Docker-secret file loading, approved inputs,
   restore rehearsal, image scans, and human security approval are complete.
-- `python3 -m local.backup create-and-verify` creates a private, Git-ignored bundle
+- `python3 -m app.backup create-and-verify` creates a private, Git-ignored bundle
   containing a PostgreSQL dump plus every complete, unexpired object already marked
   `clean`. SHA-256 manifests protect both parts. Verification restores the database
   under a UUID name and the object bytes under a UUID MinIO prefix, hashes the