@@ -9,7 +9,7 @@ A package declares how it may be installed — `installModes: ['managed', 'unman
 
 Clause-②: yes (widening: the new optional manifest key `installModes`; the new exports `INSTALL_MODES`, `InstallModeSchema`, `InstallMode`, `DEFAULT_INSTALL_MODES`, `resolveInstallModes`, `UNMANAGED_INSTALL_KEY_DISPOSITIONS`, `UNMANAGED_INSTALL_REFUSING_DISPOSITIONS`, `UnmanagedInstallKeyDisposition`, `unmanagedInstallValueCarries` and `unmanagedInstallPostureRefusal`; the install-local body field `installMode`; the CLI option `--install-mode`; the error codes `STACK_UNMANAGED_INSTALL_UNCOPYABLE` and `INSTALL_MODE_NOT_PERMITTED`)
 
-A package installs one of two ways. **Managed**: it is registered as code, stays the authority, upgrades, and nothing it ships is edited in place. **Unmanaged**: its metadata is copied once into this environment under a new writable base; the copy's items are this environment's own metadata, the next save edits them, and it follows no upgrade. One exception is carried: an item the package ships with an authored protection lock (`_lock`) keeps that lock on the copy, and its handling is an open question on #15213. This entry adds the manifest key that declares the modes a package permits, and the install door that honours it; the copy itself is the companion entry `15213-unmanaged-import-verb`.
+A package installs one of two ways. **Managed**: it is registered as code, stays the authority, upgrades, and nothing it ships is edited in place. **Unmanaged**: its metadata is copied once into this environment under a new writable base; the copy's items are this environment's own metadata, the next save edits them, and it follows no upgrade. One exception is carried: an item the package ships with an authored protection lock (`_lock`) keeps that lock on the copy as written today, and a follow-up on #15213 strips it per #22971's ruling A. This entry adds the manifest key that declares the modes a package permits, and the install door that honours it; the copy itself is the companion entry `15213-unmanaged-import-verb`.
 
 **This entry supersedes parts of that earlier entry, `15213-unmanaged-import-verb`, in this same release.** It says of the import "no door calls it yet, and no manifest key declares the mode yet". What holds now: the install door calls it for `installMode: 'unmanaged'`, and the manifest key `installModes` declares the modes a package permits. It says seed `data` and `translations` are "left to the install door, which applies them after the copy as it does for a managed install". What holds now: the import copies `translations` itself, as `translation` items, and an unmanaged install loads no seed `data` — neither the import nor the door applies it, and the door's answer says so under `seeded`. It also calls the copy "editable from then on" and says each item "is fully editable"; what holds is the sentence above: the copy's items are this environment's own metadata and the next save edits them, except an item shipped with an authored `_lock`, which keeps that lock. Where the two entries disagree, this one is current.
 
 
@@ -56,13 +56,16 @@
  *              writable base in the environment ledger
  *              (`importUnmanagedPackage`): the environment's own metadata,
  *              which the next save edits (an item shipped with an authored
- *              `_lock` keeps that lock on the copy), followed by no upgrade;
+ *              `_lock` keeps that lock on the copy as written today, and a
+ *              follow-up on #15213 strips it per #22971's ruling A),
+ *              followed by no upgrade;
  *              nothing is registered, ledgered or rehydrated under the
  *              package's id, and its sample data is not loaded. Refused
  *              `409 UNMANAGED_INSTALL_WALLED_POSTURE` on a deployment whose
  *              REQUESTED tenancy posture walls organizations: after the
- *              payload check and steps 1b–1c (package id, protocol
- *              handshake; none of them writes), before any write.
+ *              payload check, step 1b (package id), the ADR-0131 D3
+ *              walled-catalog refusal and step 1c (protocol handshake),
+ *              none of which writes, and before any write.
  *          A mode the package's `installModes` does not permit answers
  *          `422 INSTALL_MODE_NOT_PERMITTED`, before any write.
  *
@@ -1317,10 +1320,10 @@ export class MarketplaceInstallLocalPlugin implements Plugin {
             }, refusal.status);
         }
 
-        // 1e. [ADR-0131 D6] ⭐ THE INSTALL MODE — after the payload, id and
-        //     handshake checks and before every other judgement of the package
-        //     and any write, because nothing an author changes in the
-        //     package answers either refusal:
+        // 1e. [ADR-0131 D6] ⭐ THE INSTALL MODE — after the payload, id, D3
+        //     walled-catalog and handshake checks and before every other
+        //     judgement of the package and any write, because nothing an
+        //     author changes in the package answers either refusal:
         //       - the package must PERMIT the requested mode: its manifest's
         //         `installModes`, parsed by reference
         //         (`ManifestSchema.shape.installModes`) and read through the one
 
@@ -10,7 +10,8 @@
  * ruled on the D6 execution card, 2026-10-11): every metadata item is copied
  * ONCE into the environment ledger, becomes this environment's own metadata,
  * which the next save edits (an item shipped with an authored `_lock` keeps
- * that lock), and never follows an upgrade. The orchestration —
+ * that lock as written today, and a follow-up on #15213 strips it per
+ * #22971's ruling A), and never follows an upgrade. The orchestration —
  * reading the store, minting the base, writing each item through
  * `saveMetaItem`, deleting the base when a write fails — is
  * `ObjectStackProtocolImplementation.importUnmanagedPackage` (`protocol.ts`).
 
@@ -24485,8 +24485,9 @@ export class ObjectStackProtocolImplementation implements
      * door a Studio edit takes — so every copied item is environment metadata
      * from its first byte: owned by the base, `organization_id` NULL, served
      * `_provenance: 'org'`, edited by the next save (an item shipped with an
-     * authored `_lock` keeps that lock), and followed by no
-     * upgrade. The managed mode is the package install; this verb is what that
+     * authored `_lock` keeps that lock as written today, and a follow-up on
+     * #15213 strips it per #22971's ruling A), and followed by no upgrade.
+     * The managed mode is the package install; this verb is what that
      * install's manifest service is to it, and no more (see
      * `package-unmanaged-install.ts` for what is copied, what is refused, and
      * what is left to the door).
 
@@ -408,10 +408,10 @@ export function manifestIdRefusal(key: string, input: unknown): string {
  *    ledger, under a new writable base whose id differs from the package's.
  *    From then on it is the environment's own metadata and the next save
  *    edits it, except that an item shipped with an authored protection lock
- *    (`_lock`) keeps that lock on the copy (an open question on #15213); it
- *    follows no upgrade. A deployment whose
- *    tenancy posture walls organizations (`group`, `isolated`) refuses it,
- *    whatever the package permits.
+ *    (`_lock`) keeps that lock on the copy as written today, and a follow-up
+ *    on #15213 strips it per #22971's ruling A; it follows no upgrade. A
+ *    deployment whose tenancy posture walls organizations (`group`,
+ *    `isolated`) refuses it, whatever the package permits.
  *
  * The spelling is the maintainer's ruling B on the D6 execution card
  * (2026-10-11): `managed` and `unmanaged` are the two states of one property,