Reword the Molecule scenario comments

They were hard-wrapped at 80 characters, broke mid-parenthesis, and spent lines
restating what the code below them does.

Rewrapped at natural boundaries instead, with the narration dropped and only the
reasons, gotchas and surprises kept. Section dividers stay - they delineate long
plays rather than narrate them.

Comments only; no scenario behaviour changes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT

roles/custom/matrix-alertmanager-receiver/molecule/default/converge.yml

@@ -3,11 +3,9 @@
 # SPDX-License-Identifier: AGPL-3.0-or-later
 
 ---
-# The devture base roles carry the variables this role reads
-# (`devture_systemd_docker_base_*`, `devture_playbook_help_*`), the same way
-# they do when the playbook runs. `matrix-base` is deliberately NOT included:
-# it does far more than this role needs, and the two variables it would supply
-# are set directly in molecule.yml instead.
+# The devture base roles carry the variables this role reads, the same way they do when
+# the playbook runs. `matrix-base` is deliberately NOT included: it does far more than this
+# role needs, and the two variables it would supply are set directly in molecule.yml.
 - name: Include roles for matrix-alertmanager-receiver Molecule tests
   hosts: all
   become: true
@@ -26,8 +24,8 @@
       loop_control:
         loop_var: role_name
 
-# The role installs the unit but does not start it - in the playbook that is
-# `systemd_service_manager`'s job - so the scenario starts it here.
+# The role installs the unit but does not start it; in the playbook that is
+# `systemd_service_manager`'s job.
 - name: Ensure matrix-alertmanager-receiver is started
   hosts: all
   become: true