fix(workflow): leaked source paths in PRD validation report

[arcaven]

Summary

Replaces two /src/core/ source tree paths with the {project-root}/_bmad/core/ convention in validation-report-prd-workflow.md (lines 293-294).

Context

This is the remaining half of the fix for #1435, which reported both a malformed XML syntax issue and a hardcoded developer path. The issue was closed with "will fix with .4 release" — the XML syntax and the brianmadison path on line 11 were fixed, but these two /src/core/ references were missed:

- - ✅ Party-mode workflow: Exists at `/src/core/workflows/party-mode/workflow.md`
- - ✅ Advanced-elicitation task: Exists at `/src/core/workflows/advanced-elicitation/workflow.xml`
+ - ✅ Party-mode workflow: Exists at `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
+ - ✅ Advanced-elicitation task: Exists at `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`

When the installer copies this file to consumer installations, the /src/core/ paths don't match the installed _bmad/core/ layout. The {project-root}/_bmad/core/ convention is consistent with how all other Beta.4 files reference cross-module paths.

Fixes #1480

Test plan

• Verified no other files in src/bmm/ reference /src/core/ (only this file had the issue)
• Confirmed {project-root}/_bmad/core/ is the convention used by party-mode workflow, brainstorming workflow, and excalidraw resources

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR fixes absolute developer machine paths that were inadvertently committed to the validation report markdown file, normalizing them to use the {project-root}/_bmad/... convention standardized in Beta.4.

Changes

Cohort / File(s)	Summary
Path Normalization src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md	Updated two absolute file path references to use {project-root} relative paths: workflow validation path and references to party-mode and advanced-elicitation workflows.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• PR #1437: Modifies the same file with related path normalization changes to align with Beta.4 conventions.

Suggested reviewers

• bmadcode
• alexeyv

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description provides clear context about the change, references issue #1435 and #1480, explains the problem, provides the diff, and documents the test plan comprehensively.
Linked Issues check	✅ Passed	The PR fully addresses issue #1480 by replacing the two leaked /src/core/ paths with the standardized {project-root}/_bmad/core/ convention as required.
Out of Scope Changes check	✅ Passed	All changes are in-scope: the PR modifies only the two path references in validation-report-prd-workflow.md that were identified in issue #1480, with no extraneous changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title 'fix(workflow): leaked source paths in PRD validation report' accurately and specifically identifies the main change: fixing hardcoded source paths in a workflow configuration file.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[alexeyv]

looking good

[bmadcode]

good catch, thanks @arcaven