Merge pull request #210 from 777genius/dev

dev -> main

Author: 777genius

.github/workflows/dependency-review.yml

@@ -3,10 +3,10 @@ name: Dependency Review
 on:
   pull_request:
     paths:
-      - "**/package.json"
-      - "**/package-lock.json"
-      - "**/pnpm-lock.yaml"
-      - "pnpm-workspace.yaml"
+      - '**/package.json'
+      - '**/package-lock.json'
+      - '**/pnpm-lock.yaml'
+      - 'pnpm-workspace.yaml'
 
 permissions:
   contents: read
@@ -24,5 +24,7 @@ jobs:
         with:
           fail-on-severity: high
           fail-on-scopes: runtime, development, unknown
+          # Vitest is used via `vitest run`, not Vitest UI/API/browser mode.
+          allow-ghsas: GHSA-5xrq-8626-4rwp
           license-check: false
           show-patched-versions: true

docs/articles/agent-teams-opus-4-8.en.md

@@ -0,0 +1,46 @@
+# Agent Teams with Claude Opus 4.8
+
+Claude Opus 4.8 made a single agent noticeably stronger. But the real productivity jump comes when this model powers **a whole team of agents** that talk to each other, coordinate, and autonomously carry a task through to the result.
+
+Here's what that looks like in practice.
+
+## A team of agents instead of just one
+
+You assemble a team of several Opus 4.8 agents and assign roles: lead, backend, frontend, reviewer — whatever fits your task. From there they work in parallel, each in their own area.
+
+If you're not ready for a full team yet, there's a solo mode with a single agent that manages its own task list. You can grow it into a full team later.
+
+## They talk and coordinate
+
+This isn't a bunch of independent chats. The agents:
+- message each other inside the team
+- hand off results and ask each other for clarification
+- code-review each other's work
+- create and close tasks on a shared kanban board on their own
+
+And here's something you usually don't see anywhere else: **you can run multiple teams at once, and they coordinate between themselves**. Spin up parallel teams for different tracks (say, backend and frontend, or two features at once) — their leads will talk to each other, sync progress, and pass results down the chain.
+
+You set the goal at a high level — breakdown, distribution, and execution happen without you.
+
+## Everything is visible in the UI
+
+In real time:
+- **Kanban** with tasks moving across statuses
+- **Diff viewer** for every task: accept / reject / comment
+- **Agent-to-agent chat** plus direct messages with any of them
+- **Detailed logs** for every agent — what it did, which commands it ran, which decisions it made
+- **Per-task view**: open a card on the kanban and see everything tied to it — code changes, agent conversations, comments, logs. No confusion about what belongs where
+- **Active agent sessions** with open links
+- **Notifications** when the team is done or needs your input
+
+## Not just Claude
+
+Beyond Opus 4.8, you can plug **Codex** and **OpenCode** agents into the same team _(200+ models, 70+ LLM providers)_. Different runtimes coexist within a single team — pick the strengths of each where they fit best, without locking yourself into one vendor.
+
+## Under the hood
+
+Local, no cloud, free, open source. It works through the Claude / Codex / OpenCode CLIs you already have installed — no separate app-level API keys required.
+
+---
+
+> Screenshots and video below.

docs/articles/agent-teams-opus-4-8.ru.md

@@ -0,0 +1,46 @@
+# Agent Teams with Claude Opus 4.8
+
+С выходом Claude Opus 4.8 одиночный агент стал заметно сильнее. Но настоящий скачок продуктивности — когда на этой модели работает **целая команда агентов**, которые общаются между собой, координируются и автономно доводят задачу до результата.
+
+Ниже — как это выглядит на практике.
+
+## Команда агентов вместо одного
+
+Вы собираете команду из нескольких Opus 4.8-агентов и распределяете роли: лид, бэкенд, фронтенд, ревьюер — что угодно под вашу задачу. Дальше они работают параллельно, каждый в своей зоне.
+
+Если не хочется сразу команду — есть solo-режим с одним агентом, который сам ведёт свои задачи. Дальше его можно развернуть в полноценную команду.
+
+## Они общаются и координируются
+
+Это не несколько независимых чатов. Агенты:
+- пишут друг другу внутри команды
+- передают результаты, спрашивают уточнения
+- делают код-ревью работы коллег
+- сами создают и закрывают задачи на общем канбане
+
+И ещё одна штука, которой обычно нет нигде: **команд может быть несколько, и они координируются между собой**. Можно поднять параллельно несколько команд под разные направления (например, бэкенд и фронтенд, или две фичи сразу) — и их лиды будут общаться друг с другом, синхронизировать работу, передавать результаты по цепочке.
+
+Вы ставите цель на высоком уровне — декомпозиция, распределение и исполнение происходят без вашего участия.
+
+## Всё видно в UI
+
+В реальном времени:
+- **Канбан** с движением задач по статусам
+- **Diff-вьювер** на каждую задачу: accept / reject / комментарий
+- **Переписка** агентов между собой и личные DM с любым из них
+- **Подробные логи** каждого агента — что он делал, какие команды запускал, какие решения принимал
+- **Срез по задаче**: открываете карточку на канбане и видите всё, что к ней относится — изменения в коде, переписку агентов, комментарии, логи. Никакой путаницы, что к чему привязано
+- **Активные сессии агентов** с открытыми ссылками
+- **Уведомления**, когда команда закончила или ей нужно ваше решение
+
+## Не только Claude
+
+Помимо Opus 4.8, в команду можно подключать агентов на **Codex** и **OpenCode** _(200+ моделей, 70+ LLM-провайдеров)_. В одной команде спокойно уживаются разные рантаймы — берёте сильные стороны каждого там, где они уместны, без привязки к одному вендору.
+
+## Под капотом
+
+Локально, без облака, бесплатно, open source. Работает через уже установленные у вас CLI Claude / Codex / OpenCode — отдельные API-ключи на уровне приложения не нужны.
+
+---
+
+> Скриншоты и видео — ниже.

