docs(reference): generate checked blessed_core compatibility surface inventory

NOTE

The title starts with docs(reference):, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

_{github.comment.notice: false in .github/pr-lens.yml turns this note off}

No blocking findings. The generated inventory matches ADR 0053 exit criterion 10, and the committed data is internally consistent with its sources.

Checked

• Full diff at 07e86df: the new builder, the package field added to cli.json, the committed compatibility-surface.json, the support-matrix section, and the new test.
• Counts agree with the file's contents: 135 CLI paths, 166 HTTP routes, 65 phlo.__all__ names, 15 entry-point groups, 46 entry points, 11 hook event types, envelope 1.0, and configuration=1/database=5 taken from registry/support/v1.json.
• CLI ownership is derived from the callback's top-level module via packages_distributions(), with the editable phlo root named explicitly because that install has no top_level.txt. Commands from phlo-airbyte, phlo-alerting, phlo-clickhouse, phlo-mcp, phlo-sling, and phlo-transform drop out by package, and the test asserts those exclusions plus the /api/v1 + /health HTTP filter.
• Entry points are limited to the 15 groups decision 2 names; excluding phlo.plugins.dagster is deliberate and asserted.
• Wiring is accurate: make docs-reference-check is part of make check (Makefile:15) and the CI quality job (ci.yml:210). At this SHA the quality job's "Check generated reference documentation", Ruff (including C901), ty, the docs build, and the core test shards' test steps all passed, so the committed file is fresh in CI's environment.

Non-blocking wording note — docs/reference/support-matrix.md:9-13 says the file lists "the ADR 0053 decision 2 surface" and that a diff to it should be reviewed as a covered-surface change. The file is the exit-criterion-10 subset: decision 2 also covers HTTP request/response schemas, status codes, error envelope, pagination and authorisation actions; the CLI JSON envelope and exit status; phlo.plugins.base, capability specs and service.yaml; project layout/configuration shape; and the support manifest shape. None of those are recorded here, so a green diff could be read as full decision-2 coverage. Suggest describing it as the exit-criterion-10 inventory of those surfaces, leaving the rest to their decision-2 references.

Remaining validation — The API package tests and the workspace coverage shards were still running when I checked; they exercise this change only through the shared tooling suite, whose test step passed in the core shards.