Add Method doctor for issue-named branches and work-in-progress labels

[flyingrobots]

Idea

Add a Method doctor that reconciles active branches, GitHub Issues, and work-in-progress labels.

We now want work to happen in issue-named branches, with work-in-progress only on issues that are actually active. That rule is easy to say and easy to drift from unless tooling watches it.

Possible checks

• Current branch slug matches an open issue title slug.
• Active issue has work-in-progress.
• Closed/merged issue does not keep work-in-progress.
• Branches without matching issues are flagged.
• Issues with work-in-progress but no matching local/remote branch are flagged.
• PR body links the active issue.
• One issue carries exactly one lane:* label.

Why it matters

This turns the new GitHub-Issues-first Method into executable workflow instead of etiquette. It also prevents silent drift after the filesystem backlog is removed.

Acceptance sketch

• method doctor --github reports branch/issue/WIP mismatches.
• Output includes precise fix suggestions.
• The command can run read-only in CI.
• It supports repo-local tracking without central dashboards.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• Add GitHub Issues backed Method status and dashboard tooling #71

🔗 Related PRs

#22 - Add doctor command [merged]
#64 - Make GitHub Issues the Method work tracker [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!