The package remains a focused, API-backed GitHub administration layer for Pi.
Prioritization follows operator safety and workflow completeness, not API breadth
for its own sake. See BACKLOG.md for intake and milestone governance.
- Maintain offline dry-run guarantees and focused coverage for destructive paths.
- Improve structured error classification and expose sanitized GitHub request IDs.
- Keep release metadata, changelog, package contents, and dependency checks reproducible.
- Validate quickstart and recovery guidance through clean-environment feedback.
- Complete issue lifecycle: update, close/reopen, assign, and comment list/upsert.
- Complete PR lifecycle: create/update, reviewers/reviews, close/reopen, and status.
- Add branch create/existence/default/compare helpers and reviewed protection presets.
- Expand repository settings with explicit diagnostics and safe defaults.
- Collaborator, team, and organization-permission operations.
- Projects v2 and rulesets where the API surface is stable.
- Bulk synchronization, reusable repository archetypes, and a plan/apply model.
- Declarative policy packs with machine-readable remediation.
Issue #8's roadmap acceptance criteria are satisfied by this phased plan and the intake/milestone governance in BACKLOG.md. Closing the roadmap issue does not claim that every listed operation exists; each missing surface remains an independently implementable Next or Later backlog item.
Current tools cover bootstrap, comment mutation, selected PR operations, safe branch deletion, and branch protection. The remaining communication, lifecycle, organization, project, governance, and bulk-workflow areas stay explicitly deferred until decomposed into bounded issues with tests and operator evidence.