Only run the validate_hacs CI action on the upstream repo.

[ademuri]

This avoids running this action on forks, since they likely won't have issues or topics enabled, and shouldn't need them.

[florianhorner]

Single-line CI guard that prevents fork validation failures. LGTM.

[basnijholt]

Sorry it took me so long to get to this. I've been a bit overwhelmed by the number of AI-assisted PRs opened here recently, and I've also been spending nearly every spare hour on my biggest project so far, MindRoom.

I'm very supportive of using AI for coding, but many of these PRs still need careful human review because even plausible-looking changes can introduce subtle breakage. That backlog made me postpone reviewing them for a while.

I've now done a batch review with Codex / GPT-5.5 (xhigh). This comment is AI-assisted, but I've reviewed it before posting.

This looks reasonable to me. The job-level github.repository == 'basnijholt/adaptive-lighting' condition should skip fork-local validate_hacs runs while still allowing PR checks that run in the upstream repository context.

I do not see a blocker here. I would merge after a rebase/check refresh if branch protection requires it.