fix(browser): local HTTPS Try HTTPS + cert proceed (#8454) (#9104)

Co-authored-by: Jinjing <6427696+AmethystLiang@users.noreply.github.com>

src/main/runtime/rpc/methods/browser-core.ts

@@ -1,5 +1,5 @@
 import { defineMethod, type RpcMethod } from '../core'
-import { BrowserTarget } from '../schemas'
+import { BrowserTarget, requiredString } from '../schemas'
 import {
   Check,
   Drag,
@@ -34,6 +34,10 @@ import {
 } from './browser-schemas'
 import { BROWSER_TEXT_METHODS } from './browser-text-rpc-methods'
 
+const CertificateProceed = BrowserTarget.extend({
+  challengeId: requiredString('Missing required challengeId')
+})
+
 export const BROWSER_CORE_METHODS: RpcMethod[] = [
   defineMethod({
     name: 'browser.snapshot',
@@ -50,6 +54,11 @@ export const BROWSER_CORE_METHODS: RpcMethod[] = [
     params: Goto,
     handler: async (params, { runtime }) => runtime.browserGoto(params)
   }),
+  defineMethod({
+    name: 'browser.certificate.proceed',
+    params: CertificateProceed,
+    handler: async (params, { runtime }) => runtime.browserProceedCertificate(params)
+  }),
   ...BROWSER_TEXT_METHODS,
   defineMethod({
     name: 'browser.select',

src/main/runtime/rpc/methods/browser-schemas.ts

@@ -1,7 +1,5 @@
-// Why: the browser method surface area is large enough that keeping every
-// schema in the same file as its handler registration pushes the file past
-// the 300-line lint cap. Grouping all browser schemas here keeps each
-// handler file focused on dispatch wiring.
+// Why: browser schemas stay separate from handler registration so both sides
+// remain under the line cap and dispatch wiring stays scannable.
 import { z } from 'zod'
 import {
   BrowserTarget,