Host-provider reuse checkpoint¶
The existing provider-neutral contract was exercised with a real host research method and a host-managed GitHub connector reading public source. The method reused gh, a public Jina Reader request and anonymous Exa MCP search through mcporter; the connector read a commit-pinned Browser Harness README. No new crawler, provider protocol, account configuration or research authority was added.
Both successful routes returned exact-plan receipts and separate parent
admissions. Four method source records and one connector source record projected
into the existing deepresearch ledger with matching lineage; native readback
reported no write blockers and retirement readiness. A separate browser-source
connector attempt returned source_content_not_ready; its failed receipt had no
sources, was explicitly rejected and became retirement-ready without evidence
projection. An earlier successful probe was not substituted for this failure.
These are caller-declared observations, not authenticated execution attestations. The bounded result qualifies use of the existing CLI provenance journey for these operations. It does not qualify private-repository scope, all browser URLs, paid search capacity, authenticated Exa Agent, live frontend/Lark delivery, or overall research completeness. X discovery mostly yielded promotional posts; their technical claims were not admitted.
The reusable operating route is in the capability guide. Keep raw observations and host identities private. Next qualification belongs to the existing provider/surface owners: bounded revoke/failure/recovery and real downstream presentation, rather than another generic executor.