chart-drift: a cluster without KEDA fails the comparison, although hosting-audit skips the same kind #155

What happens

On a cluster that does not serve scaledobjects.keda.sh, with keda.enabled: false, the Audit's chart step stops before it compares anything:

could not read scaledobjects.keda.sh from namespace 'memex' via --via kubectl. This is a FAILURE, not an absence of drift.
error: the server doesn't have a resource type "scaledobjects"
hosting-chart-drift: ERROR: the chart-drift comparison produced no verdict (exit 1)

Why it is a defect

deploy/aks/scripts/check-chart-drift.sh reads the kind at line 331 and treats every failure as fatal. deploy/hosting-operator/bin/hosting-audit treats the same answer as "a kind this cluster does not serve is SKIPPED and recorded in the report", because nothing of that kind can exist there. The two steps of one Audit disagree.

Suggested fix

1. Apply hosting-audit's rule: doesn't have a resource type, the server could not find the requested resource and no matches for kind mean an empty list for this kind, recorded in the report.
2. Keep every other failure fatal, Forbidden above all.
3. If the render contains a ScaledObject on such a cluster, report it as CHART-ONLY, so the case does not read as clean.

What I did not establish

1. Whether later steps of the comparison hold up on such a cluster. The run stopped at this kind.
2. Whether other optional kinds in the list have the same problem.

🤖 Filed from Claude Code on behalf of an estate's operator.