feat: prepare CASAN paid PoC release package

packages/casan-enterprise/README.md

@@ -19,8 +19,14 @@ Enterprise governed AI-SDLC console. Packages: `casan-enterprise`, `casan-govern
 | Loop governance | Plan-17 loop primitives (`loop-*.py`) |
 
 ## Components still to build (NOT in this task)
-- Governed Chat Console (Plan-18) · Prompt Mode Router · Model Provider Management
-- Operator mode · Codegen mode · Agent/Skill Registry · policy-versioning UI
+- Managed enterprise deployment with enterprise OIDC, CA, network policy and
+  production secret/KMS enforcement
+- HA/DR, RPO/RTO, lifecycle compatibility, support/SLA and independent security review
+- Production immutable object storage and external evidence verification operations
+
+The Platform Preview already contains the Governed Chat/Prompt Router/Operator/
+Codegen and agent/skill/model-selection MVPs, plus the Evidence Pack Viewer.
+They are not evidence that an Enterprise edition has shipped.
 
 ## Why it refuses to package
 Per the packaging principle, a level that isn't implemented must **fail clearly** rather
@@ -29,6 +35,7 @@ than emit a fake-complete artifact. Enterprise is `status: future` in
 explanation. When the console is built, flip its status to `preview`/`implemented`.
 
 ## To implement later
-Sequence: Plan-14 (RBAC console) → Plan-13 (Control Plane) → Plan-18 (Governed Chat
-Console: read-only → operator → chat-as-loop → multi-tenant). Reuse the existing blocks
-above instead of re-writing them.
+Sequence: finish the paid-PoC evidence/Gitea flow → enterprise deployment and
+operations controls → independent review → production readiness. Reuse the existing
+blocks above instead of re-writing them. See
+[`EDITION_FEATURE_LIMITATION_MATRIX.md`](../../docs/packaging/EDITION_FEATURE_LIMITATION_MATRIX.md).