Audit directory listing status before updating public proof points

[luoyuctl]

Background

docs/launch-kit.md tracks a large set of directory/listing submissions, accepted listings, blocked targets, duplicate PRs, and repos that require manual forms or human-only contribution. README currently surfaces only a small accepted-listing set.

Evidence

• docs/launch-kit.md contains many listing PRs and follow-up states across AI coding, CLI, observability, cost, and TUI directories.
• README currently states the project is listed in Awesome Gemini CLI, Charm in the Wild, and Awesome Claude Code and Skills.
• The launch kit also records blocked or sensitive targets such as repos requiring forms, human-only submissions, maturity requirements, or no automated resubmission.
• Product is not allowed to post externally or create external PRs; this needs Growth/human follow-up rather than Product action.

User value

Users should see credible, current public proof points without stale, duplicated, or low-quality directory claims.

Adoption rationale

A tidy directory status improves discoverability and keeps public social proof accurate while avoiding repeated low-quality submissions.

Suggested scope

• Review docs/launch-kit.md directory/listing section and classify entries as accepted, pending, blocked, duplicate/closed, or do-not-resubmit.
• Compare accepted listings against README/site claims.
• Update public-facing accepted-listing copy only when there is verifiable upstream evidence.
• Keep blocked/manual-only targets documented internally for Growth routing, not public promotion.

Non-goals

• Do not submit new external PRs or issues from this task.
• Do not resubmit to targets that rejected automated or duplicate submissions.
• Do not add internal targets, platform metric goals, or artificial popularity language.

Acceptance criteria

• Launch kit directory status is easy for Growth to scan by state.
• README/site accepted-listing claims match verified accepted upstream listings.
• Blocked/manual-only external targets remain clearly marked so agents do not retry them automatically.

Suggested lane

lane/growth

Risk

Medium. Incorrect public listing claims can reduce trust, and repeated low-quality external submissions can harm reputation.

Source

Product blackboard and launch-kit review on 2026-05-10.

[luoyuctl]

Event: Handoff
Actor: Product
Scope: Issue #175
State change: keep lane/growth + status/ready-for-agent
Evidence: docs/launch-kit.md contains many directory/listing PRs and blocked/manual-only targets, while README only surfaces a small accepted-listing set. Product must not post externally or resubmit to external repos.
Next owner: Growth

Handoff to: Growth
Reason: Public proof points should match verified upstream listings, and blocked/manual-only targets need clear status to prevent repeated low-quality external submissions.
Expected output: classify launch-kit directory entries by accepted/pending/blocked/duplicate/do-not-resubmit and update README/site claims only when accepted upstream evidence exists.
Acceptance check: accepted-listing claims are current and blocked targets remain clearly marked for human-only or no-resubmission handling.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: Issue #175
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Local audit of origin/master docs/launch-kit.md on 2026-05-10 found 177 entries under Open PRs, 24 entries under Merged listings, and 17 entries under Manual-only submission. README currently surfaces only three accepted public proof points: Awesome Gemini CLI, Charm in the Wild, and Awesome Claude Code and Skills. All three appear in the launch-kit merged-listings section.
Next owner: Growth

Decision: README public proof points are conservative relative to the launch-kit merged-listings inventory, but the launch-kit itself needs clearer state grouping before any broader public proof-point update.

Handoff to: Growth
Reason: Growth can turn this into a cleaner launch-kit structure without Product posting externally or resubmitting anywhere.
Expected output: keep accepted / open / manual-only / blocked-or-do-not-resubmit states easy to scan, and only expand README/site proof points from entries with verified merged-listing evidence.
Acceptance check: README/site claims remain a subset of verified accepted listings; open PRs and manual-only or do-not-resubmit targets remain clearly separated so future agents do not retry them automatically.

[luoyuctl]

Event: Evidence / Handoff
Actor: Product
Scope: Issue #175
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Rechecked the docs/launch-kit.md Merged listings section on 2026-05-10. 23 GitHub PR URLs under Merged listings verified as MERGED; taishi-i/awesome-ChatGPT-repositories#130 also rechecked successfully after a transient TLS timeout and is MERGED. The Picrew entry is different: Picrew/awesome-agent-harness#5 is CLOSED without merge, and a fresh clone/search of Picrew/awesome-agent-harness found no agenttrace entry on upstream main.
Next owner: Growth

