ci: annotate instead of failing on dispatch error

[pratyush618]

Follow-up to #28, which merged before this landed on the branch.

gh api runs after actions/deploy-pages@v5, so a non-zero exit marks the deploy job failed even though Pages already published. A missed dispatch costs freshness, not the release — the portal's daily cron still picks the docs up — so the call now falls back to an ::error:: annotation. The failure stays visible in the run summary without turning a successful deploy red.

Chose that over continue-on-error: true, which would swallow it silently. Same change already merged in ByteVeda/reclink#71 and pending in ByteVeda/agenteval#137 and ByteVeda/flexiq#875.

[coderabbitai]

Warning

Review limit reached

Next included review available in 49 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 3 included reviews currently available. Your 40 included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 355ca861-1412-4379-b081-273f42c77653

📥 Commits

Reviewing files that changed from the base of the PR and between d13abaf and 6ee478e.

📒 Files selected for processing (1)

• .github/workflows/docs.yml

---

_{Comment @coderabbitai help to get the list of available commands.}