Some rephrasing related to QT/clazy

Author: n-n-code

AGENTS.md

@@ -13,7 +13,7 @@ Baseline shape:
 - One small library target plus one CLI target form the default example shape
 - Deterministic `CTest`, `clang-tidy`, Doxygen, release-hygiene, and Valgrind
   lanes are part of the maintained contract
-- Qt/Clazy are optional paths, not baseline assumptions
+- Qt/Clazy provide the example UI stack, not the baseline assumption
 - Public docs are generated from repo-owned headers and `docs/mainpage.md`
 - Feature plans live under `upcoming_features/` as tracked Markdown files only
 
@@ -71,8 +71,8 @@ Use the smallest validation set that proves the change, then extend as needed:
 
 - `ctest --test-dir "$BUILD_DIR" --output-on-failure`
 - `cmake --build "$BUILD_DIR" --target clang-tidy`
-- `cmake --build "$BUILD_DIR" --target clazy` for Qt-enabled projects when
-  available
+- `cmake --build "$BUILD_DIR" --target clazy` when the project uses the
+  example Qt-based UI stack and the tool is available
 - `cmake --build "$BUILD_DIR" --target lint`
 - `cmake --build "$BUILD_DIR" --target docs`
 - `bash scripts/run-valgrind.sh "$BUILD_DIR"`

CMakeLists.txt

@@ -14,8 +14,8 @@ set(CMAKE_CXX_EXTENSIONS OFF)
 
 option(FRAME_ENABLE_ASAN "Enable AddressSanitizer for repo-owned code" OFF)
 option(FRAME_ENABLE_UBSAN "Enable UndefinedBehaviorSanitizer for repo-owned code" OFF)
-option(FRAME_ENABLE_QT "Enable optional Qt integration hooks" OFF)
-option(FRAME_ENABLE_CLAZY "Enable clazy target when Qt projects need it" OFF)
+option(FRAME_ENABLE_QT "Enable the example Qt-based UI integration path" OFF)
+option(FRAME_ENABLE_CLAZY "Enable the clazy analyzer lane for the Qt-based UI path" OFF)
 
 find_package(Doxygen QUIET)
 

README.md

@@ -16,15 +16,15 @@ This frame is designed for projects that want:
 - project-local skills under `.agents/skills/`
 - CMake-only build and install flow
 - deterministic `CTest` coverage with enforced WHAT/HOW/WHY commentary
-- `clang-tidy`, optional `clazy`, Doxygen, and Valgrind lanes
+- `clang-tidy`, Doxygen, and Valgrind lanes, plus an example Qt/Clazy path for UI projects
 - release hygiene and release checklist automation
 - generic CI and release GitHub workflows
 
 Defaults:
 
 - portable C++20 library + CLI example
 - no Qt requirement by default
-- optional Qt/Clazy hooks for projects that need them
+- optional Qt/Clazy support as the example stack for projects that add a UI layer
 - MIT license
 
 ## Quick Start
@@ -71,7 +71,7 @@ upcoming_features/     Forward-looking implementation plans
 Optional local tooling:
 
 - `clang-tidy`
-- `clazy-standalone` for Qt projects
+- `clazy-standalone` when using the example Qt-based UI stack
 - `doxygen`
 - `valgrind`
 - `ninja-build`

RELEASE_CHECKLIST.md

@@ -63,6 +63,9 @@ cmake --build "$BUILD_DIR" --target clang-tidy
 cmake --build "$BUILD_DIR" --target clazy
 ```
 
+- Treat `clazy` as part of the Qt-based UI variant rather than a baseline lane
+  for CLI-only projects.
+
 - If repo-owned public headers or docs changed, also run:
 
 ```bash

docs/mainpage.md

@@ -10,7 +10,7 @@ expectations rather than end-user setup.
 - `frame_cli` is the example command-line target
 - build, docs, tests, analyzers, and release helpers are first-class repo
   concerns
-- Qt/Clazy integration is optional rather than baseline
+- Qt/Clazy form the example UI stack rather than the baseline project shape
 - deterministic tests live under `tests/`
 - future plans live under `upcoming_features/`