fix: refresh uv lockfile

[moul]

Summary

• add the editable live-memory package version to uv.lock
• refresh live-memory lock metadata from pyproject.toml
• remove httpx-sse as a direct live-memory dependency in the lockfile

Tests

• uv sync --dev
• uv run pytest tests/ -q

[chrlesur]

Review

Verdict: request changes — the refresh is correct and needed, but one field is already stale and would defeat the PR's own purpose if merged as-is.

Checks performed

• requires-dist entries verified against pyproject.toml on current main: exact match (boto3>=1.40, httpx>=0.28, mcp[cli]>=1.27.0, openai>=1.50, httpx-sse removed — consistent with the v2.0.0 dependency hardening).
• Locked (resolved) versions verified against the new minima: boto3 1.42.89, httpx 0.28.1, openai 2.31.0, mcp 1.27.0 — all satisfy the constraints.
• This unblocks uv run pytest for everyone (the lock parse error at line 431 is also called out in #28/#29).

Blocking

• version = "2.5.2" for the editable live-memory package is already stale. The project version is dynamic (version = {file = "VERSION"}) and main released v2.5.4 today (2026-07-08). Merged as-is, the lockfile is immediately out of date again (uv lock --check / uv sync --locked would fail on the version metadata mismatch) — which is exactly the failure mode this PR sets out to fix.
• Ask: rebase on current main, re-run uv lock, and push — the refreshed lock should capture 2.5.4.

Note: uv is not available on my review machine, so I could not run uv lock --check locally; please confirm it passes after the rebase.