docs: add Playwright feedback issue links

Author: aaronlab

docs/launch/day-3-targeted-communities-packet.md

@@ -178,6 +178,9 @@ https://aaronlab.github.io/browsertrace/trace.html
 Repo:
 https://github.com/aaronlab/browsertrace
 
+Playwright + LLM feedback issue:
+https://github.com/aaronlab/browsertrace/issues/12
+
 It records screenshot, URL, action label, model input/output, and failed-step
 error into a local timeline. It is not a replacement for Playwright Trace Viewer;
 it is for Playwright scripts where an LLM is part of the control loop.

docs/launch/metrics-log.md

@@ -60,3 +60,4 @@ uv run --python 3.11 python scripts/launch_metrics.py --json
 | 2026-05-09T10:49:38+00:00 | 3 | 998 | 0 | 0 | 7 | 0 | 0 | after owner launch checklist issues updated with stack landing pages |
 | 2026-05-09T10:52:41+00:00 | 3 | 998 | 0 | 0 | 7 | 0 | 0 | after comparison landing page added |
 | 2026-05-09T10:55:33+00:00 | 3 | 998 | 0 | 0 | 7 | 0 | 0 | after Browser Use no-dependency callback demo added |
+| 2026-05-09T10:57:03+00:00 | 3 | 998 | 0 | 0 | 8 | 0 | 0 | after Playwright LLM feedback issue: https://github.com/aaronlab/browsertrace/issues/12 |

docs/launch/outreach-targets.md

@@ -96,6 +96,7 @@ real reply or question to reference.
    - Best angle: "This is for Playwright scripts that include LLM decisions, not
      a replacement for Playwright trace viewer."
    - Link order: Playwright + LLM guide first, live trace second, repo third.
+   - Link to the Playwright + LLM feedback issue if asked for a tracking thread.
    - Use Discord or LinkedIn only when the topic is LLM-guided automation.
      Share only the debugging write-up unless people ask for the repo.
 4. Skyvern Discussions

docs/llms.txt

@@ -25,6 +25,7 @@ to explain why a browser run failed.
 - Press kit: https://aaronlab.github.io/browsertrace/launch/press-kit.html
 - Release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.6
 - Launch discussion: https://github.com/aaronlab/browsertrace/discussions/6
+- Playwright + LLM feedback: https://github.com/aaronlab/browsertrace/issues/12
 
 ## Core Capabilities
 

docs/playwright-llm-debugging.html

@@ -203,6 +203,7 @@ <h1>Debug Playwright scripts where an LLM chooses the next browser action</h1>
       <a class="button primary" href="https://github.com/aaronlab/browsertrace">View repo</a>
       <a class="button" href="./trace.html">Open exported trace</a>
       <a class="button" href="./integrations.html#playwright">Integration snippet</a>
+      <a class="button" href="https://github.com/aaronlab/browsertrace/issues/12">Feedback issue</a>
     </div>
 
     <section>
@@ -257,7 +258,7 @@ <h2>Share only what is safe</h2>
 
     <section>
       <div class="note">
-        BrowserTrace is not a replacement for Playwright Trace Viewer. It is a local layer for Playwright scripts where LLM decisions are part of the bug.
+        BrowserTrace is not a replacement for Playwright Trace Viewer. It is a local layer for Playwright scripts where LLM decisions are part of the bug. Playwright + LLM feedback is tracked in <a href="https://github.com/aaronlab/browsertrace/issues/12">issue #12</a>.
       </div>
     </section>
   </main>