Part E tells the learner to prompt their agent to "Take issue #43" (read from the forge) and "open a PR into main" (write to the forge). The Module 4 editor-integrated agent cannot read a forge issue or create a PR unless a host CLI (gh/glab/tea) is installed and authenticated, or forge access via MCP is wired (Module 20). But the lab's "You'll need" says the host CLI is "convenience, not a requirement" because "the web UI works for everything here" — and the web UI is exactly what the agent cannot use. So the module's headline payoff step silently fails.
Evidence
modules/11-collaboration-humans-and-agents/README.md: "the web UI works for everything here, so the CLI is convenience, not a requirement" followed by Part E: "prompt your agent: Take issue #43 … open a PR into main whose description closes #43."
Why it matters
Directly contradicts itself and breaks the "Honesty about limits" promise at the climax of Unit 2 (agent runs the loop). git push cannot create a PR; opening a PR is a forge write the human-only web UI can't delegate to the agent.
Proposed change
State that the agent-as-contributor step REQUIRES the agent to reach the forge, and offer a fallback:
Install + authenticate the host CLI (so the agent can run gh pr create / glab / tea), making the CLI a requirement for Part E specifically; OR
Have the agent do branch/commit/push and YOU open the PR in the web UI for now — noting that full agent↔forge integration via MCP arrives in Module 20.
Keep the host CLI vendor-neutral (it is already named in this lab).
Acceptance criteria
Part E no longer implies the human-only web UI suffices for the agent to open a PR.
A working path is given (host CLI required, or human-opens-PR fallback) with the Module 20 forward pointer.
Source finding F26 (realVotes 3/3). Host CLI known from Module 8; MCP forge access is Module 20.
Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.
## Problem
Part E tells the learner to prompt their agent to "Take issue #43" (read from the forge) and "open a PR into main" (write to the forge). The Module 4 editor-integrated agent cannot read a forge issue or create a PR unless a host CLI (`gh`/`glab`/`tea`) is installed and authenticated, or forge access via MCP is wired (Module 20). But the lab's "You'll need" says the host CLI is "convenience, not a requirement" because "the web UI works for everything here" — and the web UI is exactly what the agent cannot use. So the module's headline payoff step silently fails.
## Evidence
`modules/11-collaboration-humans-and-agents/README.md`: "the web UI works for everything here, so the CLI is convenience, not a requirement" followed by Part E: "prompt your agent: Take issue #43 … open a PR into main whose description closes #43."
## Why it matters
Directly contradicts itself and breaks the "Honesty about limits" promise at the climax of Unit 2 (agent runs the loop). `git push` cannot create a PR; opening a PR is a forge write the human-only web UI can't delegate to the agent.
## Proposed change
State that the agent-as-contributor step REQUIRES the agent to reach the forge, and offer a fallback:
1. Install + authenticate the host CLI (so the agent can run `gh pr create` / `glab` / `tea`), making the CLI a requirement for Part E specifically; OR
2. Have the agent do branch/commit/push and YOU open the PR in the web UI for now — noting that full agent↔forge integration via MCP arrives in Module 20.
Keep the host CLI vendor-neutral (it is already named in this lab).
## Acceptance criteria
- [ ] Part E no longer implies the human-only web UI suffices for the agent to open a PR.
- [ ] A working path is given (host CLI required, or human-opens-PR fallback) with the Module 20 forward pointer.
## Affected files
- `modules/11-collaboration-humans-and-agents/README.md`
## References
Source finding F26 (realVotes 3/3). Host CLI known from Module 8; MCP forge access is Module 20.
---
*Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.*
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
Part E tells the learner to prompt their agent to "Take issue #43" (read from the forge) and "open a PR into main" (write to the forge). The Module 4 editor-integrated agent cannot read a forge issue or create a PR unless a host CLI (
gh/glab/tea) is installed and authenticated, or forge access via MCP is wired (Module 20). But the lab's "You'll need" says the host CLI is "convenience, not a requirement" because "the web UI works for everything here" — and the web UI is exactly what the agent cannot use. So the module's headline payoff step silently fails.Evidence
modules/11-collaboration-humans-and-agents/README.md: "the web UI works for everything here, so the CLI is convenience, not a requirement" followed by Part E: "prompt your agent: Take issue #43 … open a PR into main whose description closes #43."Why it matters
Directly contradicts itself and breaks the "Honesty about limits" promise at the climax of Unit 2 (agent runs the loop).
git pushcannot create a PR; opening a PR is a forge write the human-only web UI can't delegate to the agent.Proposed change
State that the agent-as-contributor step REQUIRES the agent to reach the forge, and offer a fallback:
gh pr create/glab/tea), making the CLI a requirement for Part E specifically; ORKeep the host CLI vendor-neutral (it is already named in this lab).
Acceptance criteria
Affected files
modules/11-collaboration-humans-and-agents/README.mdReferences
Source finding F26 (realVotes 3/3). Host CLI known from Module 8; MCP forge access is Module 20.
Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.