fix(runtime): the clone door's notice names the clone's own off-switch, its status

The notice every successful clone answers told the admin to switch the
clone off through the activation toggle. A clone carries no package
envelope, so the toggle, which switches packaged flows only, refuses it:
the notice prescribed a step the platform refuses. It now names the
clone's own switch, status 'obsolete' through PUT
/api/v1/automation/NAME with the complete definition, and says the toggle
is for packaged flows such as the one the clone was copied from.

Measured at the dispatcher seam with the real engine: the clone door
answered 200 with the old notice, the clone carried no _packageId, and
the toggle it named answered RESOURCE_CONFLICT / 409 for it.

Co-authored-by: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XY5uCwTjZj7884yYtyur4H

Author: claude

.changeset/20726-clone-notice-status-switch.md

@@ -0,0 +1,7 @@
+---
+'@objectstack/runtime': patch
+---
+
+fix(runtime): the clone door's notice names the clone's own off-switch, its status (#20726)
+
+`POST /api/v1/automation/:name/clone` answers a `notice` saying the clone is armed. It told the admin to switch the clone off through `POST /api/v1/automation/NAME/toggle`. A clone carries no package envelope, so it is a flow authored in the deployment, and that switch refuses it: the switch turns packaged flows on and off only. The notice now names the clone's own switch: send its complete definition with `status: 'obsolete'` to `PUT /api/v1/automation/NAME`. It also says that the toggle switches packaged flows only, such as the flow the clone was copied from. The response shape is unchanged; only the notice text moves.

packages/runtime/src/flow-clone.ts

@@ -147,14 +147,23 @@ export const FLOW_CLONE_DROPPED_KEYS: readonly string[] = Object.freeze([
  *     record-change flow and walks away has two flows running on one trigger,
  *     and the only thing standing between them and that surprise is this
  *     sentence.
+ *
+ * [#20726, ADR-0126 §7.2] The off-switch it names is the CLONE's own: its
+ * `status`, published through `PUT /:name`. A clone carries no package
+ * envelope (see {@link FLOW_CLONE_DROPPED_KEYS}), so it is a flow authored in
+ * this deployment, and the activation toggle — which switches packaged flows
+ * only — refuses it. The toggle is named for the flow it was copied from,
+ * which is the packaged one.
  */
 export const FLOW_CLONE_NOTICE =
     'References are not re-pointed: this clone calls exactly what the original called '
     + '(subflows, actions and objects are unchanged). It is created with status `draft`, '
     + 'which is a lifecycle label and NOT an off-switch — a cloned record-change or schedule '
     + 'flow is bound to its trigger and will run alongside the flow it was copied from. '
-    + 'Disable it (`POST /api/v1/automation/<name>/toggle` with `{"enabled": false}`) if that '
-    + 'is not what you want.';
+    + 'If that is not what you want, switch the clone off through its own status: send its '
+    + 'complete definition with `status: \'obsolete\'` to `PUT /api/v1/automation/<name>`. '
+    + 'The activation toggle (`POST /api/v1/automation/<name>/toggle`) switches packaged flows '
+    + 'only, such as the one it was copied from, and refuses the clone.';
 
 /** ADR-0112 envelope for the same-name refusal: a status AND a code. */
 export const FLOW_CLONE_NAME_TAKEN_STATUS = 409;