Release: qualify and publish optional Graphify context in v1.4.1

[jeffhuber]

Part of #902.

Problem

The optional provider needs a clear install/setup path, reproducible scorecard, and release boundary after Devin v1.4.0.

Scope

Add the optional integrations picker entry, install/upgrade/docs, no-provider rehearsal, isolation/staleness tests, comparative benchmark, sanitized scorecard, version/release artifacts, campaign, Board verification, and allowlisted CodeMower.com metadata upload.

Dependencies

• Graphify: bounded query normalization and context packets #914
• Release: publish and qualify Code Mower v1.4.0 with Devin peer support #912

Acceptance criteria

• Default Claude + Codex installation gains no Graphify dependency or indexing step.
• The Context: evaluate official Graphify as a local repository provider for v1.4.1 #876 adoption thresholds remain satisfied on the release candidate.
• Fresh install, package matrix, full tests, privacy, current-head audits, and gate pass.
• v1.4.1 is published/installed/qualified before Slack release.
• Uploaded data contains no graph, query, path, citation, or source content.

Code Mower delivery

Produce exactly one independently reviewable PR for this issue. Record the named builder, keep one writer on the branch, run focused tests and applicable full checks, obtain an independent Code Mower review against the exact current head, resolve every P0/P1/P2 finding, and pass normal CI plus code-mower/gate. Update the parent epic with PR/head, review, validation, outcome, and safe metadata-only upload evidence. Do not put credentials, source, diffs, prompts, transcripts, private context, task/message prose, or raw provider output in cloud data.