Refactor .pf task files to delegate to bash scripts in bashpf/

[Copilot]

Description

The .pf task system had inline shell commands that were fragile and difficult to maintain. All 77 tasks across core.pf, secure.pf, maint.pf, and workflows.pf now delegate to individual bash scripts in a new bashpf/ directory.

Changes:

• Created bashpf/ with 77 executable bash scripts (one per task)
• Updated all .pf files to call bash bashpf/<task-name>.sh instead of inline commands
• Fixed variable quoting in workflow scripts to prevent word-splitting issues

Before:

task build-setup
  describe Bootstrap toolchain & environment
  shell bash scripts/maintenance/toolchain-check.sh
end

After:

task build-setup
  describe Bootstrap toolchain & environment
  shell bash bashpf/build-setup.sh
end

Where bashpf/build-setup.sh contains:

#!/usr/bin/env bash
bash scripts/maintenance/toolchain-check.sh

• Breaking change?
• Impacts security?
• Includes tests?

How This Was Tested

• Verified all 77 tasks load correctly via ./pf.py list
• Executed maint-docs and kernel-profile-list tasks successfully
• Code review passed with variable quoting fixes applied

Integration Instructions

N/A - Transparent change to existing task execution. All task names and behaviors remain identical.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>pfyfile .pf files all call a bash script</issue_title>
<issue_description>OKK i'm sorry brt most pf files don't work at all.

We're switching ALL pf tasks to just call bash scripts in a dir called bashpf at the root of the repo.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes pfyfile .pf files all call a bash script #158

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.