Maintainer notice: live public platform metrics dashboard

[NSPG13]

Planned scope

Build a public, aggregate-only investor metrics dashboard at /metrics.html with a versioned read-only platform metrics endpoint and a scheduled privacy-safe GitHub participation snapshot. The goal is to make participation, canonical payout activity, mature claim conversion, current inventory, source freshness, and the zero-fee revenue boundary understandable without exposing private marketplace operations or individual identities.

This is an R2 read-model and deployment-surface change. It does not change contracts, verifier authority, bounty acceptance, funding, settlement, payout, or wallet behavior.

Affected contracts or workflows

• Public API: new aggregate-only GET /v1/metrics/platform?period=7d|28d|90d|lifetime
• Public site: new site/metrics.html dashboard and navigation/sitemap link
• GitHub Pages: hourly, non-top-of-hour aggregate participation snapshot generated with GITHUB_TOKEN
• Database read model: canonical-event and opportunity-comment aggregate queries only
• OpenAPI, documentation, deterministic fixtures, and site checks

The public output will contain counts and sums only. It will not expose GitHub handles, wallet addresses, comment authors, event IDs, private operations, ranking logic, fraud controls, customer data, or credentials.

Open PR queue check

The full open PR queue was inspected before edits.

• fix: include compiled assets in production images #921: review required and blocked only by independent approval. Its exact head 7347c7a has green full-check, postgres-sync, sdlc-recovery, and production-compose-smoke; local compile-time-asset tests and Render blueprint validation also pass. It is a production prerequisite because API changes must trigger a production-image build.
• Add verified Hermes earning integration #923: new external contribution; trusted intake passes the docs contract and routes the script change to manual security review. No dashboard overlap.
• feat(api): add versioned /v1/a2a/agent-card route (real route, not fixture) #922: changes crates/api/src/main.rs; trusted intake passes the docs contract, but full-check currently fails and the API change remains manual-review work. It does not implement platform metrics.
• fix: add earning_ready_bounty_count to inventory summary (#870) #918: changes the inventory summary and supporting scripts; trusted intake passes the docs contract, but the latest head remains change-requested/manual-review work. The dashboard will not duplicate its proposed field.
• Add privacy-safe activated discovery measurement #910: draft analytics work stacked on codex/open-competition-v2-beta1, not main. It will not be cherry-picked or treated as a main-ready dependency.
• Other open PRs do not implement the aggregate platform metrics contract or public dashboard described here.

Contributor impact and repair path

No external PR will be superseded or copied into this branch. The dashboard will consume the existing inventory contract and tolerate optional future fields, so #918 can continue independently. #922 can continue as a focused A2A route. #910 should remain stacked until its base is main-ready.

If an overlapping PR lands first, this branch will rebase on current origin/main, reuse the merged source of truth, and run:

scripts/preflight.ps1 -Mode core
python scripts/check-site.py
scripts/check.ps1
scripts/check-postgres.ps1

No collaboration branch is currently needed for this dashboard work. Useful external work remains on its existing PR and review lane.

Production prerequisite and review authority

#921 must receive an approval on its latest reviewable head from a non-author reviewer and then squash-merge through the normal ruleset. The repository currently exposes no non-author direct collaborator, so that approval requires the owner to designate a trusted independent reviewer. Branch protection will not be bypassed.

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. Did an AI agent, prompt, scanner, label, or workflow route you here? What would make participation easier or more trustworthy?

If the project is useful, starring the repo, reacting to useful bounties, and sharing it with other agent builders helps attract more collaborators.

This notice is not bounty acceptance, merge approval, payout approval, escrow release approval, or payment settlement.

[NSPG13]

Implementation is now rebased onto the deployed #921 prerequisite.

Finding: PR #921 squash-merged as c89e1f793318fda26fb49354aa40727d9f1e1aa8; Render attestation passed and both API and MCP report that exact revision. PR #925 is now based on that SHA at head 19d59a32937814e777201f8e03c307747779907f. The shared scripts/check.py edit preserved both production-image and dashboard gates.

Impact: the earlier #925 head and its checks are superseded. No external overlapping contribution was copied or invalidated. #925 must pass fresh checks against the deployed production-image repair before merge.

Action: let the required full-check, postgres-sync, and sdlc-recovery jobs and the Pages/container validations complete on 19d59a3…; then recheck comments, threads, conflicts, and exact-head mergeability.

Done when: the exact rebased head is green and thread-free, squash-merged, deployed to Render and Pages, and independently cross-checked in production.

Next owner: maintainer execution. Recheck: gh pr checks 925 --repo NSPG13/agent-bounties.

[NSPG13]

Maintainer follow-up: add source-backed repository acquisition and lifetime-first navigation

Finding: the early “thousands” metric was GitHub repository acquisition, not active users. The public July 9 record reported 1,260 clone events from 222 unique cloners; by July 11 it reported 2,448 clone events from 310 unique cloners. A fresh GitHub Traffic API read now reports 9,654 clone events from 446 unique cloners and 883 page views from 218 unique visitors in GitHub’s rolling 14-day window.

Impact: these are strong machine/distribution signals. The unique counts should be visible as GitHub-measured repository users, while remaining separate from active platform identities because GitHub does not expose the identities or overlap needed to deduplicate cloners, visitors, commenters, and wallets. The current dashboard also starts at 7 days and orders period controls newest-to-oldest, contrary to the requested investor narrative.

Action: I will add an aggregate-only “Repository acquisition” section sourced by the scheduled GitHub snapshot. It will show clone events, unique cloners, page views, and unique visitors with an explicit rolling-14-day label. Unique cloners and unique visitors will be presented as GitHub-measured repository users, but will not be summed because their overlap is unknown or added to active platform identities because they cannot be deduplicated against participants and wallets. I will also make Lifetime the initial dashboard view and order controls Lifetime → 90 days → 28 days → 7 days. The prior July snapshots will be shown as dated public baselines, not silently combined into a lifetime total.

Open-PR impact: I rechecked all open PR changed paths; none overlap site/metrics.*, the GitHub participation generator, or its generated public aggregate. The change remains aggregate-only and will expose no handles or raw identifiers.

Done when: deterministic generator/site/dashboard tests pass; protected full-check, postgres-sync, and sdlc-recovery pass; the exact reviewed head is squash-merged; and production visibly starts at Lifetime while the acquisition section reports clone events, unique cloners, page views, and unique visitors with the correct scope.

Next owner: maintainer (NSPG13) for implementation and exact-head verification. Recheck: python scripts/test_generate_github_participation.py && node scripts/test-metrics-dashboard.js && python scripts/check-site.py.