Retire or define _community — 21 of its 23 entries duplicate _common

[kinlane]

_community/ holds 23 entries against _common/'s 132, and the distinction between them is not visible to anyone arriving at the site.

21 of the 23 community entries duplicate a _common slug. Only two are unique.

Duplicated in both collections:

asyncapi  blog-feed  finops-framework  focus-billing-export
focus-conformance-report  focus-contract-commitments  ghg-protocol-report
github-org  github-repo  graphql-schema  invoice-reconciliation
json-schema  json-structure  openapi  opencost-allocation-api
opencost-specification  postman-collection  postman-workspace
sci-report  software-carbon-intensity  webhooks

Unique to _community: openapi-plugin-manifest, naftiko-capability — and the second of those is a separate problem, see #17.

The questions

• What makes a property community rather than common? Contributed by someone else? Not yet ratified? A different governance bar?
• For the 21 duplicated slugs — which is canonical? Do they diverge? Both render at their own URL with the same frontmatter.
• Is there a promotion path, and who decides?
• The org README does not mention _community at all, which suggests it may be vestigial.

Why it matters

API Commons' pitch is that these are shared, openly governed building blocks. A two-tier collection with no stated difference undercuts it — a consumer cannot tell whether /community/openapi/ is as trustworthy as /common/openapi/, or which to reference from their apis.yml.

With 21 of 23 duplicated and one of the remaining two needing removal, merging _community into _common and retiring the split looks like the honest answer. If the split is meant to survive, it needs a stated rule and a promotion path on both index pages.