Design and naming review before committing to stable version

Review design decisions and naming of v1alpha features before creating a stable version of KRO. After moving features to a stable version, we must maintain backward compatibility - any changes we want to make should be done before moving features to stable.

Next step: need a doc listing design decisions to review. We can review + approve these decisions just before creating the stable version of KRO.

Start by identifying the v1alpha design decisions and naming choices that need review; the issue does not name specific files, tests, or entry points. Create the requested design-decision document, then use it to review and approve the choices before KRO moves features to a stable version.

Written by the indexing model from the issue text.