fix(backend): don't mislabel fresh lockdown-gate cache hits as stale #23

Merged

starkSV merged 1 commit from fix/lockdown-cache-status into main

2026-07-08 19:48:19 +05:30

Author	SHA1	Message	Date
Shekhar Vaidya	8b430fab5d	fix(backend): don't mislabel fresh lockdown-gate cache hits as stale The Sentinel lockdown gate served any linkCache hit as "stale" regardless of whether the entry was still within its own TTL. A link just contributed via CLI (still valid for ~24h) would get labeled stale, causing the frontend to hide it and show the CLI-only banner again instead of the working link it just received. Now checks the entry's actual expiry: still-fresh entries are labeled "cached" (frontend shows the link normally); only genuinely expired entries are labeled "stale". Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-07-08 19:47:09 +05:30

Author

SHA1

Message

Date

Shekhar Vaidya

8b430fab5d

fix(backend): don't mislabel fresh lockdown-gate cache hits as stale

The Sentinel lockdown gate served any linkCache hit as "stale"
regardless of whether the entry was still within its own TTL. A link
just contributed via CLI (still valid for ~24h) would get labeled
stale, causing the frontend to hide it and show the CLI-only banner
again instead of the working link it just received.

Now checks the entry's actual expiry: still-fresh entries are labeled
"cached" (frontend shows the link normally); only genuinely expired
entries are labeled "stale".

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-07-08 19:47:09 +05:30