feat(friend): Workflows opens from the sidebar footer

The only way into Workflows was a row inside the Bots block, which shows only
in the "sections" sidebar layout and only while expanded. The default layout is
"rail", and a bots host with no bots had no entry at all. Workflows now has a
footer item next to Kanban, shown whenever a bots host is connected, and the
Bots block row is gone. FORK.md and the design doc point to the new place.

Found in the integrated real-app pass; checked headlessly over CDP against a
dev server of this branch: footer entry, one-press save, run with its gate,
dark reload of the run page.

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

Author: IsraelAraujo70

FORK.md

@@ -365,8 +365,8 @@ run view or by direct link.
 
 ## Using workflows
 
-Open Workflows from the Bots block of the sidebar (web and desktop) or from the Workflows row of the
-Android Bots tab. It lists the bots host's workflows with their last run.
+Open Workflows from the sidebar footer, next to Kanban (web and desktop), or from the Workflows row
+of the Android Bots tab. It lists the bots host's workflows with their last run.
 
 - **Create one.** "From template" copies a ready routine under a new name; "New workflow" starts
   blank. A new workflow starts turned off.

apps/web/src/bots/BotsSidebarSection.tsx

@@ -24,11 +24,10 @@ import {
 } from "@t3tools/contracts";
 import { useNavigate } from "@tanstack/react-router";
 import { Schema } from "effect";
-import { ChevronRightIcon, PlusIcon, WorkflowIcon } from "lucide-react";
+import { ChevronRightIcon, PlusIcon } from "lucide-react";
 import { useState, type ReactNode } from "react";
 
 import { CollapsibleSectionHeader } from "../components/ui/collapsible-section-header";
-import { useSidebar } from "../components/ui/sidebar";
 import { useLocalStorage } from "../hooks/useLocalStorage";
 import { useNowMinute } from "../hooks/useNowMinute";
 import { useThreadActions } from "../hooks/useThreadActions";
@@ -727,33 +726,10 @@ export function BotsSidebarSection(props: {
           ) : null}
         </DndContext>
       )}
-      {expanded && environmentId !== null ? <WorkflowsRow environmentId={environmentId} /> : null}
     </section>
   );
 }
 
