fix(runtime)!: PATCH /packages/:id refuses a read-only package with 422 WRITABLE_PACKAGE_REQUIRED

The manifest-edit arm now asks requireWritablePackage (isWritablePackage,
the ADR-0070 D2 rule) after the manage_metadata and walled gates and before
the body is read, in the order install-overwrite, disable, publish, revert
and delete already use.

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

Author: claude

packages/runtime/src/domains/packages.ts

@@ -2255,6 +2255,15 @@ export async function handlePackagesRequest(deps: DomainHandlerDeps, path: strin
             // [ADR-0131 D12 items 7–8] Under a wall, the platform operator's.
             const walled = await refuseWalledCatalogPackageWrite(deps, _context, `Updating package "${id}"`);
             if (walled) return walled;
+            // [#24705] ADR-0070 D2: the manifest of a package the deployment
+            // ships is the deployment's, so this door refuses it with the
+            // answer install-overwrite, disable, publish, revert and delete
+            // give. Asked BEFORE the body is read, so the answer is the same
+            // whatever keys the body carries, and before `updatePackage`
+            // re-persists the edited manifest to `sys_packages`. An id nothing
+            // installed is writable by the predicate's own rule, so it still
+            // reaches the 404 below.
+            const readOnly = requireWritablePackage(deps, qlService, id, 'edit'); if (readOnly) return readOnly;
             const src = (body?.manifest && typeof body.manifest === 'object' ? body.manifest : body) ?? {};
             const patch: { name?: string; description?: string; version?: string } = {};
             if (typeof src.name === 'string') patch.name = src.name.trim();