Extract misfiled code out of packages/folded-runs

apps/hub/package.json

@@ -39,6 +39,7 @@
     "@corbits/presence": "workspace:*",
     "@corbits/routines": "workspace:*",
     "@corbits/run-key-history": "workspace:*",
+    "@corbits/run-scope": "workspace:*",
     "@corbits/sidecar-placement": "workspace:*",
     "@corbits/agent-workflow-authoring": "workspace:*",
     "@corbits/skills": "workspace:*",

apps/hub/src/index.ts

@@ -100,9 +100,9 @@ import type { FinalizedTurnToolCall } from "@corbits/turn-artifacts";
 import { decodedOrNull } from "@corbits/url-path";
 import {
   createCryptoProviderCache,
-  createTopLevelRunRoutes,
   lookupFoldedRunReconnectKey,
 } from "@corbits/folded-runs";
+import { createTopLevelRunRoutes } from "@corbits/run-scope";
 import {
   createInboxRoutes,
   createWorkbenchMailboxDelivery,

docs/local-rip.md

@@ -144,7 +144,7 @@ pick who does the work (`createMyraAgentSelectionStrategy`,
   `POST /api/tenants/:id/planner` (`dispatchPlanner`,
   `packages/tasks-ui/src/api.ts`, mounted by
   `@corbits/task-planner`'s `createPlannerRoutes`). Server-side, Myra's own
-  one-shot run (`runOneShotFoldedPrompt`, `@corbits/folded-runs`) turns
+  one-shot run (`runOneShotFoldedPrompt`, `@corbits/folded-run-one-shot`) turns
   your outcome plus the tenant's real inventory of agents/tools/skills into
   a `TaskSpec` (`packages/task-planner/src/planner-run.ts`), which then
   dispatches exactly like a manually-launched task — a real task row, and
@@ -221,7 +221,7 @@ under it; a run outside your tenant, or that never existed, reads back as
 
 A dispatched task's run is deliberately absent from the Insights landing
 page's own top-level feed (`GET /api/tenants/:id/top-level-runs`,
-`packages/folded-runs/src/scope-routes.ts`) — that feed is scoped to
+`packages/run-scope/src/scope-routes.ts`) — that feed is scoped to
 genuine top-level deployments (workbenches, scheduled routines), and a task
 is folded-run plumbing the same way an invited workbench participant is
 (`launchTask` shares `launchFoldedRun` with `@corbits/chat`'s own invite

docs/revendor-inventory.md

@@ -786,7 +786,7 @@ folded-run-<runId>`), definition loaded from that closure, run grants
    `GET /workflows/<runId>/runs/<runId>/events` stays empty: the folded
    conversational shape is one unbounded step servicing every inbound
    mail, and its per-message bracket is the `message.run.started` AGENT
-   event (`packages/folded-runs/src/agent-events.ts`), not a
+   event (`packages/agent-events/src/agent-events.ts`), not a
    workflow-host `RunStarted` in the run's durable event log. The
    milestone's RunStarted assertion is therefore an assertion about
    CL-6329's `section` mode — where every message is an `onTrigger`

package.json

@@ -57,7 +57,8 @@
     "prettier": "^3.6.2",
     "puppeteer-core": "^25.7.0",
     "typescript": "6.0.3",
-    "typescript-eslint": "^8.42.0"
+    "typescript-eslint": "^8.42.0",
+    "@corbits/run-scope": "workspace:*"
   },
   "engines": {
     "bun": ">=1.2.0"