add images

Signed-off-by: tdruez <tdruez@aboutcode.org>

Author: tdruez

docs/images/tutorial-7-policy-rules/compliance-dashboard.jpg

@@ -1,5 +1,3 @@
-.. _user_tutorial_7_policy_rules:
-
 Tutorial 7 - Managing Policy Violations
 =======================================
 
@@ -19,6 +17,8 @@ Sign into DejaCode.
 
 1. From the main menu, navigate to the :guilabel:`Compliance Dashboard`.
 
+.. image:: images/tutorial-7-policy-rules/compliance-dashboard.jpg
+
 2. The dashboard lists all your products with their compliance metrics. Look at the
    **Policy violations** column to see which products have active violations.
 
@@ -30,6 +30,8 @@ Sign into DejaCode.
 
 The **Policy violations** panel shows the active violations for the product.
 
+.. image:: images/tutorial-7-policy-rules/compliance-tab-policy-violations.jpg
+
 For each triggered rule, the table shows:
 
 - The rule label and severity, color-coded as red (error) or yellow (warning).
@@ -44,14 +46,22 @@ if only warning rules are triggered.
 .. tip::
     Click the info icon next to the panel title to open a modal listing all active
     rules with their current status: **Triggered** or **OK**. This gives you a full
-    picture of your compliance posture at a glance.
+    picture of your overall compliance status at a glance.
+
+.. image:: images/tutorial-7-policy-rules/policy-rules-modal.jpg
+   :width: 400
+   :align: center
 
 3. Drill Into Affected Packages
 -------------------------------
 
 1. In the **Policy violations** table, click the count in the **In violation** column
    for the rule you want to investigate.
 
+.. image:: images/tutorial-7-policy-rules/violation-count-link.jpg
+   :width: 140
+   :align: center
+
 2. The :guilabel:`Inventory` tab opens pre-filtered to show only the packages that
    triggered that rule.
 
@@ -70,8 +80,28 @@ by completing a vulnerability analysis.
 3. For each vulnerability, click :guilabel:`Edit analysis` and set the analysis state
    to a terminal value such as **Resolved** or **Not affected**.
 
+.. image:: images/tutorial-7-policy-rules/vulnerability-analysis-form.jpg
+   :width: 400
+   :align: center
+
 .. seealso::
     Refer to :ref:`how_to_4` for a detailed guide on vulnerability analysis.
 
 Once all vulnerabilities on a package have a terminal analysis, that package is no
 longer counted as a violation for the **Vulnerability Unresolved** rule.
+
+5. Re-evaluate and Confirm
+--------------------------
+
+After correcting the underlying condition, trigger a manual re-evaluation to update
+the violation count immediately rather than waiting for the next automatic run.
+
+1. Return to the :guilabel:`Compliance` tab of the product.
+2. Click the re-evaluate button next to the **Policy violations** panel header.
+
+.. image:: images/tutorial-7-policy-rules/reevaluate-button.jpg
+   :width: 200
+   :align: center
+
+3. The panel refreshes with updated violation counts. Rules whose conditions are no
+   longer met are cleared from the table.