feat: Add logout endpoint and dashboard logout button (NEWS-1)

.claude/commands/analyze_bug.md

@@ -0,0 +1,7 @@
+<sentry_issue>
+#$ARGUMENTS
+</sentry_issue>
+investigate this sentry_issue, I don't want you to perform actions, just investigate it
+
+
+/analyze_bug https://sentry/.....

.claude/commands/develop-us.md

@@ -0,0 +1,15 @@
+Please analyze and fix the Jira ticket: $ARGUMENTS.
+
+Follow these steps:
+
+1. Use Jira MCP to get the ticket details, whether it is the ticket id/number, keywords referring to the ticket or indicating status, like "the one in progress"
+2. Understand the problem described in the ticket
+3. Search the codebase for relevant files
+4. Start a new branch using the ID of the ticket (for example NEWS-1)
+5. Implement the necessary changes to solve the ticket 
+6. Write and run tests to verify the solution
+7. Ensure code passes linting and type checking
+8. Create a descriptive commit message that includes the Jira ticket ID (e.g., "NEWS-1") in both the commit title and description for proper linking
+9. Push and create a PR, including the Jira ticket ID (e.g., "NEWS-1") in the PR title and description so it gets linked in the Jira ticket
+
+Remember to use the GitHub CLI (`gh`) for all GitHub-related tasks.

.claude/commands/e2e.md

