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/mu4e-org-contacts-integration.el b/modules/mu4e-org-contacts-integration.el
index 68f83dd2..6aed3d4c 100644
--- a/modules/mu4e-org-contacts-integration.el
+++ b/modules/mu4e-org-contacts-integration.el
@@ -92,7 +92,7 @@ This bypasses the completion-at-point system for direct selection."
   (interactive)
   (when (mail-abbrev-in-expansion-header-p)
     (let* ((contacts (cj/get-all-contact-emails))
-           (selected (completing-read "Contact: " contacts nil t)))
+           (selected (completing-read "Insert contact email: " contacts nil t)))
       ;; If we're not at the beginning of a field, check if we need a comma
       (when (and (not (save-excursion
                         (skip-chars-backward " \t")