fix: YAML syntax error in ci.yml caused by heredoc body at column 0

[Copilot]

A bash heredoc (<<'PYEOF') inside a run: | block had its body at column 0, which terminates YAML's literal block scalar early and causes a parse error.

Change

Replaced the heredoc with printf '%s\n' lines writing to a temp file, keeping all content properly indented within the YAML block scalar:

# Before — Python lines at col 0 break YAML parsing
RELATIVE_IMPORTS=$(python3 - "$WORKFLOW" <<'PYEOF'
import sys, re
content = open(sys.argv[1]).read()
...
PYEOF
)

# After — all lines indented, equivalent behaviour
printf '%s\n' \
  'import sys, re' \
  'content = open(sys.argv[1]).read()' \
  ...
  > /tmp/gh-aw-check-imports.py
RELATIVE_IMPORTS=$(python3 /tmp/gh-aw-check-imports.py "$WORKFLOW")

[Copilot]

Pull request overview

Fixes a YAML parsing error in the CI workflow caused by an unindented bash heredoc body inside a run: | block.

Changes:

• Replaces the inline python3 - <<'PYEOF' heredoc with a printf '%s\n' ... > /tmp/... approach so all script content stays indented within the YAML literal block.
• Executes the generated temporary Python script to collect relative import paths from the added workflow.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The script is written to a predictable path in /tmp. Using a fixed filename can be vulnerable to symlink/hardlink tricks and can also collide if this step is ever reused in a context where multiple instances run on the same machine. Prefer creating the file with mktemp (or under $RUNNER_TEMP) and cleaning it up with a trap before invoking python.