You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Three fixes for groundskeeper operational issues:
1. Health-check duplicate issue creation: Stagger wellness workflow cron
schedules (+5min, +10min), use stable issue title without timestamp,
add title-based fallback search and post-creation dedup guard.
2. Auto-update missing env vars: Pass LONGTERMWIKI_SERVER_URL and scoped
API keys to the CI pipeline step (was only in "Build data layer" step).
Also switch paranoid review to use parseJsonFromLlm for better JSON
recovery from truncated LLM responses.
3. API key consistency: Migrate session-sweep and groundskeeper wiki-server
client from WIKI_SERVER_API_KEY to LONGTERMWIKI_PROJECT_KEY with
LONGTERMWIKI_SERVER_API_KEY fallback, matching snapshot-retention pattern.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
how_to_verify: "After next 8AM/PM UTC wellness run, check that only 1 wellness issue is created (not duplicates). Check next auto-update run for no LONGTERMWIKI_SERVER_URL warnings. Check groundskeeper logs for no API key errors."
0 commit comments