Charts: the Ingress column describes the Ingress mode only

With the Gateway-API sweep finished (#114), 21 charts offer httpRoute.enabled
as the mutually exclusive alternative and only rss-bridge does not - so a
column reading 'yes' no longer means the Ingress is the only mode. One note
above the table rather than 21 rewritten rows, because the per-chart detail
belongs on the chart pages: the Gateway shapes differ more than the column
could carry (two objects for keycloak and matrix-synapse, one per host entry
for homeassistant, one per app or one shared for freesailarr).

Charts.md

@@ -10,6 +10,8 @@
 grep -E '^(version|appVersion):' <chart>/Chart.yaml
 ```
 
+**The "Ingress" column describes the Ingress mode only.** Since the Gateway-API sweep finished (Gitea #114), **every chart with a routing object also offers `httpRoute.enabled` as the mutually exclusive alternative** — 21 charts, the one exception being [rss-bridge](rss-bridge), which is frozen for changes. So that column says how a chart publishes *while the Ingress is the active mode*; it is not a claim that the Ingress is the only mode. The Gateway shapes differ more than the column suggests — two objects for [keycloak](keycloak) (public + admin) and [matrix-synapse](matrix-synapse) (homeserver + delegation), one per host entry for [homeassistant](homeassistant), one per app or one shared for [freesailarr](freesailarr) — and what each mode costs its chart is on the chart's own page under "Routing: Ingress or Gateway API". The convention is [style guide §4](Chart-Style-Guide#4-ingress-and-gateway-api).
+
 | Chart | Deploys | Shape | Ingress | Notable |
 |---|---|---|---|---|
 | [apache-tika](apache-tika) | Apache Tika | Deployment + Service | no | content extraction for [paperless-ngx](paperless-ngx) |