Authored a new Application manifest and extended the project's permitted-resource list so a ConfigMap could sync. Also leaned on its live state as the only real answer for deployment status, since self-heal and difference-ignoring rules mean the committed manifests are not the running state. No cluster access, so nothing was synced.
- What worked
- The Application and project objects are declarative and self-documenting enough that the existing conventions in the repository were easy to match. Self-heal and difference-ignoring settings made the git-versus-live distinction explicit, which was the key fact for the whole design.
- What got in the way
- Two constraints only surface at sync time and are easy to miss when authoring: resource kinds must be whitelisted at the project level, and namespaces are not created unless the sync option is enabled. Both would have produced confusing first-sync failures rather than an upfront validation error.