LinAlg HLK: Integrate LinAlg coverage into the existing DXIL HLK pipeline

Goal

Complete the LinAlg-specific work needed to deliver DxilConf_SM610_LinAlg through the existing DXIL/HLSL HLK pipeline.

Reuse the established TAEF runner, package, discovery, logging and source-synchronisation mechanisms. Do not create a bespoke LinAlg runner or packaging system.

Why

The existing HLK infrastructure already carries other HLSL ExecutionTests and D3D12Conf content. LinAlg is already conditionally integrated into D3D12Conf, but it still needs final identity, requirement mapping, source synchronisation and end-to-end discovery verification before it is certification-ready.

Required work

• Reuse the existing DXIL/HLSL HLK binary, TAEF runner and WTL logging path.
• Synchronise the current public LinAlgTests.cpp through the established source-update mechanism.
• Preserve the stable identity and metadata established by #8655.
• Confirm the intended SM6.10 requirement mapping using the existing requirement mechanism.
• Add LinAlg to the appropriate existing HLK content and playlist selection paths.
• Ensure the existing package carries the public DXC/compiler and D3D12 runtime dependencies required by SM6.10 LinAlg.
• Verify standard HLK/TAEF discovery of the class and individual methods.
• Verify existing per-method WTL logging remains sufficient for LinAlg failures; add only LinAlg-specific parameter diagnostics that are genuinely missing.
• Ensure stale packaged LinAlg source is detected by the existing synchronisation workflow.
• Exercise the public dx::linalg API in packaged execution tests.

Acceptance criteria

• No new LinAlg-specific runner or packaging framework is introduced.
• The existing HLK package contains the current public LinAlg ExecutionTests.
• Stable identity and requirement metadata match public DXC source.
• LinAlg appears through the existing content and playlist selection mechanisms.
• HLK/TAEF discovers the class and individual methods using the existing pipeline.
• Existing WTL output identifies the failing LinAlg method; any added diagnostics are limited to LinAlg parameters and mismatches.
• A synchronisation check detects stale LinAlg test source.
• A clean test system can run the packaged test without a DXC developer checkout.
• Missing dependencies or unsupported setup are not reported as passing results.

Public references

• Parent tracker #7841
• Stable identity and metadata #8655
• LinAlgTests.cpp
• Existing HLK precedent in INF-0006-Long-Vector-ExecutionTest-Plan.md

Out of scope

• Building a new test runner, package format, logging system or discovery mechanism.
• Publishing private package paths, scripts, signing details or release schedules.
• Expanding operation/type/scope coverage.
• Representative-device qualification.

Assisted-by: GitHub Copilot