Software Garden has two sources: the cloud wizard's catalog Garden deploys a different flow than /flows onboarding #174

Problem

"Software Garden" has two sources, and they deploy different flows depending on how a user arrives:

So the cloud wizard's prebuilt Software Garden deploys a different flow from the one /flows onboarding generates, and from the 7 live Gardens.

Evidence (2026-10-08)

• The live Gardens (Cloud, Flows, Relay, Relaycast ×2, the Relayfile group) were built from the generator and carry Fit the generated Software Garden into Cloud's 60-minute run cap (cloud#4235) #155/feat(flows): fit the generated Software Garden into Cloud's 60-minute run cap #156 (the 60-minute shape) and fix(flows): cap generated PR and comment bodies under GitHub's 65,536-character limit #161 (the PR/comment body cap).
• The catalog source has the 1h wallclock but none of the generated Garden's machinery:
  • no relayflow_push workflow-edit push guard;
  • no body cap;
  • none of the Fit the generated Software Garden into Cloud's 60-minute run cap (cloud#4235) #155/feat(flows): fit the generated Software Garden into Cloud's 60-minute run cap #156 repair, review or draft structure.
• flows main's examples/software-factory/software-factory.flow.ts is byte-identical to v2.0.42, so a catalog "version bump" has nothing to pick up.
• Generator changes (Fit the generated Software Garden into Cloud's 60-minute run cap (cloud#4235) #155, feat(flows): fit the generated Software Garden into Cloud's 60-minute run cap #156, fix(flows): cap generated PR and comment bodies under GitHub's 65,536-character limit #161) never reach the catalog path, so the two drift further with every generator PR.

Options

(a) Recommended: the generator is the single source. agentrelay.com publishes the generated Software Garden as a versioned, integrity-hashed artifact, for example at release or deploy time. Pin it per agent-set variant if needed. The catalog entry points at that artifact (url + sha256, keeping catalogVersion 4 semantics per #143). Every surface then deploys the same bytes, and a generator change rolls out through one catalog bump.

(b) Regenerate the flows example from the generator. Regenerate examples/software-factory/software-factory.flow.ts from factorySource on each generator change and re-release flows. That keeps two repos in lockstep and makes a flows release a dependency of every generator fix.

Status

Decision pending with Khaliq. No changes have been made.

Cross-links: AgentWorkforce/cloud#4268, #143, #155, #156, #161.