It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

Addressed Gemini feedback in head 9ef677d4a0: the tool crash paths now use explicit stable exception category names instead of interpolating runtimeType, and PreparePackageException / UnpublishException are final before using explicit class names in toString().

Addressed the review feedback in 607ee2b. The bot exceptions now use $PreparePackageException / $UnpublishException, and _errorTypeName keeps the unknown-error runtimeType fallback with a local avoid_type_to_string comment explaining why Object is too lossy there. Verification rerun: formatter, targeted analyze, runner_test.dart, prepare_package_test.dart, unpublish_package_test.dart, and git diff --check all pass.

Updated in 4fc4d62 to match the maintainer feedback: the tool crash analytics path now keeps error.runtimeType.toString() with a local suppression comment, and the _errorTypeName mapping helper is removed so unknown crash types are not collapsed. The bot exceptions still use $PreparePackageException / $UnpublishException with focused tests. Verification rerun: targeted analyze, runner/github_template tests, bot exception tests, formatter check, and git diff --check.

Addressed the last review thread in 29c127e: sanitizedCrashException now keeps runtimeType.toString() for unknown crash objects so generated GitHub issues preserve the concrete error type, with focused coverage for a custom exception. Verification rerun: ../../bin/dart test test/general.shard/github_template_test.dart, ./bin/flutter analyze packages/flutter_tools/lib/src/reporting/github_template.dart packages/flutter_tools/test/general.shard/github_template_test.dart, ./bin/dart format --output=none --set-exit-if-changed packages/flutter_tools/lib/src/reporting/github_template.dart packages/flutter_tools/test/general.shard/github_template_test.dart, and git diff --check.

Addressed the two output-initialization nits in ddab037: both bot exception toString implementations now initialize output as $PreparePackageException: $message / $UnpublishException: $message and keep the existing stderr append behavior. Verification rerun: ./bin/dart format --output=none --set-exit-if-changed dev/bots/prepare_package/common.dart dev/bots/unpublish_package.dart, ./bin/dart test dev/bots/test/prepare_package_test.dart, ./bin/dart test dev/bots/test/unpublish_package_test.dart, ./bin/flutter analyze dev/bots/prepare_package/common.dart dev/bots/unpublish_package.dart dev/bots/test/prepare_package_test.dart dev/bots/test/unpublish_package_test.dart, and git diff --check.