test(cli,dogfood): the two current-app fixtures main added since b460153 declare the current protocol, ^18

main added two manifest fixtures that declare engines.protocol '^17' and
stand for a valid current app, not for an old artifact:
- packages/qa/dogfood/test/security-catalog-cold-boot-environment-holder.dogfood.test.ts
  (#22365): at protocol 18 the load-seam handshake refuses it, and all four
  cases fail with ProtocolIncompatibleError before reaching their subject.
- packages/cli/test/retry-policy-key-validate-door.test.ts (#22380): os
  validate only advises on the gap, so it stays green either way, but its
  subject is the retry-policy key door, not the protocol's age.
Both now read '^18', like the other current-app fixtures this change moved.

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

Author: claude

packages/cli/test/retry-policy-key-validate-door.test.ts

@@ -48,7 +48,7 @@ const stackOf = (retry: Retry, retryPolicy: Retry) => ({
     name: 'Retry key door probe',
     version: '1.0.0',
     type: 'app',
-    engines: { protocol: '^17' },
+    engines: { protocol: '^18' },
   },
   objects: [
     {

packages/qa/dogfood/test/security-catalog-cold-boot-environment-holder.dogfood.test.ts

@@ -67,7 +67,7 @@ const SET = 'coldboot_env_set';
 const POSITION = 'coldboot_env_position';
 
 const manifestOf = (id: string, namespace: string) => ({
-  id, namespace, version: '0.0.1', type: 'app' as const, name: id, engines: { protocol: '^17' },
+  id, namespace, version: '0.0.1', type: 'app' as const, name: id, engines: { protocol: '^18' },
 });
 
 const Note = ObjectSchema.create({