[LI (ktz03)]

Motivation & Context

A pytest parameter ID such as a|b is written unescaped inside the integration trend report's test-name cell. GitHub Flavored Markdown treats the pipe as a column separator even inside a code span, so the displayed test name is split and the file, provider and result columns shift.

Description & Review Guide

• What are the major changes? Escape pipes only in displayed short test names. Add six standard-library regression tests and run them explicitly in the existing Code Quality workflow.
• What is the impact of these changes? Python and per-framework report tables retain one cell per test name. Test identifiers, history JSON, counts, status lookup and ordering remain unchanged.
• What do you want reviewers to focus on? The regressions exercise the complete module with normal pytest-style and xunit-style XML fixtures plus the real CLI: four failures and two passing controls before the fix, all six passing afterward on Windows/Python 3.14.3. A separate local table-rendering check reuses real pytest 9.1.1 JUnit output and confirms the corrected cell contents and unchanged plain-name control. This is local validation; GitHub rendering, native .NET execution, full workspace tests, locked Ruff and official CI were not run.

Related Issue

N/A - trivial change. This corrects text escaping required by the existing table format (GFM tables, Example 200); it does not alter report data or introduce a new reporting policy.

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details: Codex: implementation, regression tests, and this PR description.

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• This is not a breaking change.

[Copilot]

🟢 Approval recommended

The localized display-only fix has focused regression coverage and no identified blocking issues; tests were not executed during this review.

No open issues 🎉

What changed in this PR

This PR fixes Markdown table alignment in integration trend reports by escaping pipes in displayed test names without changing stored identifiers or report data.

Changes:

• Escape pipes in short test names for Python and per-framework report tables.
• Add six regression tests covering formatting, unchanged history, and CLI output.
• Run the regression tests in the existing Python Code Quality workflow.

File	Description
python/​scripts/​integration_test_report/​tests/​test_trend_table.py	Adds six formatting and data-preservation regression tests.
python/​scripts/​integration_test_report/​aggregate.py	Escapes pipes in displayed short test names.
.github/​workflows/​python-code-quality.yml	Runs the new tests through unittest discovery.

_{Review effort: Balanced}