fix(troubleshoot): remove relative-path confounder from python-pipe scenario

[dmorosanu]

The python-pipe-broken-missing-module scenario was ambiguous: its Main.xaml passed a relative csv path (invoices\inv-2026-05.csv) with a blank WorkingFolder to pd.read_csv. That produces the same swallowed "Pipe is broken" signature as the intended missing-pandas cause, so a FileNotFoundError-from-relative-path diagnosis was equally supported by the evidence — making the scenario flaky and its RESOLUTION unreachable by reasoning.

Removes the confounder: absolute csv path + WorkingFolder="C:\Robot\Data", leaving the third-party import pandas as the only plausible hidden cause. Consistent with RESOLUTION.md, which already states this is "not a WorkingFolder / relative-path issue."

Scenario-only change (one Main.xaml, 2 lines); no playbook, fixture-log, or RESOLUTION edits. Validated locally via coder-eval: 5/5 runs now reach the correct missing-pandas diagnosis (skill_triggered 1.0; llm_judge graded by hand as the local judge transport is unconfigured).

[github-actions]

Claude finished @dmorosanu's task in 1m 34s —— View job

---

PR Review: fix(troubleshoot): remove relative-path confounder from python-pipe scenario

• Gather context and read review criteria
• Read full diff and changed files
• Verify file correctness and consistency
• Post review findings

---

Summary

Removes a diagnostic confounder from the python-pipe-broken-missing-module test scenario. The original Main.xaml used a relative CSV path (invoices\inv-2026-05.csv) with a blank WorkingFolder, which produced a FileNotFoundError indistinguishable from the intended missing-pandas ModuleNotFoundError — both crash the Python host and surface the same Pipe is broken signature. The fix sets WorkingFolder="C:\Robot\Data" and uses an absolute CSV path, leaving import pandas as the sole plausible hidden cause.

Change-by-Change Review

1. tests/tasks/uipath-troubleshoot/activity-packages/python-activities/python-pipe-broken-missing-module/process/Main.xaml

Severity: OK

Two targeted attribute edits:

• Line 25: WorkingFolder="" → WorkingFolder="C:\Robot\Data" — eliminates the blank-working-folder ambiguity.
• Line 33: invoices\inv-2026-05.csv → C:\Robot\Data\invoices\inv-2026-05.csv — absolute path consistent with the new WorkingFolder.

Both changes are correct:

• The absolute path is a conventional UiPath robot path (no personal or real user paths).
• RESOLUTION.md:75 already states "Not a WorkingFolder / relative-path issue" — the XAML now matches that assertion.
• XAML attribute syntax is valid (proper quoting within the element).
• No edits needed to task.yaml, RESOLUTION.md, or fixtures — the ground truth and success criteria are unaffected by this scenario-only change.

What's Missing

Nothing identified.

Area Ratings

Area	Status	Notes
Frontmatter	N/A	No SKILL.md or frontmatter changes
E2E Tests	OK	Scenario fixture updated; task.yaml and success criteria unchanged and correct
Skill Body	N/A	No skill body changes
References & Assets	OK	RESOLUTION.md already consistent with the fix
Repo Hygiene	OK	No secrets, no personal paths, change scoped to single file

Issues for Manual Review

None found.

Conclusion

Clean, well-scoped fix. The two-line change removes a legitimate diagnostic confounder without touching the scenario's ground truth or evaluation criteria. The PR description's claim of 5/5 coder-eval passes is consistent with the change. Approve.