chore: file processed eask and signal-cli handoffs to outbox

1 files changed, 15 insertions, 0 deletions

diff --git a/assets/outbox/2026-05-26-1847-from-.emacs.d-archsetup-signal-cli-request.org b/assets/outbox/2026-05-26-1847-from-.emacs.d-archsetup-signal-cli-request.org
new file mode 100644
index 0000000..ad9c903
--- /dev/null
+++ b/assets/outbox/2026-05-26-1847-from-.emacs.d-archsetup-signal-cli-request.org
@@ -0,0 +1,15 @@
+#+TITLE: Add signal-cli to the standard install
+
+Request from the .emacs.d session, 2026-05-26.
+
+* Ask
+Add =signal-cli= (AUR) to the regular package install set, so it's present on every machine archsetup provisions rather than installed by hand per machine.
+
+* Why
+I'm building a Signal client inside Emacs (a fork of the =signel= package) that uses =signal-cli= as its headless engine, driven over JSON-RPC. signal-cli is the runtime dependency that makes the whole feature work, and the Emacs config is the same across all my machines, so the dependency should be too. Without it in the standard install, every fresh machine is a manual =yay -S signal-cli= I'll forget.
+
+* Details for the recipe
+- Package: =signal-cli= (AUR, not in the official repos). Installed here with =yay -S signal-cli=.
+- Runtime: needs a JRE (OpenJDK 17+); already satisfied by the existing =jdk-openjdk= on these machines, but worth noting as a dependency if the install set is ever trimmed.
+- Keep-current caveat: signal-cli must be updated roughly every three months or Signal-Server starts rejecting it (the client-version floor moves). So it belongs in the set that gets regular AUR updates, not pinned and forgotten.
+- Linking is per-machine and interactive (scan a QR from the phone's Linked Devices), so that part stays manual. archsetup only needs to guarantee the binary is present.