@@ -0,0 +1,214 @@
+# E2E Testing Command
+
+**Description**: Run E2E tests with Playwright using the qa-criteria-validator agent
+
+**Usage**: Use `/e2e` command followed by optional test type
+
+## Command Options
+
+- `/e2e` - Interactive mode (choose what to test)
+- `/e2e full` - Run complete E2E test suite
+- `/e2e login` - Test login functionality specifically
+- `/e2e logout` - Test logout functionality specifically
+- `/e2e profile` - Test profile management functionality
+- `/e2e auth` - Test all authentication flows
+- `/e2e dashboard` - Test dashboard functionality
+- `/e2e [feature]` - Test specific feature by name
+
+## Implementation
+
+When this command is invoked, Claude should:
+
+1. **Check Application Status**
+   - Verify frontend server is running on http://localhost:5173
+   - Verify backend server is running on http://localhost:8000
+   - Alert user if servers need to be started
+
+2. **Launch qa-criteria-validator Agent**
+   - Use the Task tool with subagent_type: "qa-criteria-validator"
+   - Pass appropriate test prompt based on command argument
+
+3. **Test Prompts by Type**
+
+### Full Test Suite (`/e2e full`)
+```
+Please run comprehensive E2E tests for the entire React FastAPI application using Playwright.
+
+Test the following key areas:
+1. User authentication (login/logout)
+2. Dashboard functionality and navigation
+3. Profile management (view/edit/password change)
+4. Protected route access
+5. Error handling and edge cases
+6. User session management
+
+Application details:
+- Frontend: React app on http://localhost:5173
+- Backend: FastAPI on http://localhost:8000
+- Authentication: OAuth2 with JWT tokens
+
+Please start both servers if needed and provide a comprehensive test report.
+```
+
+### Logout Testing (`/e2e logout`)
+```
+Please test the logout functionality thoroughly using Playwright.
+
+Focus on:
+1. Logout button accessibility from dashboard
+2. Backend logout endpoint call (POST /api/v1/auth/logout)
+3. Token clearing from localStorage/sessionStorage
+4. Redirection to login page
+5. Protected route access prevention after logout
+6. Error handling scenarios
+
+Application details:
+- Frontend: http://localhost:5173
+- Backend: http://localhost:8000
+- Key components: DashboardHeader, useLogout mutation, useAuthContext
+
+Provide detailed test results and any issues found.
+```
+
+### Login Testing (`/e2e login`)
+```
+Please test the login functionality comprehensively using Playwright.
+
+Test scenarios:
+1. Valid credential login
+2. Invalid credential handling
+3. Form validation
+4. Token storage and session management
+5. Redirection to dashboard after login
+6. Protected route access after login
+7. Remember me functionality (if applicable)
+
+Application details:
+- Frontend: http://localhost:5173
+- Backend: http://localhost:8000
+- Login endpoint: POST /api/v1/auth/login
+
+Provide comprehensive test results and security validation.
+```
+
+### Authentication Flows (`/e2e auth`)
+```
+Please run comprehensive authentication flow tests using Playwright.
+
+Test the complete authentication cycle:
+1. User registration (if available)
+2. Login with various scenarios
+3. Protected route access
+4. Session management
+5. Logout functionality
+6. Token refresh (if applicable)
+7. Security edge cases
+
+Application details:
+- Frontend: http://localhost:5173
+- Backend: http://localhost:8000
+- Authentication: OAuth2 with JWT
+
+Provide detailed security assessment and functionality report.
+```
+
+### Profile Management (`/e2e profile`)
+```
+Please test the profile management functionality using Playwright.
+
+Test areas:
+1. Profile view and data display
+2. Profile editing functionality
+3. Password change feature
+4. Form validation
+5. Error handling
+6. Data persistence
+7. Navigation and user experience
+
+Application details:
+- Frontend: http://localhost:5173
+- Backend: http://localhost:8000
+- Profile routes and components
+
+Provide detailed test results for all profile features.
+```
+
+### Dashboard Testing (`/e2e dashboard`)
+```
+Please test the dashboard functionality using Playwright.
+
+Test scenarios:
+1. Dashboard loading and display
+2. Navigation elements
+3. User information display
+4. Interactive elements
+5. Responsive design
+6. Header functionality
+7. Menu and routing
+
+Application details:
+- Frontend: http://localhost:5173
+- Dashboard components and navigation
+
+Provide comprehensive dashboard functionality report.
+```
+
+### Custom Feature Testing (`/e2e [feature]`)
+```
+Please test the "{feature}" functionality using Playwright.
+
+Focus on comprehensive testing of this specific feature including:
+1. Core functionality
+2. User interactions
+3. Form validation and data handling
+4. Error scenarios
+5. Navigation and routing
+6. Integration with backend APIs
+7. User experience and accessibility
+
+Application details:
+- Frontend: React app on http://localhost:5173
+- Backend: FastAPI on http://localhost:8000
+
+Please provide detailed test results for the "{feature}" feature.
+```
+
+### Interactive Mode (`/e2e`)
+When no argument is provided, Claude should ask the user to choose from:
+1. Full application test suite
+2. Login functionality
+3. Logout functionality
+4. Profile management
+5. Authentication flows
+6. Dashboard functionality
+7. Custom feature (user specifies)
+
+## Example Usage in Claude Code
+
+**User types**: `/e2e logout`
+
+**Claude should respond**:
+"I'll run E2E tests for the logout functionality using Playwright. Let me launch the qa-criteria-validator agent to test this thoroughly."
+
+Then execute:
+```
+Task tool with:
+- subagent_type: "qa-criteria-validator"
+- description: "Test logout functionality with Playwright"
+- prompt: [logout testing prompt from above]
+```
+
+## Prerequisites
+
+- Frontend server running on http://localhost:5173
+- Backend server running on http://localhost:8000
+- qa-criteria-validator agent has access to Playwright tools
+- Test user credentials available for authentication
+
+## Notes
+
+- Always check server status before testing
+- Provide clear feedback about what's being tested
+- Include server startup instructions if servers aren't running
+- Generate comprehensive test reports
+- Handle edge cases and error scenarios

.claude/commands/worktree-from-ticket.md

@@ -0,0 +1,9 @@
+<jira_ticket>
+#$ARGUMENTS
+</jira_ticket>
+1- git worktree add ./.trees/feature-issue-$ARGUMENTS -b feature-issue-$ARGUMENTS
+2- cd .trees/feature-issue-$ARGUMENTS
+3- activate plan mode on
+4- analyze the Jira ticket #$ARGUMENTS using MCP
+5- determine the agents to be used and if they can be paralelized
+6- at the end after the confirmation of the user, commit the changes and push them to the branch