talosctl apply full replacement in Talos OS v1.6.0 limits repeatable development environments

Goal is a repeatable development environment on Talos OS v1.6.0 where cluster configuration can be reapplied consistently with minimal side effects.

talosctl apply is documented as performing a full replacement of the cluster configuration in v1.6.0. The command does not merge incremental changes, and the official documentation does not list a --patch or --merge option. talosctl generate scaffolds configuration files but provides no diff or merge assistance for identifying changed sections.

With full replacement as the only documented behavior, it is unclear how safe repeatable applies are for small edits and whether future releases will introduce incremental update support.

Will Talos introduce a flag or mechanism to apply only differences between current and new configuration? Is there documented guidance for repeatable applies that avoids unnecessary reconfiguration in v1.6.0? Does the full-replace behavior apply uniformly across all configuration sections in this version?