Why

The awesome-list submission notes include a troubleshooting reply for reviewer follow-up, local first-run issues, CI failures, and AI/coding-agent debugging. That reply should route security-sensitive reports or private trace data to the Security Policy before anyone posts details publicly.

Scope

Update docs/launch/github-awesome-list-submissions.md in the Troubleshooting Reply section with a short note that links SECURITY.md and tells contributors to use the private security path before sharing sensitive details publicly. Keep the existing JSON CLI diagnostics and First PR Recipe links.

Contributor coordination

If you want to work on this, comment here first. Maintainers will treat that comment as an active claim and leave a short claim window before taking the same issue directly.

Acceptance criteria

• docs/launch/github-awesome-list-submissions.md links SECURITY.md from the troubleshooting reply area.
• The note mentions security-sensitive reports or changes and private trace data.
• Add or update a metadata test so this guidance does not regress.
• Do not add any request for stars, upvotes, reposts, or promotional engagement.

Suggested verification

uv run --python 3.11 --extra dev pytest -q tests/test_metadata.py -k awesome_list_submission
uv run --python 3.11 --extra dev pytest -q tests/test_metadata.py
uv run --python 3.11 --extra dev pytest -q
git diff --check