Repository navigation
docs: replace AI support handoff with email guidance - #950
Conversation
Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR removes the docs Kapa support handoff form and backend endpoint, replacing the in-chat ticket path with a direct support@warp.dev mailto prompt while preserving the chat reCAPTCHA disclosure.
Concerns
- No blocking correctness, security, documentation-quality, comment-guideline, or test-guideline concerns found in the annotated diff.
- Spec alignment was not evaluated because
spec_context.mdstates that no approved or repository spec context was found for this PR.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Co-Authored-By: Warp <agent@warp.dev>
Co-Authored-By: Warp <agent@warp.dev>
Summary
/api/support-handoffroute and its dedicated environment configuration.The handoff flow has seen limited usage, so this keeps the support path clear while centralizing email, Slack, and other support channels on the existing docs page. The chat does not imply that conversation data will be attached or sent.
Related issues
None.
Validation
npm run test:kapa-support-escalation- passed, 4/4 testsnpm run test:kapa-webmcp- passed, 2/2 testsnpm run typecheck- passed with 0 errorsnpm run lint- passednpm run build- passednpm run test:heading-tocs- passednpm run test:heading-vars- passed, 5/5 testsnpm run test:homepage-json-ld- passedScreenshots
Vercel preview provides the updated support-escalation UI; no other chat surfaces changed.
Follow-ups
Co-Authored-By: Warp agent@warp.dev
Warp artifacts
Implementation conversation
Decommission plan