Initial commit with release automation

Author: vijaythecoder

.editorconfig

@@ -0,0 +1,18 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 4
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.{yml,yaml}]
+indent_size = 2
+
+[docker-compose.yml]
+indent_size = 4

.env.example

@@ -0,0 +1,74 @@
+APP_NAME=Clueless
+APP_ENV=local
+APP_KEY=
+APP_DEBUG=true
+APP_URL=http://localhost
+
+APP_LOCALE=en
+APP_FALLBACK_LOCALE=en
+APP_FAKER_LOCALE=en_US
+
+APP_MAINTENANCE_DRIVER=file
+# APP_MAINTENANCE_STORE=database
+
+PHP_CLI_SERVER_WORKERS=4
+
+BCRYPT_ROUNDS=12
+
+LOG_CHANNEL=stack
+LOG_STACK=single
+LOG_DEPRECATIONS_CHANNEL=null
+LOG_LEVEL=debug
+
+DB_CONNECTION=sqlite
+# DB_HOST=127.0.0.1
+# DB_PORT=3306
+# DB_DATABASE=laravel
+# DB_USERNAME=root
+# DB_PASSWORD=
+
+SESSION_DRIVER=database
+SESSION_LIFETIME=120
+SESSION_ENCRYPT=false
+SESSION_PATH=/
+SESSION_DOMAIN=null
+
+BROADCAST_CONNECTION=log
+FILESYSTEM_DISK=local
+QUEUE_CONNECTION=database
+
+CACHE_STORE=database
+# CACHE_PREFIX=
+
+MEMCACHED_HOST=127.0.0.1
+
+REDIS_CLIENT=phpredis
+REDIS_HOST=127.0.0.1
+REDIS_PASSWORD=null
+REDIS_PORT=6379
+
+MAIL_MAILER=log
+MAIL_SCHEME=null
+MAIL_HOST=127.0.0.1
+MAIL_PORT=2525
+MAIL_USERNAME=null
+MAIL_PASSWORD=null
+MAIL_FROM_ADDRESS="[email protected]"
+MAIL_FROM_NAME="${APP_NAME}"
+
+AWS_ACCESS_KEY_ID=
+AWS_SECRET_ACCESS_KEY=
+AWS_DEFAULT_REGION=us-east-1
+AWS_BUCKET=
+AWS_USE_PATH_STYLE_ENDPOINT=false
+
+VITE_APP_NAME="${APP_NAME}"
+
+# AI Provider Keys
+OPENAI_API_KEY=
+ANTHROPIC_API_KEY=
+GEMINI_API_KEY=
+
+# Realtime API Configuration
+VITE_OPENAI_API_KEY="${OPENAI_API_KEY}"
+VITE_REALTIME_RELAY_URL=wss://localhost:8080/realtime

.gitattributes

