fix(platform): make kyverno bundle build; defer render to Phase 2 (T-2.7)

The prior integration commit enabled kyverno in the platform render, but (a) the
admission bundle used ../policies refs that fail default kustomize load
restrictions, and (b) admission enforcement is Phase 2 (T-2.7), not Phase 0.
Fix: platform/kyverno/kustomization.yaml now lists resources with downward paths
(builds standalone); platform/kustomization.yaml re-defers kyverno with a Phase-2
note. All Phase-0 gates green: kustomize (platform, platform/kyverno, dev),
schema validation, conformance scaffold.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>

platform/kustomization.yaml

@@ -11,7 +11,10 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 resources:
-  - kyverno              # PM: enabled — admission enforcer first so policies precede other components
+  # - kyverno            # DEFERRED to Phase 2 (T-2.7): admission enforcement needs a cluster.
+  #                        Scaffolding is present & buildable at platform/kyverno/; enable it first
+  #                        (before other components) when T-2.7 activates. Kyverno's CI L0 gate is
+  #                        already live now via .gitea/ + ci/ (no cluster needed).
   - cilium
   - longhorn
   - cert-manager