chore: switch to explicit first-issue seeding fallback

[accesswatch]

Summary\n- remove create-event first-issue automation from skills-progression workflow\n- mirror same removal in qa-bundle learning-room workflow\n- update template smoke test to validate fallback mode and robustly trigger Student Progression Bot by name\n\n## Why\nTemplate-repo create-event issue seeding proved unreliable in live smoke validation. This switches to explicit issue seeding and progression-trigger flow for predictable operations.

[github-actions]

Learning Room Validation Report

Great work. Your changes look good.

Resources

• Markdown Guide
• Accessibility Standards
• Open Source Culture

[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:16:23.025Z
Questions? Check PR Guidelines or mention @Facilitator

[github-actions]

MILESTONE REACHED: 25 Merged PRs!

@accesswatch — Quarter century! Your impact is undeniable.

Your Impact:

• Contributions merged: 25
• Files improved: 0
• Community member since: 3/7/2026

Share your achievement!
Add this badge to your GitHub profile:

![25 Contributions](https://img.shields.io/badge/Learning%20Room-25%20Contributions-success)

---

Milestone celebrated by Skills Engine

[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

[github-actions]

Progress Update

Great work, @accesswatch!

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

Available Challenges:

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

Keep going!