feat: Added Verification script

Author: STAR-173

.gitignore

@@ -33,10 +33,6 @@ env/
 ENV/
 .venv/
 
-# --- Verification ---
-verify_aistudio.py
-verify_flow.py
-
 # --- Playwright ---
 test-results/
 playwright-report/

CONTRIBUTING.md

@@ -1,92 +1,187 @@
 # Contributing to LLMSession
 
-Thank you for your interest in contributing to **LLMSession**! This project is a monorepo containing both the Python and Node.js implementations. We welcome contributions to either (or both) parts of the library.
+Thank you for your interest in contributing to **LLMSession**! We welcome all contributions including bug fixes, new features, documentation improvements, and more.
 
-## 1. Project Structure
+## Project Structure
 
-*   **`python/`**: Contains the Python source code and packaging config.
-*   **`node/`**: Contains the TypeScript source code and NPM config.
+*   **`src/`**: Contains the Python source code
+*   **`verify_flow.py`**: Verification script for testing
+*   **`verify_aistudio.py`**: Additional verification script
+*   **`.github/workflows/`**: CI/CD workflows for automated publishing
+*   **`pyproject.toml`**: Package configuration and dependencies
 
-Please ensure you are working in the correct subdirectory for your changes.
+## Development Setup
 
-## 2. Python Development
+### 1. Fork and Clone
 
-### Setup
-1.  Navigate to the python directory: `cd python`
-2.  Create a virtual environment (optional but recommended):
+1.  Fork the repository on GitHub
+2.  Clone your fork locally:
+    ```bash
+    git clone https://github.com/YOUR_USERNAME/llm_session.git
+    cd llm_session
+    ```
+
+### 2. Set Up Development Environment
+
+1.  Create a virtual environment (recommended):
     ```bash
     python -m venv venv
     source venv/bin/activate  # Linux/Mac
     # or
     .\venv\Scripts\activate   # Windows
     ```
-3.  Install the package in **Editable Mode**:
+
+2.  Install the package in **Editable Mode**:
     ```bash
     pip install -e .
     ```
     *This allows you to modify code in `src/` and test it immediately without reinstalling.*
 
-### Testing
-We use a manual verification script to test the full flow (Browser launch -> Auth -> Prompt).
+3.  Install build tools (optional, for testing builds):
+    ```bash
+    pip install build
+    ```
+
+### 3. Testing Your Changes
+
+We use manual verification scripts to test the full flow (Browser launch → Auth → Prompt).
+
 ```bash
 python verify_flow.py
 ```
-*Tip: You can modify `verify_flow.py` to use `headless=False` to watch the bot work.*
 
-## 3. Node.js Development
+*Tip: You can modify `verify_flow.py` to use `headless=False` to watch the bot work in real-time.*
+
+### 4. Building Locally
+
+To test the build process locally before pushing:
+
+```bash
+python -m build
+```
+
+This will create distribution files in the `dist/` directory.
+
+## Safety Warning (Credentials)
 
-### Setup
-1.  Navigate to the node directory: `cd node`
-2.  Install dependencies:
+To test changes, you will likely need to put real credentials into `verify_flow.py`.
+
+> [!CAUTION]
+> **NEVER commit files containing your real passwords.**
+> If you modify the verification scripts with real credentials, please revert those changes before pushing, or ensure they are ignored by git.
+
+## Pull Request Process
+
+1.  **Fork & Clone**: Fork the repo and clone it locally (see above)
+2.  **Branch**: Create a feature branch from `main`:
     ```bash
-    npm install
+    git checkout -b feature/your-feature-name
     ```
-
-### Building
-Since this is a TypeScript project, you must compile the code.
-*   **One-off build**:
+3.  **Code**: Implement your changes
+    *   Adhere to **PEP 8** style guidelines
+    *   Add docstrings to new functions and classes
+    *   Keep code clean and well-commented
+4.  **Test**: Run the verification scripts to ensure everything works:
     ```bash
-    npm run build
+    python verify_flow.py
     ```
-*   **Watch mode (Recommended for Dev)**:
+5.  **Commit**: Use clear, descriptive commit messages:
     ```bash
-    npx tsc -w
+    git commit -m "Add feature: description of what you added"
     ```
