@clue-ai/cli 0.0.4 → 0.0.5

package/README.md

@@ -8,6 +8,13 @@ The Clue product repository keeps SDKs, shared schemas, and API contracts. Tool
 
 ```bash
 /clue-init
+clue-ai setup
+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 .
+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 .
 ```
@@ -16,6 +23,42 @@ clue-ai semantic-ci --request clue-semantic-request.json --repo .
 wrappers. The command collects structured setup inputs and invokes the same
 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
+repositories.
+
+`clue-ai setup` installs the target AI-tool skills and, when backend routes are
+detectable, also runs the machine-owned setup preparation:
+
+- detects the FastAPI backend root
+- writes `.clue/semantic-routes.json`
+- writes `.github/workflows/clue-semantic-snapshot.yml`
+- writes `.clue/setup-manifest.json`
+
+The AI prompt should use those generated artifacts as inputs and should not
+hand-edit route inventory or semantic CI workflow files.
+
+`clue-ai setup-detect` mechanically detects FastAPI route candidates and returns
+the framework, backend root path, service key candidate, route files, and route
+count before any AI interpretation.
+
+`clue-ai lifecycle-apply` mechanically applies an AI-produced exact replacement
+plan after validating edit paths, lifecycle API names, no broad tracking, and no
+DOM clue tags.
+
+`clue-ai setup-check` mechanically verifies installed setup skills, route
+inventory, semantic workflow shape, runtime request absence, obvious secret
+leaks, and SDK lifecycle presence when requested.
+
+`clue-ai setup-watch` polls the Clue API setup-check endpoint while you operate
+the local service. `--clue-api-base-url` is the Clue API URL, not the customer
+frontend URL. Use `--watch-targets` to list every local frontend/backend app by
+service key and the lifecycle checks expected for that service, for example
+`frontend:web[init,identify,set-account,event-sent]=<frontend-url>,backend:api[init,identify,set-account,logout,event-sent]=<backend-url>`.
+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_API_KEY`