What does this PR do?

Cleans up the deploy-site.yml workflow to reflect the new deployment architecture. The landing page has moved to a separate Vercel project, so this repo no longer needs to build or deploy it. The workflow now has two independent jobs:

1. deploy-vercel — On release, curls the Vercel deploy hook so the landing page picks up the new version number in its footer.
2. deploy-docs — Builds Docusaurus and deploys to GitHub Pages as before.

The old workflow merged the landing page and docs into a single _site/ artifact. That staging step and the landingpage/** path trigger have been removed. The CNAME injection is also gone since DNS is managed through Vercel now. Docusaurus's baseUrl: '/docs/' ensures docs continue to be served at the correct path.

Related Issue

N/A — infrastructure cleanup

Type of Change

• ♻️ Refactor (no behavior change)

Changes Made

• .github/workflows/deploy-site.yml — Replaced the single build-and-deploy job with two independent jobs (deploy-vercel and deploy-docs)
• Removed landingpage/** from push path triggers
• Removed the staging step that merged landingpage/ + website/build/ into _site/ with a CNAME file
• Docs artifact now uploads website/build directly instead of the assembled _site/docs/ directory
• Added release: types: [published] trigger for the Vercel deploy hook

How to Test

1. Verify docs still build: push a change to website/ on main and confirm the deploy-docs job runs and deploys to GitHub Pages at /docs/
2. Verify Vercel hook fires: create a release and confirm the deploy-vercel job runs (check the Vercel dashboard for a new deployment)
3. Confirm hermes-agent.nousresearch.com/docs/ still loads correctly after deployment

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features) — N/A (CI workflow only)
• I've tested on my platform — N/A (CI workflow only)

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A