refactor(agents)!: rename agents/assistant to agents/myra

AGENTS.md

@@ -22,7 +22,7 @@ never seeds data on a client's behalf.
   `apps/*` belongs in a package. `workflows/*` are plain npm-shaped packages,
   deployable to any stock Interchange hub through the stock deploy route —
   this repo does not publish them to npm.
-- **Myra is the one default agent.** `agents/assistant` is the assistant
+- **Myra is the one default agent.** `agents/myra` is the assistant
   that uses Workbench on the person's behalf; every agent package under
   `agents/*` is trim — `index.ts` (plus `system-prompt.ts` when the prompt
   is large) — with no agent-owned artifact client/tool code of its own.

ARCHITECTURE.md

@@ -39,7 +39,7 @@ address.
 
 ## Agents and workflows
 
-Myra (`agents/assistant`) is the only agent Workbench ships. There is no
+Myra (`agents/myra`) is the only agent Workbench ships. There is no
 workflow catalog to browse — Myra creates a workflow, tool, or skill
 dynamically, as code, when a job needs one, and deploys it through the
 stock workflow-deploy route. `tools/*` and `skills/*` are ordinary

PRODUCT.md

@@ -6,7 +6,7 @@ builder.
 
 ## Myra
 
-Myra (`agents/assistant`) is the one agent Workbench ships. She isn't a
+Myra (`agents/myra`) is the one agent Workbench ships. She isn't a
 template you configure — she's a coworker you talk to. Ask her for a
 capability the team doesn't have yet, and she writes it: a new tool, a
 new skill, or a scheduled workflow, deployed as code, granted only the

agents/assistant/README.md → agents/myra/README.md

@@ -1,4 +1,4 @@
-# @corbits/assistant-workflow
+# @corbits/myra
 
 Mail-triggered conversational workflow with a general-purpose assistant agent
 
