📝 Update templated files

Author: mqt-app[bot]

.github/CONTRIBUTING.md

@@ -3,6 +3,6 @@
 
 # Contributing
 
-Thank you for your interest in contributing to MQT Debugger!
-An extensive contribution guide is available in our
+Thank you for your interest in contributing to MQT Debugger! An extensive
+contribution guide is available in our
 [documentation](https://mqt.readthedocs.io/projects/debugger/en/latest/contributing.html).

.github/SECURITY.md

@@ -9,10 +9,8 @@ Security updates are applied only to the most recent releases.
 
 ## Reporting a Vulnerability
 
-To report vulnerabilities,
-you can privately report a potential security issue via the GitHub security
-vulnerabilities feature.
-This can be done here:
+To report vulnerabilities, you can privately report a potential security issue
+via the GitHub security vulnerabilities feature. This can be done here:
 
 <https://github.com/munich-quantum-toolkit/debugger/security/advisories>
 

.github/SUPPORT.md

@@ -3,20 +3,17 @@
 
 # Support
 
-If you are stuck with a problem using MQT Debugger or have questions,
-please get in touch at our [Issues] or [Discussions].
-We'd love to help.
+If you are stuck with a problem using MQT Debugger or have questions, please get
+in touch at our [Issues] or [Discussions]. We'd love to help.
 
 You can save time by following this procedure when reporting a problem:
 
 - Do try to solve the problem on your own first.
-- Search through past [Issues] and [Discussions] to see
-  if someone else already had the same problem.
-- Before filing a bug report,
-  try to create a minimal reproducible example (MRE)
-  that reproduces the problem.
-  It is much easier to identify the cause for the problem
-  if a handful of lines suffice to show that something is not working.
+- Search through past [Issues] and [Discussions] to see if someone else already
+  had the same problem.
+- Before filing a bug report, try to create a minimal reproducible example (MRE)
+  that reproduces the problem. It is much easier to identify the cause for the
+  problem if a handful of lines suffice to show that something is not working.
 
 You can also always reach us at
 [quantum.cda@xcit.tum.de](mailto:quantum.cda@xcit.tum.de).

.github/renovate.json5

@@ -81,7 +81,7 @@
       automerge: true,
     },
     {
-      description: "Disable minimum release age checks for our own GitHub Actions",
+      description: "Disable minimum release age checks for our own GitHub actions",
       matchManagers: ["github-actions"],
       matchPackageNames: [
         "munich-quantum-toolkit/*",

AGENTS.md

@@ -36,14 +36,14 @@
 
 ### C++
 
-- Targets Linux (glibc 2.28+), macOS (11.0+),
-  and Windows on x86_64 and arm64 architectures
+- Targets Linux (glibc 2.28+), macOS (11.0+), and Windows on x86_64 and arm64
+  architectures
 - C++20
 - CMake 3.24+
-- `FetchContent` for dependency management
-  (configured in `cmake/ExternalDependencies.cmake`)
-- `clang-format` and `clang-tidy` for formatting/linting
-  (see `.clang-format` and `.clang-tidy`)
+- `FetchContent` for dependency management (configured in
+  `cmake/ExternalDependencies.cmake`)
+- `clang-format` and `clang-tidy` for formatting/linting (see `.clang-format`
+  and `.clang-tidy`)
 - GoogleTest for unit tests (located in `test/`)
 
 ### Python
@@ -69,21 +69,19 @@
 
 ### General
 
-- MUST run `uvx nox -s lint` after every batch of changes.
-  This runs the full `prek` hook set from `.pre-commit-config.yaml`
-  (including `ruff`, `typos`, `ty`, formatting, and metadata checks).
-  All hooks must pass before submitting.
-- MUST add or update tests for every code change,
-  even if not explicitly requested.
+- MUST run `uvx nox -s lint` after every batch of changes. This runs the full
+  `prek` hook set from `.pre-commit-config.yaml` (including `ruff`, `typos`,
+  `ty`, formatting, and metadata checks). All hooks must pass before submitting.
+- MUST add or update tests for every code change, even if not explicitly
+  requested.
 - MUST follow existing code style by checking neighboring files for patterns.
 - MUST include a commit footer attribution in the form
   `Assisted-by: [Model Name] via [Tool Name]` (example:
   `Assisted-by: Claude Sonnet 4.6 via GitHub Copilot`) if AI tools are used to
   prepare a commit.
 - NEVER modify files that start with "This file has been generated from an
-  external template.
-  Please do not modify it directly."
-  These files are managed by
+  external template. Please do not modify it directly." These files are managed
+  by
   [the MQT templates action](https://github.com/munich-quantum-toolkit/templates)
   and changes will be overwritten.
 - PREFER running targeted tests over the full test suite during development.
@@ -92,29 +90,26 @@
 
 - MUST use Doxygen-style comments.
 - MUST use `#pragma once` for header guards.
-- MUST regenerate stubs via `uvx nox -s stubs`
-  when files in `bindings/` are added or modified.
-- NEVER edit `.pyi` files in `python/mqt/debugger/` manually;
-  they are auto-generated by nanobind stubgen.
+- MUST regenerate stubs via `uvx nox -s stubs` when files in `bindings/` are
+  added or modified.
+- NEVER edit `.pyi` files in `python/mqt/debugger/` manually; they are
+  auto-generated by `nanobind.stubgen`.
 - PREFER C++20 STL features over custom implementations.
 
 ### Python
 
 - MUST use Google-style docstrings
 - PREFER running a single Python version over the full test suite during
   development.
-- PREFER fixing reported warnings over suppressing them
-  (e.g., with `# noqa` comments for ruff);
-  only add ignore rules when necessary and document why.
-- PREFER fixing typing issues reported by `ty`
-  before adding suppression comments
-  (`# ty: ignore[code]`);
-  suppressions are sometimes necessary for incompletely typed libraries
-  (e.g., Qiskit).
+- PREFER fixing reported warnings over suppressing them (e.g., with `# noqa`
+  comments for ruff); only add ignore rules when necessary and document why.
+- PREFER fixing typing issues reported by `ty` before adding suppression
+  comments (`# ty: ignore[code]`); suppressions are sometimes necessary for
+  incompletely typed libraries (e.g., Qiskit).
 
 ## Self-Review Checklist
 
 - Did `uvx nox -s lint` pass without errors?
 - Are all changes covered by at least one automated test?
-- Were Python stubs regenerated via `uvx nox -s stubs`
-  if bindings were modified?
+- Were Python stubs regenerated via `uvx nox -s stubs` if bindings were
+  modified?