mateo-berri dc80aa8290 fix(triage): anchor reconsider provenance marker to the current open→closed cycle ... The previous provenance check returned a false positive when a different workflow that shares the github-actions[bot] identity (e.g. the repo's actions/stale workflow, which uses secrets.GITHUB_TOKEN) re-closes a PR after Agent Shin previously auto-closed it. The check only required ANY historical marker comment by the closer login, so the old Agent Shin marker satisfied it even though the most recent close was stale's. Require the marker comment to be timestamped after the most recent reopened event (if any) and no later than the most recent closed event, so it must belong to the same open→closed cycle that's being reconsidered. Stale's close cycle never posts that marker, so the cycle-anchored check refuses to override it. The legitimate Agent Shin reconsider path still passes because Agent Shin posts the marker comment immediately before calling close_pr / close_issue in the same job.		2026-05-19 08:42:48 +00:00
..
close_duplicate_issues.py	style: run black formatter on files from main merge	2026-04-17 13:02:59 -07:00
close_low_quality_prs.py	fix(triage): apply --limit consistently in dry-run and close modes	2026-05-19 07:32:56 +00:00
scan_keywords.py	style: run black formatter on files from main merge	2026-04-17 13:02:59 -07:00
triage_with_llm.py	fix(triage): anchor reconsider provenance marker to the current open→closed cycle	2026-05-19 08:42:48 +00:00