feat(git-pr): add PR diff/comment/review/checks and CI log reading

[rohanshrma222]

Description

Phase 1 of the Agentic CI/CD Gate roadmap (#860): "Tooling Foundations." Extends git_pr with diff/comment/review/checks/logs actions (backed by gh pr diff, gh pr comment, gh pr review, gh pr checks, gh run view --log-failed), adds search/pagination for CI logs so a huge log never blows the context window, and adds a standalone source/verify/trust.ts module mapping comment-only/auto-fix/full-commit trust levels to tool allowlists — unwired for now, to be consumed by the verify subcommand and --trust flag in Phases 2/4 (#861, #863).

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Changeset

• Added a changeset (pnpm changeset) describing this change for the changelog

Docs-only or internal chores need no changeset (or run pnpm changeset --empty to note that intentionally).

Not yet added — say the word and I'll run pnpm changeset before you push.

Testing

Automated Tests

• New features include passing tests in .spec.ts/tsx files
• All existing tests pass (pnpm test:all completes successfully)
• Tests cover both success and error scenarios

pnpm test:all currently fails on 103 pre-existing failures unrelated to this change (Windows-environment-specific: ANSI formatting, path separators, a ~/.bun/bin check) in files this PR never touches. Every test in the files this PR added/changed passes (git-pr.spec.tsx, log-utils.spec.ts, trust.spec.ts, utils.spec.ts, tool-manager.spec.ts — 107+ tests), and test:types/test:lint/test:format/test:knip are all clean.

Manual Testing

• Tested with Ollama
• Tested with OpenRouter
• Tested with OpenAI-compatible API
• Tested MCP integration (if applicable)

Not applicable — this PR only touches gh-CLI-backed tool logic, no provider/LLM code path. The new gh actions themselves haven't been exercised against a live PR/CI run (this repo's git-tool tests don't mock execGh, so that's consistent with how create/view/list are tested today — formatter/shape only, no live-gh integration test).

Checklist

• If this was for an open issue, I was assigned to it
• Code follows project style guidelines
• Self-review completed
• Documentation updated (if needed)
• No breaking changes (or clearly documented)
• Appropriate logging added using structured logging (see CONTRIBUTING.md)

[akramcodez]

crazy work man @rohanshrma222, merging it :)

[rohanshrma222]

crazy work man @rohanshrma222, merging it :)

Thanks akram :)