fix(ci): break long compileall line to pass yamllint

[alirezarezvani]

Summary\n\n- Splits the python -m compileall command in ci-quality-gate.yml across multiple lines to stay under the 160-character yamllint limit (was 166 chars)\n- This was a pre-existing issue surfaced after the fork PR checkout fix in #499\n\n## Test plan\n\n- [ ] Verify yamllint passes on all workflow files\n- [ ] Verify python -m compileall still compiles the same directories\n\nhttps://claude.ai/code/session_01X1RKFAkEwxgg6gQvJG1KCa

[claude]

PR Review: fix(ci): break long compileall line to pass yamllint

Summary: Minimal, focused fix for a yamllint line-length violation. No functional changes.

Code Quality ✅

The change is correct and clean:

• All original directories are preserved in the same order
• Bash \ line continuation syntax is valid inside a YAML run: | block
• Each resulting line stays well under the 160-char limit

Potential Issues — None

• Directory list is identical to the original (verified by diff inspection)
• No accidental omissions or additions
• Grouping across lines is cosmetically arbitrary but functionally irrelevant

Suggestions (non-blocking)

Consider keeping the line continuation grouping consistent with the repo's domain structure — e.g. one line per logical domain cluster. The current grouping (marketing+product+c-level / engineering+ra+eng / biz+fin+pm+scripts) works fine but is slightly arbitrary. Not a blocker.

Verdict

Approve. This is a clean, minimal CI fix with no risk of regression. The test plan items (yamllint pass + same directories compiled) are straightforward to verify in CI.