Print MiKTeX's own logs when a document fails

[pytooling-claude]

Changes

• A failed document compilation prints MiKTeX's own logs. When lualatex aborts it writes no document.log at all and points at /latex/.miktex/texmfs/data/miktex/log/lualatex.log instead:

  Sorry, but lualatex did not succeed.
  The log file hopefully contains the information to get MiKTeX going again:
    /latex/.miktex/texmfs/data/miktex/log/lualatex.log
  

  The container was removed with that file, so the reason was never visible and every occurrence read as "MiKTeX instability". An if: failure() step in the Document and Sphinx check jobs now groups the user and admin logs into the job output.

Bug Fixes

• The Specific job's outputs no longer carry literal quotes. Its tee "${GITHUB_OUTPUT}" <<EOF block wrote specific_image="<ns>/<name>:<tag>", and a heredoc does not strip quotes - so the quotes were part of the value and rendered in step names as Login and push '"pytooling/miktex:sphinx-dev"' to Docker Hub. It worked only because every use was interpolated into a shell command, which stripped them again; a container: image: reference or an API call would have got a name that does not resolve. The MiKTeX job's own block already wrote its values unquoted.

---

Related Issues and Pull-Requests

• Follows Upgrade the base image to Debian 13 Trixie #32 (Debian 13 Trixie).
• The abort this makes diagnosable has now been seen five times in two days, across dev, a release tag and the Trixie branch, always in a single font family while its siblings passed in the same run - so it is environmental rather than a defect in a document. The logs should say which resource was missing.