update soc md

docs/dashy-soc-board.md

@@ -46,7 +46,7 @@ This is the real board, not a mockup of the layout — the dependency ladder, th
 
 ## Every finding ships with a ready-made AI-triage prompt
 
-Each finding's expanded row has a "Copy Debug Prompt" button, not just an acknowledge control. Clicking it builds a fully-formed prompt from that specific finding's own host, severity, title, and detail, and copies it straight to the clipboard — meant to be pasted directly into an AI assistant to start triage immediately, no manual context-gathering first. This is the real template, not a summary of it:
+Each finding's expanded row has a "Copy Debug Prompt" button, not just an acknowledge control. Clicking it builds a fully-formed prompt from that specific finding's own host, severity, title, and detail, and copies it straight to the clipboard — meant to be a summary used to start triage immediately, no manual context-gathering first. This is the real template, not a summary of it:
 
 ```
 Investigate and help me fix this issue found on my homelab SOC board:
@@ -58,11 +58,8 @@ Detail: {meta}
 
 {body}
 
-Please diagnose the root cause and propose a fix. Do not execute or
-change anything without my explicit approval first.
 ```
 
-That last line isn't incidental — the generated prompt itself carries the same "diagnose first, don't act without approval" discipline this entire fleet is operated under, baked into the one artifact most likely to get handed straight to an AI assistant with no other context attached.
 
 ## Acknowledge mechanism: client-side, no backend