@dev.fast/whiteboard 0.2.4 → 0.2.5-preview.20261013.109

package/dist/tutorial-trace-DrBvkaeL.js

@@ -1,43 +0,0 @@
-import { r as TUTORIAL_TRACE_SESSION_ID } from "./review-agent-traces-DNJFYzc8.js";
-//#region ../trace-core/src/tutorial-trace.ts
-function loadTutorialTrace() {
-	return {
-		parserVersion: "1",
-		descriptor: {
-			sessionId: TUTORIAL_TRACE_SESSION_ID,
-			harness: "codex",
-			available: true,
-			source: null,
-			subagents: [],
-			commits: []
-		},
-		traceName: null,
-		cacheStatus: "current",
-		subagents: [],
-		trace: {
-			harness: "codex",
-			title: "Shared agent chat server — illustrative tutorial session",
-			startedAt: null,
-			endedAt: null,
-			activeMs: null,
-			userTurns: 1,
-			toolCalls: 0,
-			events: [
-				{
-					kind: "user",
-					text: "Right now, each Review window manages its own agent chats, so opening the same thread in another window can show stale messages or start a duplicate session. I think we want to have one shared server / source of truth for all agent chats. Can you move session ownership and message history into the server, and have each window subscribe to updates? Closing a window should not end the conversation. Keep the existing chat UI, and make sure reconnecting shows the messages that arrived while the window was closed."
-				},
-				{
-					kind: "assistant",
-					markdown: "I'll make the server own each thread's agent session and message history. Windows will read that history and subscribe to new messages, so opening a thread in two windows attaches both to the same conversation."
-				},
-				{
-					kind: "assistant",
-					markdown: "Closing a window will detach its subscription without stopping the agent session. On reconnect, the window will catch up from the server's stored history before displaying live updates. I'll also check that simultaneous requests to open the same thread cannot create duplicate sessions."
-				}
-			]
-		}
-	};
-}
-//#endregion
-export { loadTutorialTrace };

package/src/tutorial-conversation.ts

@@ -1,18 +0,0 @@
-import { z } from "zod";
-
-export const tutorialAuthoringConversationSchema = z.strictObject({
-  version: z.literal(1),
-  title: z.string().trim().min(1),
-  messages: z
-    .array(
-      z.strictObject({
-        role: z.enum(["user", "assistant"]),
-        body: z.string().trim().min(1),
-      }),
-    )
-    .min(2),
-});
-
-export type TutorialAuthoringConversation = z.infer<
-  typeof tutorialAuthoringConversationSchema
->;

package/tutorial/software-map.json

