frank-large: ship HALOGEN_VERBOSE=1 for permanent startup evidence

Verbose engine logging is the vendor's first-line evidence for load,
allocation and admission questions; shipping it on means an incident
report already carries the full startup account instead of needing a
restart-into-debug. HALOGEN_DMALLOC_LOG stays off (every alloc >64MB is
steady-state noise on a shared host). Doc updated with the rootless
podman-logs-vs-journalctl retrieval note.

dankclaw/frank-large/quadlet/frank-large.container

@@ -97,6 +97,13 @@ Environment=HALOGEN_KV_SLOTS=4
 Environment=HALOGEN_HOST_RESERVE_GIB=24
 # Image input (the sidecar ships inside the weights repo).
 Environment=HALOGEN_VISION_TOWER=1
+# Verbose engine logging: the vendor's first-line evidence for load,
+# allocation and admission questions. Shipping it on means an incident report
+# already has the full startup account instead of needing a restart-into-debug.
+# HALOGEN_DMALLOC_LOG is deliberately NOT set — it logs every allocation
+# over 64 MB, which is steady-state noise here; raise it only for a live
+# OOM hunt.
+Environment=HALOGEN_VERBOSE=1
 # Required by the image: the engine maps the checkpoint and registers it with
 # the GPU in place, which needs host IPC and an unconfined seccomp profile.
 PodmanArgs=--ipc=host --security-opt seccomp=unconfined