-/** Opens the bots host's Workflows, where the workflow step threads live. */
-function WorkflowsRow(props: { environmentId: EnvironmentId }) {
-  const navigate = useNavigate();
-  const { isMobile, setOpenMobile } = useSidebar();
-  return (
-    <button
-      type="button"
-      onClick={() => {
-        if (isMobile) setOpenMobile(false);
-        void navigate({
-          to: "/workflows/$environmentId",
-          params: { environmentId: props.environmentId },
-        });
-      }}
-      className="flex cursor-pointer items-center gap-1.5 px-2 py-1 text-2xs text-sidebar-muted-foreground hover:text-sidebar-foreground"
-    >
-      <WorkflowIcon className="size-3" />
-      Workflows
-    </button>
-  );
-}
-
 /** `bot:<id>`, `section:<id>` or `group:<id>` split into its kind and id. */
 function splitDragId(id: string): readonly [kind: string, id: string] {
   const colon = id.indexOf(":");

apps/web/src/bots/workflows/WorkflowsSidebarItem.tsx

@@ -0,0 +1,31 @@
+import { useNavigate } from "@tanstack/react-router";
+import { WorkflowIcon } from "lucide-react";
+import type { ComponentType, ReactNode } from "react";
+
+import { useSidebar } from "../../components/ui/sidebar";
+import { useBotsEnvironmentId } from "../../state/bots";
+
+/**
+ * The sidebar footer's Workflows button, after Kanban. Like Kanban it shows only while a bots host
+ * is connected, so Workflows is reachable in every sidebar layout and with no bots yet.
+ */
+export function WorkflowsSidebarItem({
+  Item,
+}: {
+  readonly Item: ComponentType<{ icon: ReactNode; label: string; onClick: () => void }>;
+}) {
+  const navigate = useNavigate();
+  const { isMobile, setOpenMobile } = useSidebar();
+  const environmentId = useBotsEnvironmentId();
+  if (environmentId === null) return null;
+  return (
+    <Item
+      icon={<WorkflowIcon />}
+      label="Workflows"
+      onClick={() => {
+        if (isMobile) setOpenMobile(false);
+        void navigate({ to: "/workflows/$environmentId", params: { environmentId } });
+      }}
+    />
+  );
+}

apps/web/src/components/sidebar/SidebarChrome.tsx

@@ -37,9 +37,10 @@ import { isSidebarUtilityPage, useNavigateToMainApp } from "./mainAppLocation";
 import { SidebarThreadUndoNotice } from "./SidebarThreadUndoNotice";
 import { SidebarProviderUpdatePill } from "./SidebarProviderUpdatePill";
 import { SidebarUpdateArchitectureWarning, SidebarUpdatePill } from "./SidebarUpdatePill";
-// Fork (friend): the fork Mac app's self-update notice and the kanban button.
+// Fork (friend): the fork Mac app's self-update notice and the kanban and workflows buttons.
 import { DesktopSelfUpdateNotice } from "../../bots/DesktopSelfUpdateNotice";
 import { KanbanSidebarItem } from "../../bots/kanban/KanbanSidebarItem";
+import { WorkflowsSidebarItem } from "../../bots/workflows/WorkflowsSidebarItem";
 import { PullRequestGlyph } from "~/components/pullRequest/pullRequestIcons";
 import { observeResize } from "~/lib/observeResize";
 
@@ -281,8 +282,9 @@ const SidebarUtilityMenu = memo(function SidebarUtilityMenu() {
               onClick={handlePullRequestsClick}
             />
           ) : null}
-          {/* Fork (friend): the bots host's kanban, next to pull requests. */}
+          {/* Fork (friend): the bots host's kanban and workflows, next to pull requests. */}
           <KanbanSidebarItem Item={SidebarUtilityItem} />
+          <WorkflowsSidebarItem Item={SidebarUtilityItem} />
           <SidebarUtilityItem
             icon={<ChartNoAxesColumnIcon />}
             label="Usage"

docs/friend/workflows-design.md

@@ -2054,7 +2054,7 @@ Nove arquivos do upstream. Oito já são seams hoje (`scripts/friend/seams.ts`;
 | `packages/shared/package.json`                                                 | sim, desde a fatia 1 (contains) | Export `./workflows` para `src/workflows/` (compilador, expressões, `classifyCommand`)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | O AGENTS.md reserva `packages/contracts` para schemas; lógica de runtime compartilhada mora em `packages/shared`, que só expõe subpaths declarados                                                                                                                                                                                        |
 | `evals/mcp-tool-use/run.ts`                                                    | **não, nova** (1)               | Incluir os toolkits do fork no catálogo da eval (`:303`)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | Sem isso, nenhuma ferramenta do fork tem eval, nem as de hoje                                                                                                                                                                                                                                                                             |
 
-Sem mudança em `runtimeLayer.ts`, `ws.ts`, `rpc.ts`, `RpcAuthorization.ts`, `ServerEnvironment.ts`, `GitWorkflowService`, nos adapters de provider, no `ProviderSessionManager` ou no `ThreadLaunchService`. Com os passos no host, saíram as mudanças que só existiam pelo container: o 403 do MCP para threads `wf:` no `McpHttpServer.ts:239`, o `isWorkflowLauncher` e as instâncias de workflow. O spread de `BOTS_RPCS`, os spreads de escopo e a capability `bots` já levam tudo. A entrada na barra lateral do web fica no `BotsSidebarSection`, que é do fork. Prefixos do fork em `FORK_OWNED_PREFIXES`: `packages/contracts/src/workflows.`, `packages/shared/src/workflows/` e `docs/friend/` (da fatia 1); `packages/client-runtime/src/workflows.` e `apps/web/src/routes/_chat.workflows` entram com as fatias 9 e 10.
+Sem mudança em `runtimeLayer.ts`, `ws.ts`, `rpc.ts`, `RpcAuthorization.ts`, `ServerEnvironment.ts`, `GitWorkflowService`, nos adapters de provider, no `ProviderSessionManager` ou no `ThreadLaunchService`. Com os passos no host, saíram as mudanças que só existiam pelo container: o 403 do MCP para threads `wf:` no `McpHttpServer.ts:239`, o `isWorkflowLauncher` e as instâncias de workflow. O spread de `BOTS_RPCS`, os spreads de escopo e a capability `bots` já levam tudo. A entrada na barra lateral do web fica no rodapé, ao lado do Kanban (`WorkflowsSidebarItem`, do fork, pela seam já existente em `SidebarChrome.tsx`), para aparecer em todo layout e sem nenhum bot. Prefixos do fork em `FORK_OWNED_PREFIXES`: `packages/contracts/src/workflows.`, `packages/shared/src/workflows/` e `docs/friend/` (da fatia 1); `packages/client-runtime/src/workflows.` e `apps/web/src/routes/_chat.workflows` entram com as fatias 9 e 10.
 
 ---
 

scripts/friend/seams.ts

@@ -518,7 +518,7 @@ export const SEAMS: readonly Seam[] = [
   {
     file: "apps/web/src/components/sidebar/SidebarChrome.tsx",
     markers: 3,
-    why: "the Mac app's self-update notice and the kanban button in the sidebar footer",
+    why: "the Mac app's self-update notice and the kanban and workflows buttons in the sidebar footer",
   },
   {
     file: "apps/web/src/components/sidebar/mainAppLocation.ts",