fix: add npm publishing, relay update command, and fix dist path for global install

- Publish as `relayd` on npm; remove private flag; add files/engines fields
- Move React deps to devDependencies (bundled by Vite, not needed at runtime)
- Fix distDir to resolve from import.meta.dir so dashboard loads when installed globally
- Read VERSION from package.json at runtime (semantic-release owns the bump)
- Add `relay update` — checks npm registry, self-updates via bun/npm
- Silent version check on `relay start` with one-line notice if behind
- Add semantic-release config (.releaserc.json) and GitHub Actions release workflow
- Update README with bunx/npm install instructions
- Update roadmap and todo with distribution, releases, multi-dir, X.com launch

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: adriandmitroca

.github/workflows/release.yml

@@ -0,0 +1,36 @@
+name: Release
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: oven-sh/setup-bun@v2
+        with:
+          bun-version: latest
+
+      - name: Install dependencies
+        run: bun install
+
+      - name: Build dashboard
+        run: bun run build
+
+      - name: Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: bunx semantic-release

.releaserc.json

@@ -0,0 +1,14 @@
+{
+  "branches": ["main"],
+  "plugins": [
+    "@semantic-release/commit-analyzer",
+    "@semantic-release/release-notes-generator",
+    ["@semantic-release/changelog", { "changelogFile": "CHANGELOG.md" }],
+    "@semantic-release/npm",
+    ["@semantic-release/git", {
+      "assets": ["CHANGELOG.md", "package.json"],
+      "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
+    }],
+    "@semantic-release/github"
+  ]
+}

CLAUDE.md

@@ -66,7 +66,7 @@ Projects are grouped into **workspaces** (one per client/org). Each workspace op
 
 | Module | Purpose |
 |--------|---------|
-| `src/cli.ts` | CLI entrypoint — `start`, `stop`, `version`, `help`. Flags: `--config`, `--log-level` |
+| `src/cli.ts` | CLI entrypoint — `start`, `stop`, `update`, `version`, `help`. Flags: `--config`, `--log-level`. Version read from `package.json` at runtime. `update` checks npm registry and self-updates via `bun install -g relayd` |
 | `src/constants.ts` | Shared constants: `FAILURE_HINTS`, `CallbackAction`, `CallbackData` — used by telegram, dashboard, and daemon |
 | `src/dashboard.ts` | `DashboardServer` — Hono + `Bun.serve()` at `localhost:7842`, serves React dashboard from `dist/`, WebSocket `/ws` for live updates, SPA fallback |
 | `src/api/router.ts` | Hono app combining all API routes |

README.md

