{"package":"openclaw","version":"2026.6.33","status":"score-only","score":79,"stabilityScore":{"schemaVersion":"isitstable:v1","baseScore":80,"score":79,"verdict":"pending","votePenalty":0,"evidencePenalty":1,"survivalDays":0,"survivalBonus":0,"curated":false,"curatedBonus":0,"formula":{"baseScore":80,"evidencePenalty":1,"votePenalty":0,"survivalDays":0,"survivalPointsPerDay":3,"survivalCreditedDays":0,"survivalBonus":0,"curatedBonus":0,"score":79},"affected":["telegram"],"evidence":[{"repo":"openclaw/openclaw","number":106738,"url":"https://redirect.github.com/openclaw/openclaw/issues/106738","issue":"openclaw/openclaw issue 106738","area":"telegram","type":"channel-specific","severity":1,"penalty":1,"reason":"Telegram bot-to-bot live release probe cannot observe replies on extended-stable/2026.6.33; issue explicitly lists the target branch/version and a deterministic failing release-check run."}]},"comment":"Fresh LTS watch: one Telegram release-gate gremlin has an ID badge. Evidence is recorded while the release is still inside the 24h window.","thumbsUp":0,"thumbsDown":0,"referencedIssues":[{"repo":"openclaw/openclaw","number":106738,"url":"https://redirect.github.com/openclaw/openclaw/issues/106738","title":"[Bug]: LTS Telegram bot-to-bot release probe cannot observe replies"}],"issueUrl":"https://github.com/exisz/IsItStable/issues/154","createdAt":"2026-07-21T11:25:55.513Z"}