[swashbuck]

Fixes #92

Fix

• A course name that matches no folder in builds/ is now reported, instead of rub finishing silently as though there were nothing to do.
• The message names what was asked for and lists the course names that are available, so a near-miss like m05 against m05-mycourse is obvious from the output.

Tasks.filterOutputDirs already detected this case and returned null; it just never said anything. The warning goes in at that point, before the null is returned, so the existing control flow is unchanged.

Testing

1. Open an Adapt folder whose builds/ directory holds at least one course, e.g. m05-mycourse and p101.

2. Run rub -ds m05. Expect:

   No course found matching: m05
   Available courses: p101, m05-mycourse
   Finished.
   

3. Run rub -ds m05-mycourse. Expect the build and server to run as before, with no warning.

4. Run rub -ds with no course name. Expect all courses to build as before, with no warning.

---

Posted via collaboration with Claude Code

[oliverfoster]

Ran Tasks.filterOutputDirs with rub's own modules against a layout of m05-mycourse and p101:

course names	output	returns
m05	"No course found matching: m05" / "Available courses: m05-mycourse, p101"	null (unchanged)
m05-mycourse	none	that course
none	none	all courses
m05, empty builds folder	"No course found matching: m05" / "No courses were found in this folder."	null

The destructured warn/notice are safe to call detached, since Logger's static methods reference Logger rather than this.

[github-actions]

🎉 This PR is included in version 1.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