claude: Fix latex-ua1-filtered test expectations

The test expected both standards (a-2b, ua-1) to appear in DocumentMetadata,
but quarto filters out unsupported standards before passing to pandoc.
Updated test to expect only the supported standard (a-2b) in the output.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: gordonwoodhull

tests/docs/smoke-all/pdf-standard/latex-ua1-filtered.qmd

@@ -12,23 +12,23 @@ _quarto:
     pdf:
       noErrors: default
       ensureLatexFileRegexMatches:
-        # LaTeX receives ua-1 in pdfstandard (it accepts it syntactically)
-        - ['\\DocumentMetadata\{', 'pdfstandard=\{a-2b,ua-1\}', 'tagging=on']
+        # Quarto filters out unsupported ua-1, only a-2b is passed to LaTeX
+        - ['\\DocumentMetadata\{', 'pdfstandard=\{a-2b\}']
         - []
       printsMessage:
         # ua-1 should be warned about as unsupported
         level: WARN
         regex: "PDF standard 'ua-1' is not supported by LaTeX"
 ---
 
-# Test: LaTeX Filters Unsupported Standards from Validation
+# Test: Quarto Filters Unsupported Standards
 
 This test verifies that when `pdf-standard: [a-2b, ua-1]` is specified:
 
-1. LaTeX receives both standards in `\DocumentMetadata{pdfstandard={a-2b,ua-1}}`
-2. A warning is emitted that ua-1 is not supported by LaTeX
+1. Quarto warns that ua-1 is not supported by LaTeX
+2. Only supported standards (a-2b) are passed to LaTeX in `\DocumentMetadata{pdfstandard={a-2b}}`
 3. verapdf validates ONLY against a-2b (not ua-1)
-4. The render succeeds because we don't try to validate unsupported standards
+4. The render succeeds because unsupported standards are filtered out
 
 Without filtering, verapdf would fail because the PDF isn't actually PDF/UA-1 compliant
 (LaTeX only supports ua-2 for PDF/UA).