@@ -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 open in `next` pre mode).
 
-- FROM: a publish-mode write of a list view into a package, bound outside the package's closure, answered `200` and was stored, with no issue. This covers `PUT /api/v1/meta/view/:name?package=…` (and `saveMetaItem` in publish mode), the promotion of a draft (`POST /api/v1/meta/view/:name/publish`, `publishMetaItem`), and a package draft publish (`publishPackageDrafts`).
-- TO: it answers `422 INVALID_METADATA`, with the `list-view-object-outside-closure` issue at the binding, and nothing is stored. A package draft publish fails the item, and the batch with it.
+- FROM: a publish-mode write of a list view into a package, bound outside the package's closure, answered `200` and was stored, with no issue. This covers `PUT /api/v1/meta/view/:name?package=…` (and `saveMetaItem` in publish mode), the promotion of a draft (`POST /api/v1/meta/view/: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 `list-view-object-outside-closure` issue at the binding, and nothing is stored. A package draft publish fails the item, and the batch with it. In `duplicatePackage`, a copied list view whose bound 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 bound object in the `dependencies` of the writing package's manifest, or bind the view to an object the package may reach (its own, a declared dependency's, or a platform object). Then save again. Once the object is inside the closure its fields are judged: an unknown `columns` field is refused `422 list-view-field-unknown`, as at the overlay door. Saving the view as a draft (`mode: 'draft'`) is still allowed, because drafts are never gated; publishing that draft is judged.
 
 **The next save of a stored list view bound outside its package's closure is refused with the fix; stored views keep serving until then.** The door judges writes only. A stored row is not re-judged at boot, and it loads and is served as before.
 
@@ -284,15 +284,20 @@ 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(1);
-        const [refusal] = res.failed;
+        expect(res.failed).toHaveLength(2);
+        const [refusal, viewRefusal] = 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.
         expect(refusal.error).toContain("Object 'ticket'");
         expect(refusal.error).toContain("'dupdst_ticket'");
         expect(refusal.error).toContain("'dupsrc_ticket'");
         expect(refusal.error).toContain("Rename 'ticket' on the source");
+        // [#24563] The `ticket` copy was refused, so the copy of `ticket_views`
+        // keeps the source's `ticket` — an object outside the copy package's
+        // 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]');
 
         // NEGATIVE CONTROL: the prefixed sibling took the name, with its own
         // body, and nothing of `ticket` was written under it.