[WRONG BRANCH] fix(google-antigravity): remove expired replay signatures from disk

[luvs01]

Motivation

• The durable Antigravity replay snapshot could retain thought signatures after their in-memory TTL expired because expiry paths removed only the in-memory entries and never flagged the snapshot for rewrite, creating an at‑rest retention/privacy leak.

Description

• Amend deleteExpiredReplaySessions to mark the replay state dirty when entries are removed so the debounced snapshot persist is scheduled; this causes expired sessions to be rewritten out of the on‑disk antigravity-replay.json file.
• Add a regression test that writes a signature, advances past the 1‑hour TTL, runs the sweeper, flushes persistence, and verifies the snapshot no longer contains the expired session or signature.
• Keep existing eviction, caps, and snapshot-size accounting unchanged; this is a targeted durability fix that preserves existing behavior and limits.

Testing

• bun test tests/google-antigravity-replay.test.ts — focused suite passed (all tests in that file passed).
• bun run typecheck — typecheck passed.
• bun run privacy:scan — privacy scan passed.
• bun run test — full repository test run encountered unrelated timeouts in larger management-provider tests in this environment (these failures are not caused by the adapter change and did not affect the focused antigravity tests).

---

Codex Task

[coderabbitai]

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a545e4a8-9b66-4fef-bb07-ef19e30961bf

📥 Commits

Reviewing files that changed from the base of the PR and between 1193075 and 5729479.

📒 Files selected for processing (2)

• src/adapters/google-antigravity-replay.ts
• tests/google-antigravity-replay.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5729479e9c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Compute the sweep deadline after inserting the session

If the clock advances by more than 1 ms between this timestamp capture and observeAntigravityReplay, the entry expires later than now + TTL + 1, so the sweep removes zero sessions and the new regression test fails nondeterministically under a scheduling pause or slow CI. Capture the reference time after insertion, use a comfortably later sweep time, or inject a fixed clock so the assertion always crosses the actual expiry.

Useful? React with 👍 / 👎.

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.

[luvs01]

Superseded by a clean current-dev implementation with a deterministic expiry regression and dual-Bun validation. Closing this wrong-base draft; the source branch is intentionally preserved.