SqliteSessionService:Google ADK SQLite → read-only snapshot → correction-safe OKF → memanto migrate okf → Memanto recall → OKF exportmemories/ so corrected facts cannot be reactivated during import. The artifact verifier fails closed on malformed metadata, duplicate entries, unlisted memory files, absolute paths, traversal paths, and snapshot/hash mismatches. Capture also aborts if the SQLite database changes during the read.--report, and ADK SQLite stores no token, latency, or billing baseline, so the report deliberately claims no synthetic provider savings.examples/migrations/google-adk/artifacts/adk-live-run/migration-report.jsonexamples/migrations/google-adk/artifacts/adk-live-run/evidence/recall-parity.jsonexamples/migrations/google-adk/artifacts/adk-live-run/evidence/memanto-dry-run.txtexamples/migrations/google-adk/artifacts/adk-live-run/evidence/cloud-recall-validation.jsonexamples/migrations/google-adk/artifacts/adk-live-run/roundtrip-summary.jsonexamples/migrations/google-adk/artifacts/adk-live-run/memanto-roundtrip-export/examples/migrations/google-adk/artifacts/adk-live-run/memanto-roundtrip-export/SOURCE_SESSION_MAPPING.mdexamples/migrations/google-adk/artifacts/adk-live-run/google-adk-okf/examples/migrations/google-adk/MAPPING.mdPosted Aug 2, 2026
Built a correction-safe SQLite-to-OKF migration path with 10/10 cloud imports, 8/8 recall checks, reversible export, and 32/32 focused tests.