Summary

The copyright header validation script Test-CopyrightHeaders.ps1 maintains an allow-list of file extensions it checks for SPDX license headers. Python .py files are not in this list, meaning Python scripts can merge without the required copyright header that all other source files must carry.

This is a one-line change that unblocks all subsequent Python CI work by ensuring Python files are held to the same SPDX compliance standards as PowerShell and shell scripts.

Context

PR #868 introduces the first Python skill (PowerPoint automation) with multiple .py files. Without this change, those files bypass copyright header validation entirely. The existing npm run validate:copyright command and CI workflow will automatically pick up the new extension once added.

Prior work in #634 (closed) established the CI coverage expansion pattern for skills. This issue extends that pattern to Python source files.

Changes Required

Acceptance Criteria

• *.py is included in the Test-CopyrightHeaders.ps1 extension list
• npm run validate:copyright scans Python files and reports missing headers
• Existing PowerShell and shell script validation remains unaffected
• Python files in PR feat(skills): add PowerPoint automation skill with YAML-driven deck generation #868 either pass validation or are flagged for header addition

OSSF Impact

Low direct impact, but satisfies the license_per_file_documentation criterion by ensuring Python files carry SPDX headers.

Dependencies

None. This is a standalone change with no prerequisites.

Related

• PR feat(skills): add PowerPoint automation skill with YAML-driven deck generation #868 — PowerPoint automation skill (first Python skill)
• feat(skills): Mandate unit testing, extend CI coverage, and document language support process #634 — Prior CI coverage expansion work (closed)