"""Integration: Containerfile stage-1 (frontend) asset coverage pin (phase 23). HERMETIC — no podman, no network, no database: this suite parses the ``Containerfile`` and ``frontend/`` as plain text and pins the image-build coverage that the TODO L6 bug ("Fix Containerfile build not working") demonstrated can silently rot in two independent ways: * the stage-1 ``cp`` line only copies the pages that existed when it was written (``document.html`` / ``login.html`` + their scripts + ``markdown.js`` were all missing from the image), and * absolute module imports (``import … from "/assets/header.js"``) break the esbuild bundle, so a "fixed" stage 1 can still ship a broken page. The pins (each is one test, per the phase-23 task file): 1. every ``frontend/*.html`` page is copied into stage 1's ``/out`` — exactly (a new page without a ``cp`` entry fails; a ``cp`` of a deleted page also fails); 2. every local ``assets/`` / ``/assets/`` ``src=``/``href=`` reference in the pages is produced by a stage-1 line (``esbuild … --outfile`` or ``cp``) — the missing-``markdown.js``-style gap cannot reappear; 3. the set of ``type="module"`` page scripts the HTML references equals the set of inputs esbuild ``--bundle``s in stage 1; 4. ``header.js`` is imported relatively by every page script and loaded by NO direct ``