docs: Update stale documentation - docs/templates/user-journey-template.md

[github-actions]

Stale Documentation Detected

File: docs/templates/user-journey-template.md
Current ms.date: 2026-05-20
Age: 96 days (threshold: 90 days)

---

Workflow Run: https://github.com/microsoft/hve-core/actions/runs/32711068936
Detection Date: 2026-08-24

Action Required

• Review and update this documentation file
• Update ms.date frontmatter to current date
• Verify technical accuracy of content
• Close this issue manually after fixes are merged

[AaronProbha18]

hi Jamie Kim (@jkim323),
I'd like to work on this issue.

Plan

The stale-doc warning appears to be caused by the review timestamp in the user-journey template exceeding the repository's freshness window, rather than by a known problem with the template itself. I’ll first check the relevant docs/agents/ planning and backlog areas for any newer JTBD or user-journey structure that should take precedence.

If there is no competing canonical format, the change should remain intentionally small: review the template for accuracy, update its review date, and leave the body untouched unless that review identifies genuine drift. Since the template is placeholder-driven and self-contained, I don’t expect cross-file synchronization to be necessary. I’ll also verify the existing frontmatter and freshness validation rather than adding tests for a documentation-only update.

Changes

• docs/templates/user-journey-template.md is the primary change location. It owns the reusable JTBD/user-journey structure, so its ms.date will be refreshed to the merge/review date after confirming the content remains current.
• The template’s Job Statement, User Persona, Journey Stages, Accessibility Requirements, Design Handoff, and Open Questions sections will be checked against current conventions used under docs/agents/. Any body edits will be limited to actual inconsistencies.
• The existing frontmatter fields will be preserved and validated, including title, description, sidebar_position, author, ms.date, ms.topic, keywords, and estimated_reading_time.

[jkim323]

Hello Aaron Probha (@AaronProbha18) please go for it and feel free to assign the issue to yourself. thank you for contributing!