@@ -1,139 +0,0 @@
-{
-  "people": {},
-  "systems": {
-    "orderService": {
-      "label": "Order service",
-      "description": "Accepts checkout requests, records orders, and completes fulfillment.",
-      "containers": {
-        "api": {
-          "label": "Checkout API",
-          "description": "Provides the typed checkout entry point.",
-          "components": {
-            "checkout": {
-              "label": "Checkout API",
-              "description": "Accepts a checkout request and delegates order creation.",
-              "coverage": {
-                "files": ["src/api/checkout-api.ts"]
-              }
-            }
-          }
-        },
-        "application": {
-          "label": "Order application",
-          "description": "Applies the rules for creating an order.",
-          "components": {
-            "orders": {
-              "label": "Order service",
-              "description": "Calculates the total, reserves stock, charges payment, and creates the order.",
-              "coverage": {
-                "files": [
-                  "src/orders/order-service.ts",
-                  "src/orders/order.ts",
-                  "src/inventory/inventory-service.ts",
-                  "src/payments/payment-gateway.ts"
-                ]
-              }
-            }
-          }
-        },
-        "data": {
-          "label": "Order data",
-          "description": "Stores orders and defines their persisted shape.",
-          "components": {
-            "ordersRepository": {
-              "label": "Orders repository",
-              "description": "Persists orders in memory and submits fulfillment jobs.",
-              "coverage": {
-                "files": ["src/orders/orders-repository.ts"]
-              }
-            },
-            "ordersDatabase": {
-              "label": "Orders table",
-              "description": "Defines the columns in the orders table.",
-              "coverage": {
-                "files": ["src/database/schema.ts"]
-              }
-            }
-          }
-        },
-        "fulfillment": {
-          "label": "Fulfillment",
-          "description": "Queues orders and runs one fulfillment job at a time.",
-          "components": {
-            "queue": {
-              "label": "Fulfillment queue",
-              "description": "Stores order identifiers until a worker can act.",
-              "coverage": {
-                "files": ["src/fulfillment/fulfillment-queue.ts"]
-              }
-            },
-            "worker": {
-              "label": "Fulfillment worker",
-              "description": "Loads a queued order, creates its shipment, and marks it fulfilled.",
-              "coverage": {
-                "files": ["src/fulfillment/fulfillment-worker.ts"]
-              }
-            }
-          }
-        },
-        "shipping": {
-          "label": "Shipping",
-          "description": "Creates shipment tracking records.",
-          "components": {
-            "gateway": {
-              "label": "Shipping gateway",
-              "description": "Creates a shipment for an order.",
-              "coverage": {
-                "files": ["src/shipping/shipping-gateway.ts"]
-              }
-            }
-          }
-        }
-      }
-    }
-  },
-  "relationships": [
-    {
-      "kind": "semantic",
-      "from": "orderService.api.checkout",
-      "to": "orderService.application.orders",
-      "label": "Creates an order"
-    },
-    {
-      "kind": "semantic",
-      "from": "orderService.application.orders",
-      "to": "orderService.data.ordersRepository",
-      "label": "Stores the order"
-    },
-    {
-      "kind": "semantic",
-      "from": "orderService.data.ordersRepository",
-      "to": "orderService.data.ordersDatabase",
-      "label": "Writes an order row"
-    },
-    {
-      "kind": "semantic",
-      "from": "orderService.data.ordersRepository",
-      "to": "orderService.fulfillment.queue",
-      "label": "Enqueues the order"
-    },
-    {
-      "kind": "semantic",
-      "from": "orderService.fulfillment.queue",
-      "to": "orderService.fulfillment.worker",
-      "label": "Dispatches the job"
-    },
-    {
-      "kind": "semantic",
-      "from": "orderService.fulfillment.worker",
-      "to": "orderService.shipping.gateway",
-      "label": "Creates a shipment"
-    },
-    {
-      "kind": "semantic",
-      "from": "orderService.fulfillment.worker",
-      "to": "orderService.data.ordersRepository",
-      "label": "Marks the order fulfilled"
-    }
-  ]
-}

package/tutorial/trace.json

@@ -1,20 +0,0 @@
-{
-  "label": "Shared agent chat server \u2014 illustrative tutorial session",
-  "events": [
-    {
-      "id": "0",
-      "role": "user",
-      "text": "Right now, each Review window manages its own agent chats, so opening the same thread in another window can show stale messages or start a duplicate session. I think we want to have one shared server / source of truth for all agent chats. Can you move session ownership and message history into the server, and have each window subscribe to updates? Closing a window should not end the conversation. Keep the existing chat UI, and make sure reconnecting shows the messages that arrived while the window was closed."
-    },
-    {
-      "id": "1",
-      "role": "assistant",
-      "text": "I'll make the server own each thread's agent session and message history. Windows will read that history and subscribe to new messages, so opening a thread in two windows attaches both to the same conversation."
-    },
-    {
-      "id": "2",
-      "role": "assistant",
-      "text": "Closing a window will detach its subscription without stopping the agent session. On reconnect, the window will catch up from the server's stored history before displaying live updates. I'll also check that simultaneous requests to open the same thread cannot create duplicate sessions."
-    }
-  ]
-}