@@ -72,12 +72,16 @@ Optional Telegram integration with forum topics — each task gets its own threa
 - [Claude Code](https://docs.anthropic.com/en/docs/claude-code) CLI (`claude` in PATH)
 - [GitHub CLI](https://cli.github.com) (`gh auth login` completed)
 
-### Install and run
+### Install
 
 ```sh
-bun install
-bun run build
-relay start
+# Try without installing
+bunx relayd
+
+# Install globally
+bun install -g relayd
+# or
+npm install -g relayd
 ```
 
 Your browser opens to `localhost:7842/setup`. Connect your integrations, point Relay at a project, and you're live.
@@ -94,6 +98,7 @@ bash scripts/uninstall-service.sh      # stop and remove
 ```
 relay start     Start the daemon (opens dashboard)
 relay stop      Stop the daemon
+relay update    Update to the latest version
 relay version   Show version
 ```
 

ROADMAP.md

@@ -273,17 +273,34 @@ When a reviewer comments on an Relay PR, feed those comments back to Claude to a
 
 Do this when Phase 1+2 are solid. Goal: someone can find Relay, install it, and have it running in under 10 minutes.
 
-### 3.1 Installation
+### 3.1 Distribution
 
-- `npm install -g relay` or `bunx relay init`
-- `brew install adriandmitroca/tap/relay` (Homebrew formula)
-- Single binary via `bun build --compile` — no Bun runtime required on the user's machine
+Multiple install paths to minimise friction:
 
-### 3.2 Linux + Docker Support
+- `bunx relay` — zero-install try without committing to a global install
+- `bun build --compile` — single self-contained binary, no Bun runtime required
+- `brew install adriandmitroca/tap/relay` — Homebrew formula for macOS
+- `docker-compose.yml` — containerised deployment (mounts repo dirs as volumes)
+- systemd unit file for Linux (parallel to the existing macOS LaunchAgent script)
 
-- Replace `scripts/install-service.sh` (macOS LaunchAgent) with a systemd unit file for Linux
-- Add `docker-compose.yml` for containerised deployment
-- Remove any macOS-specific path assumptions
+### 3.2 Multi-Directory Projects
+
+Many real projects are monorepos or have separate repos per layer (e.g., `api/` in one repo, `frontend/` in another). Support this in project config:
+
+```json
+{
+  "key": "acme-web",
+  "dirs": [
+    { "path": "/Users/dev/acme/api", "baseBranch": "main" },
+    { "path": "/Users/dev/acme/frontend", "baseBranch": "main" }
+  ]
+}
+```
+
+- Claude gets context from all configured directories
+- Triage and fix run with access to the full multi-dir scope
+- Commits and PRs go to the correct repo per changed file
+- Worktrees created per repo that has changes
 
 ### 3.3 Better Onboarding
 
@@ -302,6 +319,38 @@ Allow sources and notification channels to be added without modifying core:
 
 Telegram is niche — Slack is where most dev teams operate. Implement as the second notification channel (and first plugin) to validate the plugin architecture.
 
+### 3.6 Releases & Updates
+
+**Release automation:**
+- Conventional commits → semantic-release on every merge to `main`
+- Auto-bumps version in `package.json`, generates `CHANGELOG.md`, creates GitHub Release with release notes
+- CI attaches compiled binaries to the GitHub Release as assets (macOS arm64, macOS x64, Linux x64)
+- Homebrew formula auto-updated via a `homebrew-tap` repo triggered by the release
+
+**Update handling per distribution path:**
+
+| Method | How updates work |
+|--------|-----------------|
+| `bunx relay` | Always pulls latest — no action needed |
+| Binary | `relay update` checks GitHub Releases API, downloads new binary, replaces itself |
+| Homebrew | `brew upgrade relay` — formula points to latest release tarball |
+| Docker | User pulls new image tag; `latest` tag always points to newest release |
+| npm global | `npm install -g relay@latest` |
+
+**`relay update` command:**
+- Checks `https://api.github.com/repos/adriandmitroca/relay/releases/latest` against current version
+- If newer: downloads the appropriate binary for the current platform, verifies checksum, replaces the running binary
+- If already latest: prints current version and exits
+- On start: silent background check, prints one-line notice if a new version is available ("Relay v1.2.0 is available — run `relay update`")
+
+### 3.7 X.com Launch Announcement
+
+Public launch post positioning Relay as an autonomous dev agent, not just a bug-fixer:
+- Lead with the demo (GIF of dashboard + Telegram callback → merged PR)
+- Core message: "your issues, automatically triaged, fixed, and PR'd — you just review"
+- Cover: sources (Sentry, Asana, Linear, Jira), full web dashboard, optional Telegram
+- Thread format: hook → demo → how it works → how to install → what's next
+
 ---
 
 ## Open Questions

TODO.md

@@ -13,17 +13,16 @@ See `ROADMAP.md` for full context and rationale behind each item.
 
 ---
 
-## Phase 1.5 — Web UI as Primary Interface
-
-- [ ] **Make Telegram optional** — remove hard requirement for `telegram.botToken` and `telegram.chatId` in config validation; guard all Telegram calls behind `if (telegram)` checks in daemon; run dashboard by default without any notification connector
-- [ ] **Web UI action buttons** — add Start Fix / Skip / Accept / Discard / Retry buttons to issue detail view; wire them to new REST endpoints (`POST /api/issues/:id/actions`) that call the same callback handler as Telegram
-- [ ] **Web UI streaming progress** — push `tool_use` events over WebSocket during triage/fix; show live tool name, call count, elapsed time, and running cost in issue detail
-- [ ] **Web UI triage result view** — display verdict, confidence score, plan, and estimated scope inline; Start Fix / Skip buttons below the plan
-- [ ] **Web UI approval view** — show fix summary, diff viewer with syntax highlighting, cost/token stats; Accept / Discard buttons
-- [ ] **Web UI failure view** — show failure reason with human-readable hint (reuse `FAILURE_HINTS`), Retry button
-- [ ] **Integrations status page** — new `/api/config/status` endpoint returning connected sources per workspace (Sentry, Asana, Telegram) with health/auth status; render as a settings/integrations panel in the dashboard
-- [ ] **Toast notifications** — browser `Notification` API for status transitions (issue picked up, triage done, fix ready for approval, failed); opt-in via dashboard settings
-- [ ] **Keep existing debugging** — preserve `relay logs`, `relay show`, CLI `--follow`/`--pretty` flags; web UI log viewer is additive, not a replacement
+## Phase 1.5 — Web UI as Primary Interface ✅
+
+- [x] **Make Telegram optional** — `WorkspaceConfig.telegram` is optional; all Telegram calls guarded behind `ws.telegram?`
+- [x] **Web UI action buttons** — Start Fix / Skip / Accept / Discard / Retry; `POST /api/issues/:id/action`; shared `executeAction()` handler used by both Telegram and REST
+- [x] **Web UI streaming progress** — `stream_progress` WS events; live tool name, call count, elapsed time, cost in issue detail
+- [x] **Web UI triage result view** — verdict, confidence, plan, Start Fix / Skip buttons
+- [x] **Web UI approval view** — diff viewer, cost/token stats, Accept / Discard buttons
+- [x] **Web UI failure view** — failure reason badge, human-readable hint from `FAILURE_HINTS`, Retry button
+- [x] **Integrations / settings pages** — workspaces, projects, notifications, setup wizard (5-step)
+- [x] **Preserve CLI debugging** — `relay logs`, `relay show`, `--follow`/`--pretty` flags intact
 
 ---
 
@@ -37,11 +36,13 @@ See `ROADMAP.md` for full context and rationale behind each item.
 
 ## Phase 3 — Open Source Readiness
 
-- [ ] **Single binary / easy install** — `bun build --compile` for a self-contained binary; Homebrew formula; `bunx relay` fallback
-- [ ] **Linux + Docker support** — systemd unit file; `docker-compose.yml`; remove macOS-only assumptions
+- [ ] **Distribution** — `bunx relay` (zero-install try); `bun build --compile` single binary; Homebrew tap; `docker-compose.yml` for containerised setups; systemd unit for Linux
+- [ ] **Releases & updates** — semantic-release on merge to `main`; CI builds and attaches binaries to GitHub Releases; `relay update` self-update command; version check on daemon start; Homebrew formula auto-updated from release
+- [ ] **Multi-directory projects** — single project config can point to multiple directories (e.g., `api/`, `frontend/`); Claude gets context from all dirs; commits and PRs go to the right repo
 - [ ] **`relay doctor` command** — validate entire setup (Bun, claude CLI, gh auth, config, bot token, repo paths) and report what's broken with fix instructions
 - [ ] **Plugin architecture** — sources and notification channels as pluggable npm packages; validate with a reference implementation
 - [ ] **Slack notification channel** — implement as first plugin; validates the plugin architecture works end-to-end
+- [ ] **X.com launch announcement** — write and publish announcement thread positioning Relay as autonomous dev agent; include demo GIF or screenshot of dashboard + Telegram in action
 
 ---
 
@@ -53,4 +54,5 @@ Ideas worth revisiting later, not prioritised now.
 - Auto-accept for high-confidence small diffs (opt-in)
 - Issue batching (multiple errors → one fix)
 - Scheduled batch runs (overnight mode)
-- New source integrations (Linear, GitHub Issues, Jira)
+- New source integrations (GitHub Issues)
+- Browser toast notifications via `Notification` API