Ship the bridge extension inside the framework package, so the bridge browser works from npx

[suleimansh]

Follow-up to #1332 / #1718. The daemon's bridge browser installs the extension from packages/chrome-extension next to the framework package — the checkout's copy. The published framework package ships dist only (package.json files), so on an npx the-framework install the launch fails with "the extension files are not beside this package (packages/chrome-extension): the bridge browser runs from a checkout".

Until this is done, the recommended "A browser the daemon runs" option in Settings only works for people running from a git checkout — i.e. us.

What it takes

• Copy packages/chrome-extension into the package at build time (e.g. dist/chrome-extension) and have bridgeExtensionDir() look there first, then the checkout path.
• The extension's self-reload (The extension reloads itself when its files on disk change (#1711) #1712) watches its own files, so a copy under dist reloads when the package is rebuilt — same as an edit in the checkout.
• Lockstep (Extension/backend version mismatch: throw and block, not a warning #1519) is unaffected: the copy carries the version the daemon expects, by construction.

Not the Web Store: that route needs the exact-version lockstep relaxed to a minimum version first (#1519), since store updates arrive days after a release, and it is the right long-term path for the user's-own-Chrome option; this ticket is only about the daemon's browser, which never needs the store.

🤖 curated · Fable 5, effort high