Repository navigation
v0.12.0
Fixes #72. Consumer: pr-reviewer-plugin#367.
Change
gh_issue.scoped_default_repo(repo): a context manager over aContextVar;gh_issue.scoped_default()reads it.resolve_repo: explicitrepo> scoped default > configured default >GITHUB_DEFAULT_REPO/GH_REPO. Every tool resolves through it, so all read / write / review / release tools honour the scope.- An explicit repo still wins (so a caller's own guard still sees a call that names the wrong repo); an empty or malformed scope changes nothing; nesting restores the outer scope on exit.
- PROTO.md §6 documents the new precedence.
- Version 0.11.0 → 0.12.0 (manifest, pyproject, uv.lock).
Why
Vera runs review rounds across 170 repos with default_repo: "", so an omitted repo resolves to github.repos[0] = protoAgent. On mythxengine#966 a finder lane read protoAgent's CHANGELOG.md / pyproject.toml that way (pr-reviewer-plugin#367). The pr-reviewer will wrap each round in scoped_default_repo(round_repo).
Verification
Tests: precedence (scope beats configured default, explicit beats scope, nested scopes restore), malformed scopes are ignored, the scope follows asyncio tasks started inside it and not ones outside, and github_get_pr without repo targets the scoped repo inside the scope and the configured one after. ruff (0.15.10 pin) + pytest: 579 passed, 13 skipped.
🤖 Generated with Claude Code