sliccy 6.186.0 → 6.187.0

package/dist/node-server/chrome-launch.d.ts

@@ -58,6 +58,8 @@ export declare function buildChromeLaunchArgs(options: {
     launchUrl: string;
     profile: ChromeLaunchProfile;
     hosted?: boolean;
+    /** Throwaway-profile harnesses only (`SLICC_CHROME_MOCK_KEYCHAIN=1`); see below. */
+    mockKeychain?: boolean;
 }): string[];
 /**
  * Walk up from a Chrome executable path

package/dist/node-server/chrome-launch.js

@@ -224,6 +224,17 @@ export function buildChromeLaunchArgs(options) {
         '--disable-renderer-backgrounding',
         `--user-data-dir=${options.profile.userDataDir}`,
     ];
+    if (options.mockKeychain) {
+        // The dev `*-fresh` harnesses launch an ad-hoc re-signed Chrome clone
+        // (clone-labeled-chrome.sh) whose code identity is not on the Keychain ACL
+        // of the shared "Chrome Safe Storage" item. On a fresh profile Chrome then
+        // raises a SecurityAgent prompt the backgrounded harness never shows, and
+        // until it is answered every navigation hangs with an empty history. A
+        // mock keychain avoids the prompt, but it re-keys cookie/password
+        // encryption, so it is opt-in and only for throwaway profiles — a real
+        // profile would lose every saved cookie.
+        args.push('--use-mock-keychain', '--password-store=basic');
+    }
     if (options.profile.extensionPath) {
         args.push(`--disable-extensions-except=${options.profile.extensionPath}`);
         args.push(`--load-extension=${options.profile.extensionPath}`);

package/dist/node-server/index.js

@@ -471,6 +471,7 @@ async function launchChromeTarget(state) {
         launchUrl: browserLaunchUrl,
         profile: chromeProfile,
         hosted: RUNTIME_FLAGS.hosted,
+        mockKeychain: process.env.SLICC_CHROME_MOCK_KEYCHAIN === '1',
     });
     // Chrome never clears DevToolsActivePort on shutdown, so a stale file from a
     // prior crash/SIGKILL would let our active-port poller win the race with the