Roadmap: Wesley near-term contributor onramp

[flyingrobots]

Summary

This roadmap issue gives new contributors one public place to orient on Wesley's near-term work without treating repository docs as a live backlog.

Current near-term goalposts

• Current platform release / Make It a Real Platform: project manifest, config-driven schema selection, fixture module zoo, CLI reference, module authoring guide, and contributor onramp.
• v0.3.0 / Make It Truthful: Holmes evidence quality, structured findings, exact citations, report validation, and scoring honesty.
• v0.4.0 / Make It Boring / Make It Fast Without Making It Weird: repo plumbing, pre-push determinism, CLI ergonomics, and performance work.
• v0.5.0 / Platform expansion: larger external target and MCP surfaces after the domain-free compiler boundary is stable.

Contributor path

Start with issues labeled good first issue. Those issues should be small, already scoped, and scheduled into a named release lane. Avoid unscheduled work unless a maintainer explicitly asks for triage help.

Links

• Good first issues: https://github.com/flyingrobots/wesley/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22
• Milestones: https://github.com/flyingrobots/wesley/milestones
• Roadmap project: Wesley Roadmap
• Triage docs: https://github.com/flyingrobots/wesley/blob/main/docs/topics/contributing/triage.md

[coderabbitai]

🔗 Related PRs

#43 - chore(oss): add PR template, CODEOWNERS, CHANGELOG (supersedes #22) [merged]
#475 - Merge-worthy unmerged branches into omnibus reconciliation branch [merged]
#503 - Revise README.md for clarity and additional information [merged]
#506 - chore(release): v0.0.3 [merged]
#640 - chore(release): prepare v0.1.1 [merged]

---

📝 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!

[flyingrobots]

Triage-label cleanup rationale before changing labels:

The retired lane:* scheduling vocabulary conflicts with docs/topics/contributing/triage.md and the release-lane model. This issue is already correctly scheduled under v0.3.0; keeping an old retired-lane label would make its state ambiguous. I am removing only the stale retired-lane label; the issue remains open and scheduled for v0.3.0.

[flyingrobots]

Release-prep rationale before editing the body: this issue is a living contributor-onramp item scheduled for the next release, not unfinished work for the current release. Its body still names the current release by exact version, and cargo xtask release-prep-guard --version <target> intentionally treats open exact-version title/body references as blockers. I am refreshing the wording so the issue stays useful without falsely owning the current release token.

[flyingrobots]

Release workflow hygiene before editing stale comments:

This issue is scheduled future-release work, not unfinished work for the current tag. The tag publish workflow performs a broad open-issue search that also matches old comments, so I am replacing stale current-release wording in prior comments only. Issue state, labels, milestone, and scope are unchanged.