Rename repository and package from AgentPool to AgentWolf

[Million-mo]

Summary

Rename the project from AgentPool to AgentWolf across the repository, package distribution, documentation, and CLI surfaces. The new GitHub repository will be Leoyzen/agentwolf, the PyPI package will be agentwolf, and the Python namespace will be agentwolf.

Motivation

The new name aligns with the next phase of the project brand. This issue tracks the full rename effort.

Scope of Work

• Rename GitHub repository Leoyzen/agentpool → Leoyzen/agentwolf (preserves GitHub auto-redirect).
• Replace Python package name agentpool → agentwolf in pyproject.toml.
• Rename all src/agentpool* package directories and agentpool.* imports to agentwolf.
• Update CLI entry point from agentpool to agentwolf (or decide on backward compatibility).
• Update README title, badges, documentation links, and GitHub Pages references.
• Update CI workflows, issue templates, and any repository-level configuration files.
• Publish first agentwolf release to PyPI.
• Add deprecation notice to the final agentpool PyPI release pointing users to agentwolf.
• Write migration guide for users (import renames, CLI renames, config renames).

Non-Goals

• No functional behavior changes beyond the rename.
• Keep the rename PR focused; documentation rewrites can be follow-ups.

Related

• Milestone: Rebrand: AgentPool → AgentWolf

[Million-mo]

/oc

[Million-mo]

/oc

[opencode-agent]

Review: PR #334 — feat(ci): support /oc trigger on issues, not just PRs

Summary

Tiny, well-scoped PR (1 line code + 1 comment update). The change removes the github.event.issue.pull_request != null guard so /oc and /opencode comments on standalone issues (not just PRs) trigger the OpenCode review workflow.

Issues Found

1. Security: pull_request != null was removed without a replacement auth guard.
Any GitHub user can now comment /oc on any issue in this public repo to consume DEEPSEEK_API_KEY credits and runner time. The Bot check (user.type != 'Bot') only blocks automated GitHub Apps, not manual abuse.

Recommendation: Add an author_association filter to the issue_comment condition:

github.event.comment.author_association == 'OWNER' ||
github.event.comment.author_association == 'MEMBER' ||
github.event.comment.author_association == 'COLLABORATOR'

2. No diff exists when triggered on a plain issue.
actions/checkout@v6 will clone the default branch (no PR diff). The anomalyco/opencode/github@latest action will have no pull_request.number to diff against. Consider an early-exit step that checks github.event.issue.pull_request and exits 0 if null, unless the team explicitly wants to handle issue-based review contexts.

3. Concurrency group works but has a minor collision risk.
github.event.pull_request.number || github.event.issue.number resolves correctly for both PRs and issues, but PR #42 and issue #42 would share a concurrency group. Low impact (just cancels a parallel run), but worth noting.

4. Incorrect issue linkage.
This PR is linked to issue #323 (renaming AgentPool → AgentWolf), but the change is completely unrelated. It belongs to the CI/OpenCode refinement chain (PRs #326→#330→#332→#333→#334). The scope mismatch could confuse future reviewers.

Positives

• Comment was updated to accurately reflect the new behavior.
• Bot check retained, so automated infinite loops are prevented.
• Well-scoped single-purpose change.
• Concurrency group expression handles both event types correctly.

Docs check (per scope)

N/A — the PR touches no documentation, source code, or package structure. The AGENTS.md context loading table and docs/explanation/ links are unaffected.

Verdict

Approve with concerns — the change is correct in intent but needs:

1. An author_association guard to prevent token theft via public issue /oc spam.
2. An early-exit for issue_comment on plain issues (no PR diff to review).
3. Correct issue linkage.

opencode session  |  github run

[Million-mo]

Closing this issue. The rename now targets WolfHarness (wolfharness) instead of AgentWolf. A new issue has been created for the wolfharness rename.