fix(journey): add missing v0.9.80 release summary

[AutumnsGrove]

The auto-tag workflow ran before fix #368 corrected the script paths,
so the summary generation failed silently. Regenerated the summary
and synced it to the landing page.

[claude]

PR Review: v0.9.80 Release Summary

Thank you for adding the missing release summary. I have reviewed the changes.

What is Good

1. Structural Correctness - JSON structure matches established format, both files are identical, valid syntax
2. Data Accuracy - Version, date, commit hash correct, stats properly categorized, PR references included
3. Proper Sync - Correctly syncs to both snapshots and landing directories

Issues Found

CRITICAL: Summary Prose Quality

The summary field lacks the warm, engaging Grove voice found in other releases.

Current: Version v0.9.80 includes 6 new features, 7 bug fixes, and 0 refactoring changes.

Expected: A warm, narrative description using Grove's authentic voice that highlights user impact, not just stats.

Example: Grove v0.9.80 brings a safer, more polished experience. We have completed Phase 2 security remediation to keep your space protected, added beautiful seasonal logos that shift with the seasons, and shared the philosophy behind Grove in a new article.

Why this matters: The summary appears on journey and roadmap pages. Generic stats do not convey the care and intentionality that Grove represents.

Recommendations

High Priority:

1. Regenerate the summary using generate-release-summary.sh script to match Grove voice
2. Ensure OPENROUTER_API_KEY is available when regenerating

Low Priority:
3. Add validation step to workflow for summary quality

Security and Performance

• No security concerns (static JSON)
• No performance impact
• No breaking changes

Suggested Actions

Option A (Recommended): Regenerate using AI script
Option B: Manually write Grove-voiced summary
Option C: Merge as stopgap, regenerate later

Overall Assessment

The PR correctly addresses the technical requirement but summary prose does not match Grove voice. This likely occurred because AI generation failed. Fix is straightforward: regenerate with script or write proper narrative.