frank-large: correct the halogen payload contract to the Hub's truth

The first constants were wrong in three ways, found while resuming the
checkpoint (the file was COMPLETE; the manifest was not):
- checkpoint is 35,865,565,184 B / LFS sha256 274c3fc7... (not
  35,880,329,102 / 40874e7a...), 1352 tensors per the card;
- the tokenizer is a FLAT tokenizer/ DIRECTORY of 5 files mounted whole
  at /tokenizer (model-card docker-run parity; the engine's
  HALOGEN_TOKENIZER default is the directory) — there is no
  frank-large.tokenizer.gguf;
- plain git blobs (vocab/merges/jinja/config) carry no LFS oid, so the
  fetch script size-checks them and sha-verifies only the two LFS
  objects (checkpoint, tokenizer.json).

Gates flipped together (serve + deployer twins): tokenizer dir must be a
real directory and every named file a regular file, no symlinks (HF
snapshot links dangle in the mount). Fetch made idempotent: a file at
the published size skips the transfer (resuming it is a CDN 416 under
set -e). Seam rewritten to the same contract, 17/17.

serverAppConfigs-docs/LLM/frank-large-halogen27b-dflash2.md

@@ -4,8 +4,9 @@ frank-large is the Strix Halo iGPU endpoint on Dankclaw (`:7770`). Since
 2026-10-05 it runs the **halogen** engine — `ghcr.io/peonist-ai/halogen` at a
 pinned digest, launched by `scripts/serve-frank-large.sh` under a root
 systemd unit as a podman container — serving
-**`peonist-ai/halogen-qwen3.8-27b`** (`qwen3.8-27b-p1w4d-d2.hgn`, 35,880,329,102 B
-≈ 33.4 GiB) with the **DFlash2** drafter at **one slot x 200,700 ctx**.
+**`peonist-ai/halogen-qwen3.8-27b`** (`qwen3.8-27b-p1w4d-d2.hgn`,
+35,865,565,184 B ≈ 33.4 GiB, sha256 `274c3fc7…`, 1352 tensors) with the
+**DFlash2** drafter at **one slot x 200,700 ctx**.
 
 It replaced the ROCmFPX llama.cpp fork endpoint ([[frank-large-rocmfpx-q6agent-uncensored-mtp]]),
 which remains the rollback target with its payload on disk.
@@ -76,11 +77,15 @@ bearing numbers:
   storage before dispatch. NOT the 2026-09 `halogen-flash-server` repo — that
   was the Flash-Next w4b era, different image, retired.
 - **Payload:** `scripts/download-frank-large-halogen.sh` (fetch law: `curl -f`,
-  exact byte count, LFS/hub sha256, `--verify-only`, token never in argv) into
-  `/home/dank/models/halogen-qwen3.8-27b/`. The tokenizer bundle
-  (`frank-large.tokenizer.gguf`) must be a FLAT regular file — the deployer
-  and serve script both refuse a symlink or directory: an HF symlinked/snapshot
-  layout passes `test -f` but fails the engine's open at request time.
+  exact byte count, LFS sha256 where the Hub publishes one, `--verify-only`,
+  token never in argv) into `/home/dank/models/halogen-qwen3.8-27b/`. The
+  tokenizer is a FLAT DIRECTORY (`tokenizer/`, 5 files — tokenizer.json,
+  vocab.json, merges.txt, chat_template.jinja, tokenizer_config.json),
+  mounted whole at `/tokenizer`; the engine's `HALOGEN_TOKENIZER` default is
+  that directory, so the container gets no tokenizer flag (model-card
+  docker-run parity). The deployer and serve script refuse a missing file or
+  ANY symlink: an HF cache snapshot symlinks each entry into `blobs/` and
+  those links dangle inside the container mount.
 - **Unit:** `scripts/frank-large.service` (root, `User=dank`, relinked into
   `/etc/systemd/system/`), `ExecStart` = serve script, `ExecStop` = `podman
   stop -t 120 frank-large-halogen`, script `exec podman wait` so