Validate BugBundle with five external repositories

[zhou-wang-git]

BugBundle needs external workflow evidence before expanding the product surface or applying to Codex for Open Source.

Validation targets

• 5 external repositories adopt the BugBundle policy or issue workflow
• 20 reviewed reproduction bundles are created for real failures
• 3 maintainers provide a testimonial or link a resolved issue
• 1 external contributor lands a change
• contributor friction is documented at each step (preview, capture, review, upload, verify)

Pilot workflow

1. Recruit maintainers through the design-partner discussion.
2. Help each repository review the GitHub adoption kit.
3. Track only public, consented evidence. Never collect or retain private bundles.
4. Convert repeated friction into small issues with deterministic acceptance tests.
5. Reassess the CLI-versus-GitHub-Action direction after five repository trials.

This issue tracks outcomes, not npm download counts alone; automated registry traffic is not evidence of a successful maintainer workflow.

[zhou-wang-git]

Outreach batch — 2026-07-19

• Packem: Idea: try a reviewed BugBundle on one future Packem report? visulima/packem#229
• tsdown: Idea: complement tsdown reproduction links with a deterministic bug bundle rolldown/tsdown#1024
• Changesets: Idea: portable reproduction evidence for Changesets CLI failures changesets/changesets#2170

Status: awaiting maintainer responses. These are design-partner invitations, not validated adoption, and should not be counted toward the five-repository target unless a maintainer agrees to test or integrate BugBundle.