publicity: audit existing outreach PRs and make featured-in claims traceable

Opportunity / evidence

docs/promotion-pr-tracker.md is marked last audited 2026-07-28 and has many open outreach entries. README separately claims featured placement in 37 curated lists. Those are different concepts (submission, merge, and present-day listing), and the repository does not provide an obvious reproducible mapping for the headline count.

This does not assert the count is false. Audit existing evidence before increasing outreach volume.

Acceptance

• Maintain structured records with target repo, submitted PR, state, checked-at timestamp and an actual listing permalink when verified.
• Recheck existing PR status and default-branch listing presence using read-only GitHub queries; distinguish open, merged/listed, closed-unmerged and no-longer-listed.
• Deduplicate repositories and define whether a featured count means merged submissions or currently verified listings.
• Generate or cross-check the Markdown tracker and any README count from the same records; retain historical notes.
• Choose a small next set of relevant opportunities only after duplicate and contribution-rule checks, with a target-specific reason rather than a bulk submission quota.
• Do not send automated reminders, self-upvotes, heartbeat commits or unsolicited repeated submissions as part of the status audit.

This is maintenance of existing repository-owned outreach records and substantiation of publicity claims. It does not reopen website-only requests or require new external PRs to call the audit complete.

@Perry2004 please review the definition of verified inclusion and the next outreach priorities.

Start with docs/promotion-pr-tracker.md and the README claim of 37 curated lists. Review existing outreach entries, then use read-only GitHub queries to record target repositories, submitted PRs, states, checked-at timestamps, and verified listing permalinks. Done means duplicate repositories are resolved, the featured-count definition is explicit, and the tracker and README count are cross-checked from the same records while retaining historical notes.