Correct Module 9's claim that issues are enabled by default on every Module 8 forge #13

New Issue

2026-06-22T14:23:43-04:00

claude commented

2026-06-22 14:23:43 -04:00

Problem

Module 9's "You'll need" says the repo will have "issues enabled (they are by default on every forge named in Module 8)." That is false for several Module 8 forges: Bitbucket Cloud's issue tracker is off by default, Azure DevOps has no Issues feature (it uses Boards/Work Items), and SourceHut uses a separately provisioned todo.sr.ht tracker. A learner on Bitbucket/Azure hits a missing-feature wall the text says cannot happen — and it contradicts Module 9's own earlier caveat that "the feature set varies."

Evidence

modules/09-issues-and-the-task-layer/README.md (~lines 237-238): "with issues enabled (they are by default on every forge named in Module 8)."
Contradicts the same module (~lines 50-51): "GitHub Issues, GitLab Issues, … Azure Boards — the feature set varies."
Module 8 names Bitbucket, Azure DevOps, and SourceHut among its forges.

Why it matters

Breaks the vendor-agnostic ("GitHub is the default, not the requirement") and honesty-about-limits promises for learners who took the course's actively-encouraged forge-agnostic path, plus the load-bearing M8→M9 dependency.

Proposed change

Soften to match the line-50 caveat, e.g.: "Most forges enable issues by default; on a few you may need to turn the tracker on first — Bitbucket Cloud's tracker is off until enabled, Azure DevOps uses Boards/Work Items instead of Issues, and SourceHut uses a separate todo.sr.ht tracker."

Acceptance criteria

Module 9 no longer claims issues are on by default on every Module 8 forge.
Bitbucket, Azure DevOps, and SourceHut exceptions are named.
The statement is consistent with the line-50 "feature set varies" caveat.

Affected files

modules/09-issues-and-the-task-layer/README.md

References

Source finding F24 (realVotes 3/3).

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 Module 9's "You'll need" says the repo will have "issues enabled (they are by default on every forge named in Module 8)." That is false for several Module 8 forges: Bitbucket Cloud's issue tracker is off by default, Azure DevOps has no Issues feature (it uses Boards/Work Items), and SourceHut uses a separately provisioned `todo.sr.ht` tracker. A learner on Bitbucket/Azure hits a missing-feature wall the text says cannot happen — and it contradicts Module 9's own earlier caveat that "the feature set varies." ## Evidence `modules/09-issues-and-the-task-layer/README.md` (~lines 237-238): "with issues enabled (they are by default on every forge named in Module 8)." Contradicts the same module (~lines 50-51): "GitHub Issues, GitLab Issues, … Azure Boards — the feature set varies." Module 8 names Bitbucket, Azure DevOps, and SourceHut among its forges. ## Why it matters Breaks the vendor-agnostic ("GitHub is the default, not the requirement") and honesty-about-limits promises for learners who took the course's actively-encouraged forge-agnostic path, plus the load-bearing M8→M9 dependency. ## Proposed change Soften to match the line-50 caveat, e.g.: "Most forges enable issues by default; on a few you may need to turn the tracker on first — Bitbucket Cloud's tracker is off until enabled, Azure DevOps uses Boards/Work Items instead of Issues, and SourceHut uses a separate `todo.sr.ht` tracker." ## Acceptance criteria - [ ] Module 9 no longer claims issues are on by default on *every* Module 8 forge. - [ ] Bitbucket, Azure DevOps, and SourceHut exceptions are named. - [ ] The statement is consistent with the line-50 "feature set varies" caveat. ## Affected files - `modules/09-issues-and-the-task-layer/README.md` ## References Source finding F24 (realVotes 3/3). --- *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.*