feat: make Core reports commercially production-ready
This commit is contained in:
@@ -13,6 +13,7 @@ sh install.sh --level devkit
|
||||
cd /path/to/my-project
|
||||
casan init --project ticketing --client claude,codex
|
||||
casan doctor
|
||||
casan readiness --refresh
|
||||
casan verify-harness
|
||||
```
|
||||
|
||||
@@ -31,6 +32,16 @@ The viewer is single-project, offline-capable and read-only. It starts lazily on
|
||||
`127.0.0.1`, so projects do not need Platform, Node/npm or an always-running
|
||||
service merely to inspect H1–H7 and H6.
|
||||
|
||||
The dashboard and CLI expose three independent states:
|
||||
|
||||
- Core: installation acceptance and client activation;
|
||||
- Domain Pipeline: optional project-specific SRS→test configuration;
|
||||
- Provider Telemetry: optional model/provider token and cost coverage.
|
||||
|
||||
`not_configured` Domain Pipeline and `optional_unavailable` Provider Telemetry
|
||||
do not block Core. `casan report export` is on-demand and must not run after
|
||||
every prompt.
|
||||
|
||||
Use this for developer workstations and managed CI runners. CI must install the
|
||||
same release recorded by `.casan/version.lock` before running gates.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user