optimize docs

docs/guides/CASAN_PROJECT_SHELL_PRODUCTION.md

@@ -3,8 +3,8 @@
 ## Outcome
 
 CASAN can create and govern multiple independent applications without embedding product knowledge
-in root `.github`, shared harness code, patch verification, or pipeline orchestration. OKR and
-Service Desk are consumers of the same versioned contract.
+in root `.github`, shared harness code, patch verification, or pipeline orchestration. Demo
+fixtures and Service Desk are consumers of the same versioned contract.
 
 ## Trust boundaries
 
@@ -70,6 +70,6 @@ update fails, the incomplete directory is removed and the project is not exposed
 ## Verification evidence
 
 Automated tests cover valid manifests, traversal rejection, command allowlisting, conflicting-file
-protection, idempotent scaffold/harness registration, generated NestJS/React build and tests, OKR
-compatibility, Service Desk isolation, source-generation review loops, and per-project patch
+protection, idempotent scaffold/harness registration, generated NestJS/React build and tests,
+demo-fixture compatibility, Service Desk isolation, source-generation review loops, and per-project patch
 verification command selection.

docs/guides/CASAN_USING_FOR_REAL_PROJECTS_VI.md

@@ -222,7 +222,7 @@ coding agent. Miễn command đi qua harness, evidence được ghi theo cùng c
 
 ## 7. Case 3 — dự án Service Desk thật đã có trong repository này
 
-Đây là bằng chứng CASAN không chỉ dùng được cho OKR:
+Đây là ví dụ một project consumer độc lập với các demo fixture:
 
 ```bash
 node --test apps/service-desk/test/ticket.test.mjs
@@ -237,7 +237,8 @@ bash packages/casan-harness/scripts/bash/verify-harness-reuse.sh
 ```
 
 Service Desk có source/test riêng và Domain Pack riêng. Nó dùng chung đúng một
-harness version với OKR. Không có gate nào được copy riêng cho Service Desk.
+harness version với các project khác. Không có gate nào được copy riêng cho
+Service Desk.
 
 ## 8. Case 4 — muốn model thực sự “xây dự án cho tôi”