chore: tighten Challenge 2 issue validation

[accesswatch]

Summary\n- enforce Challenge 2 issue quality checks (specific title + What/Where/Why + docs/welcome.md + TODO reference)\n- post actionable revision feedback when required fields are missing\n- apply status labels: challenge-2-complete or challenge-2-needs-revision\n- update Challenge 2 issue template text in source and qa-bundle with explicit required format\n\n## Notes\n- This preserves current Challenge 2 workflow trigger behavior and only strengthens instruction adherence.

[github-actions]

Hi! I am Gandalf, your workshop agent. I bring a little magic to make this interaction clear, helpful, and fun. Here is my review of your pull request:

Report Status

Validation Needs Attention [ACTION REQUIRED]

Required Checks

• Issue Reference
  PR should reference the issue it addresses (e.g., "Closes #12")
  Add "Closes #XX" to your PR description to automatically close the issue when merged. Learn more: docs/04-working-with-issues.md

• PR Description

• File Location
  Changes should be in learning-room/ directory only
  Student contributions should modify files in learning-room/docs/ only. Other directories are workshop infrastructure.

Learning Resources

Based on your changes, these guides might help:

• Working with Issues

---

Automated validation by Learning Room Bot. Gandalf generated this review. Last updated: 2026-05-18T01:29:35.086Z
Questions? Check PR Guidelines or mention @Facilitator

[github-actions]

Learning Room Validation Report

Great work. Your changes look good.

Resources

• Markdown Guide
• Accessibility Standards
• Open Source Culture

[github-actions]

Progress Update

Great work, @accesswatch!

Current Level: Explorer
Merged PRs: 26
Next Level: Contributor (NaN more merged PRs)

Available Challenges:

• 01 Scavenger Hunt
• 02 First Issue
• 03 Join Conversation

Keep going!

[github-actions]

Peer Review Assigned

Hi @accesswatch! Your PR has been automatically paired with @taylorarndt for peer review.

For @taylorarndt:

This is a great opportunity to practice code review skills! Here's what to look for:

Content Quality:

• Does the change accomplish what the issue describes?
• Is the writing clear and helpful?
• Are there any typos or grammar issues?

Accessibility:

• Proper heading hierarchy (H1 → H2 → H3, no skips)?
• Descriptive link text (not "click here")?
• Alt text on images?
• [TODO] markers removed?

Documentation:

• Code blocks are properly formatted?
• Tables have headers?
• References/links work correctly?

Review Guidelines:

• Be kind and constructive
• Suggest improvements, don't just point out problems
• Ask questions if something is unclear
• Approve when ready or request changes with explanation

Resources:

• How to Review PRs
• Writing Good Review Comments

---

Pairing by Learning Room Grouping Engine