implement detailed build plan

docs/ahriman.core.formatters.rst

@@ -4,6 +4,14 @@ ahriman.core.formatters package
 Submodules
 ----------
 
+ahriman.core.formatters.build\_plan\_printer module
+----------------------------------------------------
+
+.. automodule:: ahriman.core.formatters.build_plan_printer
+   :members:
+   :no-undoc-members:
+   :show-inheritance:
+
 ahriman.core.formatters.aur\_printer module
 -------------------------------------------
 

docs/ahriman.models.rst

@@ -28,6 +28,14 @@ ahriman.models.auth\_settings module
    :no-undoc-members:
    :show-inheritance:
 
+ahriman.models.build\_plan module
+---------------------------------
+
+.. automodule:: ahriman.models.build_plan
+   :members:
+   :no-undoc-members:
+   :show-inheritance:
+
 ahriman.models.build\_status module
 -----------------------------------
 

docs/faq/general.rst

@@ -274,6 +274,8 @@ In this scenario, the update process must be separated into several stages. Firs
 
    sudo -u ahriman ahriman repo-check
 
+The command prints selected packages in dependency steps, with the old and proposed versions and the reason each package was selected. ``repo-update --dry-run`` uses the same preview. Proposed ``pkgrel`` values follow the ``--increment`` option. The preview describes current metadata; it does not freeze sources or guarantee later build inputs.
+
 During the check process, the service will generate changes from the last known commit and will send it to remote service. In order to verify source files changes, the web interface or special subcommand can be used:
 
 .. code-block:: shell