@clue-ai/cli 0.0.5 → 0.0.7

package/README.md

@@ -8,7 +8,7 @@ The Clue product repository keeps SDKs, shared schemas, and API contracts. Tool
 
 ```bash
 /clue-init
-clue-ai setup
+clue-ai setup --clue-api-key <key> --clue-api-base-url <url> --project-key <key> --environment dev
 clue-ai setup-detect --repo .
 clue-ai semantic-inventory --framework fastapi --backend-root-path backend --repo . --output .clue/semantic-routes.json
 clue-ai semantic-workflow --framework fastapi --backend-root-path backend --repo .
@@ -16,7 +16,7 @@ clue-ai lifecycle-apply --plan clue-lifecycle-plan.json --repo .
 clue-ai setup-check --framework fastapi --backend-root-path backend --repo . --target codex --require-sdk-lifecycle
 clue-ai setup-watch --project-key <key> --environment dev --clue-api-base-url <clue-api-base-url> --watch-targets frontend:web[init,identify,set-account,event-sent]=<frontend-url>,backend:api[init,identify,set-account,logout,event-sent]=<backend-url>
 clue-ai init --request clue-init-request.json --repo .
-clue-ai semantic-ci --request clue-semantic-request.json --repo .
+clue-ai semantic-gen --request clue-semantic-request.json --repo .
 ```
 
 `/clue-init` is the standard user-facing command for Codex and Claude Code
@@ -25,7 +25,7 @@ tool request/report contract as `clue-ai init`.
 
 `clue-ai semantic-workflow` mechanically writes the GitHub Actions workflow that
 generates `.clue/semantic-request.runtime.json` only inside CI and then runs
-`clue-ai semantic-ci`. Do not commit runtime semantic request files to client
+`clue-ai semantic-gen`. Do not commit runtime semantic request files to client
 repositories.
 
 `clue-ai setup` installs the target AI-tool skills and, when backend routes are
@@ -59,15 +59,26 @@ service key and the lifecycle checks expected for that service, for example
 Do not assume localhost ports; use the actual URLs printed by the repository's
 dev scripts or configured in its local env.
 
-## Required Secrets
+`clue-ai setup` reads Clue values from the setup screen flags, detects local
+services, writes `.clue/setup-manifest.json`, and prints service-specific env
+blocks. Do not hand-write `CLUE_SERVICE_KEY`; use the value printed for each
+detected service.
+
+## Required Environment
 
 - `CLUE_API_KEY`
-- `AI_PROVIDER_API_KEY`
+- `CLUE_AI_PROVIDER_API_KEY`
+- `CLUE_AI_PROVIDER`
+- `CLUE_AI_MODEL`
+
+`clue-ai semantic-gen` runs semantic AI inside the customer repository CI with
+the customer-configured AI provider key. Clue receives only the final
+privacy-safe semantic snapshot.
 
 ## Boundaries
 
 - The tool may read allowed source paths in the client repository.
 - The tool must not read `.env`, secrets, logs, dumps, build output, or vendor directories.
-- Raw source code is sent only from the client CI runner to the configured AI provider.
-- Raw source code, raw SQL, bind values, function names, class names, file paths, and import graphs are not sent to Clue by default.
+- Semantic generation calls the configured AI provider from customer CI.
+- Raw source code, raw SQL, bind values, function names, class names, file paths, and import graphs are not sent to Clue.
 - `clue-layer.yaml` and `clue-semantic.yaml` are not committed to client repositories.