#9398: Fix browser extension install path calculation

## Summary Fixes the `openclaw browser extension install` command that was failing with "Bundled Chrome extension is missing" error. ## Changes Changed path resolution in `bundledExtensionRootDir()` from `../../assets/chrome-extension` to `../assets/chrome-extension`. ## Root Cause From `dist/index.js`, the old path incorrectly resolved to: - `/usr/local/lib/node_modules/assets/chrome-extension` ❌ After fix, it correctly resolves to: - `/usr/local/lib/node_modules/openclaw/assets/chrome-extension` ✅ ## Testing This is a one-line path fix following the exact solution provided in the issue report. Fixes #9397 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates the bundled Chrome extension path resolution used by `openclaw browser extension install`. Specifically, `bundledExtensionRootDir()` now resolves `../assets/chrome-extension` relative to the built file’s directory, which aligns with the packaged layout where `dist/cli/*` and `dist/assets/*` are siblings. The change is localized to `src/cli/browser-cli-extension.ts` and affects only how the installer finds the bundled extension assets (`manifest.json`, icons, etc.) before copying them into the user’s state directory. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk. - The change is a single path resolution adjustment scoped to the browser extension install flow, and it matches the expected dist/package directory structure (assets next to compiled CLI files). No other call sites or behavioral changes were introduced. - No files require special attention <!-- greptile_other_comments_section --> <!-- /greptile_comment -->