@mc1global/opencode-jarvis 0.13.1 → 0.14.0

package/.opencode/devlogs/menu-ocr/2026-02-07-2044-Prompt Templates - Seed Data and Provider Model Selection.md

@@ -1,451 +0,0 @@
-# Devlog: Prompt Templates - Seed Data and Provider Model Selection
-
-**Devlog ID**: 2026-02-07-2044-menu-ocr
-**Instance**: menu-ocr
-**Started**: 2026-02-07 20:44
-**Workspace**: jarvis-opencode
-
----
-
-## Overview
-
-(Describe the goals and scope of this development log)
-
----
-
-## Progress
-
-(Progress updates will be added here)
-
----
-
-## Notes
-
-(Additional notes)
-
----
-
-## Goals
-
-1. **Seed Data**: Registrar versão inicial (seed) dos prompt templates para que o sistema inicie com dados padrão
-2. **Provider/Model por Etapa**: Cada etapa do pipeline deve permitir definir qual provider (anthropic, openai, gemini) e modelo específico usar
-
-## Current State Analysis
-
-- Prompt Templates existem mas iniciam vazios (sem seed data)
-- Não há campo para definir provider/modelo por template
-- Pipeline stages não têm configuração de qual AI usar
-
-## Expected Outcome
-
-- Sistema inicia com templates padrão funcionais
-- Admin pode configurar provider + modelo para cada etapa
-- Pipeline usa a configuração definida em cada template
-
----
-
-## Sprint Plan - EP-012
-
-### Epic Criado
-- **ID**: EP-011 (auto-incrementado pelo sistema)
-- **Título**: EP-012: Prompt Templates - Seed Data e Provider/Model Selection
-- **Workspace**: menu-ocr
-
-### Cards do Sprint (8 cards)
-
-| Card | Tipo | Título | Pts | Dependência |
-|------|------|--------|-----|-------------|
-| CD-203 | Backend | Schema: campos provider e model | 2 | - |
-| CD-204 | Backend | defaultPrompts.ts com defaults | 2 | CD-203 |
-| CD-205 | Backend | Auto-seed no startup | 2 | CD-204 |
-| CD-206 | Backend | Endpoint GET /providers/models | 2 | CD-203 |
-| CD-207 | Frontend | Dropdowns provider/model | 3 | CD-206 |
-| CD-208 | Frontend | Listagem com provider/model | 2 | CD-203 |
-| CD-209 | Backend | PromptManager integração | 3 | CD-203 |
-| CD-210 | Test | Testes unitários | 2 | CD-205, CD-209 |
-
-**Total: 18 story points**
-
-### Providers e Modelos Suportados
-
-```typescript
-const SUPPORTED_PROVIDERS = {
-  anthropic: {
-    name: 'Anthropic',
-    models: [
-      { id: 'claude-sonnet-4-20250514', name: 'Claude Sonnet 4', recommended: true },
-      { id: 'claude-3-haiku-20240307', name: 'Claude 3 Haiku', description: 'Fast & cheap' }
-    ]
-  },
-  openai: {
-    name: 'OpenAI',
-    models: [
-      { id: 'gpt-4o', name: 'GPT-4o', recommended: true },
-      { id: 'gpt-4o-mini', name: 'GPT-4o Mini', description: 'Faster' }
-    ]
-  },
-  gemini: {
-    name: 'Google Gemini',
-    models: [
-      { id: 'gemini-1.5-flash', name: 'Gemini 1.5 Flash', recommended: true },
-      { id: 'gemini-1.5-pro', name: 'Gemini 1.5 Pro', description: 'More capable' }
-    ]
-  },
-  perplexity: {
-    name: 'Perplexity',
-    models: [
-      { id: 'sonar', name: 'Sonar', recommended: true },
-      { id: 'sonar-pro', name: 'Sonar Pro', description: 'Enhanced' }
-    ]
-  }
-};
-```
-
-### Defaults por Categoria
-
-| Categoria | Provider | Model | Razão |
-|-----------|----------|-------|-------|
-| menu_extraction | anthropic | claude-sonnet-4-20250514 | Alta precisão OCR |
-| item_parsing | openai | gpt-4o | Bom parsing estruturado |
-| price_extraction | gemini | gemini-1.5-flash | Rápido e barato |
-| auto_curation | perplexity | sonar | Pesquisa web necessária |
-| batch_curation | perplexity | sonar | Pesquisa web necessária |
-| validation | gemini | gemini-1.5-flash | Validação simples |
-| general | anthropic | claude-sonnet-4-20250514 | Default seguro |
-
-### Diagrama de Dependências
-
-```
-CD-203 (schema)
-    ├── CD-204 (defaults) ──► CD-205 (auto-seed)
-    ├── CD-206 (endpoint) ──► CD-207 (dropdown) 
-    │                    └──► CD-208 (listagem)
-    └── CD-209 (integração)
-                              └──► CD-210 (testes)
-```
-
-### Context Memory
-- **Session**: ep_012:_prompt_templates--20260207_204723
-- **Note**: #353 (sprint plan)
-
----
-
-## Próximo Passo
-
-Mover CD-203 para grooming e iniciar implementação do schema.
-
-### Update - 2026-02-07 21:05
-
-Sprint Plan EP-012 criado com 8 cards (CD-203 a CD-210). Context memory session iniciada. Kanban board configurado. Pronto para implementação.
-
----
-
-## 🔄 PLANO REVISADO - GCP Parameter Manager
-
-### Mudança de Estratégia
-
-| Antes | Depois |
-|-------|--------|
-| Campos no schema MongoDB | GCP Parameter Manager |
-| Migration necessária | Zero migration |
-| Queries extras | Cache em memória |
-| Config por template | Config por categoria |
-
-### Motivo da Mudança
-
-- MongoDB é muito recurso para configuração simples
-- Já temos padrão com ProviderKeyManager (Secret Manager)
-- Parameter Manager é ideal para configurações de runtime
-
-### Cards Arquivados (Abordagem Antiga)
-- CD-203 a CD-210 → status: archived
-
-### Novos Cards (6 cards)
-
-| Card | Tipo | Título | Dependência |
-|------|------|--------|-------------|
-| CD-211 | Backend | PipelineConfigManager | - |
-| CD-212 | Backend | Endpoints GET/PUT /admin/pipeline-config | CD-211 |
-| CD-213 | Backend | Auto-seed Prompt Templates | - |
-| CD-214 | Backend | Integrar PromptManager com PipelineConfig | CD-211 |
-| CD-215 | Frontend | PipelineConfigView | CD-212 |
-| CD-216 | DevOps | Criar parameter no GCP | - |
-
-### Arquitetura Nova
-
-```
-┌─────────────────────────────────────────────────────────────────────────┐
-│                    PIPELINE CONFIGURATION                                │
-├─────────────────────────────────────────────────────────────────────────┤
-│                                                                         │
-│  Admin Portal              Backend API              GCP Parameter Mgr   │
-│  ─────────────             ───────────              ─────────────────   │
-│  • PipelineConfigView      • PipelineConfigManager  • menu-ocr-pipeline │
-│  • Dropdowns provider      • /admin/pipeline-config • JSON config       │
-│  • Dropdowns model         • Cache 5-min TTL        • Hot reload        │
-│                                                                         │
-└─────────────────────────────────────────────────────────────────────────┘
-```
-
-### Estrutura do Parameter
-
-```json
-{
-  "version": "1.0",
-  "updatedAt": "2026-02-07T21:00:00Z",
-  "categories": {
-    "menu_extraction": {
-      "provider": "anthropic",
-      "model": "claude-sonnet-4-20250514"
-    },
-    "item_parsing": {
-      "provider": "openai", 
-      "model": "gpt-4o"
-    },
-    "price_extraction": {
-      "provider": "gemini",
-      "model": "gemini-1.5-flash"
-    },
-    "auto_curation": {
-      "provider": "perplexity",
-      "model": "sonar"
-    },
-    "batch_curation": {
-      "provider": "perplexity",
-      "model": "sonar"
-    },
-    "validation": {
-      "provider": "gemini",
-      "model": "gemini-1.5-flash"
-    },
-    "general": {
-      "provider": "anthropic",
-      "model": "claude-sonnet-4-20250514"
-    }
-  }
-}
-```
-
-### Ordem de Execução
-
-```
-1. CD-216 (GCP setup) ──────────┐
-2. CD-211 (PipelineConfigManager)├──► CD-212 (endpoints) ──► CD-215 (frontend)
-3. CD-213 (auto-seed) ──────────┘
-4. CD-214 (integração PromptManager)
-```
-
-### Benefícios
-
-1. **Sem mudança no MongoDB** - schema de templates intacto
-2. **Configuração centralizada** - um JSON para todo pipeline
-3. **Hot reload** - muda config, sistema usa imediatamente
-4. **Consistência** - mesmo padrão do ProviderKeyManager
-5. **Menos código** - reutiliza lógica existente
-
----
-
-### Update - 2026-02-07 23:37
-
-CD-216 DONE: GCP Parameter criado. CD-211 DONE: PipelineConfigManager com 17 testes. Próximo: CD-212 (endpoints) e CD-213 (auto-seed).
-
-### Update - 2026-02-08 08:55
-
-CD-217 ModelDiscoveryService - Tests Fixed and Passing
-
-## Progress
-- Fixed Anthropic SDK mock for async iterator pattern
-- All 12 unit tests now passing:
-  - getModelsForProvider (anthropic, openai, gemini, perplexity)
-  - getAllModels
-  - caching (cache results, status, invalidate specific, invalidate all)
-  - fallback behavior (no API key)
-  - model filtering (GPT-4, Gemini)
-
-## Technical Details
-- Key fix: Proper Symbol.asyncIterator implementation with const assertions
-- Mock returns fresh iterator each call with Promise.resolve for next()
-- Discovered real Anthropic API response structure via curl
-
-## Remaining
-- PipelineConfigManager.test.ts needs fixes (SUPPORTED_PROVIDERS removed, missing await)
-- CD-217 ready to move to done after PipelineConfigManager tests fixed
-
-### Update - 2026-02-08 11:38
-
-CD-217 COMPLETED - Dynamic Model Discovery
-
-## Final Status
-- Card moved: review -> tested -> done
-- All 29 tests passing (ModelDiscoveryService: 12, PipelineConfigManager: 17)
-
-## Key Learnings
-- Self-review prevention: assigned agent cannot review own work
-- Async iterator mocking requires proper Symbol.asyncIterator implementation
-- Real API response structure discovered via curl (Anthropic returns paginated data array)
-
-## Next: CD-212 - REST Endpoints for Pipeline Config
-
-### Update - 2026-02-08 11:41
-
-CD-212 COMPLETED - REST Endpoints for Pipeline Config
-
-## Endpoints Created
-- GET /api/v1/admin/pipeline-config - Full config
-- GET /api/v1/admin/pipeline-config/:category - Category config
-- PUT /api/v1/admin/pipeline-config/:category - Update category
-- GET /api/v1/admin/pipeline-config/providers - All providers with models
-- GET /api/v1/admin/pipeline-config/providers/:provider/models - Provider models
-- POST /api/v1/admin/pipeline-config/cache/invalidate - Config cache
-- POST /api/v1/admin/pipeline-config/models/cache/invalidate - Models cache
-- GET /api/v1/admin/pipeline-config/health - Health check
-
-## Tests
-- 13 route tests passing
-- Total: 42 tests for EP-012 (ModelDiscoveryService + PipelineConfigManager + Routes)
-
-## Files Created
-- src/routes/admin/pipelineConfigRoutes.ts
-- src/routes/admin/__tests__/pipelineConfigRoutes.test.ts
-- Updated src/routes/admin.ts
-
-### Update - 2026-02-08 12:01
-
-CD-213 & CD-214 COMPLETED
-
-## CD-213: Auto-seed Prompt Templates
-- Created PromptTemplateSeeder service
-- Seeds on startup if collection empty
-- Prevents duplicates, tracks session state
-- 10 tests passing
-
-## CD-214: Integrate PromptManager with PipelineConfig
-- Added getExecutionContext() method
-- Added getDefaultExecutionContext() method
-- Returns provider/model from PipelineConfigManager
-- Backwards compatible with fallback defaults
-
-## EP-012 Progress
-- CD-211: PipelineConfigManager ✅
-- CD-212: REST Endpoints ✅
-- CD-213: Auto-seed ✅
-- CD-214: PromptManager Integration ✅
-- CD-215: Frontend PipelineConfigView (remaining)
-- CD-216: GCP Parameter Setup ✅
-- CD-217: Dynamic Model Discovery ✅
-
-## Total Tests: 52 passing
-
-### Update - 2026-02-08 12:23
-
-## Session Summary - EP-012 Backend Complete
-
-### Cards Completed This Session
-| Card | Title | Tests |
-|------|-------|-------|
-| CD-217 | Dynamic Model Discovery | 12 |
-| CD-212 | REST Endpoints | 13 |
-| CD-213 | Auto-seed Prompt Templates | 10 |
-| CD-214 | PromptManager Integration | - |
-
-### Total Test Coverage
-- **52 tests passing** across 4 test suites
-- ModelDiscoveryService: 12 tests
-- PipelineConfigManager: 17 tests  
-- pipelineConfigRoutes: 13 tests
-- PromptTemplateSeeder: 10 tests
-
-### Architecture Implemented
-```
-┌─────────────────────────────────────────────────────────────┐
-│                    EP-012 ARCHITECTURE                       │
-├─────────────────────────────────────────────────────────────┤
-│                                                             │
-│  ModelDiscoveryService          PipelineConfigManager       │
-│  ────────────────────           ─────────────────────       │
-│  • Anthropic API                • GCP Parameter Manager     │
-│  • OpenAI API                   • Category → Provider/Model │
-│  • Gemini API                   • 5-min cache               │
-│  • Perplexity (static)          • Fallback to defaults      │
-│  • 24h cache                                                │
-│                                                             │
-│  PromptTemplateService          PromptTemplateSeeder        │
-│  ─────────────────────          ────────────────────        │
-│  • getExecutionContext()        • seedIfEmpty() on startup  │
-│  • Returns provider/model       • Prevents duplicates       │
-│  • Integrates with Pipeline     • Session tracking          │
-│                                                             │
-│  REST Endpoints (/api/v1/admin/pipeline-config)             │
-│  ───────────────────────────────────────────────            │
-│  • GET / - Full config                                      │
-│  • GET /:category - Category config                         │
-│  • PUT /:category - Update category                         │
-│  • GET /providers - All providers with models               │
-│  • GET /providers/:provider/models - Provider models        │
-│  • POST /cache/invalidate - Config cache                    │
-│  • POST /models/cache/invalidate - Models cache             │
-│  • GET /health - Health check                               │
-│                                                             │
-└─────────────────────────────────────────────────────────────┘
-```
-
-### EP-012 Final Status
-- CD-211: PipelineConfigManager ✅
-- CD-212: REST Endpoints ✅
-- CD-213: Auto-seed ✅
-- CD-214: PromptManager Integration ✅
-- CD-215: Frontend PipelineConfigView 📋 (remaining)
-- CD-216: GCP Parameter Setup ✅
-- CD-217: Dynamic Model Discovery ✅
-
-**Backend: 6/6 complete | Frontend: 0/1 remaining**
-
-### Update - 2026-02-08 13:00
-
-EP-012 COMPLETED - All 7 cards done (CD-211 to CD-217). Final task: Fixed TypeScript errors in PipelineConfigView.vue (removed unused PipelineCategory import, added non-null assertion for models[0]). Frontend build verified passing. 52 unit tests total. Epic deliverables: PipelineConfigManager, REST endpoints, auto-seed, PromptManager integration, frontend view, GCP parameter setup, dynamic model discovery.
-
-### Update - 2026-02-08 13:07
-
-EP-013 CREATED - API Key Validation & Health Check. 8 cards criados (CD-218 a CD-225): ApiKeyValidationService, endpoints validate/health, persist validation status, frontend test button, card status badges, pipeline warning, graceful error handling. Sprint SP-011 criado. Todos cards em READY.
-
-### Update - 2026-02-08 13:16
-
-EP-013 Progress - API Key Validation & Health Check:
-
-COMPLETED:
-- CD-218: ApiKeyValidationService created (18 tests passing)
-- CD-219: POST /providers/:id/validate endpoint (validates key without saving)
-- CD-220: GET /providers/:id/health + /health/all endpoints (11 tests passing)
-
-IN PROGRESS:
-- CD-221: ProviderKeyInfo interface updated with validation fields (lastValidatedAt, lastValidationStatus, lastValidationError). Still needs: getDefaultPayload(), listProviders() updates, updateValidationStatus() method.
-
-NOT STARTED:
-- CD-222: Frontend Test Button
-- CD-223: Card Status Badges  
-- CD-224: PipelineConfig Warning
-- CD-225: Graceful Error Handling
-
-Total: 29 new tests passing
-
-### Update - 2026-02-08 13:30
-
-EP-013 COMPLETED - API Key Validation & Health Check. All 8 cards done:
-- CD-218: ApiKeyValidationService (18 tests)
-- CD-219: POST /providers/:id/validate endpoint
-- CD-220: GET /providers/:id/health endpoint (11 tests)
-- CD-221: ProviderKeyManager validation status persistence
-- CD-222: Frontend Test Key button in ProviderKeysView
-- CD-223: Card status badges (Valid/Invalid/Unknown)
-- CD-224: PipelineConfigView warning banner
-- CD-225: Graceful error handling in ModelDiscoveryService (12 tests)
-
-Total: 41 new tests. Frontend builds passing.
-
----
-
-## Devlog Closed
-
-**Ended**: 2026-02-09 18:53
-
-(Add comprehensive summary here)

