The daily upstream-drift sweep failed closed: scripts/sweep_poll.py returned status: "error" (exit 2) and produced no drift records. No PR was opened. A human triages this issue and closes it deliberately once the underlying cause is understood; the routine never auto-closes failure issues.
Fail-closed diagnostic
{
"status": "error",
"generated_at": "2026-08-03T08:10:19.748046+00:00",
"records": [],
"target_manifest_skipped": [],
"notices": [],
"errors": [
{
"kind": "github_api_http_error",
"url": "https://api.github.com/repos/WithAutonomi/ant-sdk",
"status": 403,
"auth_status": 403,
"auth": {
"status": 403,
"body_message": "GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read access is already available and you need GitHub API or write access, call add_repo again with access:\"push\" to attach the repository with credentials.",
"request_id": null,
"ratelimit_limit": null,
"ratelimit_remaining": null,
"ratelimit_used": null,
"ratelimit_reset": null,
"ratelimit_resource": null,
"retry_after": null
},
"anon": {
"status": 403,
"body_message": "GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read access is already available and you need GitHub API or write access, call add_repo again with access:\"push\" to attach the repository with credentials.",
"request_id": null,
"ratelimit_limit": null,
"ratelimit_remaining": null,
"ratelimit_used": null,
"ratelimit_reset": null,
"ratelimit_resource": null,
"retry_after": null
},
"message": "GitHub API returned 403 authenticated and 403 anonymous for /repos/WithAutonomi/ant-sdk; ls-remote fallback also failed: git ls-remote --symref https://github.com/WithAutonomi/ant-sdk.git HEAD: timeout after 30s",
"git_ls_remote": {
"url": "https://github.com/WithAutonomi/ant-sdk.git",
"error": "git ls-remote --symref https://github.com/WithAutonomi/ant-sdk.git HEAD: timeout after 30s"
}
}
]
}Cause
Both authenticated and anonymous REST reads of /repos/WithAutonomi/ant-sdk returned 403 with body_message: "GitHub access to this repository is not enabled for this session. Use add_repo to request access." — this session's egress policy scopes GitHub access to withautonomi/autonomi-developer-docs only and refuses the in-scope upstream repos, so this is not an upstream repo-state problem. The git ls-remote fallback then failed with git ls-remote --symref https://github.com/WithAutonomi/ant-sdk.git HEAD: timeout after 30s (network egress to github.com is blocked for this session), leaving the scanner with no way to resolve upstream HEAD, so it failed closed before checking any record. A run from an environment with contents: read on the in-scope upstream repos (or unblocked git egress to github.com) is required to reproduce a real drift sweep.
The daily upstream-drift sweep failed closed:
scripts/sweep_poll.pyreturnedstatus: "error"(exit 2) and produced no drift records. No PR was opened. A human triages this issue and closes it deliberately once the underlying cause is understood; the routine never auto-closes failure issues.Fail-closed diagnostic
{ "status": "error", "generated_at": "2026-08-03T08:10:19.748046+00:00", "records": [], "target_manifest_skipped": [], "notices": [], "errors": [ { "kind": "github_api_http_error", "url": "https://api.github.com/repos/WithAutonomi/ant-sdk", "status": 403, "auth_status": 403, "auth": { "status": 403, "body_message": "GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read access is already available and you need GitHub API or write access, call add_repo again with access:\"push\" to attach the repository with credentials.", "request_id": null, "ratelimit_limit": null, "ratelimit_remaining": null, "ratelimit_used": null, "ratelimit_reset": null, "ratelimit_resource": null, "retry_after": null }, "anon": { "status": 403, "body_message": "GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read access is already available and you need GitHub API or write access, call add_repo again with access:\"push\" to attach the repository with credentials.", "request_id": null, "ratelimit_limit": null, "ratelimit_remaining": null, "ratelimit_used": null, "ratelimit_reset": null, "ratelimit_resource": null, "retry_after": null }, "message": "GitHub API returned 403 authenticated and 403 anonymous for /repos/WithAutonomi/ant-sdk; ls-remote fallback also failed: git ls-remote --symref https://github.com/WithAutonomi/ant-sdk.git HEAD: timeout after 30s", "git_ls_remote": { "url": "https://github.com/WithAutonomi/ant-sdk.git", "error": "git ls-remote --symref https://github.com/WithAutonomi/ant-sdk.git HEAD: timeout after 30s" } } ] }Cause
Both authenticated and anonymous REST reads of
/repos/WithAutonomi/ant-sdkreturned 403 withbody_message: "GitHub access to this repository is not enabled for this session. Use add_repo to request access."— this session's egress policy scopes GitHub access towithautonomi/autonomi-developer-docsonly and refuses the in-scope upstream repos, so this is not an upstream repo-state problem. Thegit ls-remotefallback then failed withgit ls-remote --symref https://github.com/WithAutonomi/ant-sdk.git HEAD: timeout after 30s(network egress to github.com is blocked for this session), leaving the scanner with no way to resolve upstream HEAD, so it failed closed before checking any record. A run from an environment withcontents: readon the in-scope upstream repos (or unblocked git egress to github.com) is required to reproduce a real drift sweep.