@@ -12,13 +12,13 @@ POST /api/tenants/:id/workflows/deployments
 {
   "source": { "kind": "registry", "registry": "npm" },
   "entry": "./src/index.ts",
-  "pin": "@corbits/assistant-workflow@0.0.2",
+  "pin": "@corbits/myra@0.0.3",
   "sourceOfferingIds": ["<catalog offering id>", ...],
   "defaultSourceOfferingId": "<catalog offering id>"
 }
 ```
 
 `entry` is the package's `interchange.workflow` module path; `pin` is
-`"@corbits/assistant-workflow@0.0.2"` or a semver range on the same name. The hub
+`"@corbits/myra@0.0.3"` or a semver range on the same name. The hub
 installs, probes, gates, and freezes the definition from the registry
 tarball before creating the deployment.

agents/assistant/package.json → agents/myra/package.json

@@ -1,12 +1,12 @@
 {
-  "name": "@corbits/assistant-workflow",
-  "version": "0.0.2",
+  "name": "@corbits/myra",
+  "version": "0.0.3",
   "description": "Mail-triggered conversational workflow with a general-purpose assistant agent",
   "license": "LGPL-2.1-only",
   "repository": {
     "type": "git",
     "url": "https://github.com/corbitsdev/workbench.git",
-    "directory": "agents/assistant"
+    "directory": "agents/myra"
   },
   "files": [
     "src",

apps/web/package.json

@@ -20,9 +20,9 @@
     "@corbits/agent-directory": "workspace:*",
     "@corbits/approvals": "workspace:*",
     "@corbits/artifact-ui": "workspace:*",
-    "@corbits/assistant-workflow": "workspace:*",
     "@corbits/connections": "workspace:*",
     "@corbits/error-sink": "workspace:*",
+    "@corbits/myra": "workspace:*",
     "@corbits/react-ui": "github:corbitsdev/react-ui#3b122812a307ccb35be31386f7696020c5a84635",
     "@corbits/url-path": "workspace:*",
     "@corbits/workflows": "workspace:*",

apps/web/src/myra-deploy.ts

@@ -16,7 +16,7 @@ import {
   ASSISTANT_SYSTEM_PROMPT,
   ASSISTANT_TOOL_PACKAGE_PINS,
   ASSISTANT_WORKFLOW_ID,
-} from "@corbits/assistant-workflow/prompt";
+} from "@corbits/myra/prompt";
 import { renderWorkflowSourceTree } from "@corbits/workflows/client";
 import { type } from "arktype";
 
@@ -171,14 +171,14 @@ function tarballFilename(): string {
 const ASSISTANT_TURN_TIMEOUT_MS = 2 * 60 * 1000;
 
 /**
- * The exact `WorkflowDefinition` JSON `@corbits/assistant-workflow`'s
+ * The exact `WorkflowDefinition` JSON `@corbits/myra`'s
  * `buildAssistantWorkflow` would produce for a single-step, mail-triggered,
  * unbounded-turn assistant — hand-built here rather than calling that
  * function, because `buildAssistantWorkflow` goes through `@intx/workflow`'s
  * `defineWorkflow`/`step`, which pull in `@intx/agent`'s Node-bound runtime
  * (file locking) that a browser bundle cannot resolve (confirmed by a failed
- * `apps/web` build importing `@corbits/assistant-workflow` directly).
- * `apps/web/src/myra-deploy.test.ts` and `agents/assistant`'s own
+ * `apps/web` build importing `@corbits/myra` directly).
+ * `apps/web/src/myra-deploy.test.ts` and `agents/myra`'s own
  * `validate-push.test.ts`-style round-trip both guard this shape against
  * drift from `defineWorkflow`'s own normalization
  * (`vendor/intx/workflow/src/definition/workflow.ts`'s `normalize`/

apps/web/src/myra-source.ts

@@ -1,7 +1,7 @@
 // Myra's deploy source, pinned to what this hub can actually install
 // today.
 //
-// `@corbits/assistant-workflow` (agents/assistant) is `private: true`
+// `@corbits/myra` (agents/myra) is `private: true`
 // and unpublished, so `WorkflowDefinitionRegistrySource` (the `registry`
 // variant) has no external npm registry to resolve it from yet — that is
 // its job. The package also exports builder functions
@@ -39,7 +39,7 @@ const parsed = MyraSourceConfig({
   // tenant's own asset.
   assetName: "myra-deploy-source",
   displayName: "Myra",
-  // The rendered package's own name — never `@corbits/assistant-workflow`
+  // The rendered package's own name — never `@corbits/myra`
   // itself, which names the real, un-deployable workspace package this
   // module explicitly does not source from (see the module doc above).
   packageName: "@workbench-onboarding/myra",

packages/agent-directory/src/agent-workflow.ts

@@ -1,6 +1,6 @@
 // Builds the single-step, folded workflow definition a hand-authored
 // agent materializes as: exactly the shape `@corbits/chat`'s own
-// `buildWorkbenchHostWorkflow`/`@corbits/assistant-workflow`'s
+// `buildWorkbenchHostWorkflow`/`@corbits/myra`'s
 // `buildAssistantWorkflow` produce, but with the system prompt and
 // model left to the caller instead of fixed at build time — this is
 // the one difference that makes a defined-by-a-person agent possible

packages/agent-directory/src/routes.ts

@@ -1,7 +1,7 @@
 // The create-agent-definition surface: a tenant member submits a
 // name/handle/description/system-prompt/model, and this route
 // materializes it exactly the way the platform's own starter agents
-// (`@corbits/assistant-workflow`, `@corbits/chat`'s workbench host) are
+// (`@corbits/myra`, `@corbits/chat`'s workbench host) are
 // materialized — a `workflow`-kind asset carrying a single-step
 // definition as a source codebase (see `./definition-asset.ts`),
 // projected onto a first-class `workflow_definition` row. No git subprocess: `AssetService.populateAsset` writes the

packages/evals/package.json

@@ -14,11 +14,11 @@
   },
   "dependencies": {
     "@corbits/agent-directory": "workspace:*",
-    "@corbits/assistant-workflow": "workspace:*",
     "@corbits/connections": "workspace:*",
     "@corbits/error-sink": "workspace:*",
     "@corbits/hub-api-client": "workspace:*",
     "@corbits/migration-runner": "workspace:*",
+    "@corbits/myra": "workspace:*",
     "@corbits/webhook-triggers": "workspace:*",
     "@corbits/workflows": "workspace:*",
     "@intx/agent": "workspace:*",

packages/workflows/src/catalog.ts

@@ -16,7 +16,7 @@
 // only here, so there is no second copy for them to drift from.
 import { type } from "arktype";
 
-import assistantPkg from "../../../agents/assistant/package.json";
+import assistantPkg from "../../../agents/myra/package.json";
 
 const CorbitsWorkflowBlock = type({
   assetName: "string > 0",

tsconfig.build.json

@@ -2,7 +2,7 @@
   "files": [],
   "references": [
     {
-      "path": "./agents/assistant/tsconfig.src.json"
+      "path": "./agents/myra/tsconfig.src.json"
     },
     {
       "path": "./apps/sidecar/tsconfig.src.json"

workflows/README.md

@@ -1,10 +1,10 @@
 # Workflow packages
 
 Owner ruling (2026-09-17, LESS IS MORE): the shipped workflow catalog is
-deleted. Myra (`agents/assistant`) creates workflows dynamically for a
+deleted. Myra (`agents/myra`) creates workflows dynamically for a
 tenant's own needs; there is no seeded catalog of ready-made workflows
 any more. The `echo` fixture workflow is gone too — the e2e smoke suites
-now deploy Myra's own `agents/assistant` definition to prove the
+now deploy Myra's own `agents/myra` definition to prove the
 mail-triggered contract works.
 
 Each subdirectory is a deployable workflow package: an Interchange