feat(site-deployment): multi-tenant per-client deploy targets (MT)

[cryptoxdog]

What & why

Threads a per-client site_deployment transport config end-to-end so each client's autonomous surpass-plan edits write to that client's repo / Vercel deploy hook instead of the single shared WEBSITE_BOT_REPO. This is the C-02 enabler for multi-tenant serp:execute-surpass-plans.

The scheduler fan-out already attaches the full clients.config jsonb as job.data.clientConfig to every per-client job, so this is a surgical thread-through — no schema migration (clients.config is jsonb).

Code-only. The enabled:false → true flip on serp:execute-surpass-plans is intentionally not in this PR — it stays a separate operational change made only after real per-client config is in the DB. Safety is enforced at the siteConfigFromClient boundary, so the flip is safe-by-construction once config exists.

Changes

• types (src/types/index.ts) — add ClientSiteDeploymentConfig and an optional site_deployment on ClientConfig.
• site-deployment (src/services/site-deployment.ts)
  • siteConfigFromClient(clientConfig) — builds the per-tenant config with the same dry-run safety invariant as siteConfigFromEnv: absent or blank token/repo (and the NODE_ENV/SITE_DEPLOY_DRY_RUN env kills) force dryRun:true. A half-populated site_deployment never performs a live write.
  • optional trailing config?: SiteDeploymentConfig on all 7 action fns (updateMetaTitle, updateMetaDescription, injectSchema, updateHeading, rewritePageContent, updateFaq, triggerVercelDeploy). Additive — existing no-arg callers still compile.
• plan-executor (src/services/plan-executor.ts) — widen ActionDispatcher with a 4th siteConfig param (alias updated before any dispatcher body), resolve siteConfigFromClient(job.data.clientConfig ?? {}) in executeSurpassPlans, thread it through every dispatch and the final triggerVercelDeploy. faq_content_update keeps its documented no-op.
• add-client (scripts/add-client.ts) — prompt for + store config.site_deployment; warn when incomplete (client operates in dry-run).

Tests

• siteConfigFromClient: full→dryRun:false; missing token→dryRun:true; empty-string repo→dryRun:true (G6); NODE_ENV=test global kill honored even with a full config.
• updateMetaTitle with an explicit config reads/writes against the injected repo, not the env fallback.
• plan-executor: configured client routes its edit + final deploy to that client's repo; no site_deployment → dry-run fallback; faq_content_update dispatches no write (G3).

Verification

• tsc --noEmit = 0 (the sole remaining error is a pre-existing @infisical/sdk module-resolution artifact of this sandbox's dependency install, unrelated to this change and resolved in CI).
• vitest run — 40/40 green.

Rollback

If a future enable-flip causes an unintended write: flip enabled:true → false and redeploy; confirm no job re-enqueues next cycle; audit recent gapAnalyses rows at status='executing'.

🤖 Generated with Claude Code

---

Generated by Claude Code

[Copilot]

Pull request overview

This PR threads a per-client site_deployment transport configuration through the surpass-plan execution path so autonomous edits/deploys target each tenant’s own GitHub repo and Vercel hook (instead of the shared env-based WEBSITE_BOT_REPO).

Changes:

• Adds ClientSiteDeploymentConfig and optional site_deployment on ClientConfig for MT deploy targets.
• Introduces siteConfigFromClient(...) and threads an explicit SiteDeploymentConfig through site-deployment action functions and the plan executor dispatch path.
• Extends the add-client onboarding script and adds/updates tests for MT config resolution and routing.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
tests/services/site-deployment.test.ts	Adds coverage for siteConfigFromClient dry-run guard and explicit-config repo routing in updateMetaTitle.
tests/services/plan-executor.test.ts	Verifies per-client config threading through dispatch + deploy, dry-run fallback, and FAQ no-op behavior.
src/types/index.ts	Adds ClientSiteDeploymentConfig and optional site_deployment field to ClientConfig.
src/services/site-deployment.ts	Adds siteConfigFromClient and threads optional config through deployment actions / deploy trigger.
scripts/add-client.ts	Prompts for and stores config.site_deployment during onboarding, warning when incomplete (dry-run).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud