[STYLE] Fixed more style as per review (- WIP PR #415 -)

* these changes are related to GHI #367

Changes in file .coderabbit.yaml:
 * related work (added missing commas)
 * no functional change

Changes in file .github/AI_USAGE_POLICY.md:
 * style fixes
 * added missing commas

Changes in file multicast/__init__.py:
 * related work (added missing commas)

Changes in file multicast/__main__.py:
 * related work (added missing commas)

Author: reactive-firewall

.coderabbit.yaml

@@ -26,7 +26,7 @@ reviews:
       [Pure BASH Bible](https://github.com/dylanaraps/pure-bash-bible) standards.
     - Consider [CEP-5](https://gist.github.com/reactive-firewall/3d2bd3cf37f87974df6f7bee31a05a89)
       custom locking conventions.
-    - Verify all **BASH** files (e.g. are of MIME-type 'text/x-shellscript') start with an
+    - Verify all **BASH** files (e.g., are of MIME-type 'text/x-shellscript') start with an
       [extensive disclaimer](https://gist.github.com/reactive-firewall/866b42d175ae3ebefcb2a5878b30ea17).
 
     # Documentation Review Instructions
@@ -41,7 +41,7 @@ reviews:
     # Test Code Review Instructions
     - Ensure that test code is automated, comprehensive, and follows testing best practices.
     - Verify that all critical functionality is covered by tests.
-    - Verify that minimal acceptance tests (e.g. those run by the workflow CI-MATs) are passing and
+    - Verify that minimal acceptance tests (e.g., those run by the workflow CI-MATs) are passing and
       error free, pointing out any failure as below minimal acceptance (i.e. un-acceptable).
     - Ensure that the test coverage meets or exceeds the project's required threshold
       (e.g., aiming for 100% coverage as per Issue #53).
@@ -56,7 +56,7 @@ reviews:
       a BSD License, the Unlicence, the Apache v2 License, or that the dependency is optional. Do
       not assume a dependency is optional, confirm if it is or is not optional.
     - For **Python** code, consider [PEP 290](https://peps.python.org/pep-0290/) whenever a python
-      (e.g. has the extension '.py') file is changed.
+      (e.g., has the extension '.py') file is changed.
   request_changes_workflow: true
   high_level_summary: true
   high_level_summary_placeholder: '@coderabbitai summary'
@@ -167,7 +167,7 @@ reviews:
         4. Consider these 'requirements.txt' files the records of truth regarding project
            dependencies.
         5. Consider the 'requirements.txt' file in the base of the git repository
-           (e.g. './requirements.txt') the required python dependencies regarding Multicast project
+           (e.g., './requirements.txt') the required python dependencies regarding Multicast project
            dependencies.
     - path: tests/requirements.txt
       instructions: >-
@@ -192,7 +192,7 @@ reviews:
         1. Consider the files in the `docs/` directory tree the core/main/in-depth documentation
            of the project. Also consider the 'docs/**.md' files the second place to look for
            project documentation after the 'README.md' file.
-        2. When reviewing the documentation files (e.g. `docs/**.md`), they should additionally
+        2. When reviewing the documentation files (e.g., `docs/**.md`), they should additionally
            be linted with help from the tool `markdownlint`, pointing out any issues.
         3. When reviewing the documentation files in `docs/` directory, they should additionally
            be linted with help from the tool `languagetool`, pointing out any issues.

.github/AI_USAGE_POLICY.md

@@ -55,6 +55,7 @@ integrity.
     project content in future reviews.
 * 3.1.C Very Large PRs
   * For PRs exceeding 99 changed files, at least two human reviews are recommended.
+
 > [!NOTE]
 > Currently there is only one core maintainer. Hoping to change this.
 
@@ -88,11 +89,12 @@ integrity.
 * 4.1.A Review Line-by-Line
   * Absolutely, NO "Vibe-coding" is acceptable for this project. ALL AI-suggestions MUST be
     understood by at least one core maintainer (same as all other reviewed code needs to be).
+
 > [!TIP]
 > > Good code is its own best documentation. As you're about to add a comment, ask yourself,
 > > "How can I improve the code so that this comment isn't needed?" Improve the code and then
 > > document it to make it even clearer.
-> - Steve McConnell
+> ~ Steve McConnell
 
   * All AI-suggested code changes must be verified by a human maintainer (see 3.1.B).
 * 4.1.B Signed Commits
@@ -114,7 +116,7 @@ integrity.
   * The project implements a dual-approval system to help prevent single points of failure.
   * AI approvals are tracked separately from human approvals in the review process. Humans
     must be responsible for the actual merge of pull-requests.
-  * Every user (e.g. AI, or human) must have a distinct code-signing identity (see 4.1.B).
+  * Every user (e.g., AI, or human) must have a distinct code-signing identity (see 4.1.B).
   * Only human controlled identities may merge branches, or commit to the default branch directly.
 
 ## 5. Implementation and Compliance

multicast/__init__.py

@@ -464,7 +464,7 @@
 
 	> [!IMPORTANT]
 	> Multicast is not actually port-aware, and port filtering is instead
-	> handled at the protocol layer (e.g. UDP) instead, and may not behave
+	> handled at the protocol layer (e.g., UDP) instead, and may not behave
 	> as expected for some real-world setups.
 
 	Minimal Testing:

multicast/__main__.py

@@ -651,7 +651,7 @@ def main(*argv) -> tuple:
 
 	The main(*args) function in multicast is expected to return a POSIX compatible exit code and
 	optional detail message. Regardless of errors the result as an 'exit code' (int) is returned,
-	even if the optional details are not (e.g. `tuple(int(exit_code), None)`).
+	even if the optional details are not (e.g., `tuple(int(exit_code), None)`).
 	The only exception is when the error results in exiting the process, which will exit the
 	python runtime with the underlying return codes, instead of returning directly to the then
 	unreachable caller. See `multicast.exceptions.exit_on_exception` for the mechanisms involved.