fix(runtime): the clone notice makes no claim about the clone's source

The clone door takes any registered flow as its source, with no
provenance test, so "the toggle switches packaged flows only, such as the
one it was copied from" is false when a customer-authored flow is cloned.
The notice, its docblock and the runtime changeset now say only what
holds for every clone: the toggle switches packaged flows only and
refuses the clone. The prescription is unchanged: switch the clone off
through its own status, via PUT /api/v1/automation/NAME.

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

Author: claude

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

@@ -4,4 +4,4 @@
 
 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.
+`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 and refuses the clone, whatever flow the clone was copied from. The response shape is unchanged; only the notice text moves.

packages/runtime/src/flow-clone.ts

@@ -152,8 +152,9 @@ export const FLOW_CLONE_DROPPED_KEYS: readonly string[] = Object.freeze([
  * `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.
+ * only — refuses it. That holds whatever the clone was copied from: the clone
+ * door takes any registered flow as its source, packaged or not, so the
+ * notice makes no claim about the source's provenance.
  */
 export const FLOW_CLONE_NOTICE =
     'References are not re-pointed: this clone calls exactly what the original called '
@@ -163,7 +164,7 @@ export const FLOW_CLONE_NOTICE =
     + '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.';
+    + 'only 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;