Harden Health verification isolation

config/dot/quickshell/modules/settings/README.md

@@ -11,8 +11,10 @@ from the Settings sidebar and its live 54px footer, the degraded-only bar
 indicator, and Vicinae's **Panama: Check System Health** command. Healthy scans
 reserve no bar space and produce no notification.
 
-`services/Health.qml` owns the last accepted redacted snapshot and invokes only
-`scripts/panama-doctor`. For a concise terminal view, run:
+`services/Health.qml` owns the last accepted redacted snapshot. It invokes
+`scripts/panama-doctor` for scans and bounded repairs, `wl-copy` only for an
+explicit **Copy Report**, and bounded `notify-send` only when an external repair
+fails. For a concise terminal view, run:
 
 ```bash
 ~/.config/quickshell/scripts/panama-doctor --summary
@@ -108,11 +110,12 @@ slot**, because that is the row's default property, so only the right-hand edge
 becomes clickable. Use `activatable: true` with `onActivated` for a whole-row
 target.
 
-**A copy of the Quickshell config shares the live shell's ID.** Quickshell
-derives the Shell ID from config *content*, not path, so
-`cp -a config/dot/quickshell $tmp && qs -p $tmp kill` kills the running
-desktop, and `qs -p $tmp ipc call …` can drive it. Harnesses that point at a
-single distinct `.qml` file are safe; copying the whole directory is not.
+**A content-identical Quickshell entry can share the live shell's ID.**
+Quickshell derives the Shell ID from config *content*, not path. Runtime
+harnesses therefore create a distinct semantic entry file, address that exact
+file with `qs -p`, and discover its PID from the exact Config path in
+`qs list --all`. They terminate only that recorded PID with `kill`; never use
+`qs kill` from a copied configuration.
 
 ## Where state lives