feat(ui): name the operation in completing-read prompts

A picker prompt is the last thing shown before a command commits, so a bare noun leaves a mis-keyed command ambiguous. Hitting C-f8 (project agenda) instead of C-f9 (AI-vterm picker) gave the same "Project:" prompt with no signal which one was about to run.

Reworded 17 prompts across 8 modules so each names the operation rather than just the thing being chosen: "Project:" becomes "Show agenda for project:", "F6:" becomes "Run tests:", the dwim-shell sub-prompts gain their context (checksum algorithm, PDF compression quality, text-to-speech voice, run dwim-shell command), the two contact pickers split into "Find contact:" and "Insert contact email:", and the dirvish ediff, org finalize, and custom-comments length/box-style prompts get the same treatment.

I audited all ~124 completing-read / read-* call sites; the rest already named their operation and were left alone. These are prompt-string changes only, no logic touched.

1 files changed, 1 insertions, 1 deletions

diff --git a/modules/dirvish-config.el b/modules/dirvish-config.el
index 9e50bbc0..d9286966 100644
--- a/modules/dirvish-config.el
+++ b/modules/dirvish-config.el
@@ -78,7 +78,7 @@ Pure helper used by `cj/dired-ediff-files'."
          (pair (cj/--ediff-pair-from-files
                 (dired-get-marked-files)
                 (lambda ()
-                  (read-file-name "file: " (dired-dwim-target-directory)))
+                  (read-file-name "Ediff with file: " (dired-dwim-target-directory)))
                 #'file-newer-than-file-p)))
     (ediff-files (car pair) (cdr pair))
     (add-hook 'ediff-after-quit-hook-internal