Various formatting. Struggle with mdformat :/

Author: nicdumz

docs/model.md

@@ -48,9 +48,9 @@ reasonable redundant replicas, depending on the importance of this data.
 
 If you don't back this up or don't test your recovery story? You lose this information.
 
-In modern systems with many "Cloud Sync" options, you have surprisingly little original data with your
-systems as primary hosts. Aside: it might be worth questioning if you _really_ need or want to be the
-main stakeholder for this data or if a service may do this better for you.
+In modern systems with many "Cloud Sync" options, you have surprisingly little original data with
+your systems as primary hosts. Aside: it might be worth questioning if you _really_ need or want to
+be the main stakeholder for this data or if a service may do this better for you.
 
 Note: in the case of Cloud backed-up data, I consider the local copies of this data "cache" and not
 "data".

docs/requirements.md

@@ -4,23 +4,23 @@ A brief list of requirements so we understand what the solution will look like:
 
 - [Configuration](model.md#configuration) MUST be versioned publicly.
 
-    * Versioned for all the goodness that comes with it (tracking why a particular changes landed,
-      when, in which context.)
-    * I want to be part of an open ecosystem. I want to contribute to the set of configurations that
-      Internet strangers can look up on GitHub and learn from. (`"path:*.nix something"` is a regular
-      GitHub search query of mine when I develop on Nix / NixOS).
+    - Versioned for all the goodness that comes with it (tracking why a  
+      particular changes landed, when, in which context.)
+    - I want to be part of an open ecosystem. I want to contribute to the set   
+      of configurations that Internet strangers can look up on GitHub and learn 
+      from. (`"path:*.nix something"` is a regular GitHub search query of mine 
+      when I develop on Nix / NixOS).
+
 - System deployments or new machine installs MUST be
   [reproducible](https://en.wikipedia.org/wiki/Reproducible_builds) and deterministic.
 
-    * Importantly, if I deploy my system at a given Git revision, I get exactly the same output
-      everytime. This allows for trivial pain-free rollbacks.
+    - Importantly, if I deploy my system at a given Git revision, I get exactly the same output everytime. This allows for trivial pain-free rollbacks.
+
 - Updates (security updates, OS updates, individual software version updates) MUST not break my
   systems.
 
-    * Critical security updates MUST apply at least weekly.
-    * If a new version of a dependency becomes incompatible with my configuration, the `deploy` step
-      SHOULD fail before changing my systems. When this is not feasible, rollbacks to an earlier Git
-      revision MUST be a viable recovery path.
+    - Critical security updates MUST apply at least weekly.
+    - If a new version of a dependency becomes incompatible with my configuration, the `deploy` step SHOULD fail before changing my systems. When this is not feasible, rollbacks to an earlier Git revision MUST be a viable recovery path.
 
 Non-functional:
 

flake.nix

@@ -86,6 +86,8 @@
             ".editorconfig"
             ".envrc"
             "LICENSE"
+            # TODO: fix me
+            "docs/*.md"
           ];
           programs = {
             deadnix.enable = true;
@@ -94,9 +96,7 @@
               enable = true;
               package = channels.nixpkgs.mdformat.withPlugins (
                 p: with p; [
-                  mdformat-gfm
-                  # TODO: broken in 25.05
-                  # mdformat-gfm-alerts
+                  mdformat-mkdocs
                 ]
               );
               settings.wrap = 100;