fix template, remove okr, use casan.*

This commit is contained in:
thanhnv
2026-07-18 16:45:31 +07:00
parent 0dfd1742d3
commit 13fae3e6c3
249 changed files with 4881 additions and 5702 deletions
+25 -2
View File
@@ -7,10 +7,32 @@ Everything a new project needs to adopt the CASAN governance harness in a repeat
| Path | Purpose |
|---|---|
| `install.sh` | Install core harness + `bin/casan` into a target repo, scaffold a domain, register it |
| `project-scaffold.py` | Create an idempotent production NestJS/React monorepo shell with manifest, CI, Docker and harness |
| `Dockerfile.harness` | Minimal image to run the gate on any mounted repo (`casan gate`) |
| `templates/domain-pack/` | Per-project domain scaffold (input / golden-runs / corpus / `domain-pack.yaml`) |
| `templates/gitea-workflow/ci.yml` | Reusable Gitea Actions gate workflow |
| `templates/project/` | Minimal new-project skeleton that consumes the harness |
| `templates/project-shell/nestjs-react/` | Buildable/tested production project shell |
| `schemas/project-manifest.schema.json` | Versioned multi-project execution contract |
| `quality-profiles/enterprise-web-v1.json` | Shared quality floor and command allowlist |
## Create a new production shell
```bash
packages/casan-devkit/install.sh \
--target ../my-project \
--project ticketing \
--domain "Ticketing" \
--template nestjs-react
cd ../my-project
npm install
bin/casan project validate --manifest apps/ticketing/domain/project.manifest.json
bin/casan pipeline --manifest apps/ticketing/domain/project.manifest.json --dry-run
npm test && npm run build
```
The operation is fail-closed and idempotent: identical files are retained; a different existing
file aborts the run and is never overwritten. No generated command is passed through a shell.
## Quick adopt
```bash
@@ -28,4 +50,5 @@ bin/casan reuse # HARNESS_REUSE_VALID
- `docs/packaging/CI_GUIDE.md` — wire the gate into Gitea CI
- `docs/packaging/DOCKER_GUIDE.md` — run/build the harness image
Adoption is **config + domain only** — you never edit gate logic (H1→H7).
Adoption of an existing repository is **config + domain only**. New repositories can additionally
use the production project-shell template. In both modes, adopters never edit gate logic (H1→H7).