Clarify process for issue creation, phase-5 momentum, and scaffold assertions

[jsahleen]

Capture process learnings from #59 / #60:

1. Allow creating a GitHub issue when the user asks and none exists, before phase 1.
2. Clarify phase 5: after the user approves entering the phase, present findings and apply clear/default optimizations in the same turn (still report what changed).
3. Scaffold failing tests should use behavioral assertions aligned with real pseudo-localization (and similar) output—not assumptions about leftover ASCII letters after accenting.

Update project/process.md (and project/rules.md Testing if needed). Separate PR from feature work.

[github-actions]

🎉 This issue has been resolved in version 0.11.0 🎉

The release is available on:

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

Your semantic-release bot 📦🚀