-    *Keep this running in a separate terminal to auto-compile changes.*
+6.  **Push**: Push to your fork:
+    ```bash
+    git push origin feature/your-feature-name
+    ```
+7.  **Open PR**: Open a Pull Request against the `main` branch on GitHub
 
-### Testing
-To run the verification flow using `ts-node` (skips build step) or the compiled dist:
-```bash
-# Run directly from TypeScript source
-npx ts-node verify_flow.ts
-```
+## Code Style Guidelines
 
-## 4. Safety Warning (Credentials)
+*   Follow **PEP 8** conventions for Python code
+*   Use meaningful variable and function names
+*   Add comments for complex logic
+*   Keep functions focused and single-purpose
+*   Add type hints where appropriate
 
-To test changes, you will likely need to put real credentials into `verify_flow.py` or `verify_flow.ts`.
+## Types of Contributions
 
-> [!CAUTION]
-> **NEVER commit files containing your real passwords.**
-> If you modify the verification scripts with real credentials, please revert those changes before pushing, or ensure they are ignored.
+### Bug Fixes
+
+If you're fixing a bug:
+1.  Describe the bug in your PR
+2.  Explain how your fix resolves it
+3.  Test thoroughly before submitting
+
+### New Features
+
+If you're adding a new feature:
+1.  Open an issue first to discuss the feature
+2.  Wait for maintainer feedback before implementing
+3.  Update documentation (README.md) if needed
+4.  Add examples showing how to use the feature
+
+### Documentation
 
-## 5. Pull Request Process
+Documentation improvements are always welcome:
+*   Fix typos or unclear explanations
+*   Add more examples
+*   Improve API documentation
+*   Update outdated information
 
-1.  **Fork & Clone**: Fork the repo and clone it locally.
-2.  **Branch**: Create a feature branch (`git checkout -b feature/amazing-feature`).
-3.  **Code**: Implement your changes.
-    *   **Python**: Adhere to PEP 8.
-    *   **Node**: Adhere to standard ESLint/Prettier conventions.
-4.  **Verify**: Run the verification scripts in both languages if your change affects shared logic (like selectors).
-5.  **Commit**: Use descriptive commit messages.
-6.  **Push & PR**: Push to your fork and open a Pull Request against `main`.
+### Updating Selectors
 
-## 6. Adding New Selectors
+If you're fixing broken selectors because ChatGPT updated their UI:
+1.  Update `src/llm_session/providers/chatgpt.py`
+2.  Test thoroughly with the verification script
+3.  Document which elements changed in your PR description
 
-If you are fixing a broken selector because ChatGPT updated their UI:
-1.  Update `python/src/llm_session/providers/chatgpt.py`
-2.  Update `node/src/providers/ChatGPT.ts`
-3.  **Please update both** if possible to keep the libraries in sync.
+## Automated Publishing (For Maintainers)
+
+This project uses **GitHub Actions** for automated publishing to PyPI:
+
+*   **Push to `main`**: Automatically publishes to TestPyPI for testing
+*   **Push a version tag** (e.g., `v0.1.4`): Automatically publishes to PyPI
+
+### Creating a Release (Maintainers Only)
+
+1.  Update version in `pyproject.toml`:
+    ```toml
+    version = "0.1.4"
+    ```
+
+2.  Commit and push:
+    ```bash
+    git add pyproject.toml
+    git commit -m "Release version 0.1.4"
+    git push origin main
+    ```
+
+3.  Create and push a tag:
+    ```bash
+    git tag v0.1.4
+    git push origin v0.1.4
+    ```
+
+4.  The GitHub Actions workflow will automatically build and publish to PyPI
+
+## Getting Help
+
+If you need help with contributing:
+*   Open a [GitHub Discussion](https://github.com/star-173/llm_session/discussions)
+*   Check existing [Issues](https://github.com/star-173/llm_session/issues)
+*   Reach out to maintainers in your PR
+
+## Code of Conduct
+
+*   Be respectful and constructive
+*   Welcome newcomers and help them learn
+*   Focus on what is best for the community
+*   Show empathy towards other community members
 
 ## License
 
-By contributing, you agree that your contributions will be licensed under the MIT License.
+By contributing, you agree that your contributions will be licensed under the MIT License.
+
+---
+
+Thank you for contributing to LLMSession! 🎉