Release boundaries
One source repository builds two independently selected release lines.
Independent versions, ordered publication
VERSION selects the template release. CLI_VERSION selects the executable. The source publish workflow runs native validation, then CLI publication, then template publication. It checks whether each version is already released; changing one line does not require releasing the other.
Workspace updates
A template update applies the delta between recorded and newer tags, rather than copying a whole template over a project. Repository-owned landing files are read as evidence but not applied to a workspace.
A CLI installation changes the local executable launcher after verification. It does not rewrite workspace records or the template version.
Documentation updates
Maintain major-version guides for model changes and separate changelogs for each product's minor and patch changes. Never infer release history from matching version numbers. Use available release evidence.