Prioritize Chrome Web Store installation across docs and release metadata

[Copilot]

• Re-check latest failing workflow runs and retrieve exact logs for the reported ESLint error
• Find all workflows/jobs still running npx eslint . --ext .js,.jsx,.ts,.tsx
• Apply minimal workflow fix so CI uses the repository ESLint config format reliably
• Run targeted local validation for the updated lint command(s) and build/typecheck
• Commit only required changes, run final validation, and reply on the PR comment with commit hash

[paladini]

@copilot resolva os problemas de build desse PR

[Copilot]

@copilot resolva os problemas de build desse PR

Ajustei os problemas de build/CI do PR no commit 84b6b2d. O workflow de CI agora valida com npm run lint (typecheck) + npm run build, e os erros de TypeScript no popup foram corrigidos com tipagem explícita para chrome e ReactElement. Não houve alteração visual de UI neste ajuste.

[paladini]

@copilot continuo tendo problemas no workflow!! Erro abaixo:

Run npx eslint . --ext .js,.jsx,.ts,.tsx
npm warn exec The following package was not found and will be installed: eslint@10.2.1

Oops! Something went wrong! :(

ESLint: 10.2.1

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

Error: Process completed with exit code 2.

[Copilot]

@copilot continuo tendo problemas no workflow!! Erro abaixo:

...

Corrigi esse problema no commit f0af136. Adicionei eslint.config.js (flat config) e dependências locais de lint no package.json, então npx eslint . --ext .js,.jsx,.ts,.tsx passa sem tentar usar configuração inexistente. Também validei npm run lint e npm run build com sucesso. Screenshot: N/A (não houve alteração de UI).