feat(ai-wattch): complete extension

Author: Ganesh Mohanty

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Require admin approvals for the entire repo
+* @KothariEbrahim 

.github/workflows/auto-pr-on-push.yml

@@ -0,0 +1,52 @@
+name: Auto-create PR on branch push
+
+on:
+  push:
+    # Runs for any branch except main
+    branches-ignore: ['main']
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  create-pr:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Create PR if none exists
+        uses: actions/github-script@v6
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const owner = context.repo.owner;
+            const repo = context.repo.repo;
+            const headRef = context.ref.replace('refs/heads/','');
+            if (!headRef || headRef === 'main') {
+              core.info('No branch or branch is main — exit.');
+              return;
+            }
+
+            // Check for an existing open PR from this branch
+            const existing = await github.rest.pulls.list({
+              owner, repo,
+              head: `${owner}:${headRef}`,
+              state: 'open'
+            });
+
+            if (existing.data.length > 0) {
+              core.info(`Open PR already exists: ${existing.data[0].html_url}`);
+              return;
+            }
+
+            // Create PR into main
+            const title = `Auto PR: ${headRef}`;
+            const body = `This pull request was auto-created from a push to branch \`${headRef}\`. Please review and approve.`;
+            const pr = await github.rest.pulls.create({
+              owner, repo,
+              head: headRef,
+              base: 'main',
+              title,
+              body
+            });
+
+            core.info(`Created PR: ${pr.data.html_url}`);

.gitignore

@@ -0,0 +1,88 @@
+# Dependencies
+node_modules/
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Build outputs
+dist/
+build/
+build-*/
+*.zip
+!releases/*.zip
+
+
+# Environment variables
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# IDE files
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# Logs
+logs
+*.log
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# nyc test coverage
+.nyc_output
+
+# Dependency directories
+jspm_packages/
+
+# Optional npm cache directory
+.npm
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# next.js build output
+.next
+
+# nuxt.js build output
+.nuxt
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+
+dist/
+
+.claude

AUTHORS.md

@@ -0,0 +1,11 @@
+# Authors
+
+This project is maintained by the teams at **Antarctica** and **IT Climate Ed**.
+
+## Contributors
+
+We would like to thank all the contributors who have and intend to help improve AI Wattch.
+
+---
+
+Interested in contributing? Check out our [CONTRIBUTING.md](./CONTRIBUTING.md) to get started!

CODE_OF_CONDUCT.md

@@ -0,0 +1,43 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at conduct@itclimateed.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at [http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4).

CONTRIBUTING.md

@@ -0,0 +1,137 @@
+# Contributing to AI Wattch
+
+Thank you for your interest in contributing! We aim to keep the process as simple, transparent, and collaborative as possible.
+
+## ⚖️ Contributing & Governance
+
+We welcome contributions. Please follow these steps:
+
+1.  **Fork the repo**.
+2.  **Create a branch**: `feature/<short-description>`.
+3.  **Commit with a clear message** and open a PR.
+4.  **Add tests and update docs**.
+5.  **One feature per PR**; link relevant issue.
+
+### Pre-PR Discussion
+
+For major architectural or methodology changes, **open an issue first** to discuss design and data assumptions.
+
+- **Methodology is research-sensitive**: Maintain transparency in how variables are chosen.
+- **Cite sources**: Include citations and data sources in your PR descriptions.
+
+### Docs to Add/Maintain
+
+- [`CONTRIBUTING.md`](./CONTRIBUTING.md) (detailed)
+- [`CODE_OF_CONDUCT.md`](./CODE_OF_CONDUCT.md)
+- [`SECURITY.md`](./SECURITY.md) (vulnerability reporting)
+
+## 🚀 Development Workflow
+
+### 1. Fork & Clone
+
+```bash
+git clone https://github.com/AIWattch/AI-Wattch.git
+cd ai-wattch-ext
+```
+
+### 2. Install Dependencies
+
+```bash
+npm install
+```
+
+### 3. Development Build
+
+To start the development server with Hot Module Replacement (HMR):
+
+```bash
+npm run dev
+```
+
+### 4. Production Build
+
+To build the extension for both Chrome and Firefox:
+
+```bash
+npm run build:extension
+```
+
+This script will:
+
+- Clean previous builds
+- Build for Firefox (output in `build-firefox`)
+- Build for Chrome (output in `build-chrome`)
+- Create ZIP packages for distribution
+
+### 5. Load Extension
+
+**Chrome:**
+
+1. Open `chrome://extensions/`
+2. Enable **Developer mode** (top right)
+3. Click **Load unpacked**
+4. Select the `dist` folder (for dev) or `build-chrome` folder (for production build)
+
+**Firefox:**
+
+1. Open `about:debugging`
+2. Click **This Firefox**
+3. Click **Load Temporary Add-on**
+4. Select the `manifest.json` file from the `dist` or `build-firefox` folder
+
+## 🧩 Project Structure
+
+```
+/src
+  /assets       # Static assets (images, fonts)
+  /background   # Background service workers
+  /constants    # Global constants and configuration
+  /content      # Content scripts injected into pages
+  /core         # Core logic (emissions calculation, etc.)
+  /icons        # Icon assets
+  /modules      # Feature modules
+  /shared       # Shared utilities and components
+  /types        # TypeScript type definitions
+  /utils        # General utility functions
+```
+
+## 🧑‍💻 Code Style & Standards
+
+To maintain a consistent and clean codebase:
+
+- **TypeScript**: Use TypeScript for all new code.
+- **Functions**: Keep functions small, predictable, and pure where possible.
+- **Comments**: Add comments for complex or non-obvious logic.
+- **Utilities**: Reuse existing utilities in `src/shared` or `src/utils` — avoid duplication.
+- **Modern Syntax**: Prefer ES modules and modern syntax.
+
+## 🔧 Pull Request Process
+
+1. **Keep PRs small**: Small, focused PRs are reviewed & merged faster.
+2. **Follow Conventional Commits**:
+   - `feat(ui): add new emissions widget`
+   - `fix(api): correct model detection`
+   - `chore(build): update Vite config`
+3. **Update Documentation**: Update README or comments if you change user-facing features or complex logic.
+4. **Verify**: Ensure the extension builds and loads correctly in the browser.
+
+## 🐞 Reporting Bugs
+
+When filing an issue, please include:
+
+- Browser version (Chrome, Edge, Firefox, etc.)
+- Extension version
+- Steps to reproduce
+- Expected vs. actual behavior
+- Screenshots / logs (if applicable)
+
+## ✨ Requesting New Features
+
+Before submitting a feature request:
+
+1. Check if the feature already exists or is open as an issue.
+2. Clearly describe the use case and value.
+
+## 💬 Questions? Need Help?
+
+Open a GitHub Issue or Discussions thread. Maintainers are happy to help!

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 AIWattch
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.