[P0][Plan 6] SF-038 — Prove V1 with real providers, connectors, MCP, exports, and release gates

[Ankit6149]

Confirmed problem

Builds, unit tests, public route checks, and sparse production logs do not prove the credential-dependent product works. Real provider generation, twelve-channel load, partial failure recovery, OAuth connectors, live posting, refresh behavior, external MCP use, and full responsive acceptance remain unverified.

Scope

• Build a versioned acceptance matrix covering providers, source combinations, all twelve destinations, failure modes, persistence, exports, browsers, account states, MCP, and deployment.
• Verify at least Gemini and OpenAI with low-spend test keys; add Claude or OpenRouter as a compatibility route.
• Verify connector implementation, credentials, authorization, refresh, rejection, and posting as separate gates.
• Run external MCP client tests for the complete implemented workflow.
• Add CI, preview, production smoke, observability, correlation IDs, spending controls, incident handling, evidence storage, and rollback.

Acceptance criteria

• All Plan 1–5 acceptance gates pass.
• At least two real model providers pass short-form, long-form, and full twelve-destination campaigns.
• No P0 or P1 issue remains open.
• Every public capability claim matches verified evidence.
• Unverified connectors remain clearly marked unverified.
• Owner-only production smoke and tested rollback pass.
• Evidence contains no keys, tokens, prompts, private source content, or raw provider responses.

Required verification

• Execute and store the complete sanitized acceptance matrix.
• Run all CI checks from a clean clone.
• Preview smoke, production promotion, production smoke, controlled failure tracing, and rollback test.
• Verify docs, privacy, llms files, metadata, and UI claims after deployment.

Definition of done

Do not close this issue because code exists. Close it only when reproducible credential-backed evidence proves the product behavior described above.