2 Commits

Include renames

Author	SHA1	Message	Date
poimenandrock	a88ea918bf	test: production ingest E2E test suite with enhanced logging (#55) ... ## Summary Production testing of ingest + embedding pipeline with api-gw integration. ## Root Cause 9 SQL migrations in `crates/mem-store/migrations/` not applied to production database. Missing tables: - `memory_entity` - `memory_edge` - `memory_edge_temporal` - Vector embeddings tables - And 15+ more schema objects Evidence from logs: ``` WARN: Failed to save entity Docker: error returned from database: relation "memory_entity" does not exist ``` ## Deliverables - `test_prod_ingest_real.sh` - Full E2E test against K8s + api-gw - `apply_migrations.sh` - Manual schema migration (backup) - `collect_prod_logs.sh` - Pod log collection before/after - `run_production_test.sh` - Test orchestrator - `tests/integration_ingest_with_gw.rs` - Integration test - `tests/unit_ingest_logging.rs` - Unit tests for extraction - Enhanced logging in `ingest_worker.rs` - Per-record event tracking ## Next Steps 1. Trigger "DB Migration" workflow in Forgejo Actions 2. This applies all 9 migrations from `crates/mem-store/migrations/` 3. Pod restart (automatic) 4. Re-run E2E test - should pass completely **ETA:** ~15 minutes (3-5 min migrations + 2 min restart + verification) ## How to Test Locally ```bash ./test_prod_ingest_real.sh --verbose ``` Requires: - kubectl access to poimen namespace - Port-forwarding to memory-service --------- Co-authored-by: rock <[email protected]> Reviewed-on: #55 Co-authored-by: poimen <[email protected]>	2026-09-16 00:10:58 +00:00
Story Crater Bot	40cf736142	feat: M3.8 pluggable optimizer service (DRY + SOLID, 13 tests) ... Refactored M3.8 to be extensible and customizable: SOLID Architecture: - Single Responsibility: OptimizerPlugin (optimize), FormatHandler (format) - Open/Closed: Registry trait for extensibility without modification - Liskov Substitution: Generic SimpleRegistry<T> works for any plugin type - Interface Segregation: Traits focused, minimal methods - Dependency Inversion: OptimizerService depends on abstractions DRY Improvements: - Generic Registry<T> trait eliminates duplicate register/get/list code - PluginLocator strategy pattern replaces duplicated lookup logic - OptimizerServiceBuilder factory pattern for ergonomic creation Features: ✓ OptimizerPlugin trait (async optimization with metrics) ✓ FormatHandler trait (json, jsonl, raw, csv, yaml) ✓ Registry<T> generic trait (reusable for any plugin type) ✓ PluginLocator strategy (find optimizer by type, format by name) ✓ OptimizerService (orchestrator + dependency injection) ✓ OptimizerServiceBuilder (fluent builder) ✓ BuiltinOptimizer (wraps ContextOptimizer) ✓ 5 format handlers (JSON, JSONL, Raw, CSV, YAML) Tests (13 passing): - Registry registration and lookup - Type-based optimizer finding - Format handler discovery - Service creation via builder - Service optimization workflow - Error handling on missing formats Build: ✅ mem-core clean (130 tests total) Usage: let service = OptimizerServiceBuilder::new() .with_optimizer(Arc::new(MyOptimizer)) .with_format(Arc::new(JsonFormatter)) .build()?; let output = service.optimize(content, "text/plain", Some("json")).await?; Ready for: - Custom optimizer implementations - Custom format handlers - Query optimization (next commit) - Ingest pipeline integration (next commit)	2026-08-28 12:13:14 -07:00