Explain flagged schedule changes in the existing help

docs/change-assurance.html

@@ -102,7 +102,7 @@ <h3>Follow one complete review.</h3>
           <div><h2 id="methodTitle">Clear evidence. Clear limits.</h2><p>ProjectLens compares the fields in your exports. A person interprets them and makes the decision.</p><a href="method.md">Read the method</a></div>
           <div class="product-questions">
             <details><summary>Do my schedule files leave this browser?</summary><p>The standard review reads your files locally. Saving a draft or decision stores it on this device. Downloads give you a copy to keep or share. Optional public-record research is separately configured and receives narrative text, never XER files.</p></details>
-            <details><summary>Does a flagged change mean the project is delayed?</summary><p>A later scheduled finish is an observed difference between exports. These checks do not recalculate the critical path or establish cause, contractual entitlement or the right decision.</p></details>
+            <details><summary>Does a flagged change mean the project is delayed?</summary><p>A flagged change is a difference that needs review. Check its source and ask the owner to explain it. A later finish does not by itself prove why a project is late or who is responsible. These checks do not recalculate the critical path (the tasks that determine the finish), decide contractual rights or approve the change.</p></details>
             <details><summary>What can I compare?</summary><p>Two supported, single-project Primavera P6 XER exports from the same source project. ProjectLens checks their identity, dates and field coverage before comparing them. Missing fields and unsupported inputs are reported.</p></details>
           </div>
         </section>