[codex] Refresh community listing proof

[luoyuctl]

Summary

• add recently merged community listings to the English and Chinese READMEs
• add the same listing proof to the project site community section
• keep runtime code, release metadata, and npm publication wording unchanged

Validation

• git diff --check
• scripts/ci/check-release-surfaces.sh
• scripts/ci/check-docs-commands.sh
• scripts/ci/check-pages-artifact.sh site
• go test ./...
• go build -o /tmp/agenttrace-listings-check ./cmd/agenttrace
• /tmp/agenttrace-listings-check --version

Notes

• No runtime code changes.
• The local untracked agenttrace binary is not part of this PR.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: PR #194
State change: fixed labels to lane/growth + status/auto-merged after merge
Evidence: PR #194 merged on 2026-05-12 at b169014 and changed only README.md, README.zh-CN.md, and site/index.html. GitHub CI Test and build is SUCCESS. Product post-merge validation on origin/master b169014 passed go build, /tmp/agenttrace-product-check --doctor, scripts/ci/check-pages-artifact.sh site, scripts/ci/check-docs-commands.sh, and scripts/ci/check-release-surfaces.sh. Added proof points are backed by verified merged PRs for walkinglabs/awesome-harness-engineering, rohitg00/awesome-claude-code-toolkit, hashgraph-online/awesome-ai-plugins, and kodustech/awesome-agent-skills; QAInsights/awesome-ai-tools was verified by reading upstream README where agenttrace is listed.
Next owner: Product / Growth

Decision: Product accepts the merged public proof-point update as a docs/site visibility improvement. Follow-up remains on #175 because docs/launch-kit.md still has stale open/merged/manual-only classification and does not yet reflect all verified accepted listings in a clean inventory.