Remove stale CLAUDE.md note about an already-merged PR

The "not merged yet" branch-workflow paragraph got reintroduced by a
merge from a stale local branch (PR #4) that hadn't been rebased since
before PR #2 actually merged. That PR (and everything after it,
including production) has long since landed.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01Tn7uDYjTuZEbLPwpEiSCUw

CLAUDE.md

@@ -4,8 +4,6 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 ## Repository state
 
-All work to date landed on `feat/real-wallet-auth-and-backend-connection`, not directly on `master` — open as [PR #2](https://github.com/nexa-sol/copilot/pull/2) (React popup, real Phantom wallet auth, live backend connection, Firefox fixes). Not merged yet; pairs with backend PR #1 (same wallet-auth + lock-state wire protocol, client vs. server side). New work should branch from here (or off `master` once #2 merges) rather than committing straight to `master`.
-
 Scaffolded with [WXT](https://wxt.dev) (Vite-based, TypeScript-first, built on top of `webextension-polyfill` for the cross-browser `browser.*` API) — the popular framework for building Manifest V3 extensions that target both Firefox and Chromium from one codebase. Package manager: npm.
 
 The popup is a real React app (`@wxt-dev/module-react` in `wxt.config.ts`, `src/entrypoints/popup/App.tsx` + `main.tsx` mounted via `createRoot`) — not plain DOM manipulation. Note: WXT's generated `.wxt/tsconfig.json` doesn't set `compilerOptions.jsx`, so the root `tsconfig.json` sets `"jsx": "react-jsx"` explicitly; without it `tsc --noEmit` fails on JSX syntax even though the Vite build itself is fine (esbuild doesn't need the tsconfig flag).