@@ -12,8 +12,8 @@ Clause-②: yes (narrowing)
 
 **BREAKING — what moves for consumers.** This is an accept-set narrowing on the metadata save door, shipped as `minor` under the launch-window convention for accept-set narrowings (`.changeset/pre.json` is in `exit` mode, so the next version pass cuts 18.0.0 and this change ships in it).
 
-- FROM: a publish-mode write of a flow into a package, triggered on or sweeping an object outside the package's closure, answered `200` and was stored, with a `flow-trigger-unknown-object` save advisory. This covers `PUT /api/v1/meta/flow/:name?package=…` (and `saveMetaItem` in publish mode), the promotion of a draft (`POST /api/v1/meta/flow/:name/publish`, `publishMetaItem`) and a package draft publish (`publishPackageDrafts`).
-- TO: the same writes answer `422 INVALID_METADATA`, with the `flow-trigger-unknown-object` issue at `error` at the trigger key, and nothing is stored. A package draft publish fails the item, and the batch with it.
+- FROM: a publish-mode write of a flow into a package, triggered on or sweeping an object outside the package's closure, answered `200` and was stored, with a `flow-trigger-unknown-object` save advisory. This covers `PUT /api/v1/meta/flow/:name?package=…` (and `saveMetaItem` in publish mode), the promotion of a draft (`POST /api/v1/meta/flow/:name/publish`, `publishMetaItem`), a package draft publish (`publishPackageDrafts`), and a package copy (`duplicatePackage`), which writes its copies through the same door.
+- TO: `saveMetaItem` in publish mode, the draft promotion and `publishPackageDrafts` answer `422 INVALID_METADATA`, with the `flow-trigger-unknown-object` issue at `error` at the trigger key, and nothing is stored. A package draft publish fails the item, and the batch with it. In `duplicatePackage`, a copied flow whose trigger object stays outside the copy package's closure is refused with the same rule and listed in its `failed[]`. One way that happens is when that object's own copy was refused.
 - Fix: declare a dependency on the package that defines the trigger object in the `dependencies` of the writing package's manifest, or trigger the flow on an object the package may reach (its own, a declared dependency's, or a platform object). Then save again. Saving the flow as a draft (`mode: 'draft'`) is still allowed, because drafts are never gated; publishing that draft is judged.
 
 **The next save of a stored flow whose trigger object is outside its package's closure is refused with the fix; stored flows keep loading and firing until then.** The door judges writes only. A stored row is not re-judged at boot.
 
@@ -305,8 +305,8 @@ describe('ADR-0070 D4 — duplicatePackage of an object whose name lacks the sou
         const res = await protocol.duplicatePackage({ sourcePackageId: P, targetPackageId: Q });
 
         expect(res.success).toBe(false);
-        expect(res.failed).toHaveLength(2);
-        const [refusal, viewRefusal] = res.failed;
+        expect(res.failed, JSON.stringify(res.failed)).toHaveLength(3);
+        const [refusal, viewRefusal, flowRefusal] = res.failed;
         expect(refusal).toMatchObject({ type: 'object', name: 'ticket' });
         // Located: the object, the name it would take, who holds that name,
         // and the source rename that clears it.
@@ -319,6 +319,11 @@ describe('ADR-0070 D4 — duplicatePackage of an object whose name lacks the sou
         // closure — and the save door refuses it with the same rule.
         expect(viewRefusal).toMatchObject({ type: 'view', name: 'ticket_views' });
         expect(viewRefusal.error).toContain('views[0].object [list-view-object-outside-closure]');
+        // [#24669] And the copy of `dupsrc_on_ticket` keeps the source's
+        // `ticket` as its trigger object, outside the copy package's closure
+        // too, so the flow door refuses it — the same verdict, at the third door.
+        expect(flowRefusal).toMatchObject({ type: 'flow' });
+        expect(flowRefusal.error).toContain('flows[0].nodes[0].config.objectName [flow-trigger-unknown-object]');
 
         // NEGATIVE CONTROL: the prefixed sibling took the name, with its own
         // body, and nothing of `ticket` was written under it.