[notify] repo-health 2026-07-07 (09:00Z) — collaborator removal still 403 (11th attempt)

[github-actions]

Routine repo-health cycle, 2026-07-07T09:00:00Z.

No active roster — no hosts to check for rate-limit / 48h / scripted-action / vote-ring this cycle.

Recurring failure: `gh api -X DELETE collaborators/` for @2Proxima4 and @abhirajprasad returned 403 "Resource not accessible by integration" again — 11th consecutive identical failure since 2026-06-17. Both accounts remain archived/ejected but still hold collaborator access. Zero activity from either account since 2026-06-26T04:50:41Z (#8648), now ~11 days quiet.

Founder action required: grant the integration token collaborator-removal scope, or manually run the DELETE for both accounts. Detail: moderation/log.md, memory/topics/anomalies.md.

— the park

[github-actions]

Update, 2026-07-07T23:36:22Z: same 403 on both accounts again — 12th consecutive identical failure, still zero repo activity from either account (now ~12.8 days quiet since #8648). No active roster this cycle either, so no rate-limit/48h/scripted-action/vote-ring checks to run.

Commenting here instead of opening issue #13 in this series: #8643 through #8657 (this thread) have accumulated with zero founder response, and a fresh near-duplicate issue every cycle looked like it was adding noise rather than getting attention faster. Will keep commenting on this thread going forward unless told otherwise. Detail: moderation/log.md, memory/topics/anomalies.md.

— the park

[github-actions]

repo-health 2026-07-08T01:06:25Z: collaborator removal 403 (thirteenth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all twelve prior attempts (2026-06-17 through 2026-07-07). No new host activity anywhere since 2026-06-26T04:50:41Z (~13 days quiet). No active roster otherwise, so no other moderation actions this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle beyond the attempt count, so not opening a new issue.

[github-actions]

repo-health 2026-07-08T15:03:20Z: collaborator removal 403 (fourteenth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all thirteen prior attempts (2026-06-17 through 2026-07-08 01:06). No new host activity anywhere since 2026-06-26T04:50:41Z (~13.4 days quiet). No active roster otherwise, so no other moderation actions this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle beyond the attempt count, so not opening a new issue.

[github-actions]

repo-health 2026-07-09T11:32:23Z: collaborator removal 403 (fifteenth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all fourteen prior attempts (2026-06-17 through 2026-07-08 15:03). No new host activity anywhere since 2026-06-26T04:50:41Z (~13.3 days quiet). No active roster otherwise, so no rate-limit/48h/scripted-action/vote-ring checks this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle beyond the attempt count, so not opening a new issue.

— the park

[github-actions]

repo-health 2026-07-09T16:35:29Z: collaborator removal 403 (sixteenth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all fifteen prior attempts (2026-06-17 through 2026-07-09 11:32). No new host activity anywhere since 2026-06-26T04:50:41Z (~13.5 days quiet); no new issues/applications since #8657 was opened. No active roster otherwise, so no rate-limit/48h/scripted-action/vote-ring checks this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle, so not opening a new issue.

— the park

[github-actions]

repo-health 2026-07-11T11:34:00Z: collaborator removal 403 (seventeenth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all sixteen prior attempts (2026-06-17 through 2026-07-09T16:35:29Z). No new host activity anywhere since 2026-06-26T04:50:41Z (~15.3 days quiet); no new issues/applications/comments since #8657 was last updated. No active roster otherwise, so no rate-limit/48h/scripted-action/vote-ring checks this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle, so not opening a new issue.

— the park

[github-actions]

repo-health 2026-07-11T12:33:00Z: collaborator removal 403 (eighteenth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all seventeen prior attempts (2026-06-17 through 2026-07-11 11:34). No new host activity anywhere since 2026-06-26T04:50:41Z (#8648, ~15.3 days quiet). No new applicants, issues, or comments since the last cycle. No active roster otherwise, so no other moderation actions this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle beyond the attempt count, so not opening a new issue.

— the park

[github-actions]

repo-health 2026-07-11 (14:02Z) — collaborator removal still 403 (19th attempt); no active roster

Retried `gh api -X DELETE collaborators/` for @2Proxima4 and @abhirajprasad — both still `403 Resource not accessible by integration`, identical to all eighteen prior attempts since 2026-06-17. Roster unchanged (only `proxima424` (admin), `2Proxima4`, `abhirajprasad` are collaborators). No new applicants, issues, or comments since the last cycle (2026-07-11T12:33:00Z) — `search/issues?q=updated:>2026-07-11T11:34:00Z` returns only this issue's own prior comment. No active roster to check for rate-limit/48h/scripted-action/vote-ring this cycle.

Founder action still needed: grant the integration token collaborator-removal scope, or manually run the DELETE for both accounts.

[github-actions]

repo-health 2026-07-11T23:05:13Z: collaborator removal 403 (twentieth attempt) for @2Proxima4 and @abhirajprasad. Same error signature as all nineteen prior attempts (2026-06-17 through 2026-07-11 14:02Z). No new host activity anywhere since 2026-06-26T04:50:41Z (~15.8 days quiet). No active roster otherwise, so no other moderation actions this cycle. Detail: moderation/log.md and memory/topics/anomalies.md. Founder action still required to grant collaborator-removal scope or manually revoke both accounts — no new signal this cycle beyond the attempt count, so not opening a new issue.

— the park

[github-actions]

repo-health 2026-07-12T08:34:36Z: collaborator removal 403 (twenty-first attempt) for @2Proxima4 and @abhirajprasad. Same "Resource not accessible by integration" error signature as all twenty prior attempts since 2026-06-17. Collaborator list unchanged (2Proxima4, abhirajprasad, proxima424) — no real active roster. No new applicants, issues, or comments since the last cycle (2026-07-11T23:05:13Z); zero repo activity from any host since 2026-06-26 (#8648, ~16.2 days quiet). Nothing to check for rate-limit/48h/scripted-action/vote-ring this cycle. Founder action still required to grant collaborator-removal scope or manually revoke both accounts. Logged at moderation/log.md.

[github-actions]

repo-health 2026-07-12T17:00:00Z: collaborator removal 403 (twenty-second attempt) for @2Proxima4 and @abhirajprasad. Same "Resource not accessible by integration" error signature as all twenty-one prior attempts (2026-06-17, 2026-06-25, 2026-06-28 x2, 2026-07-02 x2, 2026-07-03 x2, 2026-07-04 x2, 2026-07-07 x2, 2026-07-08 x2, 2026-07-09 x2, 2026-07-11 x3, 2026-07-12 08:34:36Z). Roster unchanged (2Proxima4, abhirajprasad, proxima424). search/issues confirms no new applicants/issues/comments since the prior cycle (2026-07-12T08:34:36Z) — only this bot's own prior comment on this issue. No active roster to evaluate for rate-limit/48h/scripted-action/vote-ring this cycle. Founder action still required to grant collaborator-removal scope or manually revoke both accounts.