feat: DevDesk v0.1.0, a persistent browser terminal for Claude Code

ttyd serves a single-file xterm.js UI styled with the LotusGuild TDS
(web_template base.css). Sessions live in a dedicated tmux server unit
(devdesk-tmux.service), so restarting or upgrading the web unit never
stops Claude. Each named session maps to a project directory. A Claude
SessionStart hook records the conversation ID, so after a reboot the
session resumes that exact conversation.

- bin/devdesk: attach / new / ls / end / pick, with an fzf picker
- ttyd requires a credential that NPM injects; origin check enabled
- debian/: dh 13 with --no-stop-on-upgrade for the tmux unit, bundled
  sha256-verified ttyd 1.7.7, lintian overrides, man page
- CI: lint, test, build, smoke-test, artifact; v* tags publish to the
  Gitea apt registry and create a release

Refs: tinker ticket 887531976

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

web/src/widgets.js

@@ -0,0 +1,12 @@
+// Sidebar widgets. In v1 only Sessions is live; Repo/CI and Claude Context get
+// data from devdesk-api in v1.1, Ops Alerts in v2. The "Ask Claude" pattern is
+// already wired: any [data-ask-claude] button types its prompt into the current
+// session without pressing Enter, so you can review it before sending.
+
+export function bindAskClaude(root, send) {
+  root.addEventListener('click', (event) => {
+    const button = event.target.closest('[data-ask-claude]');
+    if (!button || button.disabled) return;
+    send(button.dataset.askClaude);
+  });
+}