extension: never show the bridge footer while PI_CHROME_AUTHORIZE is set

The footer was hidden through envGranted, a flag that depended on which
grant a runtime ended up with. Any grant restored from globalThis, such as
one an older build saved there before a /reload or a session switch, left
the flag false and brought the footer back.

Decide from the environment itself, on every status update: with a valid
PI_CHROME_AUTHORIZE the footer never shows, whatever grant is active. A
/reload is enough to clear the footer in a pi that has one today. The
envGranted flag is gone.

1 files changed, 9 insertions, 7 deletions

diff --git a/extensions/chrome-profile-bridge/index.ts b/extensions/chrome-profile-bridge/index.ts
index 0338c5c..97b9f33 100644
--- a/extensions/chrome-profile-bridge/index.ts
+++ b/extensions/chrome-profile-bridge/index.ts
@@ -924,9 +924,6 @@ export default function (pi: ExtensionAPI): void {
 	const bridge = new ChromeProfileBridge(DEFAULT_HOST, DEFAULT_PORT);
 	let backgroundEnabled = true;
 	let chromeAuthorizedUntil: number | "indefinite" | undefined;
-	// Whether the current grant stood in from PI_CHROME_AUTHORIZE rather than being given by
-	// the user this session. The footer announces only the latter.
-	let envGranted = false;
 	// Restore an authorization that survived a /reload. Drop it if it already expired.
 	const persistedAuth = globalState[PI_CHROME_AUTH_KEY];
 	if (persistedAuth) {
@@ -1026,7 +1023,6 @@ export default function (pi: ExtensionAPI): void {
 		chromeToolsUsable = false;
 		if (logAction && wasUsable) logChromeToolChange(logAction, { authorizedUntil: undefined });
 		chromeAuthorizedUntil = undefined;
-		envGranted = false;
 		persistAuth();
 		// Revoking control ends pi-chrome's automation for this session; tidy up the target we own.
 		void cleanupAutomationTargetBestEffort();
@@ -1083,8 +1079,16 @@ export default function (pi: ExtensionAPI): void {
 		return typeof id === "string" && id ? `session:${id}` : undefined;
 	};
 
+	// FORK: with PI_CHROME_AUTHORIZE set, Chrome control is standing configuration, not session
+	// state, so the footer never shows. Read from the environment on every update, not from any
+	// saved state, so no grant restored across /reload or a session switch can bring it back.
+	const envAuthorizes = (): boolean => {
+		const value = process.env.PI_CHROME_AUTHORIZE?.trim();
+		return !!value && parseAuthorizeArg(value) !== undefined;
+	};
+
 	const updateChromeStatus = (ctx: ExtensionContext): void => {
-		if (chromeControlAuthorized() && !envGranted) {
+		if (chromeControlAuthorized() && !envAuthorizes()) {
 			ctx.ui.setStatus("chrome", ctx.ui.theme.fg("success", "●") + " Chrome Bridge" + authCountdownLabel());
 		} else {
 			ctx.ui.setStatus("chrome", undefined);
@@ -1180,7 +1184,6 @@ export default function (pi: ExtensionAPI): void {
 			const grant = parseAuthorizeArg(autoGrant);
 			if (grant) {
 				chromeAuthorizedUntil = grant.until;
-				envGranted = true;
 			} else {
 				ctx.ui.notify(`Ignoring PI_CHROME_AUTHORIZE="${autoGrant}": use minutes (15m, 30, 45) or indefinite.`, "warning");
 			}
@@ -1415,7 +1418,6 @@ Usage rules:
 		}
 		const wasUsable = chromeToolsUsable;
 		chromeAuthorizedUntil = until;
-		envGranted = false;
 		persistAuth();
 		activateChromeTools();
 		chromeToolsUsable = true;