✨ Add replaceable QDMI drivers and stable device IDs

[burgholzer]

🤖 AI text below 🤖

Description

Allow applications to replace a QDMI driver without rebuilding and select configured devices by stable ID. The PR targets develop and retains the merged calibration and pulse removals.

The driver exports the Client Interface and reports its ABI version. Both interfaces use the QDMI release version; application–driver compatibility compares major/minor and ignores patch. The ABI macro and its documentation live together in client.h.

QDMI_DEVICE_PROPERTY_ID is the single client-visible identity. Drivers supply configured IDs, overriding device defaults as needed. Device-side reporting stays optional. Configured top-level devices have IDs; child devices may forward a device-reported ID or return NOTSUPPORTED. The example and template report their default stable identifiers, and documentation explains which driver and configuration to record with a saved ID.

Validation: release build and 97 CTest cases passed (expected read-only skips); repository lint, C11 header consumption, and Doxygen passed. The canonical configuration-path fix, optional example-driver authentication, and final-session library cleanup are included here because they repair this driver foundation. Core #2229 now reuses QDMI's example driver for runtime tests. The example uses native Windows loading and POSIX loading; the Windows paths are covered by Core's hosted Windows jobs. The downstream Core/provider changes demonstrate installed C++ and Python applications using standard QDMI symbols with interchangeable drivers.

QDMI commit: ffde5f4aa09e70b681a79418c5071eb65ba8121d. All 19 hosted checks passed on this head.

AI assistance: Codex prepared and validated these changes; human review remains required.

Checklist

• The pull request only contains commits that are focused and relevant to this change.
• I have added appropriate tests that cover the new/changed functionality.
• I have updated the documentation to reflect these changes.
• I have added entries to the changelog for any noteworthy additions, changes, fixes, or removals.
• I have added migration instructions to the upgrade guide (if needed).
• The changes follow the project's style guidelines and introduce no new warnings.
• The changes are fully tested and pass the CI checks.
• I have reviewed my own code changes.

If PR contains AI-assisted content:

• I have disclosed the use of AI tools in the PR description as per our AI Usage Guidelines.
• AI-assisted commits include an Assisted-by: [Model Name] via [Tool Name] footer.
• I confirm that I have personally reviewed and understood all AI-generated content, and accept full responsibility for it.

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://Munich-Quantum-Software-Stack.github.io/QDMI/pr-preview/pr-511/
Built to branch gh-pages at 2026-09-28 06:20 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[codecov]

Codecov Report

❌ Patch coverage is 91.17647% with 9 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
examples/driver/qdmi_example_driver.cpp	91.1%	9 Missing ⚠️

@@            Coverage Diff            @@
##           develop    #511     +/-   ##
=========================================
+ Coverage     90.6%   91.1%   +0.5%     
=========================================
  Files            6       6             
  Lines          745     778     +33     
  Branches       145     157     +12     
=========================================
+ Hits           675     709     +34     
+ Misses          70      69      -1     

Flag	Coverage Δ
cpp	91.1% <91.1%> (+0.5%)	⬆️

Files with missing lines	Coverage Δ
examples/device/src/cxx_device.cpp	94.2% <ø> (ø)
examples/driver/qdmi_example_driver.cpp	94.7% <91.1%> (+1.2%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[burgholzer]

This is mostly looking good already. There's a few minor things that I would like to fix.

[burgholzer]

Okay, this should be good now.

[burgholzer]

@ystade After quite some iteration, the next PR in this series towards the 1.4 release is ready across the board. I hope this is fairly uncontroversial. Looking forward to your feedback!