Phase 3: VISUAL feed and M-Files drawings in the worker

Migration 0004 (VISUAL and drawing caches, go-live ignored list, resource
map, job tables, order-derived columns with provenance; work order key
includes the operation sequence). The real worker on APScheduler with
settings re-read each fire, pause, run now, advisory locks, job_runs and a
heartbeat. The visual-feed job (five VisualKit reads, COPY and MERGE cache,
suspect-batch guard, the apply in one transaction: drafts, change orders,
retire-moved, work order gone, closed and cancelled observed, projects and
units from order links, auto-release) and the fingerprint. The drawing-lookup
job (queue, budget, download on version change, sha256 into assets, decision
table, staging for rev approval, drawing-origin change orders). Clerical From
VISUAL panel, flags, rev approval, hand uploads, change-order review; Admin
Feed settings and resource map. Synthetic fixture generator and a
fixture-driven worker in CI with a Playwright scenario. Docs updated.

Verified: 3249 server tests and 13 Playwright scenarios on the docker-1 CI
stack, 76 frontend tests, doctor at 0004; one feed and one drawing run
against VISUAL DEV and the vault from the developer machine (counts in the
changelog).

Co-Authored-By: Claude Fable 5.1 <[email protected]>

.env.example

@@ -5,3 +5,9 @@
 #   deploy/ci/ci.env             ->  CI and local end-to-end runs (committed, no secrets)
 # Passwords and keys are never put in an env file. They are files in SECRETS_DIR,
 # mounted as compose secrets. See docs/DEPLOY.md.
+#
+# Worker sources (phase 3). The defaults read VISUAL through VisualKit and M-Files through MFilesKit:
+#   FEED_SOURCE=visualkit      visualkit | fixture
+#   DRAWING_SOURCE=mfiles      mfiles | fixture
+#   FIXTURE_DIR=/fixtures      where the fixture sources read feed.<N>.json, drawings.<N>.json and state
+# fixture reads synthetic files from tests/fixtures/generator.py. STACK=prod refuses it.