fix(release): un-enroll connect-protocol from CI publish; drop lockfile edits

@paperclip/connect-protocol is not yet published to npm, so enrolling it
with publishFromCi:true fails the release bootstrap policy check. Per the
release-owner decision (accepted confirmation on PAP-14865), set
publishFromCi:false until the first npm publish is bootstrapped; a follow-up
re-enrolls it before any external consumer needs it (workspace link: dep only).

Also restore pnpm-lock.yaml to the merge-base state: CI owns lockfile
regeneration (regen_lockfile), and committing pnpm-lock.yaml trips the
'Block manual lockfile edits' policy step.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

pnpm-lock.yaml

@@ -330,19 +330,6 @@ importers:
         specifier: ^5.7.3
         version: 5.9.3
 
-  packages/connect-protocol:
-    dependencies:
-      zod:
-        specifier: ^3.24.2
-        version: 3.25.76
-    devDependencies:
-      '@types/node':
-        specifier: ^22.19.21
-        version: 22.19.21
-      typescript:
-        specifier: ^5.7.3
-        version: 5.9.3
-
   packages/db:
     dependencies:
       '@paperclipai/shared':
@@ -738,9 +725,6 @@ importers:
       '@aws-sdk/client-s3':
         specifier: ^3.1075.0
         version: 3.1075.0
-      '@paperclip/connect-protocol':
-        specifier: workspace:*
-        version: link:../packages/connect-protocol
       '@paperclipai/adapter-claude-local':
         specifier: workspace:*
         version: link:../packages/adapters/claude-local

scripts/release-package-manifest.json

@@ -2,7 +2,7 @@
   {
     "dir": "packages/connect-protocol",
     "name": "@paperclip/connect-protocol",
-    "publishFromCi": true
+    "publishFromCi": false
   },
   {
     "dir": "packages/adapter-utils",