docs/team-management/opencode-native-semantic-messaging-plan.md

@@ -1827,9 +1827,9 @@ OpenCode lead rule:
 
 - Mixed team with native Codex/Claude/Gemini lead: keep the existing `relayLeadInboxMessages()` path.
 - OpenCode teammate or secondary lane: use `relayOpenCodeMemberInboxMessages()`.
-- Pure OpenCode lead inbox in v1: do not mark messages read and do not report delivery success unless a real stored OpenCode `team-lead` session exists. Return a diagnostic like `opencode_lead_runtime_session_missing`.
+- Pure OpenCode lead inbox: launch and store a real OpenCode `team-lead` runtime session, then relay through `relayOpenCodeMemberInboxMessages()`. Do not mark messages read unless that delivery is accepted.
 - Do not fake lead delivery by sending to a random teammate session. That would make messages appear delivered while the actual recipient never saw them.
-- A future explicit OpenCode lead lane can reuse this selector by teaching the bridge to create/store a `team-lead` session and by passing `agent: "team-lead"` where the bridge supports it. That is not part of this v1 seam.
+- If the stored `team-lead` session is missing, keep the row retryable instead of falling back to another teammate.
 
 FileWatcher change:
 
@@ -2967,13 +2967,12 @@ it('routes native lead inbox relay through the legacy stdin path', async () => {
 ```
 
 ```ts
-it('does not silently consume pure OpenCode lead inbox when no lead session exists', async () => {
-  // Configure a pure OpenCode runtime-adapter team where isTeamAlive() is true via runtimeAdapterRunByTeam.
-  // Ensure there is no stored OpenCode session record for the canonical lead name.
+it('relays pure OpenCode lead inbox through the stored lead session', async () => {
+  // Configure a pure OpenCode runtime-adapter team with a stored team-lead session.
   // Seed inboxes/<lead>.json with one unread message.
   // Call relayInboxFileToLiveRecipient(teamName, leadName).
-  // Assert diagnostics include opencode_lead_runtime_session_missing.
-  // Assert the inbox row remains unread and no teammate session received the prompt.
+  // Assert the relay kind is opencode_member and the prompt targets team-lead.
+  // Assert the inbox row is marked read only after accepted runtime delivery.
 });
 ```
 
@@ -3464,8 +3463,8 @@ Avoid heavy E2E until targeted tests pass.
 - UI direct sends to live OpenCode teammates either confirm runtime delivery or show a visible warning; there is no log-only post-send delivery failure.
 - Persisted inbox messages addressed to OpenCode teammates are live-relayed to their runtime lanes, while native teammates keep file-watch behavior and lead keeps lead relay behavior.
 - OpenCode inbox relay is direct-to-runtime and does not reuse native `relayMemberInboxMessages()` / `SendMessage` forwarding.
-- Pure OpenCode lead inbox delivery is not silently consumed: without a real OpenCode lead session, rows remain unread and diagnostics say `opencode_lead_runtime_session_missing` or equivalent.
+- Pure OpenCode lead inbox delivery uses the stored `team-lead` runtime session and does not silently fall back to another teammate.
 - Renderer send-message actions return `SendMessageResult` on success and reject on real send failure, so pending-reply cleanup is not dependent on dead `.catch()` paths.
 - `message_send` cannot create `from: "user", to: "user"` rows; user-directed MCP replies require a configured teammate sender.
 - OpenCode replies appear in Messages UI without frontend fake state.
-- Tests cover native default, OpenCode override, assignment protocol, tool alias canonicalization, tool proof, taskRefs persistence, user-directed sender guard, local recipient canonicalization, direct-message runtime delivery result visibility, OpenCode reply feed projection, OpenCode-targeted inbox relay/dedupe, unsupported OpenCode lead diagnostics, launch identity injection, lane-scoped manifest activeRunId recovery, and runtime delivery team-change event shape.
+- Tests cover native default, OpenCode override, assignment protocol, tool alias canonicalization, tool proof, taskRefs persistence, user-directed sender guard, local recipient canonicalization, direct-message runtime delivery result visibility, OpenCode reply feed projection, OpenCode-targeted inbox relay/dedupe, pure OpenCode lead relay, launch identity injection, lane-scoped manifest activeRunId recovery, and runtime delivery team-change event shape.

landing/components/hero/CyberHeroFeatureStrip.vue

@@ -20,10 +20,10 @@ const props = defineProps<{
   reducedMotion?: boolean;
 }>();
 
-const { locale } = useI18n();
+const { t, locale } = useI18n();
 const localizedHeroFeatureRail = computed(() => getLocalizedHeroFeatureRail(locale.value));
 const localizedHeroReviewerFeatureCard = computed(() => getLocalizedHeroReviewerFeatureCard(locale.value));
-const statusLabel = computed(() => locale.value === "ru" ? "Статус:" : "Status:");
+const statusLabel = computed(() => t("common.statusLabel"));
 
 const icons = [
   mdiRobotOutline,

landing/components/hero/CyberHeroRobot.vue

@@ -7,12 +7,12 @@ const props = defineProps<{
   activeReceiver?: HeroAgentRole | "video" | null;
 }>();
 
-const { locale } = useI18n();
+const { t } = useI18n();
 const isSender = computed(() => props.activeSender === props.agent.id);
 const isReceiver = computed(() => props.activeReceiver === props.agent.id);
 const imageLoading = computed(() => (props.agent.priority ? "eager" : "lazy"));
 const imageFetchPriority = computed(() => (props.agent.priority ? "high" : "auto"));
-const statusLabel = computed(() => locale.value === "ru" ? "Статус:" : "Status:");
+const statusLabel = computed(() => t("common.statusLabel"));
 
 const rootStyle = computed(() => ({
   "--agent-x": String(props.agent.desktop.x),

landing/components/hero/CyberHeroVideoFrame.vue

@@ -1,19 +1,18 @@
 <script setup lang="ts">
-const { locale } = useI18n();
-const isRu = computed(() => locale.value === "ru");
+const { t } = useI18n();
 </script>
 
 <template>
   <div
     id="hero-demo"
     class="cyber-video-frame"
     role="region"
-    :aria-label="isRu ? 'Смотреть демо Agent Teams' : 'Watch Agent Teams demo'"
+    :aria-label="t('hero.videoFrameLabel')"
   >
     <div class="cyber-video-frame__bezel" aria-hidden="true" />
     <div class="cyber-video-frame__status" aria-hidden="true">
-      <span>{{ isRu ? 'Командная лента' : 'Team command feed' }}</span>
-      <span>{{ isRu ? 'Живое демо' : 'Live demo' }}</span>
+      <span>{{ t('hero.commandFeed') }}</span>
+      <span>{{ t('hero.liveDemo') }}</span>
     </div>
     <div class="cyber-video-frame__content">
       <HeroDemoVideo />

landing/components/sections/DownloadSection.vue

@@ -251,7 +251,7 @@ const releaseDate = computed(() => {
     day: 'numeric',
   });
 });
-const linuxRobotBubble = computed(() => locale.value === 'ru' ? 'Готов начать!' : 'Ready to start!');
+const linuxRobotBubble = computed(() => t('download.readyToStart'));
 
 </script>
 

landing/components/sections/HeroSection.vue

@@ -55,14 +55,10 @@ const supportedProviders = [
   },
 ] as const;
 const supportedProvidersLabel = computed(() => (
-  locale.value === "ru"
-    ? "Поддерживаем AI-провайдеры"
-    : "Supported AI providers"
+  t("hero.supportedProviders")
 ));
 const heroSlogan = computed(() => (
-  locale.value === "ru"
-    ? "Делайте много, почти ничего не делая"
-    : "Get a lot done by doing very little"
+  t("hero.slogan")
 ));
 
 const heroDownloadUrl = computed(() => {
@@ -79,17 +75,13 @@ const docsHref = computed(() => buildDocsHref({
 }));
 const downloadActionSubtitle = computed(() => {
   if (!selectedDownloadAsset.value) {
-    return locale.value === "ru"
-      ? "Для вашей платформы"
-      : "For your platform";
+    return t("hero.platformDefault");
   }
 
   return selectedDownloadAsset.value.actionSubtitle;
 });
 const docsActionSubtitle = computed(() => (
-  locale.value === "ru"
-    ? "Гайды и настройка"
-    : "Guides and setup"
+  t("hero.guidesSetup")
 ));
 
 function clearHeroMessageTimers() {

landing/components/sections/ScreenshotsSection.vue

@@ -27,8 +27,8 @@ const screenshots = computed(() => screenshotData.map((s) => ({
   width: s.width,
   height: s.height,
 })));
-const prevLabel = computed(() => locale.value === 'ru' ? 'Предыдущий' : 'Previous');
-const nextLabel = computed(() => locale.value === 'ru' ? 'Следующий' : 'Next');
+const prevLabel = computed(() => t('common.previous'));
+const nextLabel = computed(() => t('common.next'));
 
 const swiperRef = ref<SwiperContainerElement | null>(null);
 const swiperReady = ref(false);