fix template, remove okr, use casan.*

docs/packaging/ADOPTION_GUIDE.md

@@ -12,6 +12,20 @@ This copies the core harness + `bin/casan` into `../my-project`, scaffolds
 `apps/ticketing/domain/` from the domain-pack template, adds `.gitea/workflows/casan-ci.yml`,
 and registers the project in `project-registry.json`.
 
+## Option A2 — New production project shell
+
+```bash
+packages/casan-devkit/install.sh \
+  --target ../my-project \
+  --project ticketing \
+  --domain "Ticketing" \
+  --template nestjs-react
+```
+
+This creates a strict-TypeScript NestJS/React monorepo, health bootstrap, tests, Docker multi-stage
+images, GitHub CI, a complete Domain Pack, versioned quality profile, project manifest, CASAN CLI,
+harness, and manifest-driven pipeline. Existing different files are never overwritten.
+
 ## Option B — Core tarball (harness-only / CI gate)
 ```bash
 tar -xzf casan-core-v1.0.0.tar.gz
@@ -37,6 +51,13 @@ See `DOCKER_GUIDE.md`.
    bin/casan reuse                                            # HARNESS_REUSE_VALID
    ```
 
+For a manifest-enabled project prefer:
+
+```bash
+bin/casan project validate --manifest apps/<project>/domain/project.manifest.json
+bin/casan pipeline --manifest apps/<project>/domain/project.manifest.json
+```
+
 ## Path model (what lives where)
 - **Harness code** → `packages/casan-harness/` (never edited by adopters).
 - **Your domain data** → `apps/<project>/domain/` (via `CASAN_DOMAIN_ROOT`).