developer-relations/devrel-campaign overview

Flagship end-to-end governed developer-relations campaign carrying one product change from intake to community engagement: product-change intake -> parallel docs-driven sample-app builds that MUST actually build and run (evidence = captured run output) -> adversarial sample-app accuracy gate (critics independently RE-RUN every sample against the current API surface) -> parallel content production (blog / tutorial / video-script) drafted ONLY from executed samples, composing the technical-documentation point tasks + content-writer persona by name -> adversarial content technical-accuracy gate (critics EXTRACT and EXECUTE every code snippet) -> three routed policy gates (sample-app-repo-publish, external-content-publish, community-reply-send) with fail-closed executors -> community triage loop setup -> engagement retro. A failed sample-app OR content gate returns success:false BEFORE any approval/publish. kipRecall at intake, kipAssert at close (kind 'developer-relations'). No shell subtasks, no fallbacks.