package/.opencode/devlogs/menu-ocr/2026-02-09-1853-secure-auth-architecture.md

@@ -1,167 +0,0 @@
-# Devlog: Secure Auth Architecture - Menu OCR Client Portal
-
-**Started**: 2026-02-09 18:53
-**Instance**: menu-ocr
-**Status**: In Progress
-
----
-
-## 🎯 Goals
-
-1. Implementar autenticação segura no Client Portal usando Firebase Auth
-2. Usar Firebase Custom Claims para controle de acesso multi-tenant
-3. Garantir que apenas usuários autorizados acessem tenants específicos
-4. Admin Portal: permitir adicionar usuários a tenants
-
----
-
-## 📋 Architecture Overview
-
-### Security Model: Firebase Custom Claims
-
-```
-┌──────────────────────────────────────────────────────────────┐
-│                    AUTHENTICATION FLOW                        │
-├──────────────────────────────────────────────────────────────┤
-│                                                              │
-│  ┌─────────────┐    ┌─────────────┐    ┌─────────────┐      │
-│  │Admin Portal │    │   Backend   │    │Client Portal│      │
-│  └──────┬──────┘    └──────┬──────┘    └──────┬──────┘      │
-│         │                  │                  │              │
-│    1. Add user to tenant   │                  │              │
-│    ─────────────────────>  │                  │              │
-│                            │                  │              │
-│    2. setCustomUserClaims  │                  │              │
-│       (Firebase Admin SDK) │                  │              │
-│                            │                  │              │
-│                            │    3. Login      │              │
-│                            │  <───────────────│              │
-│                            │                  │              │
-│    4. verifyIdToken()      │                  │              │
-│       + check claims       │                  │              │
-│       + check email_verified                  │              │
-│                            │                  │              │
-│                            │  5. Authorized   │              │
-│                            │  ───────────────>│              │
-│                                                              │
-└──────────────────────────────────────────────────────────────┘
-```
-
-### JWT Token Structure (Firebase Custom Claims)
-
-```json
-{
-  "sub": "firebase-uid-123",
-  "email": "user@company.com",
-  "email_verified": true,
-  "tenants": {
-    "tnt_abc123": { "role": "owner" },
-    "tnt_xyz789": { "role": "viewer" }
-  },
-  "iat": 1699999999,
-  "exp": 1700003599,
-  "iss": "https://securetoken.google.com/project-id"
-}
-```
-
-### Security Guarantees
-
-| Aspect | Guarantee |
-|--------|-----------|
-| Token integrity | RSA signed by Google |
-| Claims tampering | Impossible (only Admin SDK can set) |
-| Email spoofing | Blocked (require email_verified) |
-| Replay attacks | Token expiration (1 hour) |
-
----
-
-## 📦 Components to Implement
-
-### 1. Backend - New Endpoints
-
-```typescript
-// POST /v1/admin/tenants/:tenantId/users
-// Add user to tenant (sets Firebase custom claims)
-
-// DELETE /v1/admin/tenants/:tenantId/users/:email
-// Remove user from tenant
-
-// GET /v1/auth/my-tenants
-// Returns tenants from JWT claims (no DB lookup needed)
-```
-
-### 2. Backend - Firebase Admin SDK Integration
-
-```typescript
-// services/FirebaseAuthService.ts
-class FirebaseAuthService {
-  async addUserToTenant(email: string, tenantId: string, role: TenantRole);
-  async removeUserFromTenant(email: string, tenantId: string);
-  async getUserTenants(uid: string): Promise<TenantClaims>;
-}
-```
-
-### 3. Admin Portal - User Management UI
-
-```
-Tenant Detail View
-└── Users Tab
-    ├── List current users (email, role, added date)
-    ├── Add User button → Modal (email, role)
-    └── Remove User button
-```
-
-### 4. Client Portal - Firebase Auth
-
-```typescript
-// composables/useFirebaseAuth.ts
-- Initialize Firebase App
-- Login with Google / Email
-- Get ID Token
-- Refresh token on expiry
-
-// middleware/authGuard.ts
-- Check if authenticated
-- Verify token has tenant access
-- Redirect to login if not
-```
-
----
-
-## 🔐 Security Checklist
-
-- [ ] Firebase Admin SDK initialized in backend
-- [ ] Verify ID token on every API request
-- [ ] Check `email_verified` claim
-- [ ] Check tenant access in custom claims
-- [ ] Implement token refresh logic
-- [ ] Rate limit login attempts
-- [ ] Audit log for user additions/removals
-
----
-
-## 📝 Progress Log
-
-### Session 1 - 2026-02-09
-
-- [x] Analyzed current authentication state (none)
-- [x] Identified security vulnerabilities in initial proposal
-- [x] Designed secure architecture with Firebase Custom Claims
-- [ ] Implementation pending
-
----
-
-## 🔗 References
-
-- [Firebase Custom Claims](https://firebase.google.com/docs/auth/admin/custom-claims)
-- [Verify ID Tokens](https://firebase.google.com/docs/auth/admin/verify-id-tokens)
-- [Multi-tenancy with Firebase](https://firebase.google.com/docs/auth/admin/manage-users)
-
-
----
-
-## Devlog Closed
-
-**Ended**: 2026-02-11 19:52
-
-(Add comprehensive summary here)