mirror of
https://github.com/aaddrick/claude-desktop-debian.git
synced 2026-05-17 00:26:21 +03:00
b351d42a2d
* docs(upstream-reports): draft anthropics/claude-code report for #546 Adds a ready-to-file draft of the upstream MCP double-spawn report, matched to the anthropics/claude-code bug_report.yml schema and written in aaddrick's documented voice. Includes a filing checklist (GitHub issue + in-app /bug + bidirectional comment back on #546) and a note about the template mismatch since the form is built for the Claude Code CLI rather than Claude Desktop. Refs #546 Co-Authored-By: Claude <claude@anthropic.com> * docs(upstream-reports): link claude-desktop-debian repo in draft body Co-Authored-By: Claude <claude@anthropic.com> * docs(upstream-reports): add download-rate context next to repo link Adds an approximate "~2,300 package downloads/day across the last 3 releases" parenthetical so the upstream report leads with a sense of how many users the bug affects. Computed from GitHub release asset download counts: 13,823 installable binary downloads (deb + rpm + AppImage, both arches) across 1.5354.0, 1.5220.0, and 1.4758.0 over a ~6-day window. Co-Authored-By: Claude <claude@anthropic.com> * docs(upstream-reports): voice pass on draft body and title Refines the draft for the upstream `anthropics/claude-code` issue through the aaddrick-voice profile. Changes are surgical: - Title: em-dash separator → colon (matches voice's documented preference for colons; removes em-dash signal site-wide). - "What's Wrong?": opens with personal-experience framing ("I was reading", "What I found"), splits compound sentences, swaps announcement-colons for periods. - "What Should Happen?": same period-for-colon swap on the fix paragraph. No content shifts. Symbol table, code blocks, log signals, links, and form-field labels untouched. Co-Authored-By: Claude <claude@anthropic.com> * docs(upstream-reports): drop bogus /bug filing step User confirmed `/bug` and `/feedback` are inert in both Claude Desktop and Claude Code. Earlier web research suggesting they route to engineering was wrong. Replaced step 4 of the filing checklist with a note about what's actually in the Help menu (Get Support goes to the support chat, wrong queue) and what the Troubleshooting submenu IS useful for (attaching Installation ID / logs to a GitHub issue). Co-Authored-By: Claude <claude@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Claude <claude@anthropic.com>