Handoff to: Growth
Reason: The Picrew row should not stay under a plain accepted/merged-listing bucket unless Growth can provide a stronger upstream-main evidence path. Current evidence says it belongs in closed/stale/needs-recheck rather than accepted public proof points.
Expected output: when restructuring launch-kit listing status, keep the 23 verified merged PRs separate from Picrew; move Picrew to a closed/stale/needs-recheck bucket or remove the accepted-listing implication unless upstream evidence is found.
Acceptance check: README/site public proof points remain limited to verified accepted listings, and launch-kit does not describe closed-without-merge entries as accepted without a verifiable upstream-main link.

[luoyuctl]

Event: Queue dependency
Actor: Product
Scope: Issue #175 / PR #156
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: The directory/listing audit remains useful, but PR #156 is still the active open Growth PR and remains draft + status/needs-human with mergeStateStatus=CLEAN and CI green. Product must not submit externally or update public proof points without verified upstream evidence.
Next owner: Growth after PR #156 is resolved / Human

Decision: This remains a valid Growth-ready task, but agents should avoid opening a parallel Growth PR while #156 is still the active blocked Growth vehicle unless a maintainer explicitly authorizes that routing. The most important retained evidence is that 23 merged listing PRs are verified, while the Picrew row is closed-without-merge and should not be treated as an accepted public proof point without fresh upstream-main evidence.

Acceptance check when picked up: launch-kit listing status clearly separates accepted/open/manual-only/closed-or-do-not-resubmit entries, and README/site public proof points remain limited to verified accepted listings.

[luoyuctl]

Event: Evidence
Actor: Product
Scope: Issue #175 / Discussion #2
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: Discussion #2 received a 2026-05-10 comment from yeaight7 saying awesome-ai-devtools approved and displays agenttrace in Terminal Agents and Agent Observability. Product verified upstream yeaight7/awesome-ai-devtools README on 2026-05-11: agenttrace appears in both sections and in New Arrivals dated 2026-05-10. Existing docs/launch-kit.md already has yeaight7/awesome-ai-devtools: https://github.com/yeaight7/awesome-ai-devtools/pull/1 under open PRs, so Growth should reclassify that entry as accepted/verified when #175 is picked up.
Next owner: Growth after PR #156 is resolved / Human

Decision: This is new accepted-listing evidence for the directory audit, but it does not by itself authorize Product to update public README/site proof points or post externally. Keep public proof-point expansion tied to #175 acceptance and the active Growth PR queue.

Acceptance check when picked up: move yeaight7/awesome-ai-devtools from open/pending to verified accepted in the launch-kit status cleanup, preserving the two category links and New Arrivals evidence; README/site proof points should only expand if Growth/Human decides the verified listing is worth surfacing.

[luoyuctl]

Event: Validation / Decision
Actor: Product
Scope: Issue #175 / PR #193
State change: no label change; keep lane/growth + status/ready-for-agent
Evidence: PR #193 merged on 2026-05-11 and added community listing proof to README.md, README.zh-CN.md, and site/index.html; GitHub CI Test and build is SUCCESS. Product post-merge validation on origin/master 609709c 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.
Next owner: Growth after PR #156 is resolved / Human

Decision: #193 improves public proof-point visibility, but #175 is not complete. The launch-kit directory inventory is still not reclassified by accepted/open/manual-only/closed-or-do-not-resubmit, and the newly verified yeaight7/awesome-ai-devtools listing is still represented in docs/launch-kit.md as an open PR entry rather than verified accepted evidence. Keep #175 open and ready for a focused Growth cleanup when the active blocked Growth PR queue allows it.

Acceptance check still remaining: restructure or update docs/launch-kit.md so verified accepted listings, open PRs, manual-only targets, and closed/do-not-resubmit rows are clearly separated; keep README/site public proof points limited to verified accepted listings.