Autoformat MAINTAINERS.md trailing whitespace

Author: steve-downey

copier/MAINTAINERS.md

@@ -1,6 +1,6 @@
 # Maintaining the Copier Template
 
-This document provides instructions for maintainers of the `exemplar` repository on how to test, update, and manage the `copier` template generation infrastructure. 
+This document provides instructions for maintainers of the `exemplar` repository on how to test, update, and manage the `copier` template generation infrastructure.
 
 For instructions on how entirely *new* users should invoke the template template using `uvx` and `copier` to start a new project, see the [main README.md](../README.md).
 
@@ -10,7 +10,7 @@ The `exemplar` repository serves a dual purpose:
 1. It is a fully functional, canonical Reference implementation of a Beman Library (the root codebase).
 2. It contains the Jinja-based template used by downstream Beman projects (the `template/` directory).
 
-To ensure that downstream templates are highly functional and that the template never falls out of sync with the reference implementation, we require that the `template/` output (`generating_exemplar=true`) perfectly recreates the root project repository, barring acceptable omissions. 
+To ensure that downstream templates are highly functional and that the template never falls out of sync with the reference implementation, we require that the `template/` output (`generating_exemplar=true`) perfectly recreates the root project repository, barring acceptable omissions.
 
 ## Utilities and Scripts
 
@@ -35,13 +35,13 @@ Performs a strict byte-for-byte validation ensuring that the `template/` generat
 While `check_copier.sh` is tailored to the `exemplar` structure, this script provisions completely neutral, third-party libraries (`generating_exemplar=false`).
 - Provisions instances utilizing different testing frameworks (e.g. `gtest` and `catch2`).
 - Tests matrix conditions (e.g. C++ Modules on vs. off).
-- Re-runs the CMake configure/build/ctest lifecycle on every variant to ensure downstream clients will not experience build breakages. 
+- Re-runs the CMake configure/build/ctest lifecycle on every variant to ensure downstream clients will not experience build breakages.
 
 ## Workflow: Updating the Templates
 
 When you make changes to the C++ code, CMake infrastructure, or CI processes within `exemplar`, you must propagate those updates to the Copier template:
 
-1. **Make changes in the canonical root directory.** Modify source, tests, workflows, etc., directly in the `exemplar` repository. 
+1. **Make changes in the canonical root directory.** Modify source, tests, workflows, etc., directly in the `exemplar` repository.
 2. **Propagate via script:** Execute `./copier/update_templates.py`. This covers 90% of file replication seamlessly.
 3. **Manually reconcile complex templates:** Look at the warnings generated by the Python script to see if structural Jinja templates (like `CMakeLists.txt.jinja` or `.github/CODEOWNERS.jinja`) require manual hand-editing.
 4. **Validate Parity:** Run `./copier/check_copier.sh`. Continue fixing template logic until the script emits `Success: Template matches project exactly.`.
@@ -51,14 +51,14 @@ When you make changes to the C++ code, CMake infrastructure, or CI processes wit
 
 The `copier` test scripts run in GitHub Actions underneath `ci_tests.yml`.
 
-- **`check_copier.sh` fails in CI:** 
-  You updated a file in the root repository (e.g. a submodule bump, a new workflow, modified C++) but forgot to update the corresponding `.jinja` file in the `template/` directory. 
+- **`check_copier.sh` fails in CI:**
+  You updated a file in the root repository (e.g. a submodule bump, a new workflow, modified C++) but forgot to update the corresponding `.jinja` file in the `template/` directory.
   **Solution:** Pull the branch locally and run `./copier/update_templates.py`. Check for regressions using `./copier/check_copier.sh` and push.
 
 - **`test_standard_project.sh` (or `copier-test` CI Job) fails:**
-  The `exemplar` generation works, but something breaks when the project generates for *other* people (`generating_exemplar=false`). 
-  **Solution:** Check the specific variant that failed. 
-  - *Did `catch2` break?* You might have modified `template/tests/beman/{{project_name}}/CMakeLists.txt.jinja` using `gtest` specifics that aren't guarded properly. 
+  The `exemplar` generation works, but something breaks when the project generates for *other* people (`generating_exemplar=false`).
+  **Solution:** Check the specific variant that failed.
+  - *Did `catch2` break?* You might have modified `template/tests/beman/{{project_name}}/CMakeLists.txt.jinja` using `gtest` specifics that aren't guarded properly.
   - *Did Modules break?* The CI test runs C++ modules using `ghcr.io/bemanproject/infra-containers-clang:latest`. Ensure the CMake module directives conditional branches haven't drifted.
-  
+
   Locally, you can simulate specific container behaviors by targeting a custom CMake preset or enabling actions mode: `GITHUB_ACTIONS=true ./copier/test_standard_project.sh llvm-release`.