print detailed info about the leaked APIs to stdout in the workflow

[devoncarew]

• print detailed info about the leaked APIs to stdout in the workflow
• remove some (non-lexical) sorting from our publishing status makrdown table; with larger mono-repos, having the packages not be lexically ordered can be confusing
• rev the firehose package version and prep for publishing
• fix Health workflow: Show leakage origins #333

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:dart_flutter_team_lints	3.3.0	already published at pub.dev
package:firehose	0.10.2	ready to publish	firehose-v0.10.2

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[github-actions]

PR Health

Breaking changes ✔️

Package	Change	Current Version	New Version	Needed Version	Looking good?
firehose	None	0.10.1	0.10.2	0.10.1	✔️

Changelog Entry ✔️

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

Coverage ⚠️

File	Coverage
pkgs/firehose/lib/firehose.dart	💔 0 % ⬇️ NaN %
pkgs/firehose/lib/src/health/health.dart	💔 94 % ⬇️ 0 %

This check for test coverage is informational (issues shown here will not fail the PR).

This check can be disabled by tagging the PR with skip-coverage-check.

API leaks ✔️

The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.

Package	Leaked API symbols

License Headers ✔️

// Copyright (c) 2025, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

[mosuem]

We could also show the origins as <details> in the comment?

[devoncarew]

We could also show the origins as <details> in the comment?

I think this makes sense. I'd like to see what info is in the json currently, so would want to land this PR as an incremental step there.