@@ -236,6 +236,7 @@ Workflows are named, ordered recipes the agent follows step by step — a thin l
 
 - `coordinator.ts` — bridges runtime and director: produces the `[WORKFLOW STEP i/total: label]` directive injected into each turn's system prompt, and compare-and-advances the runtime when a `submit_output` tagged `{ step }` completes. Already-complete and not-current ids are acknowledged without moving the cursor. Shared by both directors. Fresh and resumed runs share one listener path.
 - The built-in recipes: the atomics `update-ticket`, `improve-docs`, `write-tests`, `triage-bug`, `code-review`, `scope-project`, and the `build-feature` composite that chains them.
+- Pipeline alignment (CL-8268): `0.3.x` is the local Interchange cutover (become a client of native primitives before hub is the product); `0.4.0` is the hub-client formality (login, consume, routing). Step 1 lands in `0.3.x` as four backlog items: CL-8289 (extract `invokeStep`, no behavior change), CL-8288 (wrap the worker in `runtimeRun`), CL-8301 (default-chat workflow as one dispatch step), CL-8302 (local mailbox substrate). None is implemented yet.
 
 Invocation: workflows are **not** top-level slash commands. Recipe definitions load into the `WORKFLOWS` registry from **enabled workflow/command plugins** at startup; command surfaces on those plugins (e.g. a workflow plugin's command prefix such as `/mywf scope`). Slash commands may also be authored as data-only markdown (`commands/*.md`, no `index.ts`); see PLUGINS.md. The model never suggests or auto-starts workflows from ordinary chat. Skills (bundled `corbits-skills`, enabled plugins, or `.agents/skills/`) load on demand via `skill_search` then `use_skill`, or as `/<skill-name>` slash commands when `user-invocable` is not `false` (see Skills below). `WorkflowHost` (`src/workflows/host.ts`) owns lifecycle, capability overrides, and resume; the TUI only renders host status in the header (`⟳ name · step/total label`).