feat: fallback to site llmo folder for onboarding publish

[Copilot]

llmo-onboarding-publish handler lacked a fallback when auditContext.dataFolder was absent from the SQS message, causing silent failures.

Changes

• Handler (src/llmo-onboarding-publish/handler.js): resolves dataFolder via a 3-level chain:

  1. auditContext.dataFolder (SQS message)
  2. context.site.getConfig().getLlmoDataFolder()
  3. Site.findById(siteId).getConfig().getLlmoDataFolder()

  Skips publish with a warn log when no folder resolves. Handler remains a side-effect worker (no downstream enqueue).

• Tests (test/audits/llmo-onboarding-publish.test.js): covers all fallback paths, missing siteId, missing folder in both message and site config, and publish-helper error swallowing.

Related Issues

Thanks for contributing!

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• github.com (HTTP Only)
  • Triggering command: /usr/bin/ssh ssh -oStrictHostKeyChecking=accept-new -o SendEnv=GIT_PROTOCOL git@github.com git-upload-pack '/adobe/mysticat-data-service.git' (packet block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)