### Installer-managed configuration scope

- The installer persists only explicit operator inputs and explicit connection handoff values.
- For service/k3s-hosts workflows, values like `PROLE_K3S_SERVER` and other explicit user-entered settings are saved.
- Generated local/dev endpoint mappings, generated service hostnames, and placeholder-derived values are not persisted as installer-owned facts.

### Live service endpoints

- Live k3s service endpoints are not installer-managed configuration.
- Endpoint host/port discovery for running services is performed against the live cluster rather than persisted as static installer defaults.

### Downstream behavior

- Later Ansible phases are expected to discover current service endpoints from the running cluster.
- Installer replay/config files remain focused on explicit intent and handoff values instead of dynamic runtime topology.