docs(release): rewrite the Artur 2026.08.10 notes for the client

Author: outof-place

docs/releases/artur/2026.08.10.md

@@ -10,29 +10,27 @@ repository: Blazity/ai-workflow
 
 ## Highlights
 
-This release adds new capabilities and includes improvements and fixes.
+Automatic check-fix runs now finish the job. When CI fails on a pull request, the fix agent commits, pushes, and the run goes on to post its comment instead of stopping with a stale-commit error, so you find out on the pull request that a fix landed. The dashboard also gains a health screen that tells you at a glance whether Jira, GitHub, GitLab and single sign-on are actually reachable with the credentials this deployment holds.
 
 ## What's new
 
-- feat(dashboard): add system health diagnostics
+- A System health screen in the dashboard checks the database and every configured integration (Jira, GitHub App, GitLab, single sign-on) and reports each one as reachable or failing, so a misconfigured or expired credential is visible before a run trips over it.
   <!-- sources: 329 -->
 
 ## Improvements and fixes
 
-- fix(worker): let an autofix run publish the head it pushed itself (AIW-310)
-  <!-- sources: 324 -->
-- fix(worker): refuse the no_change_needed exit when PR review feedback is pending
+- An automatic check-fix run now completes on the commit it pushed itself. Previously the run repaired the branch and pushed it, then failed with a stale-commit error at the last two steps, so the pull request ended up fixed and green with nothing said about it and the run marked as failed. Both places that compared commits now accept the run's own push, while a push from anyone else still stops the run.
+  <!-- sources: 324,326 -->
+- When a reviewer has asked for changes on a pull request, the planning agent no longer closes the ticket with "already resolved, no code changes needed". It plans the requested changes, retries once if it refuses, and fails visibly rather than reporting a success nobody asked for.
   <!-- sources: 325 -->
-- fix(worker): comment on the head an autofix run published, not the trigger sha (AIW-310)
-  <!-- sources: 326 -->
 
 ## Do you need to do anything?
 
-No action is required.
+No action is required. The System health screen appears in the dashboard on its own.
 
 ## Known limitations
 
-No known user-facing limitations.
+Pre-PR check commands still do not report which command failed, only that the batch failed, so a red pre-PR gate needs the run log to diagnose.
 <!-- shareable:end -->
 
 ## Exact release scope