Connect Runta Crew to Cloud Agents and simplify the desktop UI

.github/workflows/ci.yml

@@ -1,9 +1,11 @@
 name: CI
 
 on:
+  workflow_dispatch:
   pull_request:
   push:
     branches: [main]
+    tags: ["*"]
 
 jobs:
   verify:
@@ -19,6 +21,18 @@ jobs:
       - run: npm run lint
       - run: npm test
       - run: npm run build
+
+  artifact:
+    if: startsWith(github.ref, 'refs/tags/')
+    needs: verify
+    runs-on: macos-15
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 22
+          cache: npm
+      - run: npm ci
       - run: npm run package
       - run: npm run smoke
       - uses: actions/upload-artifact@v4

AGENTS.md

@@ -3,11 +3,11 @@
 - Keep the Electron main process, typed preload bridge, domain model, transports, state orchestration, and renderer UI as separate layers.
 - Renderer code must not import Node.js or Electron. Keep `contextIsolation` and sandbox enabled, and `nodeIntegration` disabled.
 - Never expose generic IPC, filesystem access, shell execution, or decrypted credentials through preload.
-- Do not invent Runta Cloud Agents routes or event framing. Record assumptions in `API_INTEGRATION.md` and require route/transport injection.
-- Mock fixtures belong under `src/clients/mock`, never in React components. Mock computer UI must remain visibly labeled.
+- Keep Runta Cloud Agents routes and event framing aligned with the `runta` Cloud Agents implementation and its end-to-end tests.
+- Do not add product-side mock data or simulated computer surfaces. Tests may use bounded transport doubles, but the application must surface unavailable backend capabilities honestly.
 - Default to the light theme and preserve both theme token sets.
-- Read and follow `DESIGN_SYSTEM.md` for every UI change. Apply its visible-element admission rule and border checklist before adding permanent controls or decoration.
+- Keep every UI change minimal: add only necessary controls or decoration, and justify every visible border.
 - Use strict TypeScript; do not add `any` escapes.
 - Run `npm run typecheck`, `npm run lint`, `npm test`, `npm run build`, and packaging/smoke checks for release-facing changes.
-- Use Conventional Commits. Changes in this `runta-dev` repository must go through a feature branch and pull request.
-- Runta Crew is temporarily not onboarded to Runta Review. Do not trigger, wait for, or treat Runta Review as a merge gate for this repository. GitHub pull requests and the repository CI workflow are the required review/delivery path until this rule is explicitly changed.
+- Use Conventional Commits. Runta Crew is currently in rapid iteration: commit and push directly to the active remote branch. A pull request is not required unless the user explicitly asks for one. Keep branch history linear and never introduce merge commits.
+- Runta Crew is temporarily not onboarded to Runta Review. Do not trigger, wait for, or treat Runta Review as a merge gate for this repository.