Final polish: improved specificity, impact clarity, and real-world positioning

Author: Sai Shyam

README.md

@@ -211,7 +211,6 @@ A deployment fails mid-sprint. The engineer has three data points — coverage b
 - **Without this tool:** An engineer opens the deployment log, sees a `NullPointerException`, then separately checks coverage (62% — why?), then runs PMD and gets 120 violations with no clear connection to the runtime error. Correlation is manual, slow, and easy to get wrong under release pressure.
 - **With this tool:** One command surfaces that all three issues share a single root cause — a missing `Account` insert in `@TestSetup`. The fix is two lines of code, not three separate investigations.
 - **What Claude identified beyond the raw input:** The input only states `"error": "NullPointerException"` and `"failed_tests": 3`. Nothing in the payload mentions `@TestSetup`, parent records, or the Account relationship. The causal link between the exception and the coverage drop was inferred — not extracted from the data.
-- **Time saved:** The manual correlation step — switching tools, reading outputs, reasoning about signal relationships — is eliminated. The fix list is ready before the editor is opened.
 
 ---
 
@@ -295,11 +294,11 @@ A trigger hitting SOQL limits under load, with two components affected simultane
       "priority": "P0 - Immediate"
     },
     {
-      "action": "Re-run deployment after both fixes — coverage should recover above 75% as suppressed test paths execute",
+      "action": "Run 'sf apex run test --class-names AccountTriggerTest,ContactRollupServiceTest --result-format json' and confirm both classes pass before re-deploying — verify combined coverage is above 75% in the result JSON before triggering the pipeline",
       "priority": "P1 - High"
     },
     {
-      "action": "Run 'sf scanner run --category Performance' — resolve remaining 8 critical PMD violations to prevent recurrence of governor limit failures",
+      "action": "Run 'sf scanner run --category Performance --target force-app/main/default/triggers/AccountTrigger.trigger' — resolve all 8 critical PMD violations in AccountTrigger to prevent governor limit recurrence on the next bulk data load",
       "priority": "P1 - High"
     }
   ]
@@ -312,8 +311,7 @@ Claude connected the `LimitException` to the SOQL-in-loop PMD violations — ide
 
 ## Real-World Applicability
 
-This tool is designed to integrate directly into Salesforce DX workflows and CI/CD pipelines — the input schema maps to the JSON output of `sf project deploy` and `sf scanner run`, so deployment logs and static analysis results can be piped in automatically rather than collected manually.
-Deployment logs and static analysis results are already captured by most pipeline configurations; this tool adds the reasoning layer on top of data teams already have.
+Designed for integration with Salesforce DX and CI/CD pipelines — the input schema maps directly to the JSON output of `sf project deploy` and `sf scanner run`, so real deployment logs can be piped in automatically rather than collected manually.
 Native pipeline integration (GitHub Actions, Jenkins, Copado) is on the roadmap — the current CLI interface is the foundation for that.
 
 ---