@@ -0,0 +1,10 @@
+* text=auto eol=lf
+
+*.blade.php diff=html
+*.css diff=css
+*.html diff=html
+*.md diff=markdown
+*.php diff=php
+
+CHANGELOG.md export-ignore
+README.md export-ignore

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,48 @@
+---
+name: Bug Report
+about: Create a report to help us improve Clueless
+title: '[BUG] '
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Open the meeting assistant '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Actual behavior**
+A clear and concise description of what actually happened instead.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem. You can drag and drop images directly into this issue.
+
+**Environment Details**
+Please complete the following information:
+- **Operating System:** [e.g. macOS 14.5, Windows 11, Ubuntu 22.04]
+- **Browser (if web version):** [e.g. Chrome 120, Safari 17.2, Firefox 121]
+- **Application Version:** [e.g. 1.0.0, or commit hash if running from source]
+- **Desktop App (if using NativePHP):** [Yes/No]
+- **Node.js Version:** [if running from source, e.g. 20.10.0]
+- **PHP Version:** [if running from source, e.g. 8.2.14]
+
+**Meeting Context**
+If the bug occurred during a meeting:
+- **Meeting Type:** [e.g. Video call, Screen share, Audio only]
+- **Number of Participants:** [e.g. 2-5, 5-10, 10+]
+- **Features in Use:** [e.g. Transcription, Note-taking, Recording]
+
+**Additional context**
+Add any other context about the problem here. This might include:
+- Error messages or console logs
+- Whether the issue is reproducible or intermittent
+- Any workarounds you've discovered
+- Impact on your workflow

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,41 @@
+---
+name: Feature request
+about: Suggest an idea for this meeting assistant
+title: '[FEATURE] '
+labels: 'enhancement'
+assignees: ''
+
+---
+
+## Problem Description
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+## Proposed Solution
+<!-- A clear and concise description of what you want to happen. -->
+
+## Alternative Solutions Considered
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+## Use Case Examples
+<!-- Provide specific examples of how this feature would be used in real meeting scenarios -->
+
+### Example 1:
+<!-- Describe a specific meeting scenario where this feature would be helpful -->
+
+### Example 2:
+<!-- Another example if applicable -->
+
+## Additional Context
+<!-- Add any other context, mockups, or screenshots about the feature request here. -->
+
+### Technical Considerations
+<!-- If you have any thoughts on technical implementation, AI models, or integration requirements -->
+
+### Priority/Impact
+<!-- How important is this feature? How many users would it impact? -->
+
+## Checklist
+<!-- Put an 'x' in the boxes that apply -->
+- [ ] I have searched for similar feature requests
+- [ ] This feature would improve meeting productivity
+- [ ] This feature aligns with the app's AI-powered meeting assistant goals

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,105 @@
+# Pull Request
+
+## Description
+
+Please provide a brief description of the changes in this PR. Include the motivation for these changes and any relevant context.
+
+## Type of Change
+
+Please check the type of change your PR introduces:
+
+- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
+- [ ] ✨ New feature (non-breaking change which adds functionality)
+- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] 📝 Documentation update
+- [ ] 🎨 Code style update (formatting, renaming)
+- [ ] ♻️ Code refactoring (no functional changes, no API changes)
+- [ ] ⚡ Performance improvement
+- [ ] ✅ Test update
+- [ ] 🔧 Configuration change
+- [ ] 🏗️ Infrastructure/build change
+- [ ] 🔐 Security fix
+
+## Testing Performed
+
+Please describe the tests you've run to verify your changes. Provide instructions so reviewers can reproduce.
+
+- [ ] Unit tests pass locally (`composer test`)
+- [ ] Frontend builds successfully (`npm run build`)
+- [ ] Code follows project style guidelines (`php artisan pint` and `npm run format`)
+- [ ] Manual testing completed
+
+### Test Configuration
+- **PHP Version:**
+- **Node Version:**
+- **Browser (if applicable):**
+- **Operating System:**
+
+### Manual Testing Steps
+1. 
+2. 
+3. 
+
+## Checklist
+
+Please review the following items before submitting your PR:
+
+### Code Quality
+- [ ] My code follows the project's code style and conventions
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings or errors
+- [ ] TypeScript types are properly defined (no `any` types unless absolutely necessary)
+
+### Database Changes (if applicable)
+- [ ] I have created necessary migrations
+- [ ] Migrations have been tested on both databases (`database.sqlite` and `nativephp.sqlite`)
+- [ ] Database schema changes are backward compatible
+
+### Frontend Changes (if applicable)
+- [ ] Component changes follow Vue 3 Composition API patterns
+- [ ] UI components maintain consistency with existing design system
+- [ ] Changes are responsive and work on different screen sizes
+- [ ] Dark mode compatibility has been verified
+
+### Testing
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally
+- [ ] Any dependent changes have been merged and published
+
+## Related Issues
+
+Please link any related issues here using the format `Fixes #issue_number` or `Relates to #issue_number`
+
+- Fixes #
+- Relates to #
+
+## Screenshots (if applicable)
+
+If your changes include UI updates, please add screenshots showing:
+
+### Before
+<!-- Add screenshots of the current behavior -->
+
+### After
+<!-- Add screenshots showing your changes -->
+
+### Dark Mode (if UI changes)
+<!-- Add screenshots showing dark mode compatibility -->
+
+## Additional Notes
+
+Add any additional notes, concerns, or discussion points for reviewers.
+
+## Reviewer Checklist
+
+For reviewers to complete:
+
+- [ ] Code follows project conventions and style guide
+- [ ] Changes are well-documented and easy to understand
+- [ ] Tests adequately cover the changes
+- [ ] No security vulnerabilities introduced
+- [ ] Performance impact is acceptable
+- [ ] UI changes are consistent with design system
+- [ ] Database migrations are safe and reversible