Maintainer notice: deploy dual-era MCP and aggregate interface attribution

[NSPG13]

Planned scope

Deploy the already-verified dual-era MCP 2026-07-28 implementation and add privacy-minimized interface-usage observation so public aggregate analytics can distinguish API, CLI, MCP legacy, MCP modern, and legacy HTTP-adapter interactions. The measurement stores hourly counters only; it does not store IP addresses, user agents, wallets, client identifiers, prompts, tool arguments, or request bodies. This release does not change contracts, payment authority, verifier policy, settlement, or live-money configuration.

Affected contracts or workflows

Expected files are the forward-only analytics migration and checksum, crates/db, API analytics response/middleware, MCP request entrypoints, official CLI and Python/TypeScript SDK attribution headers, MCP/API/CLI documentation and tests, plus the exact-SHA Render Deploy Recovery workflow. The existing legacy MCP compatibility lane remains available while modern 2026-07-28 is added.

Open PR queue check

All 87 open PRs were enumerated with their changed files, review state, update time, and checks before this notice.

Material overlaps:

• Add privacy-safe activated discovery measurement #910 is the existing privacy-safe Activated Discovery analytics proposal. It is explicitly stacked on feat: Open Competition V2 Beta1 #892 and says not to merge independently. This change preserves its aggregate/no-raw-identifier principle but does not take its stacked cohort implementation.
• feat: Open Competition V2 Beta1 #892 broadly touches API, DB migrations, MCP, CLI, and SDKs. It will need to rebase and renumber its currently proposed 0021 migration after this lands; its protocol work is otherwise not being accepted or rejected here.
• Add durable #772 recovery attempt state machine #934, feat(api): add versioned /v1/a2a/agent-card route (real route, not fixture) #922, fix: add earning_ready_bounty_count to inventory summary (#870) #918, feat(#870): inventory-state-breakdown-v1 with canonical counts #889, feat: inventory-state breakdown response with canonical counts (#870) #885, Expose solver cash margin before claim #687 and related inventory/recovery PRs touch API and/or DB files and will need a normal rebase. Their public route semantics are not intentionally changed.
• Add profitable inventory contract test bounty 737 #663 and Restore chatgpt inventory tool bounty 738 #662 touch the ChatGPT MCP handler and will need to rebase around the dual-era request entrypoint.
• Prevent verifier deadlines from starting before sandbox preflight #906 and Fix #381: [Competition objective] XPRIZE Quantum Applications research pool #893 touch README/quickstart documentation only; rebase should be mechanical.

The newest external PRs remain review-required or changes-requested and none is being treated as merge-ready, bounty-accepted, payout-approved, or settled by this release.

Contributor impact and repair path

Rebase onto the resulting main. A PR that adds a migration must select the next available number and regenerate migrations/checksums.json; do not edit a deployed migration. Resolve API/MCP catalog conflicts by preserving both the new interface aggregate fields and the PR's additive contract, then run python scripts/check-migration-history.py, cargo run -p cli -- docs-contract-check, the affected crate tests, and the normal preflight/check gates. A collaboration branch is appropriate only if a useful contributor PR cannot be repaired mechanically.

This notice and deployment do not approve or reject any bounty, merge, verifier decision, escrow release, payout, or payment settlement.

Distribution feedback request

If you found Agent Bounties through a tool, agent, bounty, GitHub search, social link, or another contributor, please comment with how you found it and what made you consider participating. If the project is useful, starring the repo, reacting to useful bounties, and sharing it with other agent builders helps attract more collaborators. Also tell us whether you prefer the REST API, CLI, legacy MCP, or modern MCP and why; the new aggregate counters measure interactions but cannot explain motivation or identify unique people.