Sokongan Mega888 Respons Untuk Setiap Pemain Mungkin Mega888 Lazim

Problem

Agent access to the browser was a row inside the "…" menu, so the toolbar never showed whether agents could use the tabs or who was driving the current tab. The access request read "Let an agent use any tabs in the browser", which did not ask a question. The menu mixed two icon families, and the device toolbar used a native select that showed "Auto px" for Responsive. Clearing cookies used the system confirm box. Cookie and cache results went only to the console, so a failed clear looked like a success. "Pin across threads" used a pin icon, left the menu open, and nothing in the tab strip showed that a tab was kept in every thread. The address field had no accessible name. A new tab showed a bright white page with only a logo, even in a dark theme.

Change

• Agent access in the toolbar. A compact "Agents" status with the shared switch sits next to the menu button. The icon and tooltip tell four states apart: agents can't use browser tabs, agents can use all browser tabs, an agent is using this tab, and you have control of this tab. Take control and Resume agent stay where they were. The access row is gone from the menu.
• Access request. It now asks "Allow access to all browser tabs?" with Allow and Deny.
• Failed changes. If turning access on or off fails, the error says which change failed, and the panel re-reads the real access state, since a revocation can succeed even when its reply is lost.
• Action results near the toolbar. "Cookies cleared" and "Cache cleared" appear under the toolbar for a few seconds. Errors from navigation, take control, access changes and clearing stay there until dismissed or replaced, with the raw error as the tooltip.
• Clear cookies asks in a themed dialog: "Clear browser cookies?", "You'll be signed out of every site.", Cancel or Clear cookies.
• Menu. One icon family at one size. "Pin across threads" is now "Keep tab in every thread" with a tab glyph and a check when on. It and "Device toolbar" close the menu after selection. Zoom keeps the menu open so it can be pressed repeatedly.
• Kept tabs. A browser tab kept in every thread shows the tab glyph in the tab strip, with the tooltip "Kept in every thread".
• Device toolbar uses the shared select. Responsive shows "Auto", and other presets show the width, for example "390 px".
• Address field has the accessible label "Browser address".
• Start page. A new tab's start page uses the app theme background with the logo and one line, "Enter an address above". Visited sites keep their own appearance; only the app-owned blank page changed.

Verification

• npm run typecheck: passes.
• npx eslint on every changed source file: no errors. The three react-hooks/exhaustive-deps warnings in BrowserPanel.tsx (lines 440, 472, 539) are on lines already on the base branch.
• npx vitest run on the new test file, the browser tab tests, every unit test that references the changed browser files, and the icon and stylesheet tests: 17 files, 240 tests passed.
  • tests/renderer/browserToolbar.test.ts (new)
  • tests/browserTabs.test.ts
  • tests/reviewModel.test.ts
  • tests/movedShortcuts.test.ts
  • tests/pullRequestPanel.test.ts
  • tests/uiSelect.test.ts
  • tests/renderer/icons.test.ts
  • tests/renderer/providerIcons.test.ts
  • tests/renderer/composerRunControls.test.ts
  • tests/chatLayoutStyles.test.ts
  • tests/composerMentionList.test.ts
  • tests/titleBarLayout.test.ts
  • tests/slashCommandPopoverStyles.test.ts
  • tests/gitPanelLogic.test.ts
  • tests/updates/linuxLauncher.test.ts
  • tests/harness/boundary.test.ts
  • tests/testSelect.test.ts
• The new test file covers: the four access states staying distinct (a takeover still shows after access is turned off), the shared switch and its label, result and error notices with dismiss, the themed cookie dialog, "Auto" without px for Responsive, the shared device select, the start page's single instruction, and marking only tabs kept in every thread.
• Electron fixture tests were not run.

Before/after screenshots follow in a comment.

Notes

UI only. Access defaults, tab ownership, sessions and the browser control protocol are unchanged.

Refs #605