Compliant Chrome Extension Guidance

I need clear, Codex-friendly guidance and starter code for a Manifest V3 Chrome extension dedicated to data analysis of friend or follower activities on a social network. The work must stay fully inside both Chrome Web Store rules and the chosen platform’s terms of service.

Scope
• Outline which automation tasks Codex can safely generate—strictly read-only metrics and aggregated insights, no posting, scraping behind login barriers, or unsolicited actions.
• Provide a lightweight project skeleton: manifest.json, background/service worker, content script template, and a modular data-analysis module. Code comments should flag sections where Codex suggestions are safe versus sections that require manual vetting.
• Supply a checklist for permissions, OAuth scopes, and user consent flows that keep the extension compliant.

Deliverables
1. Written guideline (2–3 pages) detailing allowed vs. disallowed automation.
2. Starter code repository or ZIP with the files mentioned above, ready for Codex completion.
3. Quick-start README showing how to continue development in Visual Studio Code with the OpenAI extension enabled, including prompt examples.
4. Short compliance test plan to verify the finished extension before publishing.

I will consider the project complete once the code lints cleanly, loads in an unpacked state without warnings, and every guideline links back to the relevant policy clause.