feat: bug report AI drafting extension

[adrians5j]

Adds bug-report-ai, installable with webiny extension bug-report-ai.

Webiny 6.6.0 ships a bug reporter in every project (webiny/webiny-js#5736): cmd+shift+b in the Admin app, describe what broke, paste a screenshot, and a GitHub issue appears with the environment and a timeline of the last few minutes attached. On its own it files what the reporter typed, verbatim. This extension decorates that with a model call, producing a searchable title, a summary and steps to reproduce.

It lived in the webiny-js monorepo until now, which meant nobody outside the team could use it.

Shape

Follows whitelabeling, since this is an Api.Extension registered by src path rather than a component imported from the project:

"imports": [{ "specifier": "Api", "path": "webiny/extensions" }],
"component": { "name": "Api.Extension", "props": { "src": "/extensions/bugReportAi/Extension.ts" } }

packageJson brings ai and zod, matching the versions @webiny/ai-powerups resolves.

Why a decorator, not a replacement

The built-in drafter is the fallback and is used on two of the three paths through here: no model role configured, and the model call failing. Only a successful draft discards it. Losing a report because drafting broke would be the worst possible trade, since the reporter has already spent the effort. Everything factual in the issue is assembled by the bug reporter regardless, so a report that falls back is still complete. Deleting the extension puts the reporter back as it was.

Version folder

6.6.x, not 6.0.x. The extension imports webiny/api/bug-reporter, which does not exist before 6.6.0. Checked how that resolves:

Project version	Resolves to
0.0.0-local-npm.*	6.6.x
6.6.0, 6.6.3, 6.7.0	6.6.x
6.5.0	nothing, install fails

Failing on 6.5.0 is the point. 6.0.x would have installed an extension that cannot build.

Verification

Ran the installer's own updateWebinyConfig and mergePackageJson from webiny-js against a freshly scaffolded aws/ddb config, rather than reasoning about the JSON:

import { Infra, Api } from "webiny/extensions";
...
            <Cognito />
                <Api.Extension src={"/extensions/bugReportAi/Extension.ts"} />

Api merged into the existing webiny/extensions import rather than adding a second one, and ai and zod landed in dependencies. I did not run a full deploy against a live project.

The extra indentation on the inserted line is the installer, not this config: whitelabeling produces exactly the same thing through the same code path. Worth a fix in addComponentToExtensions upstream at some point.

Schema drift, not introduced here

extension.json breaks three rules in schemas/extension.schema.json, all of them identical to what whitelabeling already does: type is marked required, the import path pattern demands a relative ./… specifier, and the component name pattern disallows a dot. No extension in this repo has type, and the two dotted-component extensions are the ones that actually install, so the schema has drifted from what the installer accepts. Following the schema here would have produced something that does not work. Worth reconciling separately.

Docs for the bug reporter itself: webiny/docs.webiny.com#830.

Workspace: wby-next3 · ✨ BUG REPORTER - FINALS

🤖 Generated with Claude Code