Cline rules

1---
2description: Build, manifest, and packaging rules for webpack, esbuild, and browser-specific extension output
3globs: ["package.json", "tsconfig.json", "webpack.config.js", "build/**/*.js", "src/manifest*.json"]
4alwaysApply: false
5---
6 
7Build and packaging rules:
8- Preserve the existing combination of Webpack and esbuild.
9- Do not replace the current build pipeline unless explicitly asked.
10- Keep browser-compatible output aligned with the configured target (`chrome88`).
11- Respect the separation between generic build logic and Chrome-specific build behavior.
12 
13Manifest safety:
14- Treat `src/manifest.chrome.json` and `src/manifest.firefox.json` as sensitive files.
15- Do not add, remove, or broaden `permissions`, `host_permissions`, or `content_scripts.matches` unless explicitly requested.
16- Avoid changes that would increase extension warnings or broaden site access without a clear need.
17- Keep Chrome and Firefox packaging behavior aligned unless a browser-specific difference is required and documented.
18 
19Editing behavior:
20- If changing a manifest or build file, explain why the change is needed.
21- Prefer the smallest change that preserves current packaging behavior.