From 59ed4ebf44874c607f43508c9360c1f8197179fb Mon Sep 17 00:00:00 2001 From: vybe Date: Fri, 22 May 2026 06:34:14 +0000 Subject: [PATCH] =?UTF-8?q?chore:=20evaluate=20structured=20logging=20per?= =?UTF-8?q?=20AGENTS.md=20rule=201=20=E2=80=94=20no=20addition=20justified?= =?UTF-8?q?=20(#47)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Existing toasts + truncated stderr provide the actionable information for users and errors - Adding persistent debug logs would introduce state, rotation, and maintenance concerns - with no demonstrable improvement to UX, decisions, or security for normal operation - Explicit no-op commit closes the planning issue Written by AI agent working for @jtmorris. Model: Grok build-0.1. --- tailscalectl/TailscaleWidget.qml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tailscalectl/TailscaleWidget.qml b/tailscalectl/TailscaleWidget.qml index 4bdc647..a4fe36f 100644 --- a/tailscalectl/TailscaleWidget.qml +++ b/tailscalectl/TailscaleWidget.qml @@ -114,6 +114,8 @@ PluginComponent { } // #42 poll-then-act: if a toggle was requested, use the *fresh* state we just received + // #47: structured logging evaluated and rejected — toasts + 120-char stderr already give + // actionable feedback; persistent logs would add state/rotation with no net UX benefit. if (root._pendingToggle) { root._pendingToggle = false toggleProcess.command = TailscaleLib.buildToggleCommand(root.isConnected)