refactor(signal): retire the in-Emacs signel client to the archive

Agents drive Signal via signal-cli and signal-mcp, so the interactive client earns no keep. I moved signal-config.el and its seven test files to archive/ per the pasture convention, dropped the require from init.el, removed the dashboard's Signal launcher (row sizes now 5 4 3 2, tests updated), and unregistered the C-; M prefix from the running daemon. The ~/code/signel fork repo is untouched. The spec record stays IMPLEMENTED with a retirement history line, and the messenger-unification draft carries a premise-shift note.

1 files changed, 7 insertions, 0 deletions

diff --git a/archive/README.org b/archive/README.org
index bbc30a14..e292065a 100644
--- a/archive/README.org
+++ b/archive/README.org
@@ -46,6 +46,13 @@ Retired files keep their origin directory so a restore is a straight move back:
 - =mu4e-org-contacts-setup.el= — nothing requires it; its featurep gate would
   be nil at init in any case. The live mu4e contacts wiring lives in
   =mu4e-org-contacts-integration.el=.
+- =signal-config.el= — the in-Emacs Signal client (forked signel at
+  =~/code/signel= + signal-cli), retired whole on Craig's call 2026-07-14:
+  agents drive Signal via signal-cli / signal-mcp, so the interactive Emacs
+  client earns no keep. The fork repo itself is untouched. Its seven test
+  files moved to =archive/tests/= with it (=test-signal-config*.el=,
+  =test-signel-*.el=). The spec record is
+  =docs/specs/signal-client-spec.org= (IMPLEMENTED, then retired).
 
 ** archive/custom/