Update docs: catalog workflows are deployable, not seeded (CL-7074)

Author: TheGreatAxios

docs/bench-provisioning.md

@@ -77,8 +77,10 @@ Connecting hands the person forward immediately, and the wait on the
 other side is as short as it can honestly be: the setup agent (Myra)
 leads `DEFAULT_WORKFLOWS`, so she is deployed before anything else, and
 the land hop drops the person into her room the moment she can answer.
-The digest, recurring-task and research seeds finish behind them —
-nobody needs a scheduled digest in their first second.
+The other catalog workflows (digest, recurring-task, research) are not
+seeded at all — they are deployable through the catalog instantiate route
+(CL-7073) once someone picks one, not on a critical path nobody is waiting
+on.
 
 While she is still coming up, the shared warm loader is the whole
 screen: one honest headline and a rotating tip, never an internal count.

packages/onboarding/test/complete-credential.test.ts

@@ -1779,7 +1779,6 @@ describe("ensureSeeded (the slow half)", () => {
     });
 
     expect(workflowOrder[0]).toBe(SETUP_AGENT_ASSET_NAME);
-    expect(workflowOrder.length).toBeGreaterThanOrEqual(1);
   });
 
   test("two overlapping calls for the same tenant never double-deploy — the same 409-then-list tolerance seedTenant already has", async () => {

packages/seeding/src/seed.ts

@@ -229,8 +229,9 @@ export const SETUP_AGENT_ASSET_NAME = "assistant";
  * needs the moment they land. `echo`, `workbench-digest`, and
  * `last-30-days-research` used to live here; a signup paid a git push
  * and a sidecar probe for each of them even though nobody asked for
- * them. They now live in `CATALOG_WORKFLOWS`, deployed on demand
- * (CL-7073) rather than onto every bench. See `CATALOG_TEST_WORKFLOWS`
+ * them. They now live in `CATALOG_WORKFLOWS`, deployable through the
+ * catalog instantiate route (CL-7073) rather than seeded onto every
+ * bench. See `CATALOG_TEST_WORKFLOWS`
  * for the platform-exercise set, which never reaches a real signup at
  * all.
  *
@@ -333,7 +334,8 @@ export const CATALOG_WORKFLOWS: readonly DefaultWorkflow[] = [
  *
  * workbench-digest used to live here as a platform exercise, then moved
  * to `DEFAULT_WORKFLOWS`; it now lives in `CATALOG_WORKFLOWS` (CL-7074),
- * deployed on demand rather than onto every bench.
+ * deployable through the catalog instantiate route (CL-7073) rather than
+ * seeded onto every bench.
  */
 export const CATALOG_TEST_WORKFLOWS: readonly DefaultWorkflow[] = [
   {

workflows/heartbeat/README.md

@@ -48,5 +48,7 @@ const json = serializeHeartbeatWorkflow(definition);
 ```
 
 See [`workflows/README.md`](../README.md#status-note) for what
-registration/automatable/seeded mean — this one is seeded by default for
-every tenant, same as `workbench-digest`.
+registration/automatable/seeded mean — this one is a
+`CATALOG_TEST_WORKFLOWS` entry, kept for tests only, never seeded and
+never deployed onto a real bench. `workbench-digest` is not seeded either;
+it is deployable through the catalog instantiate route (CL-7073).

workflows/morning-brief/README.md

@@ -143,4 +143,5 @@ markdown brief.
 See [`workflows/README.md`](../README.md#status-note) for what
 registration/automatable/seeded mean — this one is `automatable: true`
 but not seeded, since it needs real Granola/Linear credentials to be
-useful, unlike `workbench-digest`.
+useful. `workbench-digest` is not seeded either; both are deployable
+through the catalog instantiate route (CL-7073).

workflows/workbench-digest/README.md

@@ -51,5 +51,5 @@ const json = serializeWorkbenchDigestWorkflow(definition);
 
 See [`workflows/README.md`](../README.md#status-note) for what
 registration/automatable/seeded mean — this one is `automatable`, and
-deployed on demand from `CATALOG_WORKFLOWS` (CL-7074), not seeded by
-default onto every tenant.
+deployable through the catalog instantiate route (CL-7073) from
+`CATALOG_WORKFLOWS` (CL-7074), not seeded